You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Wendy Smoak (JIRA)" <ji...@codehaus.org> on 2009/05/22 23:44:42 UTC

[jira] Issue Comment Edited: (CONTINUUM-2241) Continuum constantly re-starting itself

    [ http://jira.codehaus.org/browse/CONTINUUM-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177708#action_177708 ] 

Wendy Smoak edited comment on CONTINUUM-2241 at 5/22/09 4:43 PM:
-----------------------------------------------------------------

Continuum on vmbuild has re-started 17 times so far today, and when it re-starts, the build queue is empty.  This means projects aren't building, because they're not making it through the queue before it goes down again.

Info on previous restarts by day:
{noformat}
$ grep started! continuum.log.2009-05-21 | wc -l
31
$ grep started! continuum.log.2009-05-20 | wc -l
26
$ grep started! continuum.log.2009-05-19 | wc -l
24
$ grep started! continuum.log.2009-05-18 | wc -l
25
$ grep started! continuum.log.2009-05-17 | wc -l
23
$ grep started! continuum.log.2009-05-16 | wc -l
24
$ grep started! continuum.log.2009-05-15 | wc -l
24
$ grep started! continuum.log.2009-05-14 | wc -l
24
$ grep started! continuum.log.2009-05-13 | wc -l
15
$ grep started! continuum.log.2009-05-12 | wc -l
7
$ grep started! continuum.log.2009-05-11 | wc -l
7
$ grep started! continuum.log.2009-05-10 | wc -l
4
$ grep started! continuum.log.2009-05-09 | wc -l
6
$ grep started! continuum.log.2009-05-08 | wc -l
8
$ grep started! continuum.log.2009-05-07 | wc -l
5
$ grep started! continuum.log.2009-05-06 | wc -l
7
$ grep started! continuum.log.2009-05-05 | wc -l
7
$ grep started! continuum.log.2009-05-04 | wc -l
6
$ grep started! continuum.log.2009-05-03 | wc -l
5
$ grep started! continuum.log.2009-05-02 | wc -l
3
$ grep started! continuum.log.2009-05-01 | wc -l
5
$ grep started! continuum.log.2009-04-30 | wc -l
5
$ grep started! continuum.log.2009-04-29| wc -l
9
$ grep started! continuum.log.2009-04-28 | wc -l
7
$ grep started! continuum.log.2009-04-27 | wc -l
7
$ grep started! continuum.log.2009-04-26 | wc -l
8
$ grep started! continuum.log.2009-04-25 | wc -l
7
$ grep started! continuum.log.2009-04-24 | wc -ll
8
$ grep started! continuum.log.2009-04-23 | wc -l
20
$ grep started! continuum.log.2009-04-22 | wc -l
22
{noformat}

Looks like something bad happened when I upgraded on May 13th, it was [relatively] better before that.

      was (Author: wsmoak):
    Continuum on vmbuild has re-started 17 times so far today, and when it re-starts, the build queue is empty.

  
> Continuum constantly re-starting itself
> ---------------------------------------
>
>                 Key: CONTINUUM-2241
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2241
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.3.3
>         Environment: 1.3.3-SNAPSHOT,  r776815 and r777534
>            Reporter: Wendy Smoak
>            Priority: Critical
>
> While monitoring vmbuild after upgrading it, I noticed another error 503 as the page refreshed.  When I checked the log, I can see it's been re-starting fairly regularly:
> {noformat}
> imbrium:Downloads wsmoak$ grep started vmbuild-continuum-20090520.log 
> 2009-05-22 00:33:35,256 [WrapperSimpleAppMain] INFO  org.apache.maven.continuum.DefaultContinuum  - < Continuum 1.3.3-SNAPSHOT started! >
> 2009-05-22 01:32:49,367 [WrapperSimpleAppMain] INFO  org.apache.maven.continuum.DefaultContinuum  - < Continuum 1.3.3-SNAPSHOT started! >
> 2009-05-22 02:23:05,537 [WrapperSimpleAppMain] INFO  org.apache.maven.continuum.DefaultContinuum  - < Continuum 1.3.3-SNAPSHOT started! >
> 2009-05-22 03:02:45,942 [WrapperSimpleAppMain] INFO  org.apache.maven.continuum.DefaultContinuum  - < Continuum 1.3.3-SNAPSHOT started! >
> 2009-05-22 04:11:22,112 [WrapperSimpleAppMain] INFO  org.apache.maven.continuum.DefaultContinuum  - < Continuum 1.3.3-SNAPSHOT started! >
> 2009-05-22 05:08:31,257 [WrapperSimpleAppMain] INFO  org.apache.maven.continuum.DefaultContinuum  - < Continuum 1.3.3-SNAPSHOT started! >
> 2009-05-22 06:06:17,363 [WrapperSimpleAppMain] INFO  org.apache.maven.continuum.DefaultContinuum  - < Continuum 1.3.3-SNAPSHOT started! >
> 2009-05-22 06:53:23,922 [WrapperSimpleAppMain] INFO  org.apache.maven.continuum.DefaultContinuum  - < Continuum 1.3.3-SNAPSHOT started! >
> 2009-05-22 08:50:13,021 [WrapperSimpleAppMain] INFO  org.apache.maven.continuum.DefaultContinuum  - < Continuum 1.3.3-SNAPSHOT started! >
> 2009-05-22 09:18:34,881 [WrapperSimpleAppMain] INFO  org.apache.maven.continuum.DefaultContinuum  - < Continuum 1.3.3-SNAPSHOT started! >
> {noformat}
> Only one of those is an intentional re-start after the upgrade.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira