Asankha/Ruwan: It seems Synapse-1.2 version has some issue while using Topic. The same configuration works fine in previous version (Synapse-1.1.1).
A proxy over JMS (using Topic) in Synapse-1.2, throwing the following error 2008-06-16 16:54:10,951 [10.200.182.100-PS-TSAHA] [HttpClientWorker-1] INFO Log Mediator To: http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAct ion: , MessageID: urn:uuid:0CA562091BD39C4135225451412151068-1938625653, Directi on: response, Envelope: <?xml version='1.0' encoding='utf-8'?><env:Envelope xmln s:env="http://schemas.xmlsoap.org/soap/envelope/";><env:Body><ns2:echoResponse xm lns:ns2="http://ejbwebservice.westernasset.com/";><return>From host : PASDEVARCH1 Web Service Echo + Tanmay </return></ns2:echoResponse></env:Body></env:Envelop e> Exception in thread "HttpClientWorker-1" java.lang.ClassCastException: progress. message.jimpl.TopicSession cannot be cast to javax.jms.QueueSession at org.apache.synapse.transport.jms.JMSUtils.sendMessageToJMSDestination (JMSUtils.java:462) at org.apache.synapse.transport.jms.JMSSender.sendMessage(JMSSender.java :235) at org.apache.synapse.transport.base.AbstractTransportSender.invoke(Abst ractTransportSender.java:127) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:448) at org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:1 38) at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2Synap seEnvironment.java:219) at org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediato r.java:154) at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractLis tMediator.java:58) at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMe diator.java:125) at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(A xis2SynapseEnvironment.java:162) at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(S ynapseCallbackReceiver.java:301) at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(Synapse CallbackReceiver.java:131) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176) at org.apache.synapse.transport.nhttp.ClientWorker.run(ClientWorker.java :200) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source ) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) I am using the same proxy and JMS configurations in Synapse-1.1.1 and Synapse-1.2 . The JMS transport config and proxy config are attached below <transportReceiver name="jms" class="org.apache.synapse.transport.jms.JMSListener"> <parameter name="myTopicConnectionFactory"> <parameter name="java.naming.factory.initial">com.sonicsw.jndi.mfcontext.MFContextFactory</parameter> <parameter name="java.naming.provider.url">tcp://localhost:2506</parameter> <parameter name="com.sonicsw.jndi.mfcontext.domain">Domain1</parameter> <parameter name="java.naming.security.principal">Administrator</parameter> <parameter name="java.naming.security.credentials">Administrator</parameter> <parameter name="transport.jms.ConnectionFactoryJNDIName">SonicTopicConnectionFactory</parameter> <parameter name="transport.jms.ConnectionFactoryType" locked="false">topic</parameter> </parameter> <parameter name="myQueueConnectionFactory"> <parameter name="java.naming.factory.initial">com.sonicsw.jndi.mfcontext.MFContextFactory</parameter> <parameter name="java.naming.provider.url">tcp://localhost:2506</parameter> <parameter name="com.sonicsw.jndi.mfcontext.domain">Domain1</parameter> <parameter name="java.naming.security.principal">Administrator</parameter> <parameter name="java.naming.security.credentials">Administrator</parameter> <parameter name="transport.jms.ConnectionFactoryJNDIName">SonicQueueConnectionFactory</parameter> <parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter> </parameter> </transportReceiver> <transportSender name="jms" class="org.apache.synapse.transport.jms.JMSSender" /> http://www.nabble.com/file/p17875719/synapse_sample_echoProxy.xml synapse_sample_echoProxy.xml -- View this message in context: http://www.nabble.com/Seems-Synapse-1.2-JMS-transport-TopicConnectionFatory-has-some-issue-tp17875719p17875719.html Sent from the Synapse - User mailing list archive at Nabble.com.
