« Return to Thread: Mule 2.2.1 not queueing message to ActiveMQ

Mule 2.2.1 not queueing message to ActiveMQ

by jp4 :: Rate this Message:

Reply to Author | View in Thread

I am seeing a very bizarre thing when I change my log4j.xml logging level for "org.mule" from DEBUG to INFO.

When the log level is set to DEBUG, I can see through the ActiveMQ admin console that the message counts for the queue are incremented as expected.  However when I change the logging level to INFO the message count is not incremented.  

I decided to debug the code and found that an exception is caught (but never logged) in AbstractMessageDispatcher$Worker.run() line 278.  The error message is "org.mule.api.transformer.TransformerException: Failed to read input stream to create a stream message: java.net.SocketException: Socket is closed (javax.jms.JMSException)"

The exception is originally thrown from JmsMessageDispatcher.dispatchMessage(): 159 (Object message = event.transformMessage()).

If I change the logging level back to INFO I am able to step through the code with no issues.  Any help would be greatly appreciated.

Below is the configuration for the service that I am calling.

        <service name="SilverpopAccount_1_0_0">
            <inbound>
                <inbound-endpoint address="${third-party-services.SilverpopAccount_1_0_0.inbound-endpoint.url}" synchronous="false"/>
            </inbound>
            <outbound>
                <pass-through-router>
                    <jms:outbound-endpoint queue="silverpopAccountRequestQueue" synchronous="false"/>
                </pass-through-router>
            </outbound>
        </service>

Thanks,

John

 « Return to Thread: Mule 2.2.1 not queueing message to ActiveMQ