[JIRA] [core] (JENKINS-21913) java.io.StreamCorruptedException: invalid type code: 41 occured at end of build.

2014-09-01 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 commented on  JENKINS-21913


java.io.StreamCorruptedException: invalid type code: 41 occured at end of build.















Jenkins slaves communicate via stdout with the master. Regular standard output is redirected to not interfere. Slave VM crash messages still write to stdout, as may this output.



























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.


[JIRA] [core] (JENKINS-21913) java.io.StreamCorruptedException: invalid type code: 41 occured at end of build.

2014-03-04 Thread mlandma...@gmail.com (JIRA)














































boris ivan
 commented on  JENKINS-21913


java.io.StreamCorruptedException: invalid type code: 41 occured at end of build.















Occurred again today with build 1.553.

Interestingly, while I see the same stack trace later in the build as described above, I do notice some odd output slightly earlier than the stack trace.

The Maven goals this is executing are: integration-test site site:deploy

When executing the maven goal "site", it generates javadocs and a few other standard reports. It looks like it is progressing along, and then I see the following strange output below:

08:35:17 Constructing Javadoc information...
08:35:17 Standard Doclet version 1.7.0_40
08:35:17 Building tree for all the packages and classes...
...
...
08:35:17 200 warnings
08:35:17 WARNING Javadoc Warnings
08:35:17 WARNING C:\Jenkins\workspace[redacted].java:27: warning - @count is an unknown tag.
08:35:17 WARNING C:\Jenkins\workspace[redacted].java:27: warning - @volname is an unknown tag.
08:35:17 WARNING C:\Jenkins\workspace[redacted].java:80: warning - @return tag has no arguments.
08:35:17  [8mha:Yx+LCP9b85aBtbiIQSWjNKU4P0+vJLE4u1gvPjexLDVPzxdEhicW5WXmpfvll6S2fNly5fzGzauYGBgqihikoFqS8/OK83NS9ZwhNEghAwQwghQWAACwxA+XYg== [0mWARNING C:\Jenkins\workspace[redacted].java:80: warning - @param argument "hostIP" is not a parameter name.

Note the garbage above "8mha:Yx+LCAAA..."

Next, the site is deployed to an external web server (site:deploy).

After this, the 'maven' portion of the build is complete, and the email-ext plugin would normally fire. But this is what I see instead:

08:36:56 ERROR: Failed to parse POMs
08:36:56 hudson.remoting.ChannelClosedException: channel is already closed
08:36:56 	at hudson.remoting.Channel.send(Channel.java:524)
08:36:56 	at hudson.remoting.Request.call(Request.java:129)
08:36:56 	at hudson.remoting.Channel.call(Channel.java:722)
08:36:56 	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:167)
08:36:56 	at com.sun.proxy.$Proxy74.isAlive(Unknown Source)
08:36:56 	at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:930)
08:36:56 	at hudson.maven.ProcessCache$MavenProcess.call(ProcessCache.java:165)
08:36:56 	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:833)
08:36:56 	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:585)
08:36:56 	at hudson.model.Run.execute(Run.java:1676)
08:36:56 	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519)
08:36:56 	at hudson.model.ResourceController.execute(ResourceController.java:88)
08:36:56 	at hudson.model.Executor.run(Executor.java:231)
08:36:56 Caused by: hudson.remoting.DiagnosedStreamCorruptionException
08:36:56 Read back: 'o'
08:36:56 Read ahead: 'redacted.html#108"108/a/td/tr' 0x0d 0x0a
08:36:56 'tr class="b"' 0x0d 0x0a
08:36:56 'tdimg alt="Errors" src="" //td' 0x0d 0x0a
08:36:56 'tdLine is longer than 80 characters (found 82)./td' 0x0d 0x0a

Note the last line above. "Line is longer than 80 characters". That is something specific to the checkstyle reports, during the Maven "site" goal (I think). Hmm.



























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.


[JIRA] [core] (JENKINS-21913) java.io.StreamCorruptedException: invalid type code: 41 occured at end of build.

2014-02-21 Thread mlandma...@gmail.com (JIRA)














































boris ivan
 created  JENKINS-21913


java.io.StreamCorruptedException: invalid type code: 41 occured at end of build.















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


21/Feb/14 3:06 PM



Description:


Executing a Maven build with goal integration-test site site:deploy.

Everything goes as planned, and the website is published. At this point the email-ext plugin would typically fire. But here is the output:

An attempt to send an e-mail to empty list of recipients, ignored.
ERROR: Failed to parse POMs
hudson.remoting.ChannelClosedException: channel is already closed
	at hudson.remoting.Channel.send(Channel.java:524)
	at hudson.remoting.Request.call(Request.java:129)
	at hudson.remoting.Channel.call(Channel.java:722)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:167)
	at com.sun.proxy.$Proxy55.isAlive(Unknown Source)
	at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:930)
	at hudson.maven.ProcessCache$MavenProcess.call(ProcessCache.java:165)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:833)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:565)
	at hudson.model.Run.execute(Run.java:1670)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:231)
Caused by: hudson.remoting.DiagnosedStreamCorruptionException

At this point there is a lot of debug output from Jenkins of various buffers, etc. Unfortunately tons of proprietary info in those buffers so I'm not going to post here, though I could probably answer specific questions if it's essential.

The first set of messages are:

Read back: 'A'
Read ahead: '[Ljava.lang.Object;@28170a64]' 0x0d 0x0a

Later after a few pages of debug output, we see more of the stack, which seems fairly interesting..

	at hudson.remoting.FlightRecorderInputStream.analyzeCrash(FlightRecorderInputStream.java:71)
	at hudson.remoting.ClassicCommandTransport.diagnoseStreamCorruption(ClassicCommandTransport.java:94)
	at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:78)
	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
Caused by: java.io.StreamCorruptedException: invalid type code: 41
	at java.io.ObjectInputStream.readObject0(Unknown Source)
	at java.io.ObjectInputStream.readObject(Unknown Source)
	at hudson.remoting.Command.readFrom(Command.java:92)
	at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71)
	... 1 more





Environment:


Server and Remote Build Agent Windows 2012. Maven build.




Project:


Jenkins



Priority:


Critical



Reporter:


boris ivan

























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.


[JIRA] [core] (JENKINS-21913) java.io.StreamCorruptedException: invalid type code: 41 occured at end of build.

2014-02-21 Thread mlandma...@gmail.com (JIRA)














































boris ivan
 updated  JENKINS-21913


java.io.StreamCorruptedException: invalid type code: 41 occured at end of build.
















Change By:


boris ivan
(21/Feb/14 3:10 PM)




Environment:


ServerandRemoteBuildAgentWindows2012.Mavenbuild.
Jenkins1.551



























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.


[JIRA] [core] (JENKINS-21913) java.io.StreamCorruptedException: invalid type code: 41 occured at end of build.

2014-02-21 Thread mlandma...@gmail.com (JIRA)














































boris ivan
 commented on  JENKINS-21913


java.io.StreamCorruptedException: invalid type code: 41 occured at end of build.















I run the build agent (remote: Windows 2012) from the command line.

On that window, I see the following stack trace corresponding to the same time as the problem:

Feb 21, 2014 7:34:08 AM hudson.remoting.SynchronousCommandTransport$ReaderThread run
SEVERE: I/O error in channel channel
java.io.IOException: Unexpected termination of the channel
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
Caused by: java.io.EOFException
at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.readObject(Unknown Source)
at hudson.remoting.Command.readFrom(Command.java:92)
at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71)
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)



























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.