[ http://issues.apache.org/jira/browse/JAMES-713?page=all ]
Joachim Draeger updated JAMES-713:
----------------------------------
Attachment: JAMES-713.patch
Allows do configure an individual sockettimeout for each service.
I decided to use an Integer (Object), that can be null for default, in
JamesConnectionManager because it would have doubled the connect methods again.
Maybe we should refactor JamesConnectionManager to have only one methods with
nullable objects.
Please review!
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
