I have modified the code following your instructions, but I get exactly the
same behavior (socket already in use) :
...
SocketAcceptorConfig acceptorCfg = new SocketAcceptorConfig();
acceptorCfg.setDisconnectOnUnbind( false );
acceptorCfg.setReuseAddress( false );
acceptorCfg.setFilterChainBuilder( chainBuilder );
acceptorCfg.setThreadModel( threadModel );
((SocketSessionConfig)(acceptorCfg.getSessionConfig())).setTcpNoDelay(
true );
((SocketSessionConfig)(acceptorCfg.getSessionConfig())).setReuseAddress
true );
...
There must be something wrong elsewhere.
Emmanuel
On 5/16/07, Trustin Lee <[EMAIL PROTECTED]> wrote:
On 5/16/07, Alex Karasulu <[EMAIL PROTECTED]> wrote:
> I'm beginning to suspect that there may be an issue with MINA here. It
> might be
> interesting to setup a test server with MINA using the
> acceptorCfg.setReuseAddress( true );
> feature then checking to see if this problem occurs. If not another
service
> which may not
> be properly configured via MINA may be causing this trace.
acceptorCfg.setReuseAddress() should be set to 'false'.
Instead, acceptorCfg.getSessionConfig().setReuseAddress(true) should be
called.
It was a long standing issue, and I thought it's fixed. Let me fix
the problem again in the next release.
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP Key ID: 0x0255ECA6
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
