Petals BC SOAP

ConcurrentModificationException when removing the axis service

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Cannot Reproduce
  • Affects Version/s: 4.0.3
  • Fix Version/s: 4.4.0
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    I'm not able to provide a better log than that. I'm sorry but I can't provide the exact bc soap source code line. But it's a regular error (about one per week). A part of the Axis code isn't thread safe, and the bc soap run it into threads . It occurs during the stop of the esb.

    [Petals.Container.Components.petals-bc-soap]-INFO 2010-12-16 09:02:19,184 Stop Service Unit 'petals-su-soap-consumes-moveCustomer-1.0-SNAPSHOT'
[Petals.Container.Components.petals-bc-soap]-INFO 2010-12-16 09:02:19,185 Removing Axis service 'moveCustomer'
Exception in thread "Thread-45" java.util.ConcurrentModificationException
        at java.util.Hashtable$Enumerator.next(Hashtable.java:1031)
        at org.apache.axis2.engine.AxisConfiguration.getServices(AxisConfiguration.java:819)
        at org.apache.axis2.engine.ListenerManager.stop(ListenerManager.java:183)
        at org.apache.axis2.engine.ListenerManager$ListenerManagerShutdownThread.run(ListenerManager.java:244)
[Petals.Container.Components.petals-se-kpi]-INFO 2010-12-16 09:02:26,153 Shut down Service Unit 'petals-su-kpi-consumes-moveCustomer-orchestrator-1.0-SNAPSHOT'
[Petals.Container.Components.petals-se-kpi]-INFO 2010-12-16 09:02:26,181 Stop Service Unit 'petals-su-kpi-consumes-getCustomer-orchestrator-1.0-SNAPSHOT'
PEtALS container is not properly stopped - 16/12/10 09:02
[Petals.Container.Components.petals-se-kpi]-INFO 2010-12-16 09:02:34,631 Shut down Service Unit 'petals-su-kpi-consumes-getCustomer-orchestrator-1.0-SNAPSHOT'

    Then the esb crashes: all the others artifacts aren't correctly stopped (so the repository is one time again corrupted, and we've got to reinstall all the artifacts ).

    Show
    I'm not able to provide a better log than that. I'm sorry but I can't provide the exact bc soap source code line. But it's a regular error (about one per week). A part of the Axis code isn't thread safe, and the bc soap run it into threads . It occurs during the stop of the esb. 
    [Petals.Container.Components.petals-bc-soap]-INFO 2010-12-16 09:02:19,184 Stop Service Unit 'petals-su-soap-consumes-moveCustomer-1.0-SNAPSHOT'
[Petals.Container.Components.petals-bc-soap]-INFO 2010-12-16 09:02:19,185 Removing Axis service 'moveCustomer'
Exception in thread "Thread-45" java.util.ConcurrentModificationException
        at java.util.Hashtable$Enumerator.next(Hashtable.java:1031)
        at org.apache.axis2.engine.AxisConfiguration.getServices(AxisConfiguration.java:819)
        at org.apache.axis2.engine.ListenerManager.stop(ListenerManager.java:183)
        at org.apache.axis2.engine.ListenerManager$ListenerManagerShutdownThread.run(ListenerManager.java:244)
[Petals.Container.Components.petals-se-kpi]-INFO 2010-12-16 09:02:26,153 Shut down Service Unit 'petals-su-kpi-consumes-moveCustomer-orchestrator-1.0-SNAPSHOT'
[Petals.Container.Components.petals-se-kpi]-INFO 2010-12-16 09:02:26,181 Stop Service Unit 'petals-su-kpi-consumes-getCustomer-orchestrator-1.0-SNAPSHOT'
PEtALS container is not properly stopped - 16/12/10 09:02
[Petals.Container.Components.petals-se-kpi]-INFO 2010-12-16 09:02:34,631 Shut down Service Unit 'petals-su-kpi-consumes-getCustomer-orchestrator-1.0-SNAPSHOT'
    Then the esb crashes: all the others artifacts aren't correctly stopped (so the repository is one time again corrupted, and we've got to reinstall all the artifacts ).
  • Environment:
    RHEL 5, esb 3.1.1

