activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Bish <tabish...@gmail.com>
Subject Re: ActiveMQ 5.13.0 - Bug in Composite Destination using Stomp ?
Date Wed, 13 Apr 2016 22:56:33 GMT
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/


Mime
View raw message