www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <j...@apache.org>
Subject [jira] Commented: (INFRA-1336) Java Service Wrapper itself can be unable to start Continuum and give up and die
Date Sat, 20 Oct 2007 02:20:50 GMT

    [ https://issues.apache.org/jira/browse/INFRA-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536389
] 

Brett Porter commented on INFRA-1336:
-------------------------------------

this was 'fixed' by adding the following:

wrapper.on_exit.default=RESTART
wrapper.on_exit.0=SHUTDOWN
wrapper.restart.delay=30

it now restarts automatically:
STATUS | wrapper  | 2007/10/20 01:59:10 | on_exit trigger matched.  Restarting the JVM.  (Exit
code: 1)


> Java Service Wrapper itself can be unable to start Continuum and give up and die
> --------------------------------------------------------------------------------
>
>                 Key: INFRA-1336
>                 URL: https://issues.apache.org/jira/browse/INFRA-1336
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Continuum
>            Reporter: Brett Porter
>            Assignee: Emmanuel Venisse
>            Priority: Critical
>
> This was in the logs on Aug 26, and the wrapper had stopped itself as well as Continuum:
> ERROR  | wrapper  | 2007/08/26 16:16:18 | JVM appears hung: Timed out waiting for signal
from JVM.
> ERROR  | wrapper  | 2007/08/26 16:16:18 | JVM did not exit on request, terminated
> INFO   | wrapper  | 2007/08/26 16:16:18 | JVM exited on its own while waiting to kill
the application.
> STATUS | wrapper  | 2007/08/26 16:16:19 | JVM exited in response to signal SIGKILL (9).
> STATUS | wrapper  | 2007/08/26 16:16:23 | Launching a JVM...
> ERROR  | wrapper  | 2007/08/26 16:16:56 | Startup failed: Timed out waiting for a signal
from the JVM.
> ERROR  | wrapper  | 2007/08/26 16:16:56 | JVM did not exit on request, terminated
> INFO   | wrapper  | 2007/08/26 16:16:56 | JVM exited on its own while waiting to kill
the application.
> STATUS | wrapper  | 2007/08/26 16:16:56 | JVM exited in response to signal SIGKILL (9).
> STATUS | wrapper  | 2007/08/26 16:17:01 | Launching a JVM...
> ERROR  | wrapper  | 2007/08/26 16:17:33 | Startup failed: Timed out waiting for a signal
from the JVM.
> ERROR  | wrapper  | 2007/08/26 16:19:30 | JVM did not exit on request, terminated
> INFO   | wrapper  | 2007/08/26 16:19:30 | JVM exited on its own while waiting to kill
the application.
> STATUS | wrapper  | 2007/08/26 16:19:30 | JVM exited in response to signal SIGKILL (9).
> INFO   | wrapper  | 2007/08/26 16:19:30 | Wrapper Process has not received any CPU time
for 105 seconds.  Extending timeouts.
> STATUS | wrapper  | 2007/08/26 16:19:35 | Launching a JVM...
> ERROR  | wrapper  | 2007/08/26 16:20:07 | Startup failed: Timed out waiting for a signal
from the JVM.
> ERROR  | wrapper  | 2007/08/26 16:20:07 | JVM did not exit on request, terminated
> STATUS | wrapper  | 2007/08/26 16:20:09 | JVM exited in response to signal SIGKILL (9).
> ERROR  | wrapper  | 2007/08/26 16:20:09 | Unable to start a JVM
> STATUS | wrapper  | 2007/08/26 16:20:09 | <-- Wrapper Stopped

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message