OK , so if I just use the default Synapse will create the 'TestProxy' queue automatically (if its not there), but if I specify a queue name as the destination parameter this does not get created by synapse automatically? It has to match an existing one (and I have to check the jndi names) or synapse fails to start? Just want to confirm this is the expected behaviour ie in my example it would not create a dynamic queue.
Thanks again. -----Original Message----- From: Asankha C. Perera [mailto:[EMAIL PROTECTED] Sent: 01 October 2008 17:25 To: [email protected]; David Geary Subject: Re: JMS Hi David First of all you need to subscribe to the user mailing list to post questions and receive replies. I have directly copied you on this one.. > <parameter name="transport.jms.Destination" locked="true" > value="myTestQueue"/> to the proxy element synapse fails to start up and I > get the stack trace below: > > 2008-10-01 15:10:51,130 [172.25.1.248-bfs-product-1] [WrapperSimpleAppMain] > INFO JMSListener Starting to listen on destination : of type queue for > service TestProxy > 2008-10-01 15:10:51,130 [172.25.1.248-bfs-product-1] [WrapperSimpleAppMain] > FATAL ServerManager Synaps startup failed... > java.lang.ClassCastException: org.apache.activemq.jndi.ReadOnlyContext cannot > be cast to javax.jms.Destination > at java.lang.Thread.run(Unknown Source) > > > Am I doing something fundamentally wrong here or is this a bug? (Also when I > add the line <parameter name="transport.jms.ConnectionFactory" locked="true" > value="myQueueConnectionFactory"/> It gives me a warning that the connection > factory is invalid - synapse starts, but my service is disabled) > The problem here is the way you may have created your Destination "myTestQueue" - did you create this with the Web front end or the JMX console? If so the JNDI name of it may be different. Usually ActiveMQ has a concept of dynamic destinations - which gets created on first use. If you write a simple JNDI lookup program of 5-10 lines, you should be able to see your JMS Destination bound to the JNDI name you are thinking of connecting to. The above log says "Starting to listen on destination : of .." and you can see the destination name missing! The next logs shows that looking up on JNDI fora JMS Destination resulted in something else.. and thus the class cast Hope this helps.. your problems is quite simple.. you just need to get the correct JNDI name to the ESB asankha The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. The views and opinions expressed in this email may not reflect the views and opinions of any member of Lagan Technologies Limited, or any of its subsidiaries. Lagan Technologies Limited is a company registered in Northern Ireland with registration number NI 28773. The registered office of Lagan Technologies Limited is 209 Airport Road West, Belfast, Co. Antrim, BT3 9EZ.
