[Mono-dev] Using Mono.Security with .Net 1.1

[Sebastien Pouliot]

Hello Florin,

On Fri, 2009-08-07 at 17:37 +0300, Florin Daneliuc wrote: 
> Hello,
>  
> I'm working on a older project which uses Mono.Security with .Net 1.1
> for the SSL capabilities. The project is using an older version of the
> library from around 2004-2006. 

That's a wide range. A lot of work was done on this code during those
years (but it's been mostly stable since then).

> Recently while creating some test we seen that starting from a test a
> number of TLS connections (100-500) caused some of them (2-10
> connections) to get stuck in blocked state with no errors raise (the
> cause was creating connection at intervals less then 20s). 
>  
> Taking the latest sources this problem was fixed, but another one
> arouse, a System.ExecutionEngineException happens when trying to
> simulate some data transfer. The stack trace of the exception is
>  System.Runtime.Remoting.Messaging.StackBuilderSink. The exact stack
> trace is
>   mscorlib.dll!
> System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage msg, System.Runtime.Remoting.Messaging.IMessageSink replySink) + 0x1a6 bytes 
>   mscorlib.dll!
> System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.ThreadPoolCallBack(System.Object o) + 0x3f bytes 

Is that under Windows ? 

If so is it running under Mono or MS.NET ?

> The scenario is: TestService1 connects through ServiceA to
> TestService2. The exact scope is to test the ServiceA under load.
> When I start TestService1 this sends data to TestService2 (through the
> ServiceA proxy) which will send back some response data. After sending
> some packages (1 to 30 packages) from TestService1 I get this
> exception on the second service but only when I use the new
> Mono.Security version, using the older version It works just fine.
> If I compile the whole stuff using .Net 2.0 everything seems to work
> just fine. Is there a known issues compiling the Mono.Security library
> under .Net 1.1?

No there is no, known 1.1 specific bug wrt Mono.Security.dll SSL/TLS.

Sebastien