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.
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 fr
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 arc
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.
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 stompc
