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
Hide
Permalink
noddoux added a comment - Fri, 17 Dec 2010 - 15:48:39 +0100

The error is thrown from a shutdown hook.

Runtime.getRuntime().addShutdownHook(new ListenerManagerShutdownThread(this));

Is JMS enabled on the BC SOAP component ?

Show
noddoux added a comment - Fri, 17 Dec 2010 - 15:48:39 +0100 The error is thrown from a shutdown hook. 
Runtime.getRuntime().addShutdownHook(new ListenerManagerShutdownThread(this));
Is JMS enabled on the BC SOAP component ?
Hide
Permalink
Frédéric Gardes added a comment - Fri, 17 Dec 2010 - 15:59:12 +0100

No

Show
Frédéric Gardes added a comment - Fri, 17 Dec 2010 - 15:59:12 +0100 No
Hide
Permalink
noddoux added a comment - Fri, 17 Dec 2010 - 16:24:55 +0100

Is the bus stopped with Ctrl+C or by taping q in the console ?

Show
noddoux added a comment - Fri, 17 Dec 2010 - 16:24:55 +0100 Is the bus stopped with Ctrl+C or by taping q in the console ?
Hide
Permalink
Frédéric Gardes added a comment - Fri, 17 Dec 2010 - 17:47:45 +0100

with 'petals-esb stop' (after a 'petals-esb start'). We use the daemon.

Show
Frédéric Gardes added a comment - Fri, 17 Dec 2010 - 17:47:45 +0100 with 'petals-esb stop' (after a 'petals-esb start'). We use the daemon.
Hide
Permalink
noddoux added a comment - Tue, 21 Dec 2010 - 10:03:08 +0100 - edited

Does the problem occur by stopping the bus with "java -jar launcher.jar stop" ?

Actually I suppose there are two shutdown hooks executed concurrently (one set by the bus which executes the function stops on the SOAP binding component, another set by Axis2 above). If it is the case, there is no solution with this version of Axis2 (cf AXIS2-3861).

Show
noddoux added a comment - Tue, 21 Dec 2010 - 10:03:08 +0100 - edited Does the problem occur by stopping the bus with "java -jar launcher.jar stop" ? Actually I suppose there are two shutdown hooks executed concurrently (one set by the bus which executes the function stops on the SOAP binding component, another set by Axis2 above). If it is the case, there is no solution with this version of Axis2 (cf AXIS2-3861).
Hide
Permalink
Frédéric Gardes added a comment - Tue, 21 Dec 2010 - 10:11:43 +0100

Quick read and try, isn't it?
yes, I successed to reproduce this trace with 'java -jar launcher.jar stop' &.(..

Show
Frédéric Gardes added a comment - Tue, 21 Dec 2010 - 10:11:43 +0100 Quick read and try, isn't it? yes, I successed to reproduce this trace with 'java -jar launcher.jar stop' &.(..
Hide
Permalink
Christophe DENEUX added a comment - Mon, 5 Oct 2015 - 15:16:43 +0200 - edited

We mark this issue as "Cannot reproduce", and we suppose that the problem does not appear in the last BC SOAP release (4.4.0) because it embeds a version of Axis2 for which the bug mentioned below is fixed.

Show
Christophe DENEUX added a comment - Mon, 5 Oct 2015 - 15:16:43 +0200 - edited We mark this issue as "Cannot reproduce", and we suppose that the problem does not appear in the last BC SOAP release (4.4.0) because it embeds a version of Axis2 for which the bug mentioned below is fixed.

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.