On Tue, 18 Jun 2002, Mladen Turk wrote: > > We have a serious problem with jk and apache2. > Try running: > ab -n 10000 -c 100 http://localhost:8000/examples/jsp/dates/date.jsp > > I have 59 > [Tue Jun 18 18:07:14 2002] [warn] [client 127.0.0.1] handler > "jakarta-servlet" not found for: date.jsp > > Now, IMHO there is problem with map_uri_to_worker, cause it's not thread > safe, and the time spend in it causes apache to recycle the request_rec > prior the function returns. Now the problem arises only with high > concurrent load. > > The solution is possible using a mutex surrounding the call to > map_uri_worker. (I'm having a working one with the CRITICAL_SECTION), > but will translate to apr if no one objects.
Jk1.2 is not apr-based, but I think it's ok to add an HAS_APR flag, but leave the old mutex as fallback. I'm not sure I understand how request_rec gets recycled while we are in map_uri_to_worker - it is supposed to happen after the request completes. It's very weird - maybe there's another problem. Can we avoid a mutex in the critical path ? Does the same problem exists in jk2 ? Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