Activity

Ascending order - Click to sort in descending order
Frédéric Gardes made changes - Thu, 16 Dec 2010 - 09:11:04 +0100
Field Original Value New Value
Priority Major [ 3 ]
Frédéric Gardes made changes - Thu, 16 Dec 2010 - 09:13:20 +0100
Description I'm not able to provide a better log than that. I'm sorry but I can't provide the exact bc soap source code line. But it's a regular error (about one per week). A part of the Axis code isn't thread safe, and the bc soap run it into threads :D.

{code}
[Petals.Container.Components.petals-bc-soap]-INFO 2010-12-16 09:02:19,184 Stop Service Unit 'petals-su-soap-consumes-moveCustomer-1.0-SNAPSHOT'
[Petals.Container.Components.petals-bc-soap]-INFO 2010-12-16 09:02:19,185 Removing Axis service 'moveCustomer'
Exception in thread "Thread-45" java.util.ConcurrentModificationException
        at java.util.Hashtable$Enumerator.next(Hashtable.java:1031)
        at org.apache.axis2.engine.AxisConfiguration.getServices(AxisConfiguration.java:819)
        at org.apache.axis2.engine.ListenerManager.stop(ListenerManager.java:183)
        at org.apache.axis2.engine.ListenerManager$ListenerManagerShutdownThread.run(ListenerManager.java:244)
{code} 		I'm not able to provide a better log than that. I'm sorry but I can't provide the exact bc soap source code line. But it's a regular error (about one per week). A part of the Axis code isn't thread safe, and the bc soap run it into threads :D. It occurs during the stop of the esb.

{code}
[Petals.Container.Components.petals-bc-soap]-INFO 2010-12-16 09:02:19,184 Stop Service Unit 'petals-su-soap-consumes-moveCustomer-1.0-SNAPSHOT'
[Petals.Container.Components.petals-bc-soap]-INFO 2010-12-16 09:02:19,185 Removing Axis service 'moveCustomer'
Exception in thread "Thread-45" java.util.ConcurrentModificationException
        at java.util.Hashtable$Enumerator.next(Hashtable.java:1031)
        at org.apache.axis2.engine.AxisConfiguration.getServices(AxisConfiguration.java:819)
        at org.apache.axis2.engine.ListenerManager.stop(ListenerManager.java:183)
        at org.apache.axis2.engine.ListenerManager$ListenerManagerShutdownThread.run(ListenerManager.java:244)
[Petals.Container.Components.petals-se-kpi]-INFO 2010-12-16 09:02:26,153 Shut down Service Unit 'petals-su-kpi-consumes-moveCustomer-orchestrator-1.0-SNAPSHOT'
[Petals.Container.Components.petals-se-kpi]-INFO 2010-12-16 09:02:26,181 Stop Service Unit 'petals-su-kpi-consumes-getCustomer-orchestrator-1.0-SNAPSHOT'
PEtALS container is not properly stopped - 16/12/10 09:02
[Petals.Container.Components.petals-se-kpi]-INFO 2010-12-16 09:02:34,631 Shut down Service Unit 'petals-su-kpi-consumes-getCustomer-orchestrator-1.0-SNAPSHOT'
{code}
Then the esb crashes: all the others artifacts aren't correctly stopped (so the repository is one time again corrupted, and we've got to reinstall al the artificats :( ).
Frédéric Gardes made changes - Thu, 16 Dec 2010 - 09:13:45 +0100
Description I'm not able to provide a better log than that. I'm sorry but I can't provide the exact bc soap source code line. But it's a regular error (about one per week). A part of the Axis code isn't thread safe, and the bc soap run it into threads :D. It occurs during the stop of the esb.

{code}
[Petals.Container.Components.petals-bc-soap]-INFO 2010-12-16 09:02:19,184 Stop Service Unit 'petals-su-soap-consumes-moveCustomer-1.0-SNAPSHOT'
[Petals.Container.Components.petals-bc-soap]-INFO 2010-12-16 09:02:19,185 Removing Axis service 'moveCustomer'
Exception in thread "Thread-45" java.util.ConcurrentModificationException
        at java.util.Hashtable$Enumerator.next(Hashtable.java:1031)
        at org.apache.axis2.engine.AxisConfiguration.getServices(AxisConfiguration.java:819)
        at org.apache.axis2.engine.ListenerManager.stop(ListenerManager.java:183)
        at org.apache.axis2.engine.ListenerManager$ListenerManagerShutdownThread.run(ListenerManager.java:244)
[Petals.Container.Components.petals-se-kpi]-INFO 2010-12-16 09:02:26,153 Shut down Service Unit 'petals-su-kpi-consumes-moveCustomer-orchestrator-1.0-SNAPSHOT'
[Petals.Container.Components.petals-se-kpi]-INFO 2010-12-16 09:02:26,181 Stop Service Unit 'petals-su-kpi-consumes-getCustomer-orchestrator-1.0-SNAPSHOT'
PEtALS container is not properly stopped - 16/12/10 09:02
[Petals.Container.Components.petals-se-kpi]-INFO 2010-12-16 09:02:34,631 Shut down Service Unit 'petals-su-kpi-consumes-getCustomer-orchestrator-1.0-SNAPSHOT'
{code}
Then the esb crashes: all the others artifacts aren't correctly stopped (so the repository is one time again corrupted, and we've got to reinstall al the artificats :( ). 		I'm not able to provide a better log than that. I'm sorry but I can't provide the exact bc soap source code line. But it's a regular error (about one per week). A part of the Axis code isn't thread safe, and the bc soap run it into threads :D. It occurs during the stop of the esb.

{code}
[Petals.Container.Components.petals-bc-soap]-INFO 2010-12-16 09:02:19,184 Stop Service Unit 'petals-su-soap-consumes-moveCustomer-1.0-SNAPSHOT'
[Petals.Container.Components.petals-bc-soap]-INFO 2010-12-16 09:02:19,185 Removing Axis service 'moveCustomer'
Exception in thread "Thread-45" java.util.ConcurrentModificationException
        at java.util.Hashtable$Enumerator.next(Hashtable.java:1031)
        at org.apache.axis2.engine.AxisConfiguration.getServices(AxisConfiguration.java:819)
        at org.apache.axis2.engine.ListenerManager.stop(ListenerManager.java:183)
        at org.apache.axis2.engine.ListenerManager$ListenerManagerShutdownThread.run(ListenerManager.java:244)
[Petals.Container.Components.petals-se-kpi]-INFO 2010-12-16 09:02:26,153 Shut down Service Unit 'petals-su-kpi-consumes-moveCustomer-orchestrator-1.0-SNAPSHOT'
[Petals.Container.Components.petals-se-kpi]-INFO 2010-12-16 09:02:26,181 Stop Service Unit 'petals-su-kpi-consumes-getCustomer-orchestrator-1.0-SNAPSHOT'
PEtALS container is not properly stopped - 16/12/10 09:02
[Petals.Container.Components.petals-se-kpi]-INFO 2010-12-16 09:02:34,631 Shut down Service Unit 'petals-su-kpi-consumes-getCustomer-orchestrator-1.0-SNAPSHOT'
{code}
Then the esb crashes: all the others artifacts aren't correctly stopped (so the repository is one time again corrupted, and we've got to reinstall al the artifacts :( ).
Frédéric Gardes made changes - Thu, 16 Dec 2010 - 09:13:55 +0100
Description I'm not able to provide a better log than that. I'm sorry but I can't provide the exact bc soap source code line. But it's a regular error (about one per week). A part of the Axis code isn't thread safe, and the bc soap run it into threads :D. It occurs during the stop of the esb.

