[ http://issues.apache.org/jira/browse/DIRMINA-273?page=all ]
Trustin Lee resolved DIRMINA-273.
---------------------------------
Fix Version/s: 1.0.1
Resolution: Fixed
Assignee: Trustin Lee
Fixed along with DIRMINA-284.
One note: The test was using the port number 50000, and that port number was
being used by O/S to assign the local port. It was rare, but sometimes the O/S
generated a strange session whose local address and remote address are same. I
changed the test port number to 2048, and the problem went away.
> Session created with non-existent service
> -----------------------------------------
>
> Key: DIRMINA-273
> URL: http://issues.apache.org/jira/browse/DIRMINA-273
> Project: Directory MINA
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0, 0.9.5, 0.9.4
> Environment: Windows 2000 SP4, Java 1.5.0_08
> Reporter: Raman Gupta
> Assigned To: Trustin Lee
> Fix For: 1.0.1
>
> Attachments: MinaConnectTest.java, MinaConnectTest10.java
>
>
> On Windows 2000, when attempting to connect to a service on a port where no
> service is running (either locally or remotely), Mina will sometimes create
> and open a session instead of throwing an IoException. This session is of
> course unusable, and when attempting to use it an exception is thrown (the
> following exception from Mina 0.9.4):
> java.nio.channels.NotYetConnectedException
> at
> sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:129)
> at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:294)
> at
> org.apache.mina.transport.socket.nio.SocketIoProcessor.doFlush(SocketIoProcessor.java:480)
> at
> org.apache.mina.transport.socket.nio.SocketIoProcessor.doFlush(SocketIoProcessor.java:412)
> at
> org.apache.mina.transport.socket.nio.SocketIoProcessor.access$500(SocketIoProcessor.java:41)
> at
> org.apache.mina.transport.socket.nio.SocketIoProcessor$Worker.run(SocketIoProcessor.java:568)
> This is reproducible within a few seconds with the attached test case on
> Windows 2000 on Mina 0.9.4 and Mina 1.0.0. I also attempted to reproduce
> this on Linux 2.6.17 but was unable to.
> I have attached two test cases, one MinaConnectTest and one
> MinaConnectTest10, the former is for 0.9.4 and the latter is for 1.0.0 -- the
> only change is the exception caught.
> Though the attached test case fails uses only localhost (to avoid DNS
> complications), the test case also fails if a remote host is used. I tested
> with a remote host running Solaris 8 from a Windows client.
> Lastly, netcat in a tight loop was used concurrently with the test to verify
> that the port was indeed refusing connections.
--
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
