Hi,

I have Apache 2.0.52, running on a Solaris 9 system. Originally, I had
this system configured to front-end for WebLogic, using the WebLogic
Plugin for Apache to connect from Apache to WebLogic.

Recently, I also needed to have this Apache instance front-end for a
Tomcat 4.1.30 system (running on a Windows machine), so I configured
mod_proxy. I know that 4.1.30 is a quite old version of Tomcat, but the
webapp is only "certified" to run on 4.1.30, so for now, I need to stick
with that version of Tomcat.

In my Apache httpd.conf, I have:

ProxyPass /myapp http://tomcat.host.com:18001/myapp
ProxyPassReverse /myapp http://tomcat.host.com:18001/myapp

This is a test system, so just to be consistent, I switched the
Apache-to-WebLogic connections to mod_proxy also, i.e., I did:

ProxyPass /weblogapp http://weblogic.host.com:7001/weblogicapp
ProxyPassReverse /weblogicapp http://weblogic.host.com:7001/weblogicapp

This seemed to *kind of* work, but when I test with IE6, I noticed that
I was oftentimes getting an "Error on page", and parts of the page would
be missing.

I looked in the logs/error_log file on the Solaris/Apache system, and I
am seeing a LOT of msgs like:

[notice] child pid XXXX exit signal Segmentation Fault (11)

I am seeing these errors when I access both the new webapp on Tomcat, as
well as the original webapp on WebLogic.

If I switch the Apache-to-WebLogic connection back to using the WebLogic
Plugin for Apache instead of mod_proxy, I can access the WebLogic webapp
without those segfault errors (I still get segfault errors when
accessing the Tomcat webapp).

So, it seems like the segfaults must be occurring due to mod_proxy.

Is this (mod_proxy and segfaults) a known problem, and is there a fix
for this problem? I searched, and there seemed to be a lot of msgs
about similar problems with various versions of Apache2, but I couldn't
find a definitive fix.

Thanks in advance,
Jim

ohaya wrote:
> Hi,
>
> I have Apache 2.0.52, running on a Solaris 9 system. Originally, I had
> this system configured to front-end for WebLogic, using the WebLogic
> Plugin for Apache to connect from Apache to WebLogic.
>
> Recently, I also needed to have this Apache instance front-end for a
> Tomcat 4.1.30 system (running on a Windows machine), so I configured
> mod_proxy. I know that 4.1.30 is a quite old version of Tomcat, but the
> webapp is only "certified" to run on 4.1.30, so for now, I need to stick
> with that version of Tomcat.
>
> In my Apache httpd.conf, I have:
>
> ProxyPass /myapp http://tomcat.host.com:18001/myapp
> ProxyPassReverse /myapp http://tomcat.host.com:18001/myapp
>
> This is a test system, so just to be consistent, I switched the
> Apache-to-WebLogic connections to mod_proxy also, i.e., I did:
>
> ProxyPass /weblogapp http://weblogic.host.com:7001/weblogicapp
> ProxyPassReverse /weblogicapp http://weblogic.host.com:7001/weblogicapp
>
> This seemed to *kind of* work, but when I test with IE6, I noticed that
> I was oftentimes getting an "Error on page", and parts of the page would
> be missing.
>
> I looked in the logs/error_log file on the Solaris/Apache system, and I
> am seeing a LOT of msgs like:
>
> [notice] child pid XXXX exit signal Segmentation Fault (11)
>
> I am seeing these errors when I access both the new webapp on Tomcat, as
> well as the original webapp on WebLogic.
>
> If I switch the Apache-to-WebLogic connection back to using the WebLogic
> Plugin for Apache instead of mod_proxy, I can access the WebLogic webapp
> without those segfault errors (I still get segfault errors when
> accessing the Tomcat webapp).
>
> So, it seems like the segfaults must be occurring due to mod_proxy.
>
> Is this (mod_proxy and segfaults) a known problem, and is there a fix
> for this problem? I searched, and there seemed to be a lot of msgs
> about similar problems with various versions of Apache2, but I couldn't
> find a definitive fix.
>
> Thanks in advance,
> Jim


Hi,

For the record, I switched to using mod_jk, and am no longer getting the
segfaults !!

I used a binary for Solaris SPARC (V1.2.6) that I found on the Apache
archives.

Jim