You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Tanmay saha (JIRA)" <ji...@apache.org> on 2008/06/19 22:27:45 UTC
[jira] Created: (SYNAPSE-369) Multiple instances of Synapse
instances cannot form a shared subscription group to Sonic MQ
Multiple instances of Synapse instances cannot form a shared subscription group to Sonic MQ
-------------------------------------------------------------------------------------------
Key: SYNAPSE-369
URL: https://issues.apache.org/jira/browse/SYNAPSE-369
Project: Synapse
Issue Type: Bug
Components: Transports
Affects Versions: 1.1.1, 1.2
Environment: Windows XP, JDK 1.6, Sonic MQ 7.5.1
Reporter: Tanmay saha
This is a new issue. I am running 2 instances of Synapse-1.1.1 or Synapse-1.2. 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 (for example "[[grpsharedsubs]]TopicXA" ), 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 in shared subscription mode. I have all the sonic required jars in Synapse\lib folder. The associated configurations are attached here
1) JNDI Lookup name in Sonic MQ
2) JMSTransport config in axis2.xml
3) Proxy config in Synapse
4) JMS Transport config in Synapse
5) SynapseError log.
JNDI Lookup in Sonic MQ
=====================================================================
Lookup Name=TopicXA
Type =Topic
Destination Name=[[grpsharedsubs]]TopicXA
JMS Transport configuration in axis2.xml
=====================================================================
<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"/>
Proxy Service Configuration
===================================
<!-- Introduction to proxy services
-->
- <definitions xmlns="http://ws.apache.org/ns/synapse">
- <!-- define the request processing XSLT resource as a static URL source
-->
<localEntry key="xslt-key-req" src="file:repository/conf/sample/resources/transform/echo_transform.xslt" />
- <proxy name="echoProxy" transports="jms">
- <target>
- <endpoint>
<address uri="http://localhost:8082/EJBWebService/EchoBean" />
</endpoint>
- <outSequence>
<log level="full" />
- <out>
<xslt key="xslt-key-req" />
</out>
<send />
</outSequence>
</target>
<parameter name="transport.jms.ConnectionFactory">myTopicConnectionFactory</parameter>
<parameter name="transport.jms.Destination">TopicXA</parameter>
<parameter name="transport.jms.DestinationType">topic</parameter>
<parameter name="transport.jms.ReplyDestination">ReplyTopic</parameter>
<parameter name="transport.jms.ReplyDestinationType">topic</parameter>
<publishWSDL uri="file:repository/conf/sample/resources/proxy/echo_proxy.wsdl" />
</proxy>
</definitions>
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)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Assigned: (SYNAPSE-369) Multiple instances of Synapse
instances cannot form a shared subscription group to Sonic MQ
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen reassigned SYNAPSE-369:
---------------------------------------
Assignee: Andreas Veithen (was: Asankha C. Perera)
> Multiple instances of Synapse instances cannot form a shared subscription group to Sonic MQ
> -------------------------------------------------------------------------------------------
>
> Key: SYNAPSE-369
> URL: https://issues.apache.org/jira/browse/SYNAPSE-369
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: 1.1.1, 1.2
> Environment: Windows XP, JDK 1.6, Sonic MQ 7.5.1
> Reporter: Tanmay saha
> Assignee: Andreas Veithen
> Attachments: mq_getstart.pdf, Readme.txt, SharedSubscriptions.java
>
> Original Estimate: 1344h
> Remaining Estimate: 1344h
>
> This is a new issue. I am running 2 instances of Synapse-1.1.1 or Synapse-1.2. 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 (for example "[[grpsharedsubs]]TopicXA" ), 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 in shared subscription mode. I have all the sonic required jars in Synapse\lib folder. The associated configurations are attached here
> 1) JNDI Lookup name in Sonic MQ
> 2) JMSTransport config in axis2.xml
> 3) Proxy config in Synapse
> 4) JMS Transport config in Synapse
> 5) SynapseError log.
> JNDI Lookup in Sonic MQ
> =====================================================================
> Lookup Name=TopicXA
> Type =Topic
> Destination Name=[[grpsharedsubs]]TopicXA
> JMS Transport configuration in axis2.xml
> =====================================================================
> <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"/>
> Proxy Service Configuration
> ===================================
> <!-- Introduction to proxy services
> -->
> - <definitions xmlns="http://ws.apache.org/ns/synapse">
> - <!-- define the request processing XSLT resource as a static URL source
> -->
> <localEntry key="xslt-key-req" src="file:repository/conf/sample/resources/transform/echo_transform.xslt" />
> - <proxy name="echoProxy" transports="jms">
> - <target>
> - <endpoint>
> <address uri="http://localhost:8082/EJBWebService/EchoBean" />
> </endpoint>
> - <outSequence>
> <log level="full" />
> - <out>
> <xslt key="xslt-key-req" />
> </out>
> <send />
> </outSequence>
> </target>
> <parameter name="transport.jms.ConnectionFactory">myTopicConnectionFactory</parameter>
> <parameter name="transport.jms.Destination">TopicXA</parameter>
> <parameter name="transport.jms.DestinationType">topic</parameter>
> <parameter name="transport.jms.ReplyDestination">ReplyTopic</parameter>
> <parameter name="transport.jms.ReplyDestinationType">topic</parameter>
> <publishWSDL uri="file:repository/conf/sample/resources/proxy/echo_proxy.wsdl" />
> </proxy>
> </definitions>
> 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)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-369) Multiple instances of Synapse
instances cannot form a shared subscription group to Sonic MQ
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613556#action_12613556 ]
Asankha C. Perera commented on SYNAPSE-369:
-------------------------------------------
Tanmay
Can you point me to publicly available documentation and any sample code on Sonic, that describes how shared subscriptions work? I am considering this for inclusion into the JMS enhancements we are planning and it will be helpful.
Meanwhile, did you try the following on your proxy service?.. if so, did it work?
<parameter name="transport.jms.Destination">[[grpsharedsubs]]TopicXA /parameter>
asankha
> Multiple instances of Synapse instances cannot form a shared subscription group to Sonic MQ
> -------------------------------------------------------------------------------------------
>
> Key: SYNAPSE-369
> URL: https://issues.apache.org/jira/browse/SYNAPSE-369
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: 1.1.1, 1.2
> Environment: Windows XP, JDK 1.6, Sonic MQ 7.5.1
> Reporter: Tanmay saha
> Assignee: Asankha C. Perera
> Original Estimate: 1344h
> Remaining Estimate: 1344h
>
> This is a new issue. I am running 2 instances of Synapse-1.1.1 or Synapse-1.2. 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 (for example "[[grpsharedsubs]]TopicXA" ), 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 in shared subscription mode. I have all the sonic required jars in Synapse\lib folder. The associated configurations are attached here
> 1) JNDI Lookup name in Sonic MQ
> 2) JMSTransport config in axis2.xml
> 3) Proxy config in Synapse
> 4) JMS Transport config in Synapse
> 5) SynapseError log.
> JNDI Lookup in Sonic MQ
> =====================================================================
> Lookup Name=TopicXA
> Type =Topic
> Destination Name=[[grpsharedsubs]]TopicXA
> JMS Transport configuration in axis2.xml
> =====================================================================
> <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"/>
> Proxy Service Configuration
> ===================================
> <!-- Introduction to proxy services
> -->
> - <definitions xmlns="http://ws.apache.org/ns/synapse">
> - <!-- define the request processing XSLT resource as a static URL source
> -->
> <localEntry key="xslt-key-req" src="file:repository/conf/sample/resources/transform/echo_transform.xslt" />
> - <proxy name="echoProxy" transports="jms">
> - <target>
> - <endpoint>
> <address uri="http://localhost:8082/EJBWebService/EchoBean" />
> </endpoint>
> - <outSequence>
> <log level="full" />
> - <out>
> <xslt key="xslt-key-req" />
> </out>
> <send />
> </outSequence>
> </target>
> <parameter name="transport.jms.ConnectionFactory">myTopicConnectionFactory</parameter>
> <parameter name="transport.jms.Destination">TopicXA</parameter>
> <parameter name="transport.jms.DestinationType">topic</parameter>
> <parameter name="transport.jms.ReplyDestination">ReplyTopic</parameter>
> <parameter name="transport.jms.ReplyDestinationType">topic</parameter>
> <publishWSDL uri="file:repository/conf/sample/resources/proxy/echo_proxy.wsdl" />
> </proxy>
> </definitions>
> 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)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-369) Multiple instances of Synapse
instances cannot form a shared subscription group to Sonic MQ
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624243#action_12624243 ]
Asankha C. Perera commented on SYNAPSE-369:
-------------------------------------------
Hi Tanmay
I know its been quite sometime for this JIRA.. unfortunately I was not yet able to do the major re-work on the JMS transport I was planning, which deals with supporting JTA and local transactions as well as supporting the new SOAP/JMS spec among others. My idea was to tackle these enhancements together, and go through all JMS issues we have when we do these improvements.
Although I personally would like to work on this right now, my schedule is currently filled at least till end of August, to do some improvements for load balancing and JMX - which has been sponsored by another user. (Note however, that these changes will be made available with the Synapse trunk shortly for all users as well). Thus I can commit to giving you an assurance, that I will handle this before the next major build of Synapse 1.3, but right now I am unable to give you a date as it is.. hope you understand
asankha
> Multiple instances of Synapse instances cannot form a shared subscription group to Sonic MQ
> -------------------------------------------------------------------------------------------
>
> Key: SYNAPSE-369
> URL: https://issues.apache.org/jira/browse/SYNAPSE-369
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: 1.1.1, 1.2
> Environment: Windows XP, JDK 1.6, Sonic MQ 7.5.1
> Reporter: Tanmay saha
> Assignee: Asankha C. Perera
> Attachments: mq_getstart.pdf, Readme.txt, SharedSubscriptions.java
>
> Original Estimate: 1344h
> Remaining Estimate: 1344h
>
> This is a new issue. I am running 2 instances of Synapse-1.1.1 or Synapse-1.2. 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 (for example "[[grpsharedsubs]]TopicXA" ), 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 in shared subscription mode. I have all the sonic required jars in Synapse\lib folder. The associated configurations are attached here
> 1) JNDI Lookup name in Sonic MQ
> 2) JMSTransport config in axis2.xml
> 3) Proxy config in Synapse
> 4) JMS Transport config in Synapse
> 5) SynapseError log.
> JNDI Lookup in Sonic MQ
> =====================================================================
> Lookup Name=TopicXA
> Type =Topic
> Destination Name=[[grpsharedsubs]]TopicXA
> JMS Transport configuration in axis2.xml
> =====================================================================
> <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"/>
> Proxy Service Configuration
> ===================================
> <!-- Introduction to proxy services
> -->
> - <definitions xmlns="http://ws.apache.org/ns/synapse">
> - <!-- define the request processing XSLT resource as a static URL source
> -->
> <localEntry key="xslt-key-req" src="file:repository/conf/sample/resources/transform/echo_transform.xslt" />
> - <proxy name="echoProxy" transports="jms">
> - <target>
> - <endpoint>
> <address uri="http://localhost:8082/EJBWebService/EchoBean" />
> </endpoint>
> - <outSequence>
> <log level="full" />
> - <out>
> <xslt key="xslt-key-req" />
> </out>
> <send />
> </outSequence>
> </target>
> <parameter name="transport.jms.ConnectionFactory">myTopicConnectionFactory</parameter>
> <parameter name="transport.jms.Destination">TopicXA</parameter>
> <parameter name="transport.jms.DestinationType">topic</parameter>
> <parameter name="transport.jms.ReplyDestination">ReplyTopic</parameter>
> <parameter name="transport.jms.ReplyDestinationType">topic</parameter>
> <publishWSDL uri="file:repository/conf/sample/resources/proxy/echo_proxy.wsdl" />
> </proxy>
> </definitions>
> 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)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-369) Multiple instances of Synapse
instances cannot form a shared subscription group to Sonic MQ
Posted by "Tanmay saha (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608846#action_12608846 ]
Tanmay saha commented on SYNAPSE-369:
-------------------------------------
Hi Andreas:
You are correct . serviceDestinationNameMapping is being populated with ( [[groupss]]TopicXA=echoProxy ) at the start up, but in the JMS Header of the actual message , the destination name was "TopicXA" , so naturally the look up failed. I did some work around in JMSConnectionFactory, which is something like this , if the JMS Provider is Sonic MQ and if the destination name has some prefix "[[groupprefix]]" , I am removing this prefix, before populating the serviceDestinationNameMapping . I have tested this with Sonic MQ and found that shared subscription is working fine and there is no errors or warnings in Synapse log. Can you please tell me how can I submit this patch to Synapse SVN?
-Thanks
tanmay
> Multiple instances of Synapse instances cannot form a shared subscription group to Sonic MQ
> -------------------------------------------------------------------------------------------
>
> Key: SYNAPSE-369
> URL: https://issues.apache.org/jira/browse/SYNAPSE-369
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: 1.1.1, 1.2
> Environment: Windows XP, JDK 1.6, Sonic MQ 7.5.1
> Reporter: Tanmay saha
> Original Estimate: 1344h
> Remaining Estimate: 1344h
>
> This is a new issue. I am running 2 instances of Synapse-1.1.1 or Synapse-1.2. 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 (for example "[[grpsharedsubs]]TopicXA" ), 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 in shared subscription mode. I have all the sonic required jars in Synapse\lib folder. The associated configurations are attached here
> 1) JNDI Lookup name in Sonic MQ
> 2) JMSTransport config in axis2.xml
> 3) Proxy config in Synapse
> 4) JMS Transport config in Synapse
> 5) SynapseError log.
> JNDI Lookup in Sonic MQ
> =====================================================================
> Lookup Name=TopicXA
> Type =Topic
> Destination Name=[[grpsharedsubs]]TopicXA
> JMS Transport configuration in axis2.xml
> =====================================================================
> <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"/>
> Proxy Service Configuration
> ===================================
> <!-- Introduction to proxy services
> -->
> - <definitions xmlns="http://ws.apache.org/ns/synapse">
> - <!-- define the request processing XSLT resource as a static URL source
> -->
> <localEntry key="xslt-key-req" src="file:repository/conf/sample/resources/transform/echo_transform.xslt" />
> - <proxy name="echoProxy" transports="jms">
> - <target>
> - <endpoint>
> <address uri="http://localhost:8082/EJBWebService/EchoBean" />
> </endpoint>
> - <outSequence>
> <log level="full" />
> - <out>
> <xslt key="xslt-key-req" />
> </out>
> <send />
> </outSequence>
> </target>
> <parameter name="transport.jms.ConnectionFactory">myTopicConnectionFactory</parameter>
> <parameter name="transport.jms.Destination">TopicXA</parameter>
> <parameter name="transport.jms.DestinationType">topic</parameter>
> <parameter name="transport.jms.ReplyDestination">ReplyTopic</parameter>
> <parameter name="transport.jms.ReplyDestinationType">topic</parameter>
> <publishWSDL uri="file:repository/conf/sample/resources/proxy/echo_proxy.wsdl" />
> </proxy>
> </definitions>
> 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)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-369) Multiple instances of Synapse
instances cannot form a shared subscription group to Sonic MQ
Posted by "Tanmay saha (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tanmay saha updated SYNAPSE-369:
--------------------------------
Attachment: SharedSubscriptions.java
Readme.txt
mq_getstart.pdf
Hi Asankha:
It is difficult to get publicly available Sonic MQ Documentation. I am sharing the one which I have.
Please refer to page no. 56 of the attached pdf.
I am attaching the example source from sonic also.
<parameter name="transport.jms.Destination"> element of Synapse Proxy refers to the JNDI Lookup name of the JMS destination. But the shared subscription group name prefix has to be in front of the actual destination name.
Right now I have made the following changes in addDestination() method of JMSConnectionFactory.java and it is working fine. Since I do not know the purpose of serviceDestinationNameMapping, this was the simple and quick fix for me.
/**
serviceDestinationNameMapping.put(destinationName, serviceName);
log.info("Mapped JNDI name : " + destinationJNDIName + " and JMS Destination name : " +
destinationName + " against service : " + serviceName);
*/
/** Added to remove the [[sharedsubs-group-prefix]] from the destination name, before populating the serviceDestinationNameMapping **/
int index = destinationName.indexOf("]");
if( index > 0 )
{
String tempdestinationName=destinationName.substring(index+2);
serviceDestinationNameMapping.put(tempdestinationName, serviceName);
log.info("Mapped JNDI name : " + destinationJNDIName + " and JMS Destination name : " +
tempdestinationName + " against service : " + serviceName);
}
else
{
serviceDestinationNameMapping.put(destinationName, serviceName);
log.info("Mapped JNDI name : " + destinationJNDIName + " and JMS Destination name : " +
destinationName + " against service : " + serviceName);
}
Pl feel free to contact me, if you need any more info.
-Thanks
tanmay
> Multiple instances of Synapse instances cannot form a shared subscription group to Sonic MQ
> -------------------------------------------------------------------------------------------
>
> Key: SYNAPSE-369
> URL: https://issues.apache.org/jira/browse/SYNAPSE-369
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: 1.1.1, 1.2
> Environment: Windows XP, JDK 1.6, Sonic MQ 7.5.1
> Reporter: Tanmay saha
> Assignee: Asankha C. Perera
> Attachments: mq_getstart.pdf, Readme.txt, SharedSubscriptions.java
>
> Original Estimate: 1344h
> Remaining Estimate: 1344h
>
> This is a new issue. I am running 2 instances of Synapse-1.1.1 or Synapse-1.2. 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 (for example "[[grpsharedsubs]]TopicXA" ), 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 in shared subscription mode. I have all the sonic required jars in Synapse\lib folder. The associated configurations are attached here
> 1) JNDI Lookup name in Sonic MQ
> 2) JMSTransport config in axis2.xml
> 3) Proxy config in Synapse
> 4) JMS Transport config in Synapse
> 5) SynapseError log.
> JNDI Lookup in Sonic MQ
> =====================================================================
> Lookup Name=TopicXA
> Type =Topic
> Destination Name=[[grpsharedsubs]]TopicXA
> JMS Transport configuration in axis2.xml
> =====================================================================
> <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"/>
> Proxy Service Configuration
> ===================================
> <!-- Introduction to proxy services
> -->
> - <definitions xmlns="http://ws.apache.org/ns/synapse">
> - <!-- define the request processing XSLT resource as a static URL source
> -->
> <localEntry key="xslt-key-req" src="file:repository/conf/sample/resources/transform/echo_transform.xslt" />
> - <proxy name="echoProxy" transports="jms">
> - <target>
> - <endpoint>
> <address uri="http://localhost:8082/EJBWebService/EchoBean" />
> </endpoint>
> - <outSequence>
> <log level="full" />
> - <out>
> <xslt key="xslt-key-req" />
> </out>
> <send />
> </outSequence>
> </target>
> <parameter name="transport.jms.ConnectionFactory">myTopicConnectionFactory</parameter>
> <parameter name="transport.jms.Destination">TopicXA</parameter>
> <parameter name="transport.jms.DestinationType">topic</parameter>
> <parameter name="transport.jms.ReplyDestination">ReplyTopic</parameter>
> <parameter name="transport.jms.ReplyDestinationType">topic</parameter>
> <publishWSDL uri="file:repository/conf/sample/resources/proxy/echo_proxy.wsdl" />
> </proxy>
> </definitions>
> 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)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-369) Multiple instances of Synapse
instances cannot form a shared subscription group to Sonic MQ
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608854#action_12608854 ]
Andreas Veithen commented on SYNAPSE-369:
-----------------------------------------
Tanmay,
I think that the conclusion is that since the dispatching mechanism shows problems with both Active MQ and Sonic MQ, it is flawed and needs to be corrected (even if one can argue that it is because the JMS provider returns inconsistent information). I believe that we should eliminate the serviceDestinationNameMapping by having one JMSMessageReceiver instance per service as described above. But maybe I miss something and there is a good reason for the existence of serviceDestinationNameMapping.
Asankha,
Can you check my analysis and evaluate the proposed solution?
> Multiple instances of Synapse instances cannot form a shared subscription group to Sonic MQ
> -------------------------------------------------------------------------------------------
>
> Key: SYNAPSE-369
> URL: https://issues.apache.org/jira/browse/SYNAPSE-369
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: 1.1.1, 1.2
> Environment: Windows XP, JDK 1.6, Sonic MQ 7.5.1
> Reporter: Tanmay saha
> Original Estimate: 1344h
> Remaining Estimate: 1344h
>
> This is a new issue. I am running 2 instances of Synapse-1.1.1 or Synapse-1.2. 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 (for example "[[grpsharedsubs]]TopicXA" ), 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 in shared subscription mode. I have all the sonic required jars in Synapse\lib folder. The associated configurations are attached here
> 1) JNDI Lookup name in Sonic MQ
> 2) JMSTransport config in axis2.xml
> 3) Proxy config in Synapse
> 4) JMS Transport config in Synapse
> 5) SynapseError log.
> JNDI Lookup in Sonic MQ
> =====================================================================
> Lookup Name=TopicXA
> Type =Topic
> Destination Name=[[grpsharedsubs]]TopicXA
> JMS Transport configuration in axis2.xml
> =====================================================================
> <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"/>
> Proxy Service Configuration
> ===================================
> <!-- Introduction to proxy services
> -->
> - <definitions xmlns="http://ws.apache.org/ns/synapse">
> - <!-- define the request processing XSLT resource as a static URL source
> -->
> <localEntry key="xslt-key-req" src="file:repository/conf/sample/resources/transform/echo_transform.xslt" />
> - <proxy name="echoProxy" transports="jms">
> - <target>
> - <endpoint>
> <address uri="http://localhost:8082/EJBWebService/EchoBean" />
> </endpoint>
> - <outSequence>
> <log level="full" />
> - <out>
> <xslt key="xslt-key-req" />
> </out>
> <send />
> </outSequence>
> </target>
> <parameter name="transport.jms.ConnectionFactory">myTopicConnectionFactory</parameter>
> <parameter name="transport.jms.Destination">TopicXA</parameter>
> <parameter name="transport.jms.DestinationType">topic</parameter>
> <parameter name="transport.jms.ReplyDestination">ReplyTopic</parameter>
> <parameter name="transport.jms.ReplyDestinationType">topic</parameter>
> <publishWSDL uri="file:repository/conf/sample/resources/proxy/echo_proxy.wsdl" />
> </proxy>
> </definitions>
> 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)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-369) Multiple instances of Synapse
instances cannot form a shared subscription group to Sonic MQ
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607118#action_12607118 ]
Andreas Veithen commented on SYNAPSE-369:
-----------------------------------------
Normally messages received through the JMS transport are already dispatched to the service by the transport listener. The exception seems to indicate that this operation failed. Indeed, if the transport doesn't predispatch the incoming message, it will be dispatched to __SynapseService by SynapseDispatcher. However, this service is only exposed on the HTTP(S) transports, explaining the exception in validateTransport.
Why would the dispatching by the JMS message listener fail?
The strategy used by the listener is as follows (see JMSMessageReceiver.Worker#run):
(1) Get the destination name (the provider name, not the JNDI name) from the JMS message.
(2) Map the JMS destination name to an Axis2 service name using JMSConnectionFactory#serviceDestinationNameMapping (which is populated during startListeningForService).
The comment "bypass dispatching if we know the service - we already should!" in JMSMessageReceiver.Worker#run as well as the code in JMSConnectionFactory#getServiceNameForDestination ("hack to get around the crazy Active MQ dynamic queue and topic issues") suggests that this strategy is not always reliable and may be the root cause of the present issue.
As far as I can see, the (destination name, service name) map used in step (2) is only required because the JMS listener uses one JMSMessageReceiver per connection factory. Since JMSMessageReceiver is registered with MessageConsumer and we have one MessageConsumer per destination/service, I wonder why we don't create a separate JMSMessageReceiver per service? In this case JMSMessageReceiver would know the service to dispatch to and no longer needs serviceDestinationNameMapping. Or am I missing something?
> Multiple instances of Synapse instances cannot form a shared subscription group to Sonic MQ
> -------------------------------------------------------------------------------------------
>
> Key: SYNAPSE-369
> URL: https://issues.apache.org/jira/browse/SYNAPSE-369
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: 1.1.1, 1.2
> Environment: Windows XP, JDK 1.6, Sonic MQ 7.5.1
> Reporter: Tanmay saha
> Original Estimate: 1344h
> Remaining Estimate: 1344h
>
> This is a new issue. I am running 2 instances of Synapse-1.1.1 or Synapse-1.2. 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 (for example "[[grpsharedsubs]]TopicXA" ), 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 in shared subscription mode. I have all the sonic required jars in Synapse\lib folder. The associated configurations are attached here
> 1) JNDI Lookup name in Sonic MQ
> 2) JMSTransport config in axis2.xml
> 3) Proxy config in Synapse
> 4) JMS Transport config in Synapse
> 5) SynapseError log.
> JNDI Lookup in Sonic MQ
> =====================================================================
> Lookup Name=TopicXA
> Type =Topic
> Destination Name=[[grpsharedsubs]]TopicXA
> JMS Transport configuration in axis2.xml
> =====================================================================
> <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"/>
> Proxy Service Configuration
> ===================================
> <!-- Introduction to proxy services
> -->
> - <definitions xmlns="http://ws.apache.org/ns/synapse">
> - <!-- define the request processing XSLT resource as a static URL source
> -->
> <localEntry key="xslt-key-req" src="file:repository/conf/sample/resources/transform/echo_transform.xslt" />
> - <proxy name="echoProxy" transports="jms">
> - <target>
> - <endpoint>
> <address uri="http://localhost:8082/EJBWebService/EchoBean" />
> </endpoint>
> - <outSequence>
> <log level="full" />
> - <out>
> <xslt key="xslt-key-req" />
> </out>
> <send />
> </outSequence>
> </target>
> <parameter name="transport.jms.ConnectionFactory">myTopicConnectionFactory</parameter>
> <parameter name="transport.jms.Destination">TopicXA</parameter>
> <parameter name="transport.jms.DestinationType">topic</parameter>
> <parameter name="transport.jms.ReplyDestination">ReplyTopic</parameter>
> <parameter name="transport.jms.ReplyDestinationType">topic</parameter>
> <publishWSDL uri="file:repository/conf/sample/resources/proxy/echo_proxy.wsdl" />
> </proxy>
> </definitions>
> 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)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Resolved: (SYNAPSE-369) Multiple instances of Synapse
instances cannot form a shared subscription group to Sonic MQ
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen resolved SYNAPSE-369.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.3
The transport listener has been changed to create one JMSMessageReceiver instance per service. The following pieces of code are therefore no longer necessary and have been eliminated:
* JMSConnectionFactory#serviceDestinationNameMapping
* JMSConnectionFactory#getServiceNameForDestination (with the "hack to get around the crazy Active MQ dynamic queue and topic issues")
* The physical destination name to service name translation in JMSMessageReceiver.Worker#run, in particular the call to Message#getJMSDestination
Since the issue described here is caused by a mismatch between the return value of Message#getJMSDestination and the physical name of the destination retrieved from JNDI, I believe that this change solves the problem. Actually the JMS transport listener now no longer uses physical destination names at all, except for logging purposes.
> Multiple instances of Synapse instances cannot form a shared subscription group to Sonic MQ
> -------------------------------------------------------------------------------------------
>
> Key: SYNAPSE-369
> URL: https://issues.apache.org/jira/browse/SYNAPSE-369
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: 1.1.1, 1.2
> Environment: Windows XP, JDK 1.6, Sonic MQ 7.5.1
> Reporter: Tanmay saha
> Assignee: Andreas Veithen
> Fix For: 1.3
>
> Attachments: mq_getstart.pdf, Readme.txt, SharedSubscriptions.java
>
> Original Estimate: 1344h
> Remaining Estimate: 1344h
>
> This is a new issue. I am running 2 instances of Synapse-1.1.1 or Synapse-1.2. 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 (for example "[[grpsharedsubs]]TopicXA" ), 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 in shared subscription mode. I have all the sonic required jars in Synapse\lib folder. The associated configurations are attached here
> 1) JNDI Lookup name in Sonic MQ
> 2) JMSTransport config in axis2.xml
> 3) Proxy config in Synapse
> 4) JMS Transport config in Synapse
> 5) SynapseError log.
> JNDI Lookup in Sonic MQ
> =====================================================================
> Lookup Name=TopicXA
> Type =Topic
> Destination Name=[[grpsharedsubs]]TopicXA
> JMS Transport configuration in axis2.xml
> =====================================================================
> <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"/>
> Proxy Service Configuration
> ===================================
> <!-- Introduction to proxy services
> -->
> - <definitions xmlns="http://ws.apache.org/ns/synapse">
> - <!-- define the request processing XSLT resource as a static URL source
> -->
> <localEntry key="xslt-key-req" src="file:repository/conf/sample/resources/transform/echo_transform.xslt" />
> - <proxy name="echoProxy" transports="jms">
> - <target>
> - <endpoint>
> <address uri="http://localhost:8082/EJBWebService/EchoBean" />
> </endpoint>
> - <outSequence>
> <log level="full" />
> - <out>
> <xslt key="xslt-key-req" />
> </out>
> <send />
> </outSequence>
> </target>
> <parameter name="transport.jms.ConnectionFactory">myTopicConnectionFactory</parameter>
> <parameter name="transport.jms.Destination">TopicXA</parameter>
> <parameter name="transport.jms.DestinationType">topic</parameter>
> <parameter name="transport.jms.ReplyDestination">ReplyTopic</parameter>
> <parameter name="transport.jms.ReplyDestinationType">topic</parameter>
> <publishWSDL uri="file:repository/conf/sample/resources/proxy/echo_proxy.wsdl" />
> </proxy>
> </definitions>
> 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)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Assigned: (SYNAPSE-369) Multiple instances of Synapse
instances cannot form a shared subscription group to Sonic MQ
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen reassigned SYNAPSE-369:
---------------------------------------
Assignee: Asankha C. Perera
> Multiple instances of Synapse instances cannot form a shared subscription group to Sonic MQ
> -------------------------------------------------------------------------------------------
>
> Key: SYNAPSE-369
> URL: https://issues.apache.org/jira/browse/SYNAPSE-369
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: 1.1.1, 1.2
> Environment: Windows XP, JDK 1.6, Sonic MQ 7.5.1
> Reporter: Tanmay saha
> Assignee: Asankha C. Perera
> Original Estimate: 1344h
> Remaining Estimate: 1344h
>
> This is a new issue. I am running 2 instances of Synapse-1.1.1 or Synapse-1.2. 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 (for example "[[grpsharedsubs]]TopicXA" ), 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 in shared subscription mode. I have all the sonic required jars in Synapse\lib folder. The associated configurations are attached here
> 1) JNDI Lookup name in Sonic MQ
> 2) JMSTransport config in axis2.xml
> 3) Proxy config in Synapse
> 4) JMS Transport config in Synapse
> 5) SynapseError log.
> JNDI Lookup in Sonic MQ
> =====================================================================
> Lookup Name=TopicXA
> Type =Topic
> Destination Name=[[grpsharedsubs]]TopicXA
> JMS Transport configuration in axis2.xml
> =====================================================================
> <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"/>
> Proxy Service Configuration
> ===================================
> <!-- Introduction to proxy services
> -->
> - <definitions xmlns="http://ws.apache.org/ns/synapse">
> - <!-- define the request processing XSLT resource as a static URL source
> -->
> <localEntry key="xslt-key-req" src="file:repository/conf/sample/resources/transform/echo_transform.xslt" />
> - <proxy name="echoProxy" transports="jms">
> - <target>
> - <endpoint>
> <address uri="http://localhost:8082/EJBWebService/EchoBean" />
> </endpoint>
> - <outSequence>
> <log level="full" />
> - <out>
> <xslt key="xslt-key-req" />
> </out>
> <send />
> </outSequence>
> </target>
> <parameter name="transport.jms.ConnectionFactory">myTopicConnectionFactory</parameter>
> <parameter name="transport.jms.Destination">TopicXA</parameter>
> <parameter name="transport.jms.DestinationType">topic</parameter>
> <parameter name="transport.jms.ReplyDestination">ReplyTopic</parameter>
> <parameter name="transport.jms.ReplyDestinationType">topic</parameter>
> <publishWSDL uri="file:repository/conf/sample/resources/proxy/echo_proxy.wsdl" />
> </proxy>
> </definitions>
> 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)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org