From 16b838e576e825a616a022b35c0b2a19a0426c47 Mon Sep 17 00:00:00 2001 From: Guus der Kinderen Date: Tue, 8 Sep 2026 14:05:30 +0200 Subject: [PATCH] Reduce log level for message processed on closed connection This generates a `warn` logged message for every end of stream. Moving it to debug level. --- .../org/jivesoftware/openfire/nio/NettyConnectionHandler.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xmppserver/src/main/java/org/jivesoftware/openfire/nio/NettyConnectionHandler.java b/xmppserver/src/main/java/org/jivesoftware/openfire/nio/NettyConnectionHandler.java index ef6ca05c69..989264162b 100644 --- a/xmppserver/src/main/java/org/jivesoftware/openfire/nio/NettyConnectionHandler.java +++ b/xmppserver/src/main/java/org/jivesoftware/openfire/nio/NettyConnectionHandler.java @@ -161,7 +161,7 @@ public void handlerRemoved(ChannelHandlerContext ctx) { public void channelRead0(ChannelHandlerContext ctx, String message) { final Connection connection = ctx.channel().attr(CONNECTION).get(); if (connection != null && connection.isClosed()) { - Log.warn("Processing message on {} whose connection is already closed. This can cascade into a null-session error downstream: {}", + Log.debug("Processing message on {} whose connection is already closed. This can cascade into a null-session error downstream: {}", ctx.channel().remoteAddress() == null ? ctx.channel().localAddress() : ctx.channel().localAddress() + "--" + ctx.channel().remoteAddress(), message); } // Get the parser to use to process stanza. For optimization there is going