Hi, this issue has been fixed recently in the trunk https://issues.apache.org/activemq/browse/AMQ-2822
can you test it out and confirm that it works for you? Cheers -- Dejan Bosanac - http://twitter.com/dejanb Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Sat, Jul 17, 2010 at 10:20 AM, mjustin <michael.jus...@gmx.net> wrote: > > Hello, > > For my unit tests I use the xbean:activemq-demo.xml configuration provided > in the conf folder. > > On the Stomp default port 61613, in this configuration Apache ActiveMQ 5.3.2 > starts with stomp+nio: > > <transportConnector name="stomp+nio" > uri="stomp+nio://0.0.0.0:61613?transport.closeAsync=false"/> > > and all unit tests fail which try to receive a Stomp binary message (the > client can send but not receive the message) > > If I change it to stomp instead of stomp+nio > > <transportConnector name="stomp" > uri="stomp://0.0.0.0:61613?transport.closeAsync=false"/> > > it works again. > > The same problem exists in 5.3.1. Version 5.3.0 did not show the same > effect. > > Should I report this in the issue tracker? > > Regards > > > > ----- > Michael Justin > SCJP, SCJA > betasoft - Software for Delphi™ and for the Java™ platform > http://www.mikejustin.com - http://www.betabeans.de > -- > View this message in context: > http://old.nabble.com/ActiveMQ-5.3.2-5.3.1-stomp%2Bnio%3A-client-does-not-receive-binary-messages-tp29190243p29190243.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >
