You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by aanto <aa...@gmail.com> on 2016/04/13 20:55:32 UTC

ActiveMQ 5.13.0 - Bug in Composite Destination using Stomp ?

ActiveMQ: 5.13.0
Java: 1.8.0u51

Using Stomp for Sending message to a composite destination as below
generates a single queue name as 
"aanto.test1queue://aanto.test2". Ideally it should have created 2 queues -
aanto.test1 and aanto.test2.

Stomp Code.
			StompConnection stompconnection = new StompConnection();
			stompconnection.open("lcoalhost", 61613);
			stompconnection.connect("admin", "admin");
			stompconnection.begin("tx1");
			stompconnection.send("aanto.test1,aanto.test2", "message1", "tx1", null);
			stompconnection.commit("tx1");
			stompconnection.disconnect();


This same test using tcp/openwire works well, creates 2 separate queues.
Quickly tested against an older activemq install, (5.6), which seems to be
working.

Thanks



--
View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-13-0-Bug-in-Composite-Destination-using-Stomp-tp4710740.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: ActiveMQ 5.13.0 - Bug in Composite Destination using Stomp ?

Posted by aanto <aa...@gmail.com>.
This bug fix seems to be a partial fix, which was part of 5.13.3.

stompconnection.send("queue://test.aanto1.queue,topic://test.aanto2.topic",
"messsage1", "tx1", null);
=> PASS: creates QUEUE "test.aanto1.queue"
=> FAIL: creates QUEUE "topic://test.aanto2.topic", instead of creating a
TOPIC "test.aanto2.topic"

stompconnection.send("test.aanto1.queue,queue://test.aanto2.queue",
"messsage1", "tx1", null);
=> PASS: creates QUEUE "test.aanto1.queue" 
=> FAIL: creates QUEUE "queue://test.aanto2.queue", instead of creating a
QUEUE "test.aanto2.queue"

stompconnection.send("topic://test.aanto1.topic,topic://test.aanto2.topic",
"messsage1", "tx1", null);
=> PASS: creates TOPIC "test.aanto1.topic" 
=> FAIL: creates QUEUE "topic://test.aanto2.topic", instead of creating a
TOPIC "test.aanto2.topic"

Thank you
Aanto.



--
View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-13-0-Bug-in-Composite-Destination-using-Stomp-tp4710740p4712878.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: ActiveMQ 5.13.0 - Bug in Composite Destination using Stomp ?

Posted by Timothy Bish <ta...@gmail.com>.
On 04/14/2016 04:20 PM, aanto wrote:
> Hi Tim,
>
> Thank you for the quick fix. What is the timeline for 5.13.3 release ?
>
> Thank you
> Aanto.
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-13-0-Bug-in-Composite-Destination-using-Stomp-tp4710740p4710790.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
Soon, we don't really set dates though since a critical issue can appear 
at any time.

-- 
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


Re: ActiveMQ 5.13.0 - Bug in Composite Destination using Stomp ?

Posted by aanto <aa...@gmail.com>.
Hi Tim,

Thank you for the quick fix. What is the timeline for 5.13.3 release ?

Thank you
Aanto.



--
View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-13-0-Bug-in-Composite-Destination-using-Stomp-tp4710740p4710790.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: ActiveMQ 5.13.0 - Bug in Composite Destination using Stomp ?

Posted by Timothy Bish <ta...@gmail.com>.
On 04/13/2016 02:55 PM, aanto wrote:
> ActiveMQ: 5.13.0
> Java: 1.8.0u51
>
> Using Stomp for Sending message to a composite destination as below
> generates a single queue name as
> "aanto.test1queue://aanto.test2". Ideally it should have created 2 queues -
> aanto.test1 and aanto.test2.
>
> Stomp Code.
> 			StompConnection stompconnection = new StompConnection();
> 			stompconnection.open("lcoalhost", 61613);
> 			stompconnection.connect("admin", "admin");
> 			stompconnection.begin("tx1");
> 			stompconnection.send("aanto.test1,aanto.test2", "message1", "tx1", null);
> 			stompconnection.commit("tx1");
> 			stompconnection.disconnect();
>
>
> This same test using tcp/openwire works well, creates 2 separate queues.
> Quickly tested against an older activemq install, (5.6), which seems to be
> working.
>
> Thanks
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-13-0-Bug-in-Composite-Destination-using-Stomp-tp4710740.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
This is fixed now: https://issues.apache.org/jira/browse/AMQ-6246 will 
be in 5.13.3

-- 
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/