You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Simon R?ss (JIRA)" <ji...@apache.org> on 2006/11/13 19:54:37 UTC
[jira] Created: (DIRMINA-306) Invalid sequence of events with
VmPipe Transport
Invalid sequence of events with VmPipe Transport
------------------------------------------------
Key: DIRMINA-306
URL: http://issues.apache.org/jira/browse/DIRMINA-306
Project: Directory MINA
Issue Type: Bug
Components: Transport
Affects Versions: 1.0
Reporter: Simon R?ss
Sometimes when using VmPipe transport, event sequences get out of order. Namely, the messageReceived method is invoked before the sessionOpened. To following sequence of events highlights the problem:
- using VmPipeConnector and VmPipeAcceptor
- client connects to server
- server's IoHandler#sessionOpened method is called
- server sends a message from the sessionOpened method
- client receives that message (IoHandler#messageReceived)
- client's IoHandler#sessionOpened method is invoked
IoHandler#sessionOpened should always be invoked before the first invocation of IoHandler#messageReceived.
--
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
[jira] Commented: (DIRMINA-306) Invalid sequence of events with
VmPipe Transport
Posted by "Simon R?ss (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRMINA-306?page=comments#action_12449482 ]
Simon R?ss commented on DIRMINA-306:
------------------------------------
I've tried to reproduce the above scenario in a simple example. However, that proves to be more difficult than expected (even in my library the issue does not show up in more than 20% of all launches). I will further try to create a simple sample that has the same issue. In the meantime, here is the log output from my library (an experimental implementation of RFC 3080):
7451 [AnonymousIoService-5] INFO ch.iserver.beepj.transport.mina.MinaTransport - transport session opened
7452 [AnonymousIoService-5] INFO ch.iserver.beepj.internal.SessionImpl - [2044542|<initial>|false] connection established to anonymous(12855300)
7453 [AnonymousIoService-5] INFO ch.iserver.beepj.internal.SessionImpl - [2044542|<initial>|false] sendRPY on channel 0 to message 0
7463 [AnonymousIoService-5] INFO ch.iserver.beepj.internal.SessionImpl - [2882193|<initial>|true] received RPY: channel=0,message=0
7473 [AnonymousIoService-6] INFO ch.iserver.beepj.internal.SessionImpl - [2882193|<alive>|true] connection established to vm:8002
The last two statements are mixed up. 2044542 is the identity hash code of the server session, while 2882193 is the identity hash code of the client session.
> Invalid sequence of events with VmPipe Transport
> ------------------------------------------------
>
> Key: DIRMINA-306
> URL: http://issues.apache.org/jira/browse/DIRMINA-306
> Project: Directory MINA
> Issue Type: Bug
> Components: Transport
> Affects Versions: 1.0
> Reporter: Simon R?ss
>
> Sometimes when using VmPipe transport, event sequences get out of order. Namely, the messageReceived method is invoked before the sessionOpened. To following sequence of events highlights the problem:
> - using VmPipeConnector and VmPipeAcceptor
> - client connects to server
> - server's IoHandler#sessionOpened method is called
> - server sends a message from the sessionOpened method
> - client receives that message (IoHandler#messageReceived)
> - client's IoHandler#sessionOpened method is invoked
> IoHandler#sessionOpened should always be invoked before the first invocation of IoHandler#messageReceived.
--
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