Uploaded image for project: 'Mule'
  1. Mule
  2. MULE-4589

java.lang.IllegalStateException: Phase 'start' has already been executed

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.2 (EE only)
    • Fix Version/s: 3.0.0
    • Labels:
      None
    • User impact:
      High
    • Migration Impact:
      This fix did not make it to Mule 3.0
    • Similar Issues:

      Description

      I am using Mule ESB EE 2.2.2 and testing it using Junit tests with the FunctionalTestCase mechanism (that is my Junit tests all subclass from this). I get this except intermittently when running the tests.

      java.lang.IllegalStateException: Phase 'start' has already been executed
      at org.mule.lifecycle.GenericLifecycleManager.checkPhase(GenericLifecycleManager.java:174)
      at org.mule.DefaultMuleContext.start(DefaultMuleContext.java:159)
      at org.mule.tck.AbstractMuleTestCase.setUp(AbstractMuleTestCase.java:409)
      at org.mule.tck.AbstractMuleTestCase.runBare(AbstractMuleTestCase.java:291)
      at org.mule.tck.AbstractMuleTestCase.run(AbstractMuleTestCase.java:270)

      The fix to the problem is below. It turns out that when I run the test cases it starts my configuration which includes several examples. The way the OSDT examples work is that they are started in a different thread; because of the thread execution order the start intermittently fails because of the problem below.

      In DefaultMuleClient.start():

      public synchronized void start() throws MuleException
      {
      lifecycleManager.checkPhase(Startable.PHASE_NAME);
      if (!isStarted())
      {
      if (getSecurityManager() == null)

      { throw new MuleRuntimeException(CoreMessages.objectIsNull("securityManager")); }

      if (getQueueManager() == null)

      { throw new MuleRuntimeException(CoreMessages.objectIsNull("queueManager")); }

      ....

      The lifecycleManager.checkPhase() call should be inside of the !isStarted().

      What's happening in my tests is that I spawn a thread that starts up MuleClients which causes a the MuleContext to start. Remembering the stack trace in the previous message, this thread is called by the setUp() method in the AbstractMuleTestCase. If the thread starts and gets into the synchronized block of the above start() method, then the main thread will block there while the lengthy startup process is happening. Then the main thread will die because it will fail the checkPhase() call.

        Attachments

          Activity

            People

            • Assignee:
              ross Ross Mason
              Reporter:
              francis Francis Upton
            • Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Fix Release Date:
                14/Sep/10