netty timeout exception
-----------------------
Key: CAMEL-3081
URL: https://issues.apache.org/activemq/browse/CAMEL-3081
Project: Apache Camel
Issue Type: Bug
Components: camel-netty
Affects Versions: 2.4.0
Environment: tomcat
Reporter: Anand
Priority: Critical
eventhough message was received by netty procuder, it thows a timeout exception
after 30 secs. here is the route and log. as this is a basic functionality I
think this is critical priority.
from("netty:tcp://localhost:6205?textline=true&sync=true").process(new
Processor() {
int i=0;
public void process(Exchange exchange) throws Exception
{
String body = exchange.getIn().getBody(String.class);
Thread.sleep(5000);
exchange.getOut().setBody("Bye 1" + body);
// if(i++%2==1) throw new IOException("custom
exception");
}
});
from("file:///test/test/response")
.convertBodyTo(String.class)
.threads(1)
.to(ExchangePattern.InOut,"netty:tcp://localhost:6205?textline=true&sync=true")
.to("log:+++ reply++++");
2010-08-25 11:33:29,963 [1 - file:///test/test/response] FileConsumer
DEBUG Total 1 files to consume
2010-08-25 11:33:29,963 [1 - file:///test/test/response] FileConsumer
DEBUG About to process file:
GenericFile[C:\test\test\response\hello1.txt] using exchange:
Exchange[GenericFileMessage with file:
GenericFile[C:\test\test\response\hello1.txt]]
2010-08-25 11:33:31,510 [ Camel Thread 6 - Threads] SendProcessor
DEBUG >>>> Endpoint[tcp://localhost:6205] Exchange[GenericFileMessage
with body: hello1]
2010-08-25 11:33:31,682 [ Camel Thread 6 - Threads] NettyProducer
DEBUG Creating connector to address: localhost:6205
2010-08-25 11:33:31,682 [ Camel Thread 6 - Threads] NettyProducer
DEBUG Writing body: hello1
2010-08-25 11:33:31,697 [ New I/O client worker #1-1] NettyProducer
DEBUG Operation complete
org.jboss.netty.channel.defaultchannelfut...@944dbd
2010-08-25 11:33:31,697 [ New I/O server worker #1-1] ServerChannelHandler
DEBUG Incoming message: hello1
2010-08-25 11:33:36,697 [ New I/O server worker #1-1] ServerChannelHandler
DEBUG Writing body: Bye 1hello1
2010-08-25 11:33:36,697 [ New I/O client worker #1-1] ClientChannelHandler
DEBUG Message received: Bye 1hello1
2010-08-25 11:33:36,697 [ New I/O client worker #1-1] SendProcessor
DEBUG >>>> Endpoint[log://+++ reply++++] Exchange[GenericFileMessage
with body: Bye 1hello1]
2010-08-25 11:33:36,713 [ New I/O client worker #1-1] +++ reply++++
INFO Exchange[ExchangePattern:InOut, BodyType:String, Body:Bye 1hello1]
2010-08-25 11:33:36,713 [ New I/O client worker #1-1]
GenericFileOnCompletion DEBUG Done processing file:
GenericFile[C:\test\test\response\hello1.txt] using exchange:
Exchange[GenericFileMessage with body: Bye 1hello1]
2010-08-25 11:33:36,713 [ New I/O client worker #1-1] FileUtil
DEBUG Tried 1 to delete file:
C:\test\test\response\hello1.txt.camelLock with result: true
2010-08-25 11:33:36,713 [ New I/O client worker #1-1]
nericFileRenameProcessStrategy DEBUG Renaming file:
GenericFile[C:\test\test\response\hello1.txt] to:
GenericFile[C:\test\test\response\.camel\hello1.txt]
2010-08-25 11:33:36,713 [ New I/O client worker #1-1] FileUtil
DEBUG Tried 1 to rename file: C:\test\test\response\hello1.txt to:
C:\test\test\response\.camel\hello1.txt with result: true
2010-08-25 11:34:06,886 [ Hashed wheel timer #1] DefaultErrorHandler
DEBUG Failed delivery for exchangeId:
f5eb372d-a214-4418-a60f-62c0557768d2. On delivery attempt: 0 caught:
org.apache.camel.ExchangeTimedOutException: The OUT message was not received
within: 30000 millis. Exchange[GenericFileMessage with body: Bye 1hello1]
2010-08-25 11:34:06,886 [ Hashed wheel timer #1] DefaultErrorHandler
ERROR Failed delivery for exchangeId:
f5eb372d-a214-4418-a60f-62c0557768d2. Exhausted after delivery attempt: 1
caught: org.apache.camel.ExchangeTimedOutException: The OUT message was not
received within: 30000 millis. Exchange[GenericFileMessage with body: Bye
1hello1]
org.apache.camel.ExchangeTimedOutException: The OUT message was not received
within: 30000 millis. Exchange[GenericFileMessage with body: Bye 1hello1]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
