This is an automated email from the ASF dual-hosted git repository.
btellier pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/james-project.git
The following commit(s) were added to refs/heads/master by this push:
new 56f6136 JAMES-2625 Remove stacktrace upon ClosedChannelException
56f6136 is described below
commit 56f6136d857c8ec6dbdfcfcc054269f0961856fe
Author: Benoit Tellier <[email protected]>
AuthorDate: Fri Aug 13 11:53:22 2021 +0700
JAMES-2625 Remove stacktrace upon ClosedChannelException
This stacktrace is especially annoying when behind a load balancer
doing port checks: connecting and disconnecting straight away, then the
banner can not be sent to the client.
These checks were encountered with for instance F5 Big Ip load
balancers.
---
.../org/apache/james/protocols/netty/BasicChannelUpstreamHandler.java | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/protocols/netty/src/main/java/org/apache/james/protocols/netty/BasicChannelUpstreamHandler.java
b/protocols/netty/src/main/java/org/apache/james/protocols/netty/BasicChannelUpstreamHandler.java
index 9732306..1c8af40 100644
---
a/protocols/netty/src/main/java/org/apache/james/protocols/netty/BasicChannelUpstreamHandler.java
+++
b/protocols/netty/src/main/java/org/apache/james/protocols/netty/BasicChannelUpstreamHandler.java
@@ -242,7 +242,7 @@ public class BasicChannelUpstreamHandler extends
SimpleChannelUpstreamHandler {
transport.writeResponse(Response.DISCONNECT, session);
}
if (e.getCause() instanceof ClosedChannelException) {
- LOGGER.info("Unable to process request", e.getCause());
+ LOGGER.info("Channel closed before we could send in flight
messages to the users (ClosedChannelException): {}", e.getCause().getMessage());
} else {
LOGGER.error("Unable to process request", e.getCause());
}
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
