general/7661: Apache/JServ fails to start intermittently with a fatal error

[Anton Ivanov <ai...@ispheres.com>]

>Number:         7661
>Category:       general
>Synopsis:       Apache/JServ fails to start intermittently with a fatal error
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Apr 30 15:30:03 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     ai@ispheres.com
>Release:        1.3.9
>Organization:
apache
>Environment:
HP-UX 11.00 on 9000/800.  Compiled with gcc 2.95.2.  JServ version 1.1.2, jdk 1.3 from HP
>Description:
Apache/JServ fail to start intermittently with the error message:
 [Wed Apr 25 16:25:38 2001] [crit] Apache JServ encountered a fatal error; check
your ApJServLogFile for details if none are present in this file.  Exiting.

However, the file designated by the ApJServLogFile directive does not contain anything.  (I built it with --disable-debugging, but wouldn't fatal errors show up?) I noticed that the problem will occur several times in a row, and then things will work several times in a row.  "Working" means apache started and the JServ status URL worked.  However, whenever the server "worked", the following line would appear in the log file:
[Mon Apr 30 14:45:39 2001] [error] (22)Invalid argument: shmctl() could not set
segment #3204
 

I tried truss'ing the httpd process when it failed to start, but didn't spot anything out-of-the ordinary.
>How-To-Repeat:
build apache on HP-UX 11.00 with
./configure --prefix=... --enable-shared=max
and JServ with
./configure \
  --prefix=... \
  --with-apxs=... \
  --with-jdk-home=... \
  --with-JSDK=<path to JSDK 2.0 "jsdk.jar"> \
  --disable-debugging

and restart apache a dozen times.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]