[JIRA] [core] (JENKINS-23917) Protocol deadlock while uploading artifacts from ppc64

[ji...@gmx.net (JIRA)]

jimis jimis commented on JENKINS-23917 Protocol deadlock while uploading artifacts from ppc64 Hi, I'm experiencing the same issue using Jenkins 1.580.1 on ppc64 running AIX 5.3. In particular I'm seeing the exact same bytes that you have posted in the attached file "slavelog-from-slave.log": java.io.StreamCorruptedException: invalid stream header: 009AACED Searching the web I found the following explanation for this sequence of bytes: Object stream data is preceded by a 4 byte 'magical' sequence AC ED 00 05. An ObjectInputStream will peek for this data at construction time rather than before the first read. And that's logical: one wants to be sure it is a proper stream before being too far in an application. The sequence is buffered by the ObjectOutputStream at construction time so that it is pushed on the stream at the first write. This method often leads to complexities in buffered situations or transferring via pipes or sockets. Fortunately there is a just as simple as effective solution to all these problems: Flush the ObjectOutputStream immediately after contruction! Looking at the similarity in the byte sequence, it looks like either an endianess issue or an off-by-one error. Thank you for providing the workaround, I'll set up the buildslave using JNLP.

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/d/optout.