[ 
http://issues.apache.org/jira/browse/DIRMINA-162?page=comments#action_12436125 
] 
            
Greg Duffy commented on DIRMINA-162:
------------------------------------

Sorry about that! I tried my best to resist the format keystroke in Eclipse, 
but I must have slipped up. I know how annoying that can be.

I did run the unit tests successfully before my v7, but not before the v6. My 
mistake. Was the bug due to upgrading the lock incorrectly as I fixed in v7, or 
was it another one?

Good ideas on the modifications. I hope I at least saved you a little time in 
getting this implemented.

> 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
>         Assigned To: Trustin Lee
>            Priority: Minor
>             Fix For: 1.0
>
>         Attachments: mina-datagram-session-management-v2.diff, 
> mina-datagram-session-management-v3.diff, 
> mina-datagram-session-management-v4.diff, 
> mina-datagram-session-management-v5.diff, 
> mina-datagram-session-management-v6.diff, 
> mina-datagram-session-management-v7.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

        

Reply via email to