activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mjustin <michael.jus...@gmx.net>
Subject ActiveMQ 5.3.2/5.3.1 stomp+nio: client does not receive binary messages
Date Sat, 17 Jul 2010 08:20:38 GMT

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.


Mime
View raw message