[CAMEL-9527] camel-netty4 - Should not log stacktrace when client has received reply

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.16.2
• Fix Version/s: 2.15.6, 2.16.3, 2.17.0
• Component/s: camel-netty4
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Claus Ibsen
• Created: 24/Jan/16 11:14
• Updated: 15/Feb/21 14:14
• Resolved: 24/Jan/16 11:50

Description

If you do request/reply over netty4 you may get a stacktace in the logs even if a message was received and the channel was closed when the server stops etc.

[l-1) thread #33 - ShutdownTask] DefaultShutdownStrategy        INFO  Route: route1 shutdown complete, was consuming from: Endpoint[direct://start]
[                          main] DefaultShutdownStrategy        INFO  Graceful shutdown of 2 routes completed in 0 seconds
]

Message History
---------------------------------------------------------------------------------------------------------------------------------------
RouteId              ProcessorId          Processor                                                                        Elapsed (ms)
[route1            ] [route1            ] [direct://start                                                                ] [     29673]
[route1            ] [to1               ] [netty4:tcp://127.0.0.1:8888?sync=true&decoder=#hl7decoder&encoder=#hl7encoder ] [     29668]
[route1            ] [process1          ] [Processor@0x484094a5                                                          ] [     28571]
[route1            ] [to2               ] [log:foo                                                                       ] [         3]
[route1            ] [to3               ] [mock:result                                                                   ] [         0]

Exchange
---------------------------------------------------------------------------------------------------------------------------------------
Exchange[
	Id                  ID-davsclaus-air-56167-1453631664458-0-2
	ExchangePattern     InOut
	Headers             {breadcrumbId=ID-davsclaus-air-56167-1453631664458-0-1, CamelRedelivered=false, CamelRedeliveryCounter=0}
	BodyType            String
QRD|20080805120000
]

Stacktrace
---------------------------------------------------------------------------------------------------------------------------------------
org.apache.camel.CamelExchangeException: No response received from remote server: 127.0.0.1:8888. Exchange[ID-davsclaus-air-56167-1453631664458-0-2][Message: MSH|^~\&|MYSENDER||||200701011539||ADR^A19^ADR_A19|456|P|2.4
MSA|AA|123
QRD|20080805120000
]
	at org.apache.camel.component.netty4.handlers.ClientChannelHandler.channelInactive(ClientChannelHandler.java:126)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:218)
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:204)
	at io.netty.handler.codec.ByteToMessageDecoder.channelInactive(ByteToMessageDecoder.java:332)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:218)
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:204)
	at io.netty.channel.DefaultChannelPipeline.fireChannelInactive(DefaultChannelPipeline.java:828)
	at io.netty.channel.AbstractChannel$AbstractUnsafe$7.run(AbstractChannel.java:625)
	at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)
	at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
	at java.lang.Thread.run(Thread.java:745)
[                          main] DefaultCamelContext            INFO  Apache Camel 2.17-SNAPSHOT (CamelContext: camel-1) uptime 30.572 seconds

Issue Links

• causes: CAMEL-16178 Enrich with REST+netty hangs when connection is closed without response