camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bwest <bwesterfi...@gmail.com>
Subject camel-netty: no response received from remote server.
Date Tue, 25 Nov 2014 15:24:48 GMT
Greetings, 

I have a need to send a request via tcp to a socket server.  I'm trying to
use the camel-netty component to do this.  So I send a request and then I
get
I get errors the following error thrown out: 

*org.apache.camel.CamelExecutionException: Exception occurred during
execution on the exchange: Exchange[Message: ☻97244♥]
        at
org.apache.camel.util.ObjectHelper.wrapCamelExecutionException(ObjectHelper.java:1380)
        at
org.apache.camel.util.ExchangeHelper.extractResultBody(ExchangeHelper.java:622)
        at
org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:471)
        at
org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:133)
        at
org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:149)
        at
org.apache.camel.impl.DefaultProducerTemplate.requestBody(DefaultProducerTemplate.java:301)
        at
com.ta.shop.integration.routes.paymentprocessing.ABSPostAuthorizationProducerTest.testDataTransmission(ABSPostAuthorizationProducerTest.java:53)
Caused by: org.apache.camel.CamelExchangeException: No response received
from remote server: xx.xx.xx.xx:xxxx. Exchange[Message: ☻97244♥]
        at
org.apache.camel.component.netty.handlers.ClientChannelHandler.channelClosed(ClientChannelHandler.java:118)
        at
org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:88)
        at
org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
        at
org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
        at
org.jboss.netty.handler.codec.oneone.OneToOneDecoder.handleUpstream(OneToOneDecoder.java:60)
        at
org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
        at
org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
        at
org.jboss.netty.handler.codec.frame.FrameDecoder.cleanup(FrameDecoder.java:493)
        at
org.jboss.netty.handler.codec.frame.FrameDecoder.channelClosed(FrameDecoder.java:371)
        at
org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:88)
        at
org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
        at
org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)
        at
org.jboss.netty.channel.Channels.fireChannelClosed(Channels.java:468)
        at
org.jboss.netty.channel.socket.nio.AbstractNioWorker.close(AbstractNioWorker.java:375)
        at
org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:93)
        at
org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108)
        at
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:318)
        at
org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)
        at
org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
        at
org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
        at
org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)*
		
		
Now just to make sure, I did a tcp trace on the and I did see the request
being sent and I do see the server responding.  So I'm not sure why this
error is being thrown.  

Here is my statement for good measure, it doesn't make it past the .to
statement before the error is thrown.  

/from("direct:sendAuthMessage")
			//.setBody(simple("${body}", String.class))
			.transform().body(String.class)
		
.to("netty:tcp://xx.xx.xx.xx:xxxx?sync=true&textline=true&autoAppendDelimiter=false&keepAlive=false").process(new
testProcessor())
			.log("${body}")
			.to("file:/tmp/output/")
			.to("mock:authorization");/

 Any ideas?  
 
 Thanks,



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

Mime
View raw message