Mule
  1. Mule
  2. MULE-4381

stdio transport fails with hot deployment

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 3.0.0-M1
    • Fix Version/s: None
    • Labels:
      None
    • User impact:
      Medium
    • Log Output:
      Hide
      Please enter something:
      some thing
      WARN 2009-06-01 07:50:45,956 [SystemStreamConnector.receiver.3] org.mule.context.notification.ServerNotificationManager: Notification not enqueued after ServerNotificationManager disposal: ExceptionNotification{action=exception, resourceId=null, serverId=dzapata-laptop.Not clustered.b9f7b855-d3f5-430a-ac28-954b8d82a1f0, timestamp=1243871445956}
      ERROR 2009-06-01 07:50:45,957 [SystemStreamConnector.receiver.3] org.mule.DefaultExceptionStrategy:
      ********************************************************************************
      Message : Cannot route event as component "EchoUMO" is stopped. Component that caused exception is: SedaService{EchoUMO}. Message payload is of type: String
      Type : org.mule.api.service.ServiceException
      Code : MULE_ERROR--2
      JavaDoc : http://www.mulesource.org/docs/site/current2/apidocs/org/mule/api/service/ServiceException.html
      Payload : some thing
      ********************************************************************************
      Exception stack is:
      1. Cannot route event as component "EchoUMO" is stopped. Component that caused exception is: SedaService{EchoUMO}. Message payload is of type: String (org.mule.api.service.ServiceException)
        org.mule.service.AbstractService:435 (http://www.mulesource.org/docs/site/current2/apidocs/org/mule/api/service/ServiceException.html)
      ********************************************************************************
      Root Exception stack trace:
      org.mule.api.service.ServiceException: Cannot route event as component "EchoUMO" is stopped. Component that caused exception is: SedaService{EchoUMO}. Message payload is of type: String
      at org.mule.service.AbstractService.dispatchEvent(AbstractService.java:435)
      at org.mule.DefaultMuleSession.dispatchEvent(DefaultMuleSession.java:274)
      at org.mule.routing.inbound.DefaultInboundRouterCollection.dispatch(DefaultInboundRouterCollection.java:223)
      at org.mule.routing.inbound.DefaultInboundRouterCollection.route(DefaultInboundRouterCollection.java:192)
      at org.mule.transport.AbstractMessageReceiver$DefaultInternalMessageListener.onMessage(AbstractMessageReceiver.java:359)
      at org.mule.transport.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:252)
      at org.mule.transport.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:175)
      at org.mule.transport.stdio.StdioMessageReceiver.poll(StdioMessageReceiver.java:150)
      at org.mule.transport.PollingReceiverWorker.run(PollingReceiverWorker.java:47)
      at org.mule.work.WorkerContext.run(WorkerContext.java:310)
      at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
      at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
      at java.lang.Thread.run(Thread.java:595)

      Show
      Please enter something: some thing WARN 2009-06-01 07:50:45,956 [SystemStreamConnector.receiver.3] org.mule.context.notification.ServerNotificationManager: Notification not enqueued after ServerNotificationManager disposal: ExceptionNotification{action=exception, resourceId=null, serverId=dzapata-laptop.Not clustered.b9f7b855-d3f5-430a-ac28-954b8d82a1f0, timestamp=1243871445956} ERROR 2009-06-01 07:50:45,957 [SystemStreamConnector.receiver.3] org.mule.DefaultExceptionStrategy: ******************************************************************************** Message : Cannot route event as component "EchoUMO" is stopped. Component that caused exception is: SedaService{EchoUMO}. Message payload is of type: String Type : org.mule.api.service.ServiceException Code : MULE_ERROR--2 JavaDoc : http://www.mulesource.org/docs/site/current2/apidocs/org/mule/api/service/ServiceException.html Payload : some thing ******************************************************************************** Exception stack is: 1. Cannot route event as component "EchoUMO" is stopped. Component that caused exception is: SedaService{EchoUMO}. Message payload is of type: String (org.mule.api.service.ServiceException)   org.mule.service.AbstractService:435 ( http://www.mulesource.org/docs/site/current2/apidocs/org/mule/api/service/ServiceException.html ) ******************************************************************************** Root Exception stack trace: org.mule.api.service.ServiceException: Cannot route event as component "EchoUMO" is stopped. Component that caused exception is: SedaService{EchoUMO}. Message payload is of type: String at org.mule.service.AbstractService.dispatchEvent(AbstractService.java:435) at org.mule.DefaultMuleSession.dispatchEvent(DefaultMuleSession.java:274) at org.mule.routing.inbound.DefaultInboundRouterCollection.dispatch(DefaultInboundRouterCollection.java:223) at org.mule.routing.inbound.DefaultInboundRouterCollection.route(DefaultInboundRouterCollection.java:192) at org.mule.transport.AbstractMessageReceiver$DefaultInternalMessageListener.onMessage(AbstractMessageReceiver.java:359) at org.mule.transport.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:252) at org.mule.transport.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:175) at org.mule.transport.stdio.StdioMessageReceiver.poll(StdioMessageReceiver.java:150) at org.mule.transport.PollingReceiverWorker.run(PollingReceiverWorker.java:47) at org.mule.work.WorkerContext.run(WorkerContext.java:310) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575) at java.lang.Thread.run(Thread.java:595)
    • Similar Issues:
      MULE-4715Re-test transport hot deployment with CXF
      MULE-4797GroovyExpressionEvaluator script is unable to load user classes when used with hot deployment
      MULE-4792XStream XmlToObject transformer unable to load classes when running in hot deployment mode
      MULE-400Hot deployment of components and other artifacts
      MULE-4995Drop any stdio input endpoints from Mule examples
      MULE-5137Mule hot deployment functionlity : application installation does not go through when Xslt transformer is used in mule-configuration
      MULE-5018Loanbroker ESB example needs updating for hot deployment changes
      MULE-4906Hot Deployment documentation steps cause RuntimeException: MuleContext is not available msg (Hot Deployed app doesn't work)
      MULE-5423after hot deployment, jms message will not be processed.
      MULE-5338Custom transports fail to load when bundled in a Mule app (vs deployed in Mule system libs)

      Description

      stdio transport appears to fail for hot deployment with the following steps:

      1. Start echo example and select option 1
      2. Enter some input and verify that it returns the same input
      3. Edit the conf/echo-config.xml (I just added more text under the description element
      4. After a few seconds, you will see Mule shutdown and restart
      5. Enter some text when you see the 'Please enter something:' prompt
      6. You will see the error in the 'log output' section of this defect
      7. If you enter more text, it will work properly

      AP thinks that the stdio transport doesnt clean up properly after shutdown

        Activity

        Daniel Zapata created issue -
        Hide
        Daniel Feist added a comment -

        Known issue, stdio doesn't dispose or itself correctly maybe.

        Show
        Daniel Feist added a comment - Known issue, stdio doesn't dispose or itself correctly maybe.
        Daniel Feist made changes -
        Field Original Value New Value
        Fix Version/s Bug Backlog (2.1.x, 2.2.x) [ 10522 ]
        Priority To be reviewed [ 6 ] Minor [ 4 ]
        Ramiro Rinaudo made changes -
        Workflow Fixed Main Mule Workflow (after JIRA upgrade) [ 74465 ] Main Mule Workflow v1.0 [ 140885 ]
        Ramiro Rinaudo made changes -
        Fix Version/s Bug Backlog [ 10522 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            Daniel Zapata
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development