Bamboo service keeps restarting with JVM heartbeat failure

The Bamboo service keeps restarting when the webapp wrapper detectes that the JVM is unresponsive, it appears that the JVM is crashing and so failing to respond the the wrapper heartbeat ping. This was happening intermittently evry hour or two, it now happens every few minutes:

INFO | jvm 18 | 2012/04/24 20:11:02 | 2012-04-24 20:11:02,208 WARN PluginSchedulerTask-upmPluginNotificationJob NotificationCacheUpdaterImpl Automatic plugin update check failed

INFO | jvm 18 | 2012/04/24 20:11:02 | com.atlassian.plugins.PacException: Unexpected Response

INFO | jvm 18 | 2012/04/24 20:11:02 | at com.atlassian.plugins.client.service.AbstractServiceClient.executeMethod(AbstractServiceClient.java:400)

INFO | jvm 18 | 2012/04/24 20:11:02 | at com.atlassian.plugins.client.service.AbstractRestServiceClient.list(AbstractRestServiceClient.java:129)

INFO | jvm 18 | 2012/04/24 20:11:02 | at com.atlassian.plugins.client.service.plugin.PluginVersionServiceClientImpl.findUpdates(PluginVersionServiceClientImpl.java:81)

INFO | jvm 18 | 2012/04/24 20:11:02 | at com.atlassian.upm.pac.PacClientImpl.getUpdates(PacClientImpl.java:163)

INFO | jvm 18 | 2012/04/24 20:11:02 | at com.atlassian.upm.notification.cache.NotificationCacheUpdaterImpl.updatePluginUpdateNotification(NotificationCacheUpdaterImpl.java:67)

INFO | jvm 18 | 2012/04/24 20:11:02 | at com.atlassian.upm.notification.cache.NotificationCacheUpdaterImpl.updateAllNotifications(NotificationCacheUpdaterImpl.java:53)

INFO | jvm 18 | 2012/04/24 20:11:02 | at com.atlassian.upm.notification.cache.NotificationCacheUpdateScheduler$NotificationCacheUpdateJob.execute(NotificationCacheUpdateScheduler.java:107)

INFO | jvm 18 | 2012/04/24 20:11:02 | at com.atlassian.sal.core.scheduling.TimerPluginScheduler$PluginTimerTask.run(TimerPluginScheduler.java:72)

INFO | jvm 18 | 2012/04/24 20:11:02 | at java.util.TimerThread.mainLoop(Unknown Source)

INFO | jvm 18 | 2012/04/24 20:11:02 | at java.util.TimerThread.run(Unknown Source)

INFO | jvm 18 | 2012/04/24 20:11:02 | Caused by: java.net.ConnectException: Connection timed out: connect

INFO | jvm 18 | 2012/04/24 20:11:02 | at java.net.PlainSocketImpl.socketConnect(Native Method)

INFO | jvm 18 | 2012/04/24 20:11:02 | at java.net.PlainSocketImpl.doConnect(Unknown Source)

INFO | jvm 18 | 2012/04/24 20:11:02 | at java.net.PlainSocketImpl.connectToAddress(Unknown Source)

INFO | jvm 18 | 2012/04/24 20:11:02 | at java.net.PlainSocketImpl.connect(Unknown Source)

INFO | jvm 18 | 2012/04/24 20:11:02 | at java.net.SocksSocketImpl.connect(Unknown Source)

INFO | jvm 18 | 2012/04/24 20:11:02 | at java.net.Socket.connect(Unknown Source)

INFO | jvm 18 | 2012/04/24 20:11:02 | at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(Unknown Source)

INFO | jvm 18 | 2012/04/24 20:11:02 | at com.sun.net.ssl.internal.ssl.SSLSocketImpl.<init>(Unknown Source)

INFO | jvm 18 | 2012/04/24 20:11:02 | at com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl.createSocket(Unknown Source)

INFO | jvm 18 | 2012/04/24 20:11:02 | at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:81)

INFO | jvm 18 | 2012/04/24 20:11:02 | at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:126)

INFO | jvm 18 | 2012/04/24 20:11:02 | at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:706)

INFO | jvm 18 | 2012/04/24 20:11:02 | at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1321)

INFO | jvm 18 | 2012/04/24 20:11:02 | at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:386)

INFO | jvm 18 | 2012/04/24 20:11:02 | at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)

INFO | jvm 18 | 2012/04/24 20:11:02 | at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)

INFO | jvm 18 | 2012/04/24 20:11:02 | at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)

INFO | jvm 18 | 2012/04/24 20:11:02 | at com.atlassian.plugins.client.service.AbstractServiceClient.executeMethod(AbstractServiceClient.java:395)

INFO | jvm 18 | 2012/04/24 20:11:02 | ... 9 more

INFO | jvm 18 | 2012/04/24 20:11:03 | 2012-04-24 20:11:03,427 INFO qtp1298336441-20 AccessLogFilter tabtis GET http://rawpscm103v.rwwa.com.au:8085/rest/api/latest/server?_=1335355862074 49647kb

DEBUG | wrapper | 2012/04/24 20:11:03 | JVM process exited with a code of -1, setting the wrapper exit code to -1.

ERROR | wrapper | 2012/04/24 20:11:03 | JVM exited unexpectedly.

We are using: Java Version : 1.6.0_31-b05 on Windows Server 2008, any indications as to why this is happening or have you seen this behaviour before?

Thanks

Regards

John

1 answer

1 accepted

This widget could not be displayed.

Hi John,

Not sure whats going on here but it might be best to get in contact with support.

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Wednesday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

124 views 2 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you