mod_jserv/7213: The mod_jserve does not want to start java VM

[Nick Kanakakorn <sk...@yahoo.com>]

>Number:         7213
>Category:       mod_jserv
>Synopsis:       The mod_jserve does not want to start java VM
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    jserv
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Feb 07 10:40:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     skanan@yahoo.com
>Release:        1.3.14
>Organization:
apache
>Environment:
Solaris 
SunOS stage 5.6 Generic_105181-23 sun4u sparc SUNW,UltraSPARC-IIi-Engine 
>Description:
The is the log from mod_jserv.log
[07/02/2001 04:05:09:329] (INFO) spawn ap_standalone, getppid = 1 10829
[07/02/2001 04:05:09:329] (INFO) Apache-JServ 1rst  initialization: JVM will be started later 1 10830 10829
[07/02/2001 04:05:09:336] (INFO) Apache Module was cleaned-up
[07/02/2001 04:05:09:352] (INFO) spawn ap_standalone, getppid = 1 10830
[07/02/2001 04:05:09:352] (INFO) Apache-JServ 1rst  initialization: JVM will be started later 1 10831 10830
[07/02/2001 04:05:48:069] (INFO) Apache Module was cleaned-up

Please notice that I added some debugging statement in jserv_wrapper_unix.c.
The problem is that the mod_jserve should go to start JVM instead of going
back to the 1rst initialization again.

The problems happended to 3 solaris machines that I have but looks fine on
the other two machines. 
>How-To-Repeat:
I built apache1.3.14 + mod_jserv by following the instruction exactly.
It is difficult to reproduce because it is machine dependent.  But once
it happended, it always happend on that machine.
>Fix:
It might be Solaris problem but I suspected timing problem.  I have the code
on jserv_wrapper_unix.c that I modified if that is helpful.
>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!     ]