We have the same stack trace. We noticed this issue after upgrading Jenkins.

Jenkins ver. 1.480.3.1 (Jenkins Enterprise by CloudBees 12.11)
Slaves are Windows Server 2003 R2

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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to