You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Raiden <ra...@wonko.inow.com> on 2003/01/11 10:27:46 UTC
Various bugs with mod_jk and mod_jk2? And does Apache2.0.43+mod_jk2=inevitable
hanging?
Hello,
I wanted to get Apache 2.0.43 and mod_jk2 working. They seemed to setup
fine, and handle requests just great. But after a while, Apache starts
hanging on every other request. I tried mod_jk, and it still does
this. I removed all traces of both mod_jks, and it still does eventually
starts hanging, even on static image requests that are not run through
Tomcat. I'm assuming it's a problem with Apacheand my setup (Redhat
8.0). Anyone else have similar issues?
Anyhow, so I went back to Apache 1.3.27, which does not hang at all. Now,
here's where I noticed two weird things:
#1) Apache 1.3.27 with mod_jk2 - mod_rewrites that have the [P] flag to
proxy don't seem to actually get interpreted and sent over to Tomcat.
#2) Apache 1.3.27 with mod_jk - mod_rewrites DO get interpreted. But,
with Apache and Tomcat residing on two physical servers, Apache does not
send over a request for index.jsp if the URL does not exactly specify it,
even if the DirectoryIndex is set. (So, /index.jsp WILL go to Tomcat,
but / will not, and is just processed as an Apache level index view.)
I've had to actually create fake index.jsp files in a mock directory
structure on the Apache side to trick it into sending index.jsp as
default to Tomcat.
Does anyone know how to fix either of those strange behaviors? Or BETTER
yet, has anyone had the hanging problem with Apache 2.0.43 and mod_jk2,
and found a way to fix it?
Thanks,
-Raiden
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Various bugs with mod_jk and mod_jk2? And does
Apache2.0.43+mod_jk2=inevitable hanging?
Posted by Raiden <ra...@wonko.inow.com>.
In the tomcat-dev group there were a few discussions/code patches to
support a ForwardDirectories JkOption in mod_jk (which didn't work for me
when I tried, BTW) which would send a request to Tomcat for each file
listed in the DirectoryIndex (if it matched the correct URI mappings).
I was hoping there was some sort of option like that currently in use.
-Raiden
On Sun, 12 Jan 2003, Bill Barker wrote:
>
> "Raiden" <ra...@wonko.inow.com> wrote in message
> news:Pine.LNX.4.44.0301112018590.29544-100000@wonko.inow.com...
> > Just as a followup, even though all of the below still holds true, I did
> > find out my problem with Apache 2.0.43 (it was a DNS misconfiguration that
> > eventually held Apache up, even though I don't have it resolving host
> > names).
> >
> > So, Apache 2.0.43 is now running fine with mod_jk2. However, it still has
> > the problem where DirectoryIndex won't check for an index.jsp through
> > tomcat by default, which creates a problem for those of us that have
> > Apache on Tomcat running on separate machines.
>
> And how, exactly is Apache supposed to figure this out? ;-)
>
> The simplest way to work around this is to create a minimalist directory
> structure on the Apache box with dummy (e.g. zero length) index.jsp files.
> Apache can then figure out that it needs to serve 'index.jsp', and send the
> request to the Tomcat box to serve the actual page.
>
> >
> > Anyone have a workaround for this? (Besides creating empty index.jsp files
> > to trick Apache).
> >
> > Thanks,
> > -Raiden
> >
> >
> > On Sat, 11 Jan 2003, Raiden wrote:
> >
> > > Hello,
> > >
> > > I wanted to get Apache 2.0.43 and mod_jk2 working. They seemed to setup
> > > fine, and handle requests just great. But after a while, Apache starts
> > > hanging on every other request. I tried mod_jk, and it still does
> > > this. I removed all traces of both mod_jks, and it still does
> eventually
> > > starts hanging, even on static image requests that are not run through
> > > Tomcat. I'm assuming it's a problem with Apacheand my setup (Redhat
> > > 8.0). Anyone else have similar issues?
> > >
> > > Anyhow, so I went back to Apache 1.3.27, which does not hang at all.
> Now,
> > > here's where I noticed two weird things:
> > >
> > > #1) Apache 1.3.27 with mod_jk2 - mod_rewrites that have the [P] flag to
> > > proxy don't seem to actually get interpreted and sent over to Tomcat.
> > >
> > > #2) Apache 1.3.27 with mod_jk - mod_rewrites DO get interpreted. But,
> > > with Apache and Tomcat residing on two physical servers, Apache does not
> > > send over a request for index.jsp if the URL does not exactly specify
> it,
> > > even if the DirectoryIndex is set. (So, /index.jsp WILL go to Tomcat,
> > > but / will not, and is just processed as an Apache level index view.)
> > > I've had to actually create fake index.jsp files in a mock directory
> > > structure on the Apache side to trick it into sending index.jsp as
> > > default to Tomcat.
> > >
> > > Does anyone know how to fix either of those strange behaviors? Or
> BETTER
> > > yet, has anyone had the hanging problem with Apache 2.0.43 and mod_jk2,
> > > and found a way to fix it?
> > >
> > > Thanks,
> > > -Raiden
> > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> > > For additional commands, e-mail:
> <ma...@jakarta.apache.org>
> > >
>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Various bugs with mod_jk and mod_jk2? And does Apache2.0.43+mod_jk2=inevitable hanging?
Posted by Bill Barker <wb...@wilshire.com>.
"Raiden" <ra...@wonko.inow.com> wrote in message
news:Pine.LNX.4.44.0301112018590.29544-100000@wonko.inow.com...
> Just as a followup, even though all of the below still holds true, I did
> find out my problem with Apache 2.0.43 (it was a DNS misconfiguration that
> eventually held Apache up, even though I don't have it resolving host
> names).
>
> So, Apache 2.0.43 is now running fine with mod_jk2. However, it still has
> the problem where DirectoryIndex won't check for an index.jsp through
> tomcat by default, which creates a problem for those of us that have
> Apache on Tomcat running on separate machines.
And how, exactly is Apache supposed to figure this out? ;-)
The simplest way to work around this is to create a minimalist directory
structure on the Apache box with dummy (e.g. zero length) index.jsp files.
Apache can then figure out that it needs to serve 'index.jsp', and send the
request to the Tomcat box to serve the actual page.
>
> Anyone have a workaround for this? (Besides creating empty index.jsp files
> to trick Apache).
>
> Thanks,
> -Raiden
>
>
> On Sat, 11 Jan 2003, Raiden wrote:
>
> > Hello,
> >
> > I wanted to get Apache 2.0.43 and mod_jk2 working. They seemed to setup
> > fine, and handle requests just great. But after a while, Apache starts
> > hanging on every other request. I tried mod_jk, and it still does
> > this. I removed all traces of both mod_jks, and it still does
eventually
> > starts hanging, even on static image requests that are not run through
> > Tomcat. I'm assuming it's a problem with Apacheand my setup (Redhat
> > 8.0). Anyone else have similar issues?
> >
> > Anyhow, so I went back to Apache 1.3.27, which does not hang at all.
Now,
> > here's where I noticed two weird things:
> >
> > #1) Apache 1.3.27 with mod_jk2 - mod_rewrites that have the [P] flag to
> > proxy don't seem to actually get interpreted and sent over to Tomcat.
> >
> > #2) Apache 1.3.27 with mod_jk - mod_rewrites DO get interpreted. But,
> > with Apache and Tomcat residing on two physical servers, Apache does not
> > send over a request for index.jsp if the URL does not exactly specify
it,
> > even if the DirectoryIndex is set. (So, /index.jsp WILL go to Tomcat,
> > but / will not, and is just processed as an Apache level index view.)
> > I've had to actually create fake index.jsp files in a mock directory
> > structure on the Apache side to trick it into sending index.jsp as
> > default to Tomcat.
> >
> > Does anyone know how to fix either of those strange behaviors? Or
BETTER
> > yet, has anyone had the hanging problem with Apache 2.0.43 and mod_jk2,
> > and found a way to fix it?
> >
> > Thanks,
> > -Raiden
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> > For additional commands, e-mail:
<ma...@jakarta.apache.org>
> >
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Various bugs with mod_jk and mod_jk2? And does
Apache2.0.43+mod_jk2=inevitable hanging?
Posted by Raiden <ra...@wonko.inow.com>.
Just as a followup, even though all of the below still holds true, I did
find out my problem with Apache 2.0.43 (it was a DNS misconfiguration that
eventually held Apache up, even though I don't have it resolving host
names).
So, Apache 2.0.43 is now running fine with mod_jk2. However, it still has
the problem where DirectoryIndex won't check for an index.jsp through
tomcat by default, which creates a problem for those of us that have
Apache on Tomcat running on separate machines.
Anyone have a workaround for this? (Besides creating empty index.jsp files
to trick Apache).
Thanks,
-Raiden
On Sat, 11 Jan 2003, Raiden wrote:
> Hello,
>
> I wanted to get Apache 2.0.43 and mod_jk2 working. They seemed to setup
> fine, and handle requests just great. But after a while, Apache starts
> hanging on every other request. I tried mod_jk, and it still does
> this. I removed all traces of both mod_jks, and it still does eventually
> starts hanging, even on static image requests that are not run through
> Tomcat. I'm assuming it's a problem with Apacheand my setup (Redhat
> 8.0). Anyone else have similar issues?
>
> Anyhow, so I went back to Apache 1.3.27, which does not hang at all. Now,
> here's where I noticed two weird things:
>
> #1) Apache 1.3.27 with mod_jk2 - mod_rewrites that have the [P] flag to
> proxy don't seem to actually get interpreted and sent over to Tomcat.
>
> #2) Apache 1.3.27 with mod_jk - mod_rewrites DO get interpreted. But,
> with Apache and Tomcat residing on two physical servers, Apache does not
> send over a request for index.jsp if the URL does not exactly specify it,
> even if the DirectoryIndex is set. (So, /index.jsp WILL go to Tomcat,
> but / will not, and is just processed as an Apache level index view.)
> I've had to actually create fake index.jsp files in a mock directory
> structure on the Apache side to trick it into sending index.jsp as
> default to Tomcat.
>
> Does anyone know how to fix either of those strange behaviors? Or BETTER
> yet, has anyone had the hanging problem with Apache 2.0.43 and mod_jk2,
> and found a way to fix it?
>
> Thanks,
> -Raiden
>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Various bugs with mod_jk and mod_jk2? And does
Apache2.0.43+mod_jk2=inevitable hanging?
Posted by Raiden <ra...@wonko.inow.com>.
Almost forgot... I'm using Tomcat 4.1.18.
-Raiden
On Sat, 11 Jan 2003, Raiden wrote:
> Hello,
>
> I wanted to get Apache 2.0.43 and mod_jk2 working. They seemed to setup
> fine, and handle requests just great. But after a while, Apache starts
> hanging on every other request. I tried mod_jk, and it still does
> this. I removed all traces of both mod_jks, and it still does eventually
> starts hanging, even on static image requests that are not run through
> Tomcat. I'm assuming it's a problem with Apacheand my setup (Redhat
> 8.0). Anyone else have similar issues?
>
> Anyhow, so I went back to Apache 1.3.27, which does not hang at all. Now,
> here's where I noticed two weird things:
>
> #1) Apache 1.3.27 with mod_jk2 - mod_rewrites that have the [P] flag to
> proxy don't seem to actually get interpreted and sent over to Tomcat.
>
> #2) Apache 1.3.27 with mod_jk - mod_rewrites DO get interpreted. But,
> with Apache and Tomcat residing on two physical servers, Apache does not
> send over a request for index.jsp if the URL does not exactly specify it,
> even if the DirectoryIndex is set. (So, /index.jsp WILL go to Tomcat,
> but / will not, and is just processed as an Apache level index view.)
> I've had to actually create fake index.jsp files in a mock directory
> structure on the Apache side to trick it into sending index.jsp as
> default to Tomcat.
>
> Does anyone know how to fix either of those strange behaviors? Or BETTER
> yet, has anyone had the hanging problem with Apache 2.0.43 and mod_jk2,
> and found a way to fix it?
>
> Thanks,
> -Raiden
>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>