directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rainer Bieniek (JIRA)" <>
Subject [jira] Commented: (DIRMINA-162) datagram session management fails
Date Wed, 18 Jan 2006 09:37:23 GMT
    [ ] 

Rainer Bieniek commented on DIRMINA-162:

I think you're right on the issue with sessions being opened / closed. Main thing is that
only the higher level protocol (on top of UDP) can really determine the meaning of a
'session' in its very own context. It might be possible to design some kind of protocol filter
which implements generic session tracking on top of simple message delivery by:
- tracking received message from the remote peer and fire off a sessionOpened() event BEFORE
passing the message onto the next filter in the chain
- implement a timeout-based mechanism that tracks the data messages passing through and closes
the session if the timeout passes by (including firing the event)
But it does not seem feasible to implement this as a generic behauviour of the datagram acceptor
(as there are protocol which do not have the concept of a session at all)

But I do think that it is a bug in the implementation of the datagram acceptor if it does
not assembly the filter chains when the individual session get create. I understand that it
is currently needed ot create a session per received message but it should then assemble the
filter chain per session as one should expect from the documentation. It would then be 
necessary to document this as an user might need to take special precautions in this chain
builder implementation.

> datagram session management fails
> ---------------------------------
>          Key: DIRMINA-162
>          URL:
>      Project: Directory MINA
>         Type: Bug
>     Versions: 0.9
>     Reporter: Rainer Bieniek
>     Priority: Minor

> 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:
For more information on JIRA, see:

View raw message