You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Jorge Alonso de Armiño Escudero <ja...@abysal.com> on 2003/03/05 17:22:07 UTC
Is JK2 via ajp13 MT-safe
Hi all,
we are developing a jk2 connector to communicate our own Web Server with Tomcat4.1.18 via ajp13, and when we connect simultaneously more than one thread against Tomcat, some of them stay blocked in jk2_channel_socket_readN().
Is jk2 via ajp13 MT-Safe?
Is there any configuration option that we must know?
Thanks in advance,
Jorge
Re: Is JK2 via ajp13 MT-safe
Posted by Henri Gomez <hg...@apache.org>.
Jorge Alonso de Armiño Escudero wrote:
> Hi all,
>
>
>
> we are developing a jk2 connector to communicate our own Web Server with Tomcat4.1.18 via ajp13, and when we connect simultaneously more than one thread against Tomcat, some of them stay blocked in jk2_channel_socket_readN().
>
>
>
> Is jk2 via ajp13 MT-Safe?
>
> Is there any configuration option that we must know?
Under which OS ?
From what I see jk2_channel_socket_readN make use of read calls
on a socket descriptor (endpoint->sd)...
Should be safe but under windows there is a :
if(SOCKET_ERROR == this_time) {
errno = WSAGetLastError() - WSABASEERR;
}
which may hurt ?
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org