[ 
https://issues.apache.org/jira/browse/JAMES-4206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18081163#comment-18081163
 ] 

Benoit Tellier commented on JAMES-4206:
---------------------------------------

IMO let silent the SessionTerminatedException and let's keep solely

{code:java}
2026-05-15T10:03:56.166Z [INFO ] o.a.j.m.n.ManageSieveChannelUpstreamHandler - 
Connection closed for X.X.X.X 
{code}

We have had similar fixes for IMAP & SMTP in the past

> Log cluttered by ManageSieve errors
> -----------------------------------
>
>                 Key: JAMES-4206
>                 URL: https://issues.apache.org/jira/browse/JAMES-4206
>             Project: James Server
>          Issue Type: Bug
>            Reporter: Felix
>            Priority: Minor
>
> Every proper logout of the ManageSieve server writes a log message of 
> severity `WARN`
> Here is an excerpt from the log for one regular ManageSieve session:
>  
>  
> {code:java}
> 2026-05-15T10:03:55.778Z [INFO ] o.a.j.m.n.ManageSieveChannelUpstreamHandler 
> - Connection established from X.X.X.X
> 2026-05-15T10:03:55.790Z [INFO ] o.a.j.m.n.ManageSieveChannelUpstreamHandler 
> - Connection from Y.Y.Y.Y runs through Z.Z.Z.Z proxy
> 2026-05-15T10:03:56.153Z [WARN ] o.a.j.m.n.ManageSieveChannelUpstreamHandler 
> - Error while processing ManageSieve request
> org.apache.james.managesieve.api.SessionTerminatedException: null
>     at 
> org.apache.james.managesieve.core.CoreProcessor.logout(CoreProcessor.java:283)
>     at 
> org.apache.james.managesieve.transcode.ArgumentParser.logout(ArgumentParser.java:76)
>     at 
> org.apache.james.managesieve.transcode.ManageSieveProcessor.matchCommandWithImplementation(ManageSieveProcessor.java:137)
>     at 
> org.apache.james.managesieve.transcode.ManageSieveProcessor.handleRequest(ManageSieveProcessor.java:71)
>     at 
> org.apache.james.managesieveserver.netty.ManageSieveChannelUpstreamHandler.channelRead(ManageSieveChannelUpstreamHandler.java:87)
>     at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)
>     at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
>     at 
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
>     at 
> io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:107)
>     at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)
>     at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
>     at 
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
>     at 
> io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:346)
>     at 
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:318)
>     at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)
>     at 
> io.netty.channel.AbstractChannelHandlerContext.access$600(AbstractChannelHandlerContext.java:61)
>     at 
> io.netty.channel.AbstractChannelHandlerContext$7.run(AbstractChannelHandlerContext.java:425)
>     at 
> io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:173)
>     at 
> io.netty.util.concurrent.DefaultEventExecutor.run(DefaultEventExecutor.java:66)
>     at 
> io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:998)
>     at 
> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
>     at java.base/java.lang.Thread.run(Unknown Source)
> 2026-05-15T10:03:56.166Z [INFO ] o.a.j.m.n.ManageSieveChannelUpstreamHandler 
> - Connection closed for X.X.X.X {code}
>  
> I am currently working on a fix that catches this Exception to produce a 
> single INFO line in the log.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to