Hi,

I have Apache 2.0.52, which I compiled using the gcc from (I think) the 
Companion CD for Solaris 9) awhile ago, running on a Solaris 9 SPARC 
system.  I think that the gcc version was 2.95(?).

Originally, I had this system configured to front-end for WebLogic 
running on another Solaris 9 system, using the WebLogic Plugin for 
Apache to connect from Apache to WebLogic.  Everything was working fine.

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 using apxs from the original Apache 2.0.52 source directory 
(which I luckily kept on the system).  I know that V4.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 tested 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 was seeing these errors when I access both the new webapp on Tomcat, 
as well as the original webapp on WebLogic, but I found that 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.

I was wondering if anyone here might have been run into this problem 
before?  Are there any kernel parameters that I should be tweaking?

Is this (mod_proxy and segfaults) a known problem, and is there a fix 
for this problem?  I been searching, 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, which I compiled using the gcc from (I think) the 
> Companion CD for Solaris 9) awhile ago, running on a Solaris 9 SPARC 
> system.  I think that the gcc version was 2.95(?).
> 
> Originally, I had this system configured to front-end for WebLogic 
> running on another Solaris 9 system, using the WebLogic Plugin for 
> Apache to connect from Apache to WebLogic.  Everything was working fine.
> 
> 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 using apxs from the original Apache 2.0.52 source directory 
> (which I luckily kept on the system).  I know that V4.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 tested 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 was seeing these errors when I access both the new webapp on Tomcat, 
> as well as the original webapp on WebLogic, but I found that 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.
> 
> I was wondering if anyone here might have been run into this problem 
> before?  Are there any kernel parameters that I should be tweaking?
> 
> Is this (mod_proxy and segfaults) a known problem, and is there a fix 
> for this problem?  I been searching, 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 installed and switched to using the mod_jk connector 
in place of mod_proxy, and the segfaults are gone.  I don't know if I 
originally had something wrong with my mod_proxy compile or whatevever, 
but it seems like mod_proxy is somewhat problematic.

Jim

We just had this problem caused by an improperly compiled module for
Weblogic.

Dave wrote:
> We just had this problem caused by an improperly compiled module for
> Weblogic.


Dave.

Sorry to keep this OT thread going, but I'm curious when you said that 
you compiled a "module for WebLogic".  In my case, the .SO file making 
up the "WebLogic Plugin for Apache2" was including in the WebLogic (on 
Solaris) files after installing WebLogic (on Solaris).  Which module did 
you have to compile?

The mod_proxy that I referred to in my original post was compiled by me, 
using "apxs" using source from the original 2.0.52 source distribution. 
  I don't remember exactly, but I did that by cd to the "proxy" 
directory in the source tree, then doing something like "apxs .... *.c".

Jim

ohaya wrote:
> Dave wrote:
>> We just had this problem caused by an improperly compiled module for
>> Weblogic.
> 
> 
> Dave.
> 
> Sorry to keep this OT thread going, but I'm curious when you said that 
> you compiled a "module for WebLogic".  In my case, the .SO file making 
> up the "WebLogic Plugin for Apache2" was including in the WebLogic (on 
> Solaris) files after installing WebLogic (on Solaris).  Which module did 
> you have to compile?
> 
> The mod_proxy that I referred to in my original post was compiled by me, 
> using "apxs" using source from the original 2.0.52 source distribution. 
>  I don't remember exactly, but I did that by cd to the "proxy" directory 
> in the source tree, then doing something like "apxs .... *.c".
> 
> Jim
> 

P.S.  The mod_jk SO I used was a binary that I downloaded from 
www.apache.org, and is mod_jk 1.2.6 (for Apache2), I think, compiled for 
Solaris 8 (seems to work ok on Solaris 9 :))...

Jim