Hi Yuri, the error is harmless. The connection is kept alive for 15 seconds (also configurable in tntnet.conf) and when no traffic is detected, tntnet tries to shutdown the connection cleanly. But this fails. I have changed the message to a debug message instead of error in openssl already but forgot to do that in gnutls.
But after looking for the gnutls implementation I found some bugs. The gnutls part of tntnet has problems with error and timeout handling. I fixed this and uploaded a snapshot here: http://www.tntnet.org/download/tntnet-1.6.1.2.20080329-1.tar.gz Also the gnutls is far faster when it comes to parallel request. I tested with ab (apachebench) without keep alive but 10 parallel requests and this is about twice as fast than the previous version. What I did is that I split up the handshake from accept. The handshake is now done in parallel with other requests. Would you please test this. (And by the way: you can answer to the list only. I get your answer twice, when you send me and the list.) Tommi ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
