You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Brett Porter (JIRA)" <ji...@apache.org> on 2007/08/27 02:29:30 UTC

[jira] Created: (INFRA-1336) Java Service Wrapper itself can be unable to start Continuum and give up and die

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
            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.


[jira] Commented: (INFRA-1336) Java Service Wrapper itself can be unable to start Continuum and give up and die

Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
    [ 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.


[jira] Closed: (INFRA-1336) Java Service Wrapper itself can be unable to start Continuum and give up and die

Posted by "Emmanuel Venisse (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Venisse closed INFRA-1336.
-----------------------------------

    Resolution: Fixed
      Assignee: Emmanuel Venisse

Fixed by INFRA-1326

> 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.


[jira] Closed: (INFRA-1336) Java Service Wrapper itself can be unable to start Continuum and give up and die

Posted by "Emmanuel Venisse (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Venisse closed INFRA-1336.
-----------------------------------

    Resolution: Fixed

Maven zone had one build definition with 'fresh build' option too. I remove it and deleted all latest builds in failures of the Maven Plugins group so the change list of them won't be use in the merge process

> 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.


[jira] Updated: (INFRA-1336) Java Service Wrapper itself can be unable to start Continuum and give up and die

Posted by "Emmanuel Venisse (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Venisse updated INFRA-1336:
------------------------------------

    Comment: was deleted

> 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
>            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.


[jira] Commented: (INFRA-1336) Java Service Wrapper itself can be unable to start Continuum and give up and die

Posted by "Emmanuel Venisse (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523310 ] 

Emmanuel Venisse commented on INFRA-1336:
-----------------------------------------

The build don't need to do a build fresh that is a clean checkout instead of an update

> 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
>            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.


[jira] Reopened: (INFRA-1336) Java Service Wrapper itself can be unable to start Continuum and give up and die

Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter reopened INFRA-1336:
---------------------------------


this still happens if the machine gets sufficiently loaded to be unresponsive - we need to find out if that's Continuum's fault, or can just happen under other circumstances.

Though vmbuild is fine, I'm seeing the one on the Maven zone fall down in the same way (and doesn't seem to have any memory issues).

> 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.