DEV Bornali
2013-07-23 07:03:58 UTC
Hi,
I am using cruisecontrol 2.8.3.
I've been getting the following message repeatedly. I am not sure what is causing that, didn't make any upgrades or recent changes to cruisecontrol.
Though the builds are running normally, these annoying warnings show up in the cruisecontrol log. It may also be delaying other processes.
I have searched the net for any concrete solution to this, but couldn't exactly find an answer.
I do have <modificationset> defined in all projects and I'm using the binary distribution.
I read in one of the post that I might need to increase the jetty's socket time out defined by maxidletime (probably in this path cruisecontrol\etc\jetty.xml), but other servers running cruisecontrol have the same value for maxidletime and don't have this issue.
Any help would be appreciated.
2013-07-23 13:58:37,379 [Timer-7 ] WARN BuildLoopStatusReportTask - Failed to reach dashboard instance : http://localhost:8080/dashboard/buildloop/listener, either the dashboard has not started up or there is a network problem.
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:77)
at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:105)
at org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1115)
at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1832)
at org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1590)
at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:995)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)
at net.sourceforge.cruisecontrol.report.BuildLoopStatusReportTask.run(BuildLoopStatusReportTask.java:90)
at net.sourceforge.cruisecontrol.report.BuildLoopStatusReportTask.run(BuildLoopStatusReportTask.java:75)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
2013-07-23 14:25:29,297 [btpool0-1] INFO XSLTag
Thanks.
Bornali
Before printing, please consider the environment
IMPORTANT NOTICE: This e-mail and any attachment to it are intended only to be read or used by the named addressee. It is confidential and may contain legally privileged information. No confidentiality or privilege is waived or lost by any mistaken transmission to you. Roads and Maritime Services (RMS) is not responsible for any unauthorised alterations to this e-mail or attachment to it. Views expressed in this message are those of the individual sender, and are not necessarily the views of RMS. If you receive this e-mail in error, please immediately delete it from your system and notify the sender. You must not disclose, copy or use any part of this e-mail if you are not the intended recipient.
I am using cruisecontrol 2.8.3.
I've been getting the following message repeatedly. I am not sure what is causing that, didn't make any upgrades or recent changes to cruisecontrol.
Though the builds are running normally, these annoying warnings show up in the cruisecontrol log. It may also be delaying other processes.
I have searched the net for any concrete solution to this, but couldn't exactly find an answer.
I do have <modificationset> defined in all projects and I'm using the binary distribution.
I read in one of the post that I might need to increase the jetty's socket time out defined by maxidletime (probably in this path cruisecontrol\etc\jetty.xml), but other servers running cruisecontrol have the same value for maxidletime and don't have this issue.
Any help would be appreciated.
2013-07-23 13:58:37,379 [Timer-7 ] WARN BuildLoopStatusReportTask - Failed to reach dashboard instance : http://localhost:8080/dashboard/buildloop/listener, either the dashboard has not started up or there is a network problem.
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:77)
at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:105)
at org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1115)
at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1832)
at org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1590)
at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:995)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)
at net.sourceforge.cruisecontrol.report.BuildLoopStatusReportTask.run(BuildLoopStatusReportTask.java:90)
at net.sourceforge.cruisecontrol.report.BuildLoopStatusReportTask.run(BuildLoopStatusReportTask.java:75)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
2013-07-23 14:25:29,297 [btpool0-1] INFO XSLTag
Thanks.
Bornali
Before printing, please consider the environment
IMPORTANT NOTICE: This e-mail and any attachment to it are intended only to be read or used by the named addressee. It is confidential and may contain legally privileged information. No confidentiality or privilege is waived or lost by any mistaken transmission to you. Roads and Maritime Services (RMS) is not responsible for any unauthorised alterations to this e-mail or attachment to it. Views expressed in this message are those of the individual sender, and are not necessarily the views of RMS. If you receive this e-mail in error, please immediately delete it from your system and notify the sender. You must not disclose, copy or use any part of this e-mail if you are not the intended recipient.