Trustin Lee wrote: > > On 5/9/07, seven <[EMAIL PROTECTED]> wrote: >> >> Hello, >> >> I have a problem with mina-filter-ssl-1.1.0 release: sometimes for >> unknown >> reasons and in an arbitrary way, after a client connects to a SSL enabled >> server, it does not send anything. On the server side and the client side >> as >> well, only CREATED and OPENED events are fired and nothing further >> happens ( >> except IDDLE events ) even if the client issued the first >> session.write(). >> >> In order to reproduce this, I wrote a simple client that connects to the >> echo server found in the examples. >> org.apache.mina.example.echoserver.Main should be modified with >> USE_SSL=true, PORT = 8090 and bogus.cert has to be generated as >> documented >> in org.apache.mina.example.echoserver.ssl.BogusSSLContextFactory and >> placed >> in the classpath of the server and server launchers. >> >> Until mina-1.1.0 was released I worked with a snapshot release and did >> not >> encounter this problem. So if one uses a >> mina-filter-ssl-1.1.0-SNAPSHOT.jar >> instead of mina-filter-ssl-1.1.0.jar the 'silence' problem does not >> occur. >> Fortunately I have the snapshot sources from the svn that were used to >> build >> mina-filter-ssl-1.1.0-SNAPSHOT.jar. >> The revision number for the working SSLHandler is 471502 respectively >> 507461 >> for SSLFilter. >> >> Attached is the client source that reproduces the problem. It has to be >> placed in org.apache.mina.example.echoserver package. >> >> Regards, >> Horia >> http://www.nabble.com/file/8269/Client.java Client.java > > I made a big change in SSLFilter and SSLHandler to fix a deadlock > issue when releasing 1.1.0. But I couldn't reproduce your problem > with the source code you provided. How often can it be reproduced? > > Please attach the full thread dump and the log file with DEBUG level > enabled for MINA. > > Trustin > -- > what we call human nature is actually human habit > -- > http://gleamynode.net/ > -- > PGP Key ID: 0x0255ECA6 > >
The problem can be reproduced always. I reproduced this situation with JDK1.5.0 as well even if with JDK1.5.0 takes much longer to happen: let it run for 5 minutes or more. With JDK1.6.0 it happens in few seconds. Below I attached 4 files: 2 for the server and client with jdk1.5.0_05 and the other 2 for server and client with jdk1.6.0_01. I've hit Ctlr+Break when I saw that the client did't send any data. In the JDK1.6.0 related files you can see how the client and server were started. http://www.nabble.com/file/8419/jdk1.5.0_5.client.txt jdk1.5.0_5.client.txt http://www.nabble.com/file/8420/jdk1.5.0_5.server.txt jdk1.5.0_5.server.txt http://www.nabble.com/file/8421/jdk1.6.0_01.client.txt jdk1.6.0_01.client.txt http://www.nabble.com/file/8422/jdk1.6.0_01.server.txt jdk1.6.0_01.server.txt DEBUG ) level is wanted, could you please tell me how can I enable DEBUG level for the Simple wrapper of SLF4J? Regards, Horia -- View this message in context: http://www.nabble.com/SSL-Client-does-not-send-any-data-tf3714505.html#a10617860 Sent from the mina dev mailing list archive at Nabble.com.
