|
||||||||
|
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/d/optout.
The Java version, and AIX version with patch level is in the "Environment" section. I've not yet seen this on any other platform (including HP-UX, which is another non-Oracle JVM) so I'm not yet sure how to reproduce this somewhere sane.
I'm still working on this and I'll update the issue if I discover anything new.
I was poking around in the source code and, as a wild-ass guess, I think putting an serialVersionUID = 1 in the anonymous inner class in SSHAuthenticator.newInstance() might be the correct solution. I know we've had trouble in the past with different default serialVersionUIDs from different VMs when doing any kind of RMI.
Edit: I've not tried it yet, but I think an IBM VM (http://www.ibm.com/developerworks/java/jdk/) running on Linux might show the same behaviour. That would at least take AIX out of the mix. I'll see if I can break loose some time to experiment with that.