james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joachim Draeger (JIRA)" <server-...@james.apache.org>
Subject [jira] Resolved: (JAMES-713) Socket timeout should be configurable per Service
Date Fri, 08 Dec 2006 07:27:22 GMT
     [ http://issues.apache.org/jira/browse/JAMES-713?page=all ]

Joachim Draeger resolved JAMES-713.

    Resolution: Won't Fix

There is a practical alternative solution:
create a custom connection manager for the service like done in r477890.

> Socket timeout should be configurable per Service
> -------------------------------------------------
>                 Key: JAMES-713
>                 URL: http://issues.apache.org/jira/browse/JAMES-713
>             Project: James
>          Issue Type: New Feature
>          Components: James Core, IMAPServer
>    Affects Versions: Next Major
>            Reporter: Joachim Draeger
>         Assigned To: Joachim Draeger
>         Attachments: JAMES-713.patch
> At the moment the socket timeout is defined globally for the ConnectionManager:
>    <connections>
>       <idle-timeout>300000</idle-timeout>
> This has been fine for SMTP/ POP3/ RemoteManager because they require a similar low timeout
(e.g. <5 minutes).
> IMAP RFC3501 requires a timeout of > 30 min. 
> I am not completely sure who requires this why, because there is also a connectiontimeout
enforced by a watchdog thread.
> Because I am not so familiar with SimpleConnectionManager and AbstractService/Handler
I'm going to attach a patch for review.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message