www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benjamin Gu <binqua...@yahoo.com>
Subject mod_jserv/5956: Java VM not respond and
Date Tue, 04 Apr 2000 06:41:12 GMT

>Number:         5956
>Category:       mod_jserv
>Synopsis:       Java VM not respond and
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    jserv
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Apr 03 23:50:00 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     binquangu@yahoo.com
>Release:        1.3.6
>Organization:
apache
>Environment:
solaris 2.6
>Description:
We were running scalability testing for a 3 tier java application, middle tier is using jserv
1.1, we were using automatic mode of jserv and only one VM was running, at some random time,
we saw the following error in mod_jserv.log.

We raised the ulimit filedescriptor to 1024, and problem still happens.
Is that an known issue with that jserv cannot scale?

[01/04/2000 11:01:05:646] (INFO) wrapper: Java VM spawned (PID=21647, PPID=21594
)
[01/04/2000 11:01:15:643] (INFO) wrapper: watching processes (PID=21594,PPID=215
93,JVM PID=21647)
[01/04/2000 11:06:31:417] (INFO) wrapper: Java VM not responding (PID=21594) [ti
meout]
[01/04/2000 11:06:31:420] (EMERGENCY) ajp12[1]: cannot scan servlet headers  (50
0)
[01/04/2000 11:06:31:420] (ERROR) an error returned handling request via protoco
l "ajpv12"                       
[01/04/2000 11:06:32:417] (EMERGENCY) ajp12: ping: no reply (-1)             Ple
ase make sure that the wrapper.classpath is pointing             to the correct
version of ApacheJServ.jar
[01/04/2000 11:06:32:417] (INFO) wrapper: Java VM restarting (PID=21594)
[01/04/2000 11:06:32:419] (INFO) wrapper: Java VM spawned (PID=21662, PPID=21594
)
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@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!     ]
 
 


Mime
View raw message