[mule-user] jms transport error - Failed to load transport temp-queue error

7 views

Skip to first unread message

topclimber

unread,

Aug 30, 2010, 2:19:10 AM8/30/10

to us...@mule.codehaus.org

Hi Guys

Could you help me identify what error this is and how to resolve it?

I am using mule CE 2.2.1 and active MQ5.3.2. I have no idea why there is: Failed to load transport temp-queue error if I put a jms transport there.

Config and log are below:

<global-property name="jms.url" value="tcp://localhost:61616"/>
<jms:activemq-connector name="jmsConnector" specification="1.1" brokerURL="${jms.url}"/>

<model name="mule1"><!--

<default-service-exception-strategy>
<vm:outbound-endpoint path="finalWsResponseEP" synchronous="false" />
</default-service-exception-strategy>

--><service name="helloService">
<inbound>
<cxf:inbound-endpoint address="http://localhost:8888/testsvc"
serviceClass="org.example.sol18.HelloWorld" synchronous="true" />
</inbound>
<outbound>
<filtering-router>
<vm:outbound-endpoint path="java1preProc" synchronous="false"/>
<expression-filter evaluator="groovy" expression="message.getProperty('cxf_operation').getLocalPart() =='createAcct'"/>
</filtering-router>
</outbound>

<async-reply timeout="120000">
<vm:inbound-endpoint address="vm://finalWsResponseEP"/>
<single-async-reply-router/>
</async-reply>

</service>

<service name="soapFaultHandler">
<inbound>
<vm:inbound-endpoint path="soapFaultHandler"/>
</inbound>

</mule>

INFO 2010-08-30 16:08:50,131 [connector.VM.0.dispatcher.1] org.mule.transport.vm.VMMessageDispatcher: Connected: endpoi
nt.outbound.vm://java1preProc
INFO 2010-08-30 16:08:50,131 [connector.VM.0.dispatcher.1] org.example.sol18.Java1: preProc executed ....
INFO 2010-08-30 16:08:50,147 [connector.VM.0.dispatcher.2] org.mule.transport.vm.VMMessageDispatcher: Connected: endpoi
nt.outbound.vm://vm1
INFO 2010-08-30 16:08:50,147 [jmsConnector.dispatcher.1] org.mule.transport.jms.JmsMessageDispatcher: Connected: endpoi
nt.outbound.jms://jms1
WARN 2010-08-30 16:08:50,178 [jmsConnector.dispatcher.1] org.mule.transport.jms.JmsMessageUtils: Header: Accept-Encodin
g is not compliant with JMS specification (sec. 3.5.1, 3.8.1.1). It will cause problems in your and other applications.
Please update your application code to correct this. Mule renamed it to Accept_Encoding
WARN 2010-08-30 16:08:50,178 [jmsConnector.dispatcher.1] org.mule.transport.jms.JmsMessageUtils: Header: Content-Length
is not compliant with JMS specification (sec. 3.5.1, 3.8.1.1). It will cause problems in your and other applications. P
lease update your application code to correct this. Mule renamed it to Content_Length
WARN 2010-08-30 16:08:50,178 [jmsConnector.dispatcher.1] org.mule.transport.jms.JmsMessageUtils: Header: Content-Type i
s not compliant with JMS specification (sec. 3.5.1, 3.8.1.1). It will cause problems in your and other applications. Ple
ase update your application code to correct this. Mule renamed it to Content_Type
WARN 2010-08-30 16:08:50,178 [jmsConnector.dispatcher.1] org.mule.transport.jms.JmsMessageUtils: Header: User-Agent is
not compliant with JMS specification (sec. 3.5.1, 3.8.1.1). It will cause problems in your and other applications. Pleas
e update your application code to correct this. Mule renamed it to User_Agent
WARN 2010-08-30 16:08:50,178 [jmsConnector.dispatcher.1] org.mule.transport.jms.JmsMessageUtils: Header: http.context.p
ath is not compliant with JMS specification (sec. 3.5.1, 3.8.1.1). It will cause problems in your and other applications
. Please update your application code to correct this. Mule renamed it to http_context_path
WARN 2010-08-30 16:08:50,178 [jmsConnector.dispatcher.1] org.mule.transport.jms.JmsMessageUtils: Header: http.method is
not compliant with JMS specification (sec. 3.5.1, 3.8.1.1). It will cause problems in your and other applications. Plea
se update your application code to correct this. Mule renamed it to http_method
WARN 2010-08-30 16:08:50,178 [jmsConnector.dispatcher.1] org.mule.transport.jms.JmsMessageUtils: Header: http.request i
s not compliant with JMS specification (sec. 3.5.1, 3.8.1.1). It will cause problems in your and other applications. Ple
ase update your application code to correct this. Mule renamed it to http_request
WARN 2010-08-30 16:08:50,178 [jmsConnector.dispatcher.1] org.mule.transport.jms.JmsMessageUtils: Header: http.request.p
ath is not compliant with JMS specification (sec. 3.5.1, 3.8.1.1). It will cause problems in your and other applications
. Please update your application code to correct this. Mule renamed it to http_request_path
WARN 2010-08-30 16:08:50,178 [jmsConnector.dispatcher.1] org.mule.transport.jms.JmsMessageUtils: Header: http.version i
s not compliant with JMS specification (sec. 3.5.1, 3.8.1.1). It will cause problems in your and other applications. Ple
ase update your application code to correct this. Mule renamed it to http_version
INFO 2010-08-30 16:08:50,241 [connector.VM.0.dispatcher.3] org.mule.transport.vm.VMMessageDispatcher: Connected: endpoi
nt.outbound.vm://vm2
INFO 2010-08-30 16:08:50,241 [ActiveMQ Session Task] org.mule.transport.jms.JmsReplyToHandler: Reply Message sent to: t
emp-queue://ID:SYD01034W-2923-1283148524256-0:0:1 with correlationID:0df21218-b3fd-11df-bbe3-593e256b52d5
INFO 2010-08-30 16:08:50,256 [connector.VM.0.dispatcher.4] org.mule.transport.vm.VMMessageDispatcher: Connected: endpoi
nt.outbound.vm://vm3
INFO 2010-08-30 16:08:50,256 [connector.VM.0.dispatcher.4] org.example.sol18.Java1: postProc executed ....
INFO 2010-08-30 16:08:50,256 [connector.VM.0.dispatcher.4] org.example.sol18.Java1: 160:2333
INFO 2010-08-30 16:08:50,256 [connector.VM.0.dispatcher.4] org.example.sol18.Java1: 161
INFO 2010-08-30 16:08:50,256 [connector.VM.0.dispatcher.4] org.example.sol18.Java1: 162
INFO 2010-08-30 16:08:50,272 [connector.VM.0.dispatcher.5] org.mule.transport.vm.VMMessageDispatcher: Connected: endpoi
nt.outbound.vm://finalWsResponseEP
ERROR 2010-08-30 16:08:50,288 [connector.VM.0.dispatcher.3] org.mule.service.DefaultServiceExceptionStrategy:
********************************************************************************
Message : Failed to load transport temp-queue
Type : org.mule.api.registry.ServiceException
Code : MULE_ERROR-57
JavaDoc : http://www.mulesource.org/docs/site/current2/apidocs/org/mule/api/registry/ServiceException.html

********************************************************************************
Exception stack is:
1. Failed to load transport temp-queue (org.mule.api.registry.ServiceException)
org.mule.registry.MuleRegistryHelper:466 (http://www.mulesource.org/docs/site/current2/apidocs/org/mule/api/registry/S
erviceException.html)
********************************************************************************
Root Exception stack trace:
org.mule.api.registry.ServiceException: Failed to load transport temp-queue
at org.mule.registry.MuleRegistryHelper.createServiceDescriptor(MuleRegistryHelper.java:466)
at org.mule.registry.MuleRegistryHelper.lookupServiceDescriptor(MuleRegistryHelper.java:446)
at org.mule.endpoint.MuleEndpointURI.initialise(MuleEndpointURI.java:162)
at org.mule.endpoint.AbstractEndpointBuilder.doBuildOutboundEndpoint(AbstractEndpointBuilder.java:174)
at org.mule.endpoint.AbstractEndpointBuilder.buildOutboundEndpoint(AbstractEndpointBuilder.java:93)
at org.mule.endpoint.DefaultEndpointFactory.getOutboundEndpoint(DefaultEndpointFactory.java:86)
at org.mule.transport.DefaultReplyToHandler.getEndpoint(DefaultReplyToHandler.java:103)
at org.mule.transport.DefaultReplyToHandler.processReplyTo(DefaultReplyToHandler.java:64)
at org.mule.service.AbstractService.processReplyTo(AbstractService.java:832)
at org.mule.model.seda.SedaService.doSend(SedaService.java:264)
at org.mule.service.AbstractService.sendEvent(AbstractService.java:500)
at org.mule.DefaultMuleSession.sendEvent(DefaultMuleSession.java:354)
at org.mule.routing.inbound.DefaultInboundRouterCollection.send(DefaultInboundRouterCollection.java:228)
at org.mule.routing.inbound.DefaultInboundRouterCollection.route(DefaultInboundRouterCollection.java:188)
at org.mule.transport.AbstractMessageReceiver$DefaultInternalMessageListener.onMessage(AbstractMessageReceiver.j
ava:364)
at org.mule.transport.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:252)
at org.mule.transport.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:175)
at org.mule.transport.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:168)
at org.mule.transport.vm.VMMessageReceiver.onMessage(VMMessageReceiver.java:99)
at org.mule.transport.vm.VMMessageDispatcher$1.doInTransaction(VMMessageDispatcher.java:75)
at org.mule.transaction.TransactionTemplate.execute(TransactionTemplate.java:99)
at org.mule.transport.vm.VMMessageDispatcher.doDispatch(VMMessageDispatcher.java:79)
at org.mule.transport.AbstractMessageDispatcher$Worker.run(AbstractMessageDispatcher.java:262)
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(Unknown Source)

********************************************************************************

ERROR 2010-08-30 16:08:50,303 [connector.VM.0.dispatcher.4] org.mule.service.DefaultServiceExceptionStrategy:
********************************************************************************
Message : Failed to load transport temp-queue
Type : org.mule.api.registry.ServiceException
Code : MULE_ERROR-57
JavaDoc : http://www.mulesource.org/docs/site/current2/apidocs/org/mule/api/registry/ServiceException.html

********************************************************************************

WARN 2010-08-30 16:08:50,366 [connector.VM.0.dispatcher.3] org.mule.config.ExceptionHelper: Failed to load error mappin
gs from: META-INF/services/org/mule/config/vm-exception-mappings.properties This may be because there are no error code
mappings for protocol: vm
ERROR 2010-08-30 16:14:20,381 [ActiveMQ Connection Worker: tcp://localhost/127.0.0.1:61616] org.mule.DefaultExceptionStr
ategy:
********************************************************************************
Message : Initialisation Failure: java.io.EOFException
Type : org.mule.transport.ConnectException
Code : MULE_ERROR-84
JavaDoc : http://www.mulesource.org/docs/site/current2/apidocs/org/mule/transport/ConnectException.html
JMS Code : null
Object : ActiveMQJmsConnector{this=47e53a, started=true, initialised=true, name='jmsConnector', disposed=
false, numberOfConcurrentTransactedReceivers=4, createMultipleTransactedReceivers=true, connected=true, supportedProtoco
ls=[jms], serviceOverrides=null}
********************************************************************************
Exception stack is:
1. null (java.io.EOFException)
java.io.DataInputStream:-1 (null)
2. java.io.EOFException(JMS Code: null) (javax.jms.JMSException)
org.apache.activemq.util.JMSExceptionSupport:49 (http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/jms/JMSException.
html)
3. Initialisation Failure: java.io.EOFException (org.mule.transport.ConnectException)
org.mule.transport.jms.JmsConnector:454 (http://www.mulesource.org/docs/site/current2/apidocs/org/mule/transport/Conne
ctException.html)
********************************************************************************
Root Exception stack trace:
java.io.EOFException
at java.io.DataInputStream.readInt(Unknown Source)
at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:269)
at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:203)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:195)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:183)
at java.lang.Thread.run(Unknown Source)

********************************************************************************

INFO 2010-08-30 16:14:20,381 [ActiveMQ Connection Worker: tcp://localhost/127.0.0.1:61616] org.mule.DefaultExceptionStr
ategy: There is no current event available, routing Null message with the exception
ERROR 2010-08-30 16:14:20,397 [ActiveMQ Connection Worker: tcp://localhost/127.0.0.1:61616] org.mule.DefaultExceptionStr
ategy: The object that failed was:
ActiveMQJmsConnector{this=47e53a, started=true, initialised=true, name='jmsConnector', disposed=false, numberOfConcurren
tTransactedReceivers=4, createMultipleTransactedReceivers=true, connected=true, supportedProtocols=[jms], serviceOverrid
es=null}
INFO 2010-08-30 16:14:20,397 [ActiveMQ Connection Worker: tcp://localhost/127.0.0.1:61616] org.mule.DefaultExceptionStr
ategy: There is no current event available, routing Null message with the exception

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Chris Campos

unread,

Jan 4, 2011, 1:34:20 PM1/4/11

to us...@mule.codehaus.org

Did you ever find a solution to this problem?

Chris

Reply all

Reply to author

Forward

0 new messages