I'm going to throw my 2 cents worth in here, did you, perhaps, stop
Tomcat after starting Apache? I seem to remember that every time you stop
Tomcat, you must also stop Apache, then start Tomcat and start Apache.
Randy
> -----Original Message-----
> From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 26, 2001 10:20 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Odd Tomcat 3.3m3 Problem
>
>
> >I know where to find the documentation on increasing the
> >threads, but I thought it was set to 100 by default. If that's
> >the case, I'd love to know how 1 user could exhaust 100
> >threads in a little less than 30 minutes. This machine isn't
> >live yet...I've just been doing testing on our new setup.
>
> 100 max by default but not a startup :)
>
> >Keep in mind, these entries below are from the Apache
> >machine, not Tomcat. My thought was that mod_jk was
> >caching connections to Tomcat, and when they needed
> >to be used again, the connection was gone resulting in
> >the errors below. I could only guess that the error wasn't
> >handled properly resulting in the odd results.
>
> What's you workers.properties file, could you send us a copy ?
>
> >Anyway, thanks for the recommendation. I'll switch my
> >thread settings to make sure I know what they are and
> >will see what happens. If that doesn't work, I guess I'll
> >go to ajp12. Looks like I've got to find time to dig into the
> >mod_jk code and work some of these problems out for
> >myself.
>
> in ajp12 you'll see a performance loss since Apache will loose
> time to reestablish the connection. Also did you have a firewall
> between Apache and Tomcat, something which could drop connections
> after a certain time of inactivity ?
>
>
> >Best Regards,
> >
> >Jason
> >
> >
> >On Tue, 26 Jun 2001 08:20:57 +0200, GOMEZ Henri wrote:
> >
> >>>In my mod_jk.log file, I'm getting a lot of different error
> >>>messages that must
> >>>be getting handled properly as this isn't happening as often
> >>>as there are
> >>>messages in the log. The one that looks to be of the
> >frequency of this
> >>>problem follows:
> >>>
> >>>[Mon Jun 25 12:01:05 2001] [jk_ajp13_worker.c (579)]: Error
> >>>sending request try
> >>> another pooled connection
> >>>[Mon Jun 25 12:01:08 2001] [jk_ajp13_worker.c (579)]: Error
> >>>sending request try another pooled connection
> >>
> >>You seems to be out of thread process on the java side.
> >>Try to increase the number of Ajp13 threads (in server.xml
> >but I didn't
> >>remember how :)
> >
> >
> >
>
