AMQ-3742 created.
Instead of reproducing the whole stomp test, I've just added a test case to it
and submitted the patch - I hope that's ok
Cheers,
-- David
On 27/02/2012, at 10:10 PM, tabish...@gmail.com [via ActiveMQ] wrote:
> On Sun, 2012-02-26 at 22:45 -0800, davidw wrote
. So the workaround is simple (for us): if the body is null, set
the body to be empty string.
If you consider this a bug I'd be happy to write a junit test for it.
-- David
On 25/02/2012, at 1:03 AM, tabish...@gmail.com [via ActiveMQ] wrote:
> On Thu, 2012-02-23 at 19:38 -0800, davi
OH - here's an example of what gets printed to the logs when it works
and the message that seems to break it
--
View this message in context:
http://activemq.2283324.n4.nabble.com/JMS-goes-in-sometimes-STOMP-comes-out-but-not-always-tp4416098p4416114.html
Sent from the ActiveMQ - User mailin
I'm seeing a weird issue in an AMQ installation.
basically I can see with TCP dump that a JMS message gets published to
ActiveMQ, but if that message is a particular type of message, ActiveMQ
doesn't forward that on to it's (STOMP) subscribers.
AMQ version: 5.5.1
Setup:
Glassfish v3.1.1, conne
