HI Tsaha, We had an issue with Ques and Topics both being used on the JMS transport with 1.1.1 release which is fixed with the 1.2 release. Is there any possibility for you to switch to the 1.2 release? At least give it a try with 1.2, so that if it is working with 1.2 we know the issue.
Thanks, Ruwan (PS: there may be people who had encountered this issue on the community, there for please don't direct the question only to Asankha and me. There is a equal chance of getting the answer from any one in the community) On Wed, Jun 18, 2008 at 2:33 AM, tsaha <[EMAIL PROTECTED]> wrote: > > Asankha/Ruwan: > > This is a new issue. I am running 2 instances of Synapse-1.1.1. Deployed a > Proxy over JMS in both instances. Goal is to make sure that when a JNDI > Topic Entry is created in Sonic MQ with [[groupprefix]] in front of the > actual topic, at a time one Synapse instance will receive message from > Sonic > MQ. But Synapse throws some error. I ran a similar test by uisng a plain > java jms client, which works fine. The required files are attached here. > > 1) Screen shot of Sonic MQ JNDI Entry > 2) Proxy config in Synapse > 3) JMS Transport config in Synapse > 4) SynapseError log. > 5) The java jms client. > > We have to make this feature working, in order to implement Synapse here. > So > please help. > > > http://www.nabble.com/file/p17937245/sonic_jndi.bmp sonic_jndi.bmp > http://www.nabble.com/file/p17937245/synapse_sample_echoProxy.xml > synapse_sample_echoProxy.xml > http://www.nabble.com/file/p17937245/JNDISharedSubs.javaJNDISharedSubs.java > > <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"/> > > THE SYNAPSE ERROR LOG > > 2008-06-17 13:06:23,933 [10.200.182.100-PS-TSAHA] [WrapperSimpleAppMain] > INFO ServerManager Ready for processing > 2008-06-17 13:22:49,794 [10.200.182.100-PS-TSAHA] [JMS Session Delivery > Thread] DEBUG JMSMessageReceiver Received JMS message to destination : > TopicXA > Message ID : ID:ffffffffcbed081a:2c060009:11A9831ACB2 > Correlation ID : null > ReplyTo ID : null > 2008-06-17 13:22:49,810 [10.200.182.100-PS-TSAHA] [jms-Worker-1] DEBUG > JMSListener Error receiving message > org.apache.axis2.AxisFault: The service cannot be found for the endpoint > reference (EPR) > at > > org.apache.axis2.engine.DispatchPhase.validateTransport(DispatchPhase.java:216) > at > > org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:93) > at org.apache.axis2.engine.Phase.invoke(Phase.java:308) > at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212) > at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:132) > at > > org.apache.synapse.transport.base.AbstractTransportListener.handleIncomingMessage(AbstractTransportListener.java:210) > at > > org.apache.synapse.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageReceiver.java:201) > 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) > -- > View this message in context: > http://www.nabble.com/Multiple-Synapse-instances-as-shared-subscribers-to-Sonic-MQ-tp17937245p17937245.html > Sent from the Synapse - User mailing list archive at Nabble.com. > > -- Ruwan Linton http://wso2.org - "Oxygenating the Web Services Platform" http://ruwansblog.blogspot.com/
