[
https://issues.apache.org/jira/browse/DIRMINA-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRMINA-835.
---------------------------------------
Resolution: Incomplete
Fix Version/s: 2.0.5
I must admit I read this message many times, and I still have no clue about
what could be the issue. I therefore close the issue, until the user provide
some clear informations about how to reproduce the problem/
> IoHandler's sessionCreated and sessionOpened method can receive notifications
> when MINA's internal socket connection built
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DIRMINA-835
> URL: https://issues.apache.org/jira/browse/DIRMINA-835
> Project: MINA
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0.2
> Environment: win xp sp3,jre6
> Reporter: censhao
> Fix For: 2.0.5, 2.0.2
>
> Original Estimate: 504h
> Remaining Estimate: 504h
>
> when I start NioSocketAcceptor,my codec sometimes receive strange data which
> not cames from my client.
> At first, I really appreciate the open source MINA framework and MIMA
> development team. The reason why I send this email is that I want to submit a
> bug. After binding website, NioSocketAcceptor will open multiple sockets that
> connect each other. Does there exist a IoSession connected with a socket? If
> there did, can I receive notification with the method of IoHandler
> sessionCreated and IoHandler sessionOpened? So how to distinguish IoSession
> belonging to external or internal?
> Shown by pseudo-code:
> if ( exists a IoSession connected with socket ? ){
> if (the method of IoHandler sessionCreated and IoHandler sessionOpened can
> receive notification ? ){
> How to distinguish IoSession belonging to external or internal?
> } else {
> So good
> }
> } else {
> ....
> }
> My question is:
> My program appears a weird problem, sometimes, the codec can receive the
> internal data in the socket.
> I suppose if I am able to distinguish IoSession belonging to external or
> internal (from client connetion), I can control the codec's work (ignoring
> the internal IoSession data), and so this problem is solved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
