Hi Ravindra,
I was setting up using axis2.xml, when I switched to inbound endpoint it
worked. But I believe we need to fix this for axis2 xml as well.

Hi Dilshani,
Shall we add a test case for testing shared subscription configured via
axis2 as well.

On Fri, May 27, 2016 at 11:51 PM, Ravindra Ranwala <ravin...@wso2.com>
wrote:

> Hi Manuranga,
>
> The shared subscription feature works fine and we used to test it with HornetQ
> broker. This could be due to some missing configuration. Could you please
> follow the blog post [1], and check the correctness in your configuration.
>
>
> [1] http://ravindraranwala.blogspot.com/
>
>
> Thanks & Regards,
>
> On Fri, May 27, 2016 at 8:51 PM, Manuranga Perera <m...@wso2.com> wrote:
>
>> I am trying to connect to IBM MQ using JMS 2
>>
>> <proxy xmlns="http://ws.apache.org/ns/synapse"; name="TReaderPxy2"
>> startOnLoad="true">
>>    <target>
>>       <inSequence>
>>          <property name="OUT_ONLY" value="true"/>
>>          <log level="full"/>
>>          <drop/>
>>       </inSequence>
>>    </target>
>>    <parameter name="transport.jms.DestinationType">topic</parameter>
>>    <parameter name="transport.jms.DurableSubscriberName">mySub</parameter>
>>    <parameter name="transport.jms.Destination">TestQ49</parameter>
>>    <parameter name="transport.jms.SubscriptionDurable">true</parameter>
>>    <parameter name="transport.jms.DurableSubscriberClientID">1</parameter>
>>    <parameter
>> name="transport.jms.ConnectionFactory">myTopicParams</parameter>
>>    <parameter name="transport.jms.JMSSpecVersion">2.0</parameter>
>>    <parameter name="transport.jms.SharedSubscription">true</parameter>
>> </proxy>
>>
>> First ESB instance can connect successfully and I can publish messages.
>> But when I start another identical instance I see following error.
>> It connects if subscriber names are distinct, but then messages are
>> cloned, not shared.
>>
>> Please help me identify the issue.
>>
>> TID: [-1234] [] [2016-05-27 11:11:07,719]  INFO
>> {org.apache.axis2.transport.jms.JMSListener} -  JMS listener started
>> {org.apache.axis2.transport.jms.JMSListener}
>> TID: [-1234] [] [2016-05-27 11:11:07,720] DEBUG
>> {org.apache.axis2.transport.jms.JMSEndpoint} -  JMS reply destination type
>> not given. default queue {org.apache.axis2.transport.jms.JMSEndpoint}
>> TID: [-1234] [] [2016-05-27 11:11:07,738] DEBUG
>> {org.apache.axis2.transport.jms.JMSUtils} -  Creating a GenericConnection
>> using credentials : (null/null) {org.apache.axis2.transport.jms.JMSUtils}
>> TID: [-1234] [] [2016-05-27 11:11:08,011]  INFO
>> {org.apache.axis2.transport.jms.JMSListener} -  Connection attempt: 1 for
>> JMS Provider for service: TReaderPxy2 was successful!
>> {org.apache.axis2.transport.jms.JMSListener}
>> TID: [-1234] [] [2016-05-27 11:11:08,011] DEBUG
>> {org.apache.axis2.transport.jms.ServiceTaskManager} -  The JMS Connection,
>> Session and MessageConsumer will be cached and shared between successive
>> poller task invocations {org.apache.axis2.transport.jms.ServiceTaskManager}
>> TID: [-1234] [] [2016-05-27 11:11:08,017]  INFO
>> {org.apache.axis2.transport.jms.ServiceTaskManager} -  Task manager for
>> service : TReaderPxy2 [re-]initialized
>> {org.apache.axis2.transport.jms.ServiceTaskManager}
>> TID: [-1] [] [2016-05-27 11:11:08,020] DEBUG
>> {org.apache.axis2.transport.jms.ServiceTaskManager} -  New poll task
>> starting : thread id = 82
>> {org.apache.axis2.transport.jms.ServiceTaskManager}
>> TID: [-1] [] [2016-05-27 11:11:08,026] DEBUG
>> {org.apache.axis2.transport.jms.ServiceTaskManager} -  Connected to the JMS
>> connection factory : USAPP2D.TCF
>> {org.apache.axis2.transport.jms.ServiceTaskManager}
>> TID: [-1] [] [2016-05-27 11:11:08,027] DEBUG
>> {org.apache.axis2.transport.jms.JMSUtils} -  Creating a TopicConnection
>> using credentials : (null/null) {org.apache.axis2.transport.jms.JMSUtils}
>> TID: [-1] [] [2016-05-27 11:11:08,055] DEBUG
>> {org.apache.axis2.transport.jms.ServiceTaskManager} -  JMS Connection for
>> service : TReaderPxy2 created and started
>> {org.apache.axis2.transport.jms.ServiceTaskManager}
>> TID: [-1] [] [2016-05-27 11:11:08,056] DEBUG
>> {org.apache.axis2.transport.jms.ServiceTaskManager} -  Creating a new JMS
>> Session for service : TReaderPxy2
>> {org.apache.axis2.transport.jms.ServiceTaskManager}
>> TID: [-1] [] [2016-05-27 11:11:08,113] DEBUG
>> {org.apache.axis2.transport.jms.ServiceTaskManager} -  Creating a new JMS
>> MessageConsumer for service : TReaderPxy2
>> {org.apache.axis2.transport.jms.ServiceTaskManager}
>> TID: [-1] [] [2016-05-27 11:11:08,143] DEBUG
>> {org.apache.axis2.transport.jms.ServiceTaskManager} -  JMS Destination with
>> JNDI name : TestQ49 found for service TReaderPxy2
>> {org.apache.axis2.transport.jms.ServiceTaskManager}
>> TID: [-1] [] [2016-05-27 11:11:08,198] ERROR
>> {org.apache.axis2.transport.jms.ServiceTaskManager} -  Error creating JMS
>> consumer for service : TReaderPxy2. JMSWMQ0026: Failed to subscribe to
>> topic 'TestQ49' with selector 'none' using MQSUB.
>> {org.apache.axis2.transport.jms.ServiceTaskManager}
>> com.ibm.msg.client.jms.DetailedIllegalStateException: JMSWMQ0026: Failed
>> to subscribe to topic 'TestQ49' with selector 'none' using MQSUB.
>> There may have been a problem creating the subscription due to it being
>> used by another message consumer.
>> Make sure any message consumers using this subscription are closed before
>> trying to create a new subscription under the same name. Please see the
>> linked exception for more information.
>> at
>> com.ibm.msg.client.wmq.common.internal.Reason.reasonToException(Reason.java:472)
>> at
>> com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:214)
>> at
>> com.ibm.msg.client.wmq.internal.WMQMessageConsumer.checkJmqiCallSuccess(WMQMessageConsumer.java:212)
>> at
>> com.ibm.msg.client.wmq.internal.WMQMessageConsumer.checkJmqiCallSuccess(WMQMessageConsumer.java:112)
>> at
>> com.ibm.msg.client.wmq.internal.WMQConsumerShadow.initialize(WMQConsumerShadow.java:1038)
>> at
>> com.ibm.msg.client.wmq.internal.WMQSyncConsumerShadow.initialize(WMQSyncConsumerShadow.java:134)
>> at
>> com.ibm.msg.client.wmq.internal.WMQMessageConsumer.<init>(WMQMessageConsumer.java:470)
>> at
>> com.ibm.msg.client.wmq.internal.WMQSession.createDurableSubscriber(WMQSession.java:897)
>> at
>> com.ibm.msg.client.jms.internal.JmsSessionImpl.createDurableSubscriber(JmsSessionImpl.java:1166)
>> at com.ibm.mq.jms.MQSession.createDurableSubscriber(MQSession.java:539)
>> at
>> org.apache.axis2.transport.jms.JMSUtils.createConsumer(JMSUtils.java:794)
>> at
>> org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConsumer(ServiceTaskManager.java:924)
>> at
>> org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.getMessageConsumer(ServiceTaskManager.java:785)
>> at
>> org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.receiveMessage(ServiceTaskManager.java:535)
>> at
>> org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:447)
>> at
>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> at java.lang.Thread.run(Thread.java:745)
>> Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed
>> with compcode '2' ('MQCC_FAILED') reason '2429'
>> ('MQRC_SUBSCRIPTION_IN_USE').
>> at
>> com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:202)
>> ... 17 more
>> --
>> With regards,
>> *Manu*ranga Perera.
>>
>> phone : 071 7 70 20 50
>> mail : m...@wso2.com
>>
>
>
>
> --
> Ravindra Ranwala
> Software Engineer
> WSO2, Inc: http://wso2.com
> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg>
> Mobile: +94714198770
>
>


-- 
With regards,
*Manu*ranga Perera.

phone : 071 7 70 20 50
mail : m...@wso2.com
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to