directory-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-54) ProtocalSession begins reading(decoding) before the session has been opened
Date Wed, 08 Jun 2005 00:22:40 GMT
    [ http://issues.apache.org/jira/browse/DIRMINA-54?page=comments#action_12312970 ] 

Trustin Lee commented on DIRMINA-54:
------------------------------------

sessionOpened is not called if you're using stateless transport types like Datagram.  SessionCreated
is always called.  The difference between sessionCreated and sessionOpened is that sessionCreated
is not filtered by filter chains so that it is always called in the same thread with which
the selector thread runs in. 

Could you please close this issue if it is resolved? :)

Thanks,
Trustin

> ProtocalSession begins reading(decoding) before the session has been opened
> ---------------------------------------------------------------------------
>
>          Key: DIRMINA-54
>          URL: http://issues.apache.org/jira/browse/DIRMINA-54
>      Project: Directory MINA
>         Type: Bug
>     Versions: 0.7.1
>  Environment: windows xp using TCP/IP
>     Reporter: Daniel Fellars
>     Assignee: Trustin Lee
>      Fix For: 0.7.2

>
> With a local connection, I have seen it over the network but not as often, MINA regularly
will call the Decoder.decode(..) method before it calls ProtocolHandler.sessionOpened
> Inside the decode, I use the protocolSession attachment, which is set in the ProtocolHandler.sessionOpened
> so on these occassions, i am unable to read properly because my attachment object is
not available.
> I have an ugly hack for my needs that requires synchronizing on the protocolsession in
both methods, but would think that MINA should properly manage the lifecycle to gaurantee
that sessionOpened is always called before any read/writes on the protocolsession.

-- 
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


Mime
View raw message