On 10/08/17 17:55, Robbie Gemmell wrote:
I dont think any of the points on unsupported features below actually
relate to what you are seeing, with it instead just being a difference
in what the AMQP JMS Mapping does for passing JMS subscription
details, versus the approach Service Bus is using/ex
The client isn't tested against RabbitMQ, the brokers current
behaviour around the 'modified' disposition will essentially prevent
them being used together for now. I filed an issue for it along with
another last year when debugging some issues with a different client:
https://github.com/rabbitmq/r
I dont think any of the points on unsupported features below actually
relate to what you are seeing, with it instead just being a difference
in what the AMQP JMS Mapping does for passing JMS subscription
details, versus the approach Service Bus is using/expecting.
>From what you outlined, it appea
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 <4integrat...@gmai
Correct (to my understanding).
Also another drawback is that if you have two or more subscriptions (e.g.
SUB-A and SUB-B for APP-A and APP-B) on the same topic there are no
authorization on subscription level - only on topic. So APP-A can receive
"subscribe" on SUB-B. Also missing wildcard subscrip
On 10/08/17 12:01, 4 Integration wrote:
I have found the answer:
It is not possible to create durable subscriptions dynamically with
QPid/AMQ v1.0 due to:
https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-java-how-to-use-jms-api-amqp#unsupported-features-and-restrictions
U
I have found the answer:
It is not possible to create durable subscriptions dynamically with
QPid/AMQ v1.0 due to:
https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-java-how-to-use-jms-api-amqp#unsupported-features-and-restrictions
Unsupported features and restrictions
The
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.
<>
On 08/08/17 12:37, Gordon Sim wrote:
You could try a further experiment with another see if we can rule out
one or other of these
E.g. if it is easy to get proton python client, you could use the
simple_recv.py example with -a
my-namespace.servicebus.windows.net:5671/test.topic and see what t
On 08/08/17 12:46, 4 Integration wrote:
/(Also, service bus appears to be sending the detach *before* echoing
the attach, which is a protocol error)./
Just for clarification, that part was from a different run where the
detach was before the attach. That is not the case on the latest trace.
Additional input from Gordon: "
*This looks like either there is no source called test.topic configured on
the service bus, or it doesn't like the 'topic' capability. (You could try
a further experiment with another see if we can rule out one or other of
these).The ~15 seems to be coming from some
On 08/08/17 12:27, 4 Integration wrote:
As suggested by Gordon => Running with env var PN_TRACE_FRM=1 and post the
protocol trace you see.
Configured a proper logger and got more details:
This looks like either there is no source called test.topic configured
on the service bus, or it doesn't
As suggested by Gordon => Running with env var PN_TRACE_FRM=1 and post the
protocol trace you see.
Configured a proper logger and got more details:
2017-08-08T12:27:31.202 TRACE [org.apache.qpid.jms.transports.TransportSupport]
- Getting SSLContext instance using protocol: TLS
2017-08-08T12:27:3
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
Does a non-durable subscription work?
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
Thanks, I have updated the source but still get the same error.
javax.jms.InvalidDestinationException: The messaging entity
'my-namespace:topic:test.topic~15|test1' could not be found.
TrackingId:12ecc2a3-f8f3-42a3-8bd5-ad5d9823c367_B20,
SystemTracker:my-namespace:topic:test.topic~15|test1, Timest
On 08/07/2017 09:26 AM, 4 Integration wrote:
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|t
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
18 matches
Mail list logo
