Hi, looks like your Stomp message is not properly formated. Why don't you skip Stomp for putting messages in the queue (and use Camel ActiveMQ component) and then just consume messages from Ruby using Stomp?
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 Sun, Aug 1, 2010 at 3:41 AM, faushouse <leef...@me.com> wrote: > > Can someone shed some light into what this code is doing. I am trying to use > Camel + ActiveMQ with HL7 MLLP messages. When the message comes in, I get > this error in the debug logs. I have tried ActiveMQ 5.3.0 and just tested > 5.4.0 snapshot. I get the same error. > > java.io.EOFException > at java.io.DataInputStream.readByte(DataInputStream.java:250) > at > org.apache.activemq.transport.stomp.StompWireFormat.readLine(StompWireFormat.java:146) > at > org.apache.activemq.transport.stomp.StompWireFormat.parseAction(StompWireFormat.java:162) > > I have a logger statement in my code to see the actual message body makes it > from MLLP, but when trying to put the message on the queue the error is > thrown. Then on the Ruby side, the message.body length is 0 using the Stomp > Gem. Any help is greatly appreciated. > > Lee > -- > View this message in context: > http://old.nabble.com/ActiveMQ-Stomp-Client-Error-tp29316053p29316053.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >
