|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
@Ruslan, @Fran,
I'm filtering the issues to cut a new release. This issue already happened twice in the past. One occurrence of this issue is registered here. The other one may be registered here too, under other issue, or maybe in testlink-java-api issues or in my private e-mail inbox.
But in both cases, I remember well that it wasn't caused by any bug in neither Jenkins TestLink Plug-in nor in testlink-java-api. Once it was a wrong URL, and the other time we set up a VPS with TestLink. The reporter pointed his Jenkins to this server and successfully downloaded and executed tests using the plug-in.
This way, we could isolate the problem, making sure it was either in TestLink or in the web server.
Basically, this issue is caused when the XML-RPC client asks for a XML response from a server, but it gets something that is not a valid XML or any stream of data with extra characters (even if not visible - i.e. can't be decoded in console/editor) before the XML content.
There's not much I can do to help in this case. If you guys could intercept the communication (using QDPF, Wireshark, etc) between the client and server, perhaps we can analyse what's happening. But besides that, there's not much I can do in the code to help you guys. Sorry :/
Cheers, Bruno