|
||||||||
|
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.
Found this, and I had 2 virtual servers.
https://gist.github.com/andrewg4153/3693577
If you have a Glassfish domain with multiple virtual servers, you will be tempted to select them all when you deploy the Jenkins CI web application. This is a bad thing to do, as the Jenkins core code contains a singleton class: http://sorcerer.jenkins-ci.org/source-view.html?jenkins/model/Jenkins.js#678 When you do this, you'll get the following in your logs:
java.lang.IllegalStateException: second instance
at jenkins.model.Jenkins.<init>(Jenkins.java:744)
at hudson.model.Hudson.<init>(Hudson.java:81)
at hudson.model.Hudson.<init>(Hudson.java:77)
at hudson.WebAppMain$2.run(WebAppMain.java:217)
Just deploy to one of the virtual servers, and everything will be okay.
I deployed on 1 of them and it now works!
Well, I guess it's the bug to fix...