{code}
[Petals.Container.Components.petals-bc-soap]-INFO 2010-12-16 09:02:19,184 Stop Service Unit 'petals-su-soap-consumes-moveCustomer-1.0-SNAPSHOT'
[Petals.Container.Components.petals-bc-soap]-INFO 2010-12-16 09:02:19,185 Removing Axis service 'moveCustomer'
Exception in thread "Thread-45" java.util.ConcurrentModificationException
        at java.util.Hashtable$Enumerator.next(Hashtable.java:1031)
        at org.apache.axis2.engine.AxisConfiguration.getServices(AxisConfiguration.java:819)
        at org.apache.axis2.engine.ListenerManager.stop(ListenerManager.java:183)
        at org.apache.axis2.engine.ListenerManager$ListenerManagerShutdownThread.run(ListenerManager.java:244)
[Petals.Container.Components.petals-se-kpi]-INFO 2010-12-16 09:02:26,153 Shut down Service Unit 'petals-su-kpi-consumes-moveCustomer-orchestrator-1.0-SNAPSHOT'
[Petals.Container.Components.petals-se-kpi]-INFO 2010-12-16 09:02:26,181 Stop Service Unit 'petals-su-kpi-consumes-getCustomer-orchestrator-1.0-SNAPSHOT'
PEtALS container is not properly stopped - 16/12/10 09:02
[Petals.Container.Components.petals-se-kpi]-INFO 2010-12-16 09:02:34,631 Shut down Service Unit 'petals-su-kpi-consumes-getCustomer-orchestrator-1.0-SNAPSHOT'
{code}
Then the esb crashes: all the others artifacts aren't correctly stopped (so the repository is one time again corrupted, and we've got to reinstall al the artifacts :( ). 		I'm not able to provide a better log than that. I'm sorry but I can't provide the exact bc soap source code line. But it's a regular error (about one per week). A part of the Axis code isn't thread safe, and the bc soap run it into threads :D. It occurs during the stop of the esb.

{code}
[Petals.Container.Components.petals-bc-soap]-INFO 2010-12-16 09:02:19,184 Stop Service Unit 'petals-su-soap-consumes-moveCustomer-1.0-SNAPSHOT'
[Petals.Container.Components.petals-bc-soap]-INFO 2010-12-16 09:02:19,185 Removing Axis service 'moveCustomer'
Exception in thread "Thread-45" java.util.ConcurrentModificationException
        at java.util.Hashtable$Enumerator.next(Hashtable.java:1031)
        at org.apache.axis2.engine.AxisConfiguration.getServices(AxisConfiguration.java:819)
        at org.apache.axis2.engine.ListenerManager.stop(ListenerManager.java:183)
        at org.apache.axis2.engine.ListenerManager$ListenerManagerShutdownThread.run(ListenerManager.java:244)
[Petals.Container.Components.petals-se-kpi]-INFO 2010-12-16 09:02:26,153 Shut down Service Unit 'petals-su-kpi-consumes-moveCustomer-orchestrator-1.0-SNAPSHOT'
[Petals.Container.Components.petals-se-kpi]-INFO 2010-12-16 09:02:26,181 Stop Service Unit 'petals-su-kpi-consumes-getCustomer-orchestrator-1.0-SNAPSHOT'
PEtALS container is not properly stopped - 16/12/10 09:02
[Petals.Container.Components.petals-se-kpi]-INFO 2010-12-16 09:02:34,631 Shut down Service Unit 'petals-su-kpi-consumes-getCustomer-orchestrator-1.0-SNAPSHOT'
{code}
Then the esb crashes: all the others artifacts aren't correctly stopped (so the repository is one time again corrupted, and we've got to reinstall all the artifacts :( ).
Christophe DENEUX made changes - Mon, 5 Oct 2015 - 15:15:34 +0200
Status New [ 10000 ] Resolved [ 10004 ]
Fix Version/s 4.4.0 [ 10405 ]
Resolution Cannot Reproduce [ 5 ]

People

Dates

  • Created:
    Thu, 16 Dec 2010 - 09:10:42 +0100
    Updated:
    Mon, 5 Oct 2015 - 15:18:43 +0200
    Resolved:
    Mon, 5 Oct 2015 - 15:15:34 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.