|
||||||||
|
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.
I am experiencing the exact same issue on Tomcat 6.0. The 'test connection' button works fine, but the deployment fails. I'm not sure if this additional information is helpful in triangulating the issue or not. But I'll share, just in case. I am working in an environment where there are numerous firewalls. And as a temporary end-around to the firewall issue I first setup the connection between the Jenkins server and the WAS server by ssh tunneling around the firewall. This meant that I was configuring Jenkins to communicate with localhost:8879 and the tunnel took it to <was-server>:8879. In this configuration a connection was made and I would see entries in the Jenkins logging regarding whether or not the app being deployed was new or already existed, and that it was stopping the existing application. I would then get an error which is not relevant here. After the firewall issue was resolved in the appropriate way I was able to 'telnet <was-server> 8879' and see that the connection was made. I then updated the Jenkins config to use <was-server> instead of localhost. In this configuration the 'test connection' button works, but when I actually attempt to deploy, I get the exact same stacktrace as originally reported in this ticket.