[ http://issues.apache.org/jira/browse/DIRMINA-273?page=comments#action_12444186 ] Raman Gupta commented on DIRMINA-273: -------------------------------------
I also tried and failed to reproduce this on Linux. In addition, I tried and failed to reproduce this on Solaris 8. I did however, reproduce this with Windows 2000 client and server, and Windows 2000 client / Solaris 8 server. I haven't tried Windows XP. I captured the packets on the wire for my Windows 2000 / Solaris 8 test. I don't see any difference between the failure case and the success case. xxx.xxx.46.131 is the Windows 2000 client. xxx.yyy.250.203 is the Solaris 8 server. Here is the success case: 17.867041 xxx.xxx.46.131 -> xxx.yyy.250.203 TCP 3066 > 2048 [SYN] Seq=0 Len=0 MSS=1460 17.891806 xxx.yyy.250.203 -> xxx.xxx.46.131 TCP 2048 > 3066 [RST, ACK] Seq=0 Ack=1 Win=0 Len=0 18.346760 xxx.xxx.46.131 -> xxx.yyy.250.203 TCP 3066 > 2048 [SYN] Seq=0 Len=0 MSS=1460 18.371193 xxx.yyy.250.203 -> xxx.xxx.46.131 TCP 2048 > 3066 [RST, ACK] Seq=0 Ack=1 Win=0 Len=0 18.848381 xxx.xxx.46.131 -> xxx.yyy.250.203 TCP 3066 > 2048 [SYN] Seq=0 Len=0 MSS=1460 18.872702 xxx.yyy.250.203 -> xxx.xxx.46.131 TCP 2048 > 3066 [RST, ACK] Seq=0 Ack=1 Win=0 Len=0 Here is the failure case: 21.433021 xxx.xxx.46.131 -> xxx.yyy.250.203 TCP 3069 > 2048 [SYN] Seq=0 Len=0 MSS=1460 21.457739 xxx.yyy.250.203 -> xxx.xxx.46.131 TCP 2048 > 3069 [RST, ACK] Seq=0 Ack=1 Win=0 Len=0 21.958292 xxx.xxx.46.131 -> xxx.yyy.250.203 TCP 3069 > 2048 [SYN] Seq=0 Len=0 MSS=1460 21.982454 xxx.yyy.250.203 -> xxx.xxx.46.131 TCP 2048 > 3069 [RST, ACK] Seq=0 Ack=1 Win=0 Len=0 22.459891 xxx.xxx.46.131 -> xxx.yyy.250.203 TCP 3069 > 2048 [SYN] Seq=0 Len=0 MSS=1460 22.484242 xxx.yyy.250.203 -> xxx.xxx.46.131 TCP 2048 > 3069 [RST, ACK] Seq=0 Ack=1 Win=0 Len=0 Seems to be no different. Perhaps the TCP/IP stack in Windows 2000 has a bug and is reporting something strange to java. Or perhaps the JVM on Windows has a bug and is reporting something strange to Mina. I am starting to suspect its not a problem with Mina though. > 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.4, 0.9.5 > 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, > MinaConnectTestNew.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
