You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Gerard Horan <ge...@clarent.com> on 2000/10/18 02:19:45 UTC

ISAPI plugin for IIS , Servlets FAIL on dual Processor NT Machi nes

I have been debugging jk_isapi_plugin.c in the isapi_redirect.dll

Problem: When we run our servlets on a DUAL Processor NT
machine using IIS + isapi_redirect.dll + Tomcat they fail since the Filter 
does not get properly redirected.

I have tracked it down to an Assumption in the code that the thread that
executes the HttpExtensionProc and the HttpFilterProc are different. On
single processor machines  IT IS ALWAYS the same thread. TLS (Thread Local
Storage) is
used to pass data from HttpFilterProc to  HttpExtensionProc. Since we cannot
depend
on the same thread being run, TLS is not a valid means to store/pass data.

Does this make sense? Have I made a configuration error?

Any pointers appreciated

regards

ger

See Log below

jk_isapi_plugin.c (396)]: In HttpFilterProc
/ClarentAssist/servlet/ca?_verb=DoEdit&_tablename=subscriber should redirect
to ajp12
[jk_isapi_plugin.c (407)]: In HttpFilterProc  THREADID::381 , TLSINDEX 9
URI::/ClarentAssist/servlet/ca?_verb=DoEdit&_tablename=subscriber,
Worker::ajp12 should redirect
[jk_isapi_plugin.c (411)]: <<<<<<<<<<<<<<<<<<<<<<<<<<<<<In HttpFilterProc
TLSINDEX 9 
[jk_isapi_plugin.c (416)]: In HttpFilterProc  Setting URI and WORKER
[jk_isapi_plugin.c (713)]: >>>>>>>>>>>>>>>>>>>>>>>>In init_ws_service
tls_index 9 <<<<<<<<<< 
[jk_isapi_plugin.c (719)]: In init_ws_service THREAD ID is  245
[jk_isapi_plugin.c (742)]: In init_ws_service tlsIndex 9 
[jk_isapi_plugin.c (763)]: In init_ws_service
URI=/ClarentJakarta/isapi_redirect.dll TLSINDEX 9