If you read the fine print below, you'll see that I am running my server on using UNIX. Most webmasters use some form of Unix/Linux. Please don't be angry with us. We have our own troubles with trying to build mod_jk on our various platforms, so we can sympathize. However, I did find the following page which discusses installation of mod_jk.dll on Windows. It includes a link (which works) to a downloadable version of mod_jk.dll at the jakarta web site.
http://www.tek-tips.com/gfaqs.cfm/lev2/3/lev3/22/spid/65/sfid/1814 HTH, Jeff ----- Original Message ----- From: "steve Burrus" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Friday, August 02, 2002 1:44 PM Subject: Re: Apache + Tomcat sometimes pegs CPU > Hello there, I need the file--mod_jk.dll--to be able to smoothly "connect" the > Tomcat 4.0.* Server with the Apache HTTP Server!!! Does anyone out there have the > download link to access and then install this file WHICH I STILL DON'T HAVE! I am > getting sick and tired of seeing other members of the tomcat users newsgroup > referring to this file, but I still do not have access to it!!! > ********************************************************************** *************** > > Jeff Larsen wrote: > > > Thanks, I figured that I wasn't the first one to see > > this. Is my current mod_jk going to need upgrading also? > > > > Jeff > > > > ----- Original Message ----- > > From: "Tim Funk" <[EMAIL PROTECTED]> > > To: "Tomcat Users List" <[EMAIL PROTECTED]> > > Sent: Friday, August 02, 2002 12:28 PM > > Subject: Re: Apache + Tomcat sometimes pegs CPU > > > > > Upgrade to 4.0.4. Earlier (4.0.X) versions have a problems with POST > > > requests when the browser terminates before sending enough data. > > This > > > caused an infinite loop between apache and tomcat. > > > > > > Here is the simple way to reproduce, (and watch your cpu go way up): > > > ------------------------------------ > > > % telnet webserver 80 > > > POST /somepage.jsp HTTP/1.1 > > > Host: webserver:80 > > > Connection: Close > > > Content-Type: application/x-www-form-urlencoded > > > Content-Length: 200 > > > PutStuff here and kill telnet session before 200 chars > > > ------------------------------------ > > > > > > -Tim > > > > > > Jeff Larsen wrote: > > > > I forgot to mention... Even when the CPU is pegged, > > > > the site functions normally. > > > > > > > > Jeff > > > > > > > > ----- Original Message ----- > > > > From: "Jeff Larsen" <[EMAIL PROTECTED]> > > > > To: "tomcat-user" <[EMAIL PROTECTED]> > > > > Sent: Friday, August 02, 2002 12:02 PM > > > > Subject: Apache + Tomcat sometimes pegs CPU > > > > > > > > > > > > > > > >>I'm running Apache 1.3.23/Tomcat 4.0.3 (jdk1.3.1) > > > >>on Solaris 7 connected with mod_jk. Sometimes I > > > >>I find that the CPU on the web server box is pegged > > > >>at 100%. It's a dedicated server and I am bouncing > > > >>Apache and Tomcat once a week to help alleviate the > > > >>problem. If I didn't restart every week, it would just > > > >>be a matter of time before things spiraled out of > > > >>control again. > > > >> > > > >>The processes that are responsible are java (Tomcat) > > > >>and libhttpd.ep (Apache, with --enable-rule=SHARED_CORE) > > > >>each with about 50% of the CPU. > > > >> > > > >>If I bounce Tomcat, no change. If I bounce Apache, > > > >>it returns to normal (low) CPU usage. I have Apache > > > >>running on other machines without Tomcat and this > > > >>does not happen. > > > >> > > > >>So it's got to be a mod_jk thing. There are no log > > > >>messages of any significance. Any ideas on how to > > > >>fix it? > > > >> > > > >>Thanks, > > > >> > > > >>Jeff > > > >> > > > >> > > > >> > > > >>-- > > > >>To unsubscribe, e-mail: > > > > > > > > <mailto:[EMAIL PROTECTED]> > > > > > > > >>For additional commands, e-mail: > > > > > > > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > > > > > -- > > > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > > > > > > > > > > > > > -- > > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > > > -- > > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
