Hi, I don't see the same behavior. Can you take a look at
StompTest.testSubscribeWithAutoAckAndBytesMessage() test and create a similar one that exposes a problem you see? http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/transport/stomp/StompTest.java?view=co Cheers -- Dejan Bosanac Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Wed, Jun 10, 2009 at 6:38 PM, Aleksandar Ivanisevic < aleksan...@ivanisevic.de> wrote: > > > I googled a lot and found a lot of discussions over this but its still > not clear to me ;) > > If a producer sends a binary message via STOMP (with content-length > header), should the consumer of that message also get a binary message > or not? > > Right now (AMQ 5.2.0) it seems that all messages sent by AMQ come out > as text messages, i.e. without content-length header, no matter how > they are sent. > > Is there a way to force a binary message somehow? > > >
