Create durable subscription to Azure Service Bus

2017-08-07 Thread 4 Integration
Hi, Testing QPid JMS (AMQP v1.0) with Azure Service Bus (SB). Trying to get durable subscriptions to work. I have created a topic in SB When starting my test app I get: javax.jms.JMSException: The messaging entity 'mynamespace:topic:test.topic~15|test1' could not be found. TrackingId:12ecc2a3-f

Re: Create durable subscription to Azure Service Bus

2017-08-08 Thread 4 Integration
e.printStackTrace(); } } public void close() throws JMSException { connection.close(); } } / Joacim On Mon, Aug 7, 2017 at 3:34 PM, Timothy Bish wrote: > On 08/07/2017 09:26 AM, 4 Integration wrote: > >> Hi, >> >> Testing QPid JMS

Re: Create durable subscription to Azure Service Bus

2017-08-08 Thread 4 Integration
Tested to change but the same error. //subscriber = subscriberSession.createDurableSubscriber(topic, "DurableSubscriber1"); subscriber = subscriberSession.createConsumer(topic); In the exception - what is "~15" characters? javax.jms.InvalidDestinationException: The messaging ent

Idle timeout with Azure Service Bus

2017-08-08 Thread 4 Integration
Hi, Using Qpid JMS 0.23 with Azure Service Bus. When using the URI: amqps://my-namespace.servicebus.windows.net:5671" I get: javax.jms.JMSException: Idle timeout value specified in connection OPEN ('3 ms') is not supported. Minimum idle timeout is '6' ms. When setting amqps://my-namespa

Re: Idle timeout with Azure Service Bus

2017-08-08 Thread 4 Integration
Thanks for explanation. / Joacim On Tue, Aug 8, 2017 at 11:25 AM, Rob Godfrey wrote: > On 8 August 2017 at 11:09, 4 Integration <4integrat...@gmail.com> wrote: > > > Hi, > > > > Using Qpid JMS 0.23 with Azure Service Bus. > > Wh

Re: Create durable subscription to Azure Service Bus

2017-08-08 Thread 4 Integration
oolExecutor$Worker.run( ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) 2017-08-08T12:28:25.904 TRACE [org.apache.qpid.jms.transports.netty.NettyTcpTransport] - New data read: 8 bytes incoming: PooledUnsafeDirectByteBuf(ridx: 0, widx: 8, cap: 69) [350616316:0] <- Empty

Re: Create durable subscription to Azure Service Bus

2017-08-08 Thread 4 Integration
ith topic "" but same exception javax.jms.InvalidDestinationException: The messaging entity 'my-namespace:topic:aaaa~15|qpid ... On Tue, Aug 8, 2017 at 1:27 PM, 4 Integration <4integrat...@gmail.com> wrote: > As suggested by Gordon => Running with env var PN_TRACE_FRM=1 and post the &g

Re: Create durable subscription to Azure Service Bus

2017-08-08 Thread 4 Integration
On the topic defined in Azure Service Bus "test.topic" I have a static subscription defined named "sub1". When publishing I use: env.put("topic.TOPIC", "test.topic"); When subscribing to "sub1" I have env.put("topic.TOPIC", "test.topic/Subscriptions/sub1"); The naming here seems required i.e. <>

Re: Create durable subscription to Azure Service Bus

2017-08-10 Thread 4 Integration
sessions and distributed transactions are not supported. If required then need to use Azure SB API https://github.com/Azure/azure-service-bus-java Regards Joacim On Tue, Aug 8, 2017 at 2:09 PM, 4 Integration <4integrat...@gmail.com> wrote: > On the topic defined in Azure Service Bus &q

Re: Create durable subscription to Azure Service Bus

2017-08-10 Thread 4 Integration
g wildcard subscriptions...we are leaning toward RabbitMQ as of now. But experiencing some issues with Qpid JMS 0.23 with that also... Do you know if Qpid JMS is tested to RabbitMQ? / Joacim On Thu, Aug 10, 2017 at 2:07 PM, Gordon Sim wrote: > On 10/08/17 12:01, 4 Integration wrote: > >> I

Re: Create durable subscription to Azure Service Bus

2017-08-10 Thread 4 Integration
As in a post last week: https://groups.google.com/d/msg/rabbitmq-users/_6bD9bQDlZ0/isl651WeAQAJ and: "*amqp:modified:list is not currently supported by the plugin. As far as I can see,* *our test suite confirms this.*" / Joacim On Thu, Aug 10, 2017 at 3:10 PM, 4 Integration