-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
Jenkins ver. 1.628, running directly as a Windows Service
hosted on Windows Server 2008
WebSphere ver. 8.5
WebSphere Deployer Plugin ver. 1.3.4
When configuring my Jenkins build to deploy to WebSphere, the connection test will succeed if I do not provide credentials (user / pw fields are blank). If I enter credentials, it will continue to succeed, but deployments fail with the error
Error deploying to IBM WebSphere Application Server: org.jenkinsci.plugins.websphere.services.deployment.DeploymentServiceException: Could not determine if artifact 'patient-portal-schedule-ear' is installed: ADMA0089E: The AppManagement MBean is not found.
If I then restart Jenkins, any connection test done with credentials provided fails with the error
Error opening socket: java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext); targetException=java.lang.IllegalArgumentException: Error opening socket: java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)]
If I clear the user / pw fields again, the connection test will succeed again, and continue to until I restart Jenkins again.
I realize probably need to go back and make sure that I've imported the (self-signed) certificate for the websphere host everywhere it needs to be, but this behavior seemed odd.