Re: [jira] Created: (JAMES-713) Socket timeout should be configurable per Service

[Joachim Draeger <jd...@joachim-draeger.de>]

Hi Stefano,

Am Dienstag, den 21.11.2006, 17:13 +0100 schrieb Stefano Bagnara:

> I would say let's create a specific connection manager for each single 
> service instead of using a shared connection manager, but we would loose 
> the "overall connection-limit per IP".

What about introducing a global "overall connection-limit per IP" broker
service? :-) In a spring environment I wouldn't hesitate a second to
introduce it... Phoenix feels often a bit cumbersome. 

> In the end I, currently, have a preference for the 1 connection manager 
> per service solution: this would clobber our config.xml with many 
> blocks, but it seems to me the most simple/most flexible thing.

After thinking a bit it seems to be a good solution. 
The config.xml won't grow significantly, the only drawback would be that
the connection stuff would be outside the service conf.
>>From the container view it makes absolutely sense:
The connection-manager gets configured separately and connected to the
service.
With Spring such things just feel a bit more elegant... <sigh />


:-)

Joachim




> 

> 
> Stefano
> 
> 
> >                  Key: JAMES-713
> >                  URL: http://issues.apache.org/jira/browse/JAMES-713
> >              Project: James
> >           Issue Type: New Feature
> >           Components: IMAPServer, James Core
> >     Affects Versions: Next Major
> >             Reporter: Joachim Draeger
> >          Assigned To: Joachim Draeger
> > 
> > 
> > 
> > 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.
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org


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