Found a solution:

The request was running over a proxy. When I avoid the use of
this proxy and connect directly to the servlet everything
works smooth.
My explanation for the error:
Due to the multi requests at once it might be that there is a
short time delay in which the renegotiation is hand over to the
server from the proxy. Simultaneously the proxy is
still sending data from the server to the client, which causes
the "unexpected record" error.

Thanks so far.
-Chris

-----Original Message-----
From: curl-users-bounces_at_cool.haxx.se
[mailto:curl-users-bounces_at_cool.haxx.se]
Sent: Mittwoch, 22. Februar 2006 20:00
To: the curl tool
Subject: Re: Endless loop when using cURL in multi command shells

On Wed, 22 Feb 2006, Fitzner, Christoph (dit) wrote:

> For stresstests I'm letting it run parallel in multi command shells and I
> get sooner or later into the following endless loop:
> * SSL read: error:140940F5:SSL routines:SSL3_READ_BYTES:unexpected record,
> errno 0
> * SSLv3, TLS alert, Server hello (2):
>
> For me it seems to be that the server is sending data to the client while
> the client requests a renegotiation, and the client fails because he gets
> unexpected data.

If so, it sounds like a bug. Any chance you can investigate and debug this
further? Is this truly the case and shouldn't we then make sure it acts
accordinly instead of causing this error?

> Is there any chance to retry, instead of getting into the endless loop?

Are you seriously asking if we want to fix bugs or if we prefer having it
act
in funny ways?

Either way: yes of course we want it to do right.

> Unfortunately the --retry <num> parameter doesn't help.

The least it should do is to return a proper error without doing the loop.
However, I don't think such a failure should be the cause of a retry as
--retry is meant to.

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html