Hi,
after some testing with Apache JMS client using OpenWire protocol I solved
my problem.
With the ApacheMQ web console enabled I noticed that when was using Qpid JMS
Client with AQMP protocol I did not create Topics but Queues, even if I was
using the API for Topics. I'm not sure how this could
sks wrote
> I am testing durable topics.
>
> I'm using the JAVA to programatically create the topic and the durable
> subscriber.
> The test closes the subscriber, session and connection and then exits
>
> If i use the ActiveMQ web console, it still shows the number of consumers
> at 1.
> I would
Hi Tim,
thanks for your reply. I can definitely give a try with ActiveMQ JMS client.
However, I think that if the client lib itself was a problem, I should have
been able to read the payload after I shutdown the client process and
restart it. But, that doesn't happen. So it seems to be some "state
Hi all,
I have a Topic in ActiveMQ where I publish BytesMessage using
javax.jms.TopicPublisher implementation provided by Qpid JMS Client.
Accessing the message from a consumer A (again, a javax.jms.TopicConsumer
implementation from Qpid) the first time returns the correct data. And the
same happ