Re: HL7/netty4/BodyType: io.netty.buffer.UnpooledUnsafeDirectByteBuf

2016-01-25 Thread Walzer, Thomas
This was definitely a PEBKAC problem. I was missing the decoder= part in the netty4 configuration. So the response never got decoded to something meaningful. Sorry for bothering you all and being completely blind. Claus & Willem I owe you at least one beer. Cheers, Thomas. Am 24.01.2016 um 12:

Re: HL7/netty4/BodyType: io.netty.buffer.UnpooledUnsafeDirectByteBuf

2016-01-24 Thread Claus Ibsen
The HL7 message may contains some characters that causes the logger to not log the message. (eg the pipes and other control chars it may contain). I can see the same on adding some logging to the camel-hl7 unit tests. So that may be why your "log ${body}" do not print anything. On Sun, Jan 24, 2

Re: HL7/netty4/BodyType: io.netty.buffer.UnpooledUnsafeDirectByteBuf

2016-01-24 Thread Walzer, Thomas
I am using Camel 2.15.2 & blueprint. When using to uri=„log:…“ (Log component) it shows the body-type as unpooledunsafedirectbytebuf. This statement works ok. And yes, it should contain the ack response. When using (or anything else that needs a string, like convertbodytostring, etc) I get exce

Re: HL7/netty4/BodyType: io.netty.buffer.UnpooledUnsafeDirectByteBuf

2016-01-22 Thread Claus Ibsen
On Fri, Jan 22, 2016 at 3:58 PM, Walzer, Thomas wrote: > Problem is: I have a simple example that works fine. My more elaborate > version breaks. But basically it is: > queue->transacted->convertbodytostring->setSomeHeaders->log->netty4->log > > The netty4 listening to my message gets the message

Re: HL7/netty4/BodyType: io.netty.buffer.UnpooledUnsafeDirectByteBuf

2016-01-22 Thread Walzer, Thomas
Problem is: I have a simple example that works fine. My more elaborate version breaks. But basically it is: queue->transacted->convertbodytostring->setSomeHeaders->log->netty4->log The netty4 listening to my message gets the message and returns an ack. When I try to get it as a string—>it breaks

Re: HL7/netty4/BodyType: io.netty.buffer.UnpooledUnsafeDirectByteBuf

2016-01-21 Thread Claus Ibsen
On Tue, Jan 19, 2016 at 4:54 PM, Walzer, Thomas wrote: > Hi, > > camel-2.15.2 > > I can successfully send to a HL7-Server, however I have troubles accessing > the resulting ACK. > Unfortunately it is of type UnpooledUnsafeDirectByteBuf and type conversion > to string fails: > > On delivery a

Re: HL7/netty4/BodyType: io.netty.buffer.UnpooledUnsafeDirectByteBuf

2016-01-21 Thread Willem Jiang
It looks like netty handler just releases the UnpooledUnsafeDirectByteBuf automatically. Can you show us a simple test case of it? -- Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On January 20, 2016 at

Re: HL7/netty4/BodyType: io.netty.buffer.UnpooledUnsafeDirectByteBuf

2016-01-20 Thread Walzer, Thomas
I tried . If I try that: ...invalidpayloadexception: no body available of type: java.lang.String but has value: UnpooledUnsafeDirectByteBuf(freed) of type: io.netty.buffer.UnpooledUnsafeDirectByteBuf on... I am sorry, logging does and did not really work. I had many headers that looked like the

Re: HL7/netty4/BodyType: io.netty.buffer.UnpooledUnsafeDirectByteBuf

2016-01-20 Thread Willem Jiang
Can you just turn the message into String before logging it? It looks like the UnpooledUnsafeDirectByteBuf is consumed. -- Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On January 19, 2016 at 11:54:39 PM,

HL7/netty4/BodyType: io.netty.buffer.UnpooledUnsafeDirectByteBuf

2016-01-19 Thread Walzer, Thomas
Hi, camel-2.15.2 I can successfully send to a HL7-Server, however I have troubles accessing the resulting ACK. Unfortunately it is of type UnpooledUnsafeDirectByteBuf and type conversion to string fails: On delivery attempt: 2 caught: org.apache.camel.TypeConversionException: Error during