Hi Akalanka,

Thank you for the support. The error is little bit misleading, and it was a
configuration issue which causes the error. In jndi properties topic name
is "example.MyTopic", but specifying topic name in CEP end, it has to be
just "MyTopic".

Thanks

On Wed, Mar 18, 2015 at 10:53 AM, Akalanka Pagoda Arachchi <
[email protected]> wrote:

> Hi Tharik,
>
> Please check the AMQP version used in CEP for this connection. Currently
> MB only supports up to AMQP 0.9.1 and it looks like CEP is using a later
> version than that for this connection.
>
> Thanks,
> Akalanka.
>
> On Wed, Mar 18, 2015 at 10:22 AM, Tharik Kanaka <[email protected]> wrote:
>
>>
>> Hi all,
>>
>> I am trying to connect MB (2.2.0) as producer and CEP (4.0.0) as consumer
>> using input adapters. I am getting following error continously once i have
>> connected the CEP with MB.
>>
>> ERROR - {NativeWorkerPool}  Uncaught exception
>> java.lang.UnsupportedOperationException: The new addressing based sytanx
>> is not supported for AMQP 0-8/0-9 versions
>> at
>> org.wso2.andes.client.AMQSession_0_8.handleAddressBasedDestination(AMQSession_0_8.java:577)
>> at org.wso2.andes.client.AMQSession.registerConsumer(AMQSession.java:2868)
>> at org.wso2.andes.client.AMQSession.access$500(AMQSession.java:109)
>> at org.wso2.andes.client.AMQSession$5.execute(AMQSession.java:2061)
>> at org.wso2.andes.client.AMQSession$5.execute(AMQSession.java:2027)
>> at
>> org.wso2.andes.client.AMQConnectionDelegate_8_0.executeRetrySupport(AMQConnectionDelegate_8_0.java:315)
>> at
>> org.wso2.andes.client.AMQConnection.executeRetrySupport(AMQConnection.java:621)
>> at
>> org.wso2.andes.client.failover.FailoverRetrySupport.execute(FailoverRetrySupport.java:102)
>> at
>> org.wso2.andes.client.AMQSession.createConsumerImpl(AMQSession.java:2025)
>> at org.wso2.andes.client.AMQSession.createConsumer(AMQSession.java:1028)
>> at
>> org.wso2.carbon.event.input.adaptor.jms.internal.util.JMSUtils.createConsumer(JMSUtils.java:472)
>> at
>> org.wso2.carbon.event.input.adaptor.jms.internal.util.JMSTaskManager$MessageListenerTask.createConsumer(JMSTaskManager.java:982)
>> at
>> org.wso2.carbon.event.input.adaptor.jms.internal.util.JMSTaskManager$MessageListenerTask.getMessageConsumer(JMSTaskManager.java:850)
>> at
>> org.wso2.carbon.event.input.adaptor.jms.internal.util.JMSTaskManager$MessageListenerTask.receiveMessage(JMSTaskManager.java:599)
>> at
>> org.wso2.carbon.event.input.adaptor.jms.internal.util.JMSTaskManager$MessageListenerTask.run(JMSTaskManager.java:520)
>> at
>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>> at java.lang.Thread.run(Thread.java:695)
>>
>>
>> Following are CEP jndi properties
>>
>> # register some connection factories
>> # connectionfactory.[jndiname] = [ConnectionURL]
>> connectionfactory.TopicConnectionFactory = amqp://admin:admin@clientID
>> /carbon?brokerlist='tcp://localhost:5674'
>>
>> connectionfactory.QueueConnectionFactory = amqp://admin:admin@clientID
>> /carbon?brokerlist='tcp://localhost:5674''
>>
>> # register some queues in JNDI using the form
>> # queue.[jndiName] = [physicalName]
>> queue.MyQueue = example.MyQueue
>>
>> # register some topics in JNDI using the form
>> # topic.[jndiName] = [physicalName]
>> topic.MyTopic = example.MyTopic
>>
>>
>> This the CEP input adapter
>>
>> <inputEventAdaptor name="jmsInputAdapter" statistics="disable"
>>   trace="disable" type="jms" xmlns="
>> http://wso2.org/carbon/eventadaptormanager";>
>>   <property
>> name="java.naming.provider.url">repository/conf/jndi.properties</property>
>>   <property
>> name="java.naming.factory.initial">org.wso2.andes.jndi.PropertiesFileInitialContextFactory</property>
>>   <property
>> name="transport.jms.ConnectionFactoryJNDIName">TopicConnectionFactory</property>
>>   <property name="transport.jms.DestinationType">topic</property>
>> </inputEventAdaptor>
>>
>>
>> Is it causing due to mismatching of AMQP version?
>>
>>
>> --
>>
>> *Tharik Kanaka* | Associate Software Engineer
>>
>> WSO2, Inc |#20, Palm Grove, Colombo 03, Sri Lanka
>>
>> Email: [email protected] | Web: www.wso2.com
>>
>> _______________________________________________
>> Dev mailing list
>> [email protected]
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Darshana Akalanka Pagoda Arachchi,*
> *Software Engineer*
> *078-4721791*
>



-- 

*Tharik Kanaka* | Associate Software Engineer

WSO2, Inc |#20, Palm Grove, Colombo 03, Sri Lanka

Email: [email protected] | Web: www.wso2.com
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to