We're working in asynchronous mode where they send all of the messages and I send the response back as each one is processed using ActveMQ for JMS queuing. It worked fine in my own testing but is failing here.
What I don't understand is the length of the message: 189616968 bytes The hex for the message in the log is for one ADT message with only 6 segments. It's pretty small so I'm not sure why or how the buffer length was reached? If the sender sends async a continous stream with each message sparated by the MLLP special characters, would the HL7MLLPCODEC cut off each one and process separately? It may not be doing that. But then again the log HEX only contains one HL7 message with starting and ending characters. -- View this message in context: http://camel.465427.n5.nabble.com/HL7-Mina-throwing-org-apache-mina-filter-codec-ProtocolDecoderException-org-apache-mina-common-Buffen-tp5726292p5726296.html Sent from the Camel - Users mailing list archive at Nabble.com.
