[#PETALSBCSOAP-67] ConcurrentModificationException when removing the axis service - Petals Link JIRA

Details

Type: Bug
Status: Resolved
Priority: 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

Petals BC SOAP

ConcurrentModificationException when removing the axis service

Details

Activity

People

Dates