apache plugin segmentation fault

[Thomas Olausson]

I have this setup (both Linux, suse 9)
web server: Apache 2.0.46 + was_ap20_module
app server: WAS 5.1

The web server "proxies" /myapp to WAS. This worked fine until
yesterday. Now, the apache log says

child pid 8080 exit signal Segmentation fault (11)

everytime I hit /myapp.

I've turned the LogLevel up to Trace

Log LogLevel="Trace"


in the plugin-cfg.xml file, and it does say that

TRACE: mod_was_ap20_http: as_map: WebSphere will handle: /myapp

but that's about it. The request is never handled by WAS,
so the plugin must die on its way.

Has anyone gotten this before? The WAS server is running and I can
hit the /myapp url straight on WAS.

My only fallback it to use Apache's own reverse proxy module or remove the web server completely from the picture.

/Tom
[ October 20, 2004: Message edited by: Tom Bombadyll ]

[Thomas Olausson]

The IBM documentation is a little vague on what config options you have with the apache module.

In the examples I've seen, apache and was runs on the same server.
Isn't that a non-typical? A web server normally sits in a DMZ, and the WAS server on another network.

To take advantage of fail over and load balancing, those two services won't run on the same server.

Does the was apache module need anything else from the WAS install directory?
Since I have to separate machines, the httpd server doesn't have access to
any files in /opt/WebsSphere/,
I basically copied the mod_was_ap20_http.so to the httpd's modules directory.

/Tom