camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bwest <bwesterfi...@gmail.com>
Subject Re: camel-netty: no response received from remote server.
Date Wed, 26 Nov 2014 16:37:23 GMT
Hi Claus, 

This is the what my route currently looks like:  

from("direct:sendAuthMessage")
			.log("Logging Incoming message -->" + "${body}")
			.setBody(simple("${body}", String.class))
		
.to("netty:tcp://10.98.1.41:1100?clientPipelineFactory=#cpf&sync=true&textline=true&autoAppendDelimiter=false").delay(3000)
			.to("log:Socket response??showAll=true")     // <-- This show the body as
blank.
			//.to("file:/tmp/output/")
			.to("mock:authorization");

My Logging statement is showing the following:  
Headers: {breadcrumbId=ID-BWEST-52331-1417019441385-0-1}, BodyType: String,
Body: , Out: null: ]


I am using the textline codec.  I'm also using a custom pipeline in order to
implement a custom delimiterbasedframedecoder, not sure if that would have
something to do with this.


I'm not sure why the Unit test can trap this value as a String but the route
can't seem to get at it.  I'm new with camel, so am I not doing something
correctly in the route?  
 



--
View this message in context: http://camel.465427.n5.nabble.com/camel-netty-no-response-received-from-remote-server-tp5759592p5759660.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Mime
View raw message