[
http://jira.codehaus.org/browse/CONTINUUM-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180217#action_180217
]
Wendy Smoak commented on CONTINUUM-2241:
----------------------------------------
On dev@ Emmanuel mentioned reducing the JVM memory to 1024m.
I'm still seeing it re-start constantly... 26 times so far today.
wsm...@vmbuild:/home/continuum/services/continuum/logs$ grep hung wrapper.log |
grep '2009/06/12'
ERROR | wrapper | 2009/06/12 00:19:22 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 00:28:00 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 00:36:20 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 00:51:22 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 01:02:12 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 01:13:00 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 01:24:13 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 02:03:50 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 02:23:32 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 02:42:26 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 03:00:45 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 03:15:27 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 03:32:17 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 03:50:12 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 04:00:35 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 04:09:45 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 06:44:07 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 07:53:39 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 08:17:09 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 10:24:12 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 11:37:30 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 12:33:34 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 13:37:41 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 13:50:58 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 14:38:59 | JVM appears hung: Timed out waiting
for signal from JVM.
ERROR | wrapper | 2009/06/12 15:42:52 | JVM appears hung: Timed out waiting
for signal from JVM.
similarly,
wsm...@vmbuild:/home/continuum/services/continuum/logs$ grep started!
continuum.log | wc -l
28
> 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
> 1.3.4-SNAPSHOT, r781487
> 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
