[mule-user] Problem with MuleClient after upgrading to 2.1.1

2 views
Skip to first unread message

Geir Arnesen

unread,
Oct 29, 2008, 3:02:53 PM10/29/08
to us...@mule.codehaus.org

I have a simple piece of code which worked perfectly in 2.0.2.. I can't get
it work after upgrading to 2.1.1.

I am just sending a simple message to a jms url.

The Mule.xml does just contain the: jms:activemq-connector

MuleClient client = new MuleClient("Mule.xml");
String s = "test message"
client.send("jms://siebel.invoicing", s,null );

I get this error? What changes should I do to be able to send this message?


Exception in thread "main" org.mule.api.transport.DispatchException: Failed
to route event via endpoint:
DefaultOutboundEndpoint{endpointUri=jms://siebel.invoicing,
connector=ActiveMQJmsConnector{this=ce994b, started=false, initialised=true,
name='jmsConnector.main', disposed=false,
numberOfConcurrentTransactedReceivers=4,
createMultipleTransactedReceivers=true, connected=false,
supportedProtocols=[jms], serviceOverrides=null},
transformer=[ObjectToJMSMessage{this=b24759, name='null',
ignoreBadInput=false, returnClass=interface javax.jms.Message,
sourceTypes=[]}], name='endpoint.jms.siebel.invoicing', properties={},
transactionConfig=Transaction{factory=null, action=NEVER, timeout=0},
filter=null, deleteUnacceptedMessages=false, securityFilter=null,
synchronous=false, initialState=started, remoteSync=false,
remoteSyncTimeout=3000, endpointEncoding=UTF-8}. Message payload is of type:
String
at
org.mule.transport.AbstractMessageDispatcher.send(AbstractMessageDispatcher.java:195)
at org.mule.transport.AbstractConnector.send(AbstractConnector.java:1910)
at
org.mule.endpoint.DefaultOutboundEndpoint.send(DefaultOutboundEndpoint.java:77)
at org.mule.DefaultMuleSession.sendEvent(DefaultMuleSession.java:327)
at org.mule.module.client.MuleClient.send(MuleClient.java:650)
at org.mule.module.client.MuleClient.send(MuleClient.java:627)
at org.mule.module.client.MuleClient.send(MuleClient.java:580)
at no.aftenposten.jms.SendInvoicing.main(SendInvoicing.java:34)
Caused by: javax.jms.JMSException: Not connected
at org.mule.transport.jms.JmsConnector.getSession(JmsConnector.java:528)
at org.mule.transport.jms.JmsConnector.getSession(JmsConnector.java:521)
at
org.mule.transport.jms.JmsMessageDispatcher.dispatchMessage(JmsMessageDispatcher.java:128)
at
org.mule.transport.jms.JmsMessageDispatcher.doSend(JmsMessageDispatcher.java:359)
at
org.mule.transport.AbstractMessageDispatcher.send(AbstractMessageDispatcher.java:168)
... 7 more

--
View this message in context: http://www.nabble.com/Problem-with-MuleClient-after-upgrading-to-2.1.1-tp20233737p20233737.html
Sent from the Mule - User mailing list archive at Nabble.com.


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

http://xircles.codehaus.org/manage_email


Geir Arnesen

unread,
Oct 30, 2008, 11:01:54 AM10/30/08
to us...@mule.codehaus.org

The solution was to put in:
client.getMuleContext().start();

This wasn't necessary in 2.0.2

Geir

--
View this message in context: http://www.nabble.com/Problem-with-MuleClient-after-upgrading-to-2.1.1-tp20233737p20248719.html

Reply all
Reply to author
Forward
0 new messages