> > -Original Message-
> > From: Scott, Sean
> > > -1 on mutex/wait approach.
> > >
> > > Using that we would reinvent the wheel.
> > >
> > > There is an excellent API in the APR-UTILS that will allow
> > us to do a
&g
> > From: Scott, Sean
> >
> > I have locally modified the head revision of the jk2 project
> > and would like some feedback before submitting the
> > enhancements for review.
> >
> > The change in behavior that we desired was that rather than
>
I have locally modified the head revision of the jk2 project and would like
some feedback before submitting the enhancements for review.
The change in behavior that we desired was that rather than returning an
error when the max_connections for the endpoint cache were reached, the
worker would wai
,
You start by discussing and sending patches to the list. Commit status
possibly comes later. http://jakarta.apache.org/site/getinvolved.html
Yoav Shapira
Millennium ChemInformatics
>-Original Message-
>From: Scott, Sean [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, December 03, 2
How do I go about getting commit status to that project?
Thanks
-sean
CONFIDENTIALITY NOTICE - This e-mail transmission, and any documents, files or
previous e-mail messages attached to it may contain information that is confidential
or legally privileged. If you are not the intended recipie
I am curious as to why the endpoint cache for the ajp 1.3 worker is not in
shared memory. It seems that if you want to limit the number of connections
to tomcat you would want to it across all of apache, not per process. Is
there a reason why it is implemented this way?
Example:
httpd.conf
Start
