NPE in MuleClient because DispatcherWorkManager has not been created

• User impact:

  Medium
• Configuration:

  Hide

  <vm:connector name="vmQueues" queueEvents="true" />

  <service name="inbound">
  <inbound>
  <vm:inbound-endpoint path="in" />
  </inbound>
  <test:component />
  <outbound>
  <pass-through-router>
  <vm:outbound-endpoint path="out" />
  </pass-through-router>
  </outbound>
  </service>

  Show

  <vm:connector name="vmQueues" queueEvents="true" /> <service name="inbound"> <inbound> <vm:inbound-endpoint path="in" /> </inbound> <test:component /> <outbound> <pass-through-router> <vm:outbound-endpoint path="out" /> </pass-through-router> </outbound> </service>
• Log Output:

  Hide

  java.lang.NullPointerException
  at org.mule.transport.AbstractConnector.dispatch(AbstractConnector.java:2015)
  at org.mule.endpoint.DefaultOutboundEndpoint.dispatch(DefaultOutboundEndpoint.java:82)
  at org.mule.DefaultMuleSession.dispatchEvent(DefaultMuleSession.java:264)
  at org.mule.module.client.MuleClient.dispatch(MuleClient.java:279)
  at org.mule.module.client.MuleClient.dispatch(MuleClient.java:262)
  

  Show

  java.lang.NullPointerException at org.mule.transport.AbstractConnector.dispatch(AbstractConnector.java:2015) at org.mule.endpoint.DefaultOutboundEndpoint.dispatch(DefaultOutboundEndpoint.java:82) at org.mule.DefaultMuleSession.dispatchEvent(DefaultMuleSession.java:264) at org.mule.module.client.MuleClient.dispatch(MuleClient.java:279) at org.mule.module.client.MuleClient.dispatch(MuleClient.java:262)
• Similar Issues:

  None

There is some race condition which causes this. I can reproduce it with as few as 10 messages with a complex config.

Created the following simple test case for it:
org.mule.test.integration.client.MuleClientInThreadTestCase

We should verify that this is fixed in 3.x