Re: Webobjects Adaptor Causing Apache Segfault

I remember getting this error a couple of years back.

Some declaration had to be changed in the adaptor code to make it work:

http://www.omnigroup.com/mailman/archive/webobjects-dev/2001-November/ 
016996.html:

 > Also have a look to the logfiles of apache. (logs/error_log in your  
apache
 > directory). Are there segmentation faults? If yes, compile the  
adaptor again
 > with the option FINDLEAKS enabled. You must edit the file  
"womalloc.h".

Cheers,

Oliver.



On 29.04.2004, at 18:33, Ken Schweigert wrote:

> Our WO adaptor is on a RedHat-9 install with Apache 1.3.29.  I  
> compiled the
> adaptor from the WO5.1 install CD.  Our WO application server is  
> OSX-10.1.4
> box.  It runs 24 instances of a single application.
>
> This application has been running great for a few years now, and until  
> last
> week, has been very stable.  We made a pretty substantial change to  
> the app
> last week and that's when we started getting complaints from customers.
> Things like "I clicked the 'next' button and it just refreshed the  
> page" or
> "I can only get past a certain point if I fill in the form four or five
> times" or in Safari "the page returned contains no data".
>
> Assuming it had to do something with the app, we had our developer  
> start
> looking through the code while I looked around the servers.  Checking  
> the
> Apache error_log I found a lot of entries like:
>
> [root@www Apache]# tail -f /usr/local/apache/logs/error_log
> [Thu Apr 29 11:29:13 2004] [notice] child pid 9709 exit signal  
> Segmentation fault (11)
> [Thu Apr 29 11:39:48 2004] [notice] child pid 9746 exit signal  
> Segmentation fault (11)
> [Thu Apr 29 11:40:21 2004] [notice] child pid 9731 exit signal  
> Segmentation fault (11)
>
> With some testing we were able to produce these segfaults when the  
> user would
> get the errors.  Click 'next'; see the segfault; 'contains no data'  
> error.
>
> In one post  
> (http://lists.debian.org/debian-apache/2002/debian-apache-200207/ 
> msg00005.html)
> it recommended reseating the RAM and that it was probably hardware  
> related.
> Reseating did not help, nor did running the system with  
> one-or-the-other
> sticks.  So we've probably ruled out hardware.
>
> Another post recommended running Apache through gdb to see what is  
> causing the
> problem.  I did that and see that it is definately the apache adaptor.
>
> [root@www bin]# gdb ./httpd
> GNU gdb Red Hat Linux (5.3post-0.20021129.18rh)
> Copyright 2003 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and  
> you are
> welcome to change it and/or distribute copies of it under certain  
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for  
> details.
> This GDB was configured as "i386-redhat-linux-gnu"...
> (gdb) run -X
> Starting program: /usr/local/apache/bin/httpd -X
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x42074462 in _int_malloc () from /lib/tls/libc.so.6
> (gdb)
> (gdb) bt
> #0  0x42074462 in _int_malloc () from /lib/tls/libc.so.6
> #1  0x4207378d in malloc () from /lib/tls/libc.so.6
> #2  0x42062123 in __fopen_internal () from /lib/tls/libc.so.6
> #3  0x420621ee in fopen@@GLIBC_2.1 () from /lib/tls/libc.so.6
> #4  0x402778ae in WOLog () from  
> /usr/local/apache/libexec/mod_WebObjects.so
> #5  0x4027b5ac in tr_handleRequest () from  
> /usr/local/apache/libexec/mod_WebObjects.so
> #6  0x40273e86 in WebObjects_handler () from  
> /usr/local/apache/libexec/mod_WebObjects.so
> #7  0x080553bb in ap_invoke_handler ()
> #8  0x0806a20f in process_request_internal ()
> #9  0x0806a26e in ap_process_request ()
> #10 0x080613a4 in child_main ()
> #11 0x0806156a in make_child ()
> #12 0x080616d0 in startup_children ()
> #13 0x08061d6d in standalone_main ()
> #14 0x080625a5 in main ()
> #15 0x42015704 in __libc_start_main () from /lib/tls/libc.so.6
> (gdb)
>
>
> Does this mean there is an incompatibility with this version of the
> adaptor and the installed version of glibc (2.3.2)?
>
> Can anyone think of anything else to try or recommend something to fix
> the segfaults?
>
> Thanks!
> -- 
> Ken Schweigert, Network Administrator
> Byte Productions, LLC
> http://www.byte-productions.com
> _______________________________________________
> WebObjects-admin mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-admin