On Thu, Aug 07, 2003 at 10:34:41AM -0700, C Man wrote:
I have been trying to get Apache (1.3.27-54) to proxy requests to Weblogic (6.1 sp5) on our linux box (Kernel 2.4.19) but have been experiencing issues.
After following BEA's instructions (running apxs on mod_wl.so, ensuring the (LoadModule and AddModule) entries were automatically made in the httpd.conf, adding the appropriate IfModule and Location blocks), I get
Is mod_wl.so available as source code? Did you build it yourself? If yes, if you build the module with apxs you should be fine, because apxs uses the same compiler flags that apache was built with. The compiler flags (among other things) can be queried like this: # echo $(apxs -q CFLAGS) -O2 -march=i586 -mcpu=i686 -fmessage-length=0 -DEAPI_MM -fPIC -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DHARD_SERVER_LIMIT=2048 -DDYNAMIC_MODULE_LIMIT=128 -DSSL_EXPERIMENTAL_PERDIRCA_IGNORE -DSSL_EXPERIMENTAL_PROXY_IGNORE -DLINUX=22 -DMOD_SSL=208115 -DEAPI Note that -DEAPI is present. The EAPI ("extended API") is what mod_ssl introduces by patching Apache, which involves changes of the API (Application Program(ming) Interface). If you do not have built the module from source because it is distributed in binary form only (I don't know, just speculating), you would need to contact BEA to provide a module that is built with that way.
[warn] Loaded DSO /usr/lib/apache/mod_wl.so uses plain Apache 1.3 API, this module might crash under EAPI! (please recompile it with -DEAPI) though apache still starts correctly and serves static content. However, if I do try the proxying it doesn't work and [notice] child pid XXXX exit signal Segmentation fault (11) shows up in the log
...and it does indeed crash, just as the warning said. How did you build the module? Peter