[ http://issues.apache.org/jira/browse/DIRMINA-162?page=comments#action_12433772 ] Greg Duffy commented on DIRMINA-162: ------------------------------------
Great! I'm happy I could help. I'll leave the refactoring to you, since you have a better view of the high level stuff. I guess the Expiry thread will need to be run by the Executor now, per Peter's e-mail. If I get a chance, I'll take a closer look at DatagramAcceptor/Connector and see if there's anything else I can think of doing. > 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-v2.diff, > mina-datagram-session-management-v3.diff, > 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
