mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Trustin Lee (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRMINA-162) datagram session management fails
Date Fri, 08 Sep 2006 05:56:25 GMT
    [ http://issues.apache.org/jira/browse/DIRMINA-162?page=comments#action_12433335 ] 
Trustin Lee commented on DIRMINA-162:

Oh, hehe.  I deleted my duplicate reply.  You are right.  We need sessionDestroyed(IoSession)
there, too.  Probably it's not an event handler but a recycler, we might need different names.
 Here's my suggestion:

* IoSessionRecycler
  * void put(IoSession);
  * IoSession recycle(SocketAddress localAddress, SocketAddress remoteAddress);
  * void remove(IoSession);

For now, I don't have any idea on recycling a session with transports with connections.  Do
you have any idea?

And at last but least, we need a default implementation.  We could provide the default implementation
with timeout.  A session, which is not being recycled for a certain amount of time (in seconds).
could be removed and sessionClosed() event could be fired automatically.

> datagram session management fails
> ---------------------------------
>                 Key: DIRMINA-162
>                 URL: http://issues.apache.org/jira/browse/DIRMINA-162
>             Project: Directory MINA
>          Issue Type: Bug
>    Affects Versions: 0.9
>            Reporter: Rainer Bieniek
>            Priority: Minor
>             Fix For: 1.0
>         Attachments: mina-datagram-session-management.diff
> As of mina 0.9.0 the session management does not work in various ways:
> - a new session is created per received package. The worker thread does not cache created
session but only assign the select key to the session and drops it after processing the package.
It would be better to attach the session to the RegistrationRequest and check it while processing
the received package.
> - the provided IoFilterChainBuilder does get applied to the created datagram session.
It is cached in the RegistrationRequest but not used on the session
> - The sessionClose lifecycle event is not applied on the session either. 

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


View raw message