|
|
Forums -> Security Library Forum
| hang on datasend or datareceive |
|
|
by Thomas
posted on 2003/11/05 |
|
Hi!
I've implemented a client/server application using the mentalis.org secure-sockets.
If I'm setting the secure-protocol to Ssl.SecureProtocol.None, everything is working fine.
But when I switch it to use ssl3 or tls1 and I deploy a certificate, some strange things occure.
After establishing the connection (this works fine), I can transfer a few commands, but suddenly, the connection hangs. It seems, like the server can transfer to the client, but not vice versa. When I invoke the securesocket.send method im my client application, the onDataReceive callback-method of my server doesn't fire an event.
I got the same (or better, a similar) behaviour earlier when using no secure protocol. The reason was, that my commands are very short (e.g. ATQ or LNQ = mostly only a few letters). Since TCP seems to buffer some bytes before sending then, I set some socket options (NoDelay, Expedited, BsdUrgent) and solved the problem. Perhaps, this is a hint in finding the other problem?
Hoping, to get some feedback, since I don't have any further ideas .... |
by Pieter Philippaerts [Pieter at mentalis dot org]
posted on 2003/11/05 |
|
Can you tell me what version of the library you're using? Are you using the latest version [v1.0.13.692]? |
by Thomas
posted on 2003/11/06 |
|
Hi Pieter.
Yes, I guess, I'm using the latest version.
Viewing the properties of the org.mentalis.security reference in my project explorer, the version is 1.0.13.692. But there is another version number: runtimeversion=1.0.3705. What is this meaning?
As I experienced these problems, I took a look at your website and found out, that there is an update, addressing connection-hang problems. So I changed the reference in both, client and server application to use this latest version, but unforunately, the problem still occured (and is occuring).
cu
Thomas |
by Scott [tze_ma at hotmail dot com]
posted on 2003/11/25 |
|
I'm having the same issue as well. Anyone has any suggestions? It got hang on SecureSocket.Receive (internally, it is on the line "ret.AsyncResult.AsyncWaitHandle.WaitOne()" inside SocketController.cs.
|
by Scott
posted on 2003/11/25 |
|
Btw, I'm using the latest code 1.0.13.692. |
by Bryan [bstenfors at stenco dot net]
posted on 2003/11/25 |
|
Having the same issues. Is there a fix or update available for this issue? |
|
|
