continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-2656) Distributed build may never return
Date Wed, 24 Aug 2011 00:27:32 GMT


Brett Porter commented on CONTINUUM-2656:

Actually, it seems in this case the error of CONTINUUM-2655 was received on the server and
couldn't be parsed, which was returned to the agent, but not cleaned up on the server:

2011-08-23 18:13:02,927 [qtp169456094-176294] ERROR org.apache.xmlrpc.server.XmlRpcErrorLogger
 - Failed to parse XML-RPC request: A
n invalid XML character (Unicode: 0xc) was found in the element content of the document.
org.apache.xmlrpc.XmlRpcException: Failed to parse XML-RPC request: An invalid XML character
(Unicode: 0xc) was found in the element
 content of the document.
        at org.apache.xmlrpc.server.XmlRpcStreamServer.getRequest(
        at org.apache.xmlrpc.server.XmlRpcStreamServer.execute(
        at org.apache.xmlrpc.webserver.XmlRpcServletServer.execute(
        at org.apache.xmlrpc.webserver.XmlRpcServlet.doPost(
        at javax.servlet.http.HttpServlet.service(
        at javax.servlet.http.HttpServlet.service(

Not sure if you can do an error handler for the XML-RPC request, or if the client needs to
send a new one - but either way the description still applies.

> Distributed build may never return
> ----------------------------------
>                 Key: CONTINUUM-2656
>                 URL:
>             Project: Continuum
>          Issue Type: Bug
>          Components: Distributed Builds
>    Affects Versions: 1.4.1 (Beta)
>            Reporter: Brett Porter
> Under the circumstances outlined in CONTINUUM-2655, the build result is never returned
to the server. In this case, the server never times out waiting for the response, and further
pings do not encourage the agent to present the failure.
> The build will run forever if it was forced and not respecting the timeout value. It
can no longer be cancelled as it doesn't appear in the queue.
> Two things are needed:
> - A failure to respond should generate a new error response (with a simpler message less
likely to fail)
> - The server should check for a lack of response and end the build if the job has finished

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message