-
1. Re: TSSA 8.9.04 compatibility with BAO 7.9.01.001
Bill RobinsonFeb 25, 2019 8:44 AM (in response to Markus Kruse)
The recieved error is: Error 25.02.2019 15:06:56 Failed to connect to Atrium Orchestrator, Please check AO configuration parameters or verify that AO is up and running.
where is this received ?
BAO certificate is up to date and TSSA certificates we're completly renewed last weekend.
bao certificate is up to date where ?
i believe there's a 'check connection' option in the ao config. what does that show ? anything in the appserver logs when you try and use the connection ?
-
2. Re: TSSA 8.9.04 compatibility with BAO 7.9.01.001
Markus Kruse Feb 25, 2019 8:53 AM (in response to Bill Robinson)Hello Bill,
the Error
"Error 25.02.2019 15:06:56 Failed to connect to Atrium Orchestrator, Please check AO configuration parameters or verify that AO is up and running."
is recieved in TSSA Workflowjob Log.
With BAO Certificate I mean the .keystore file in <install_dir> \BAO\CDP\tomcat\conf
The check in the AO config shows following: AO connection failed. Secure connection to AO failed, Please check your Secure connection setup.
In appserver log there is no error that seems to be together with the problem.
But there is indeed an error in appserver log
[BLSSOPROXY] javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
com.bladelogic.sso.engine.ClientDisconnectedException: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
at com.bladelogic.sso.engine.StreamMessaging.receiveMessage(StreamMessaging.java:145)
at com.bladelogic.sso.engine.StreamMessaging.receiveToken(StreamMessaging.java:243)
at com.bladelogic.om.infra.mfw.net.BlSessionServerConnection.authenticate(BlSessionServerConnection.java:245)
at com.bladelogic.om.infra.mfw.net.BlSessionNshServerConnection.internalHandshake(BlSessionNshServerConnection.java:161)
at com.bladelogic.om.infra.mfw.net.BlSessionNshServerConnection.doHandshake(BlSessionNshServerConnection.java:133)
at com.bladelogic.om.infra.mfw.fw.BlSessionNshProxyPair.setupClient(BlSessionNshProxyPair.java:318)
at com.bladelogic.om.infra.mfw.fw.BlSessionNshProxyPair.init(BlSessionNshProxyPair.java:164)
at com.bladelogic.om.infra.mfw.fw.NshProxyWorkerThread.execute(NshProxyWorkerThread.java:113)
at com.bladelogic.om.infra.mfw.fw.NshProxyWorkerThread.execute(NshProxyWorkerThread.java:24)
at com.bladelogic.om.infra.app.service.thread.BlBlockingThread.run(BlBlockingThread.java:104)
Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:994)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367)
at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:931)
at sun.security.ssl.AppInputStream.read(AppInputStream.java:105)
at sun.security.ssl.AppInputStream.read(AppInputStream.java:71)
at com.bladelogic.om.infra.mfw.fw.BlSessionNshProxyPair.handleNshProxySessionData(BlSessionNshProxyPair.java:173)
at com.bladelogic.om.infra.mfw.fw.BlSessionNshProxyPair.setupClient(BlSessionNshProxyPair.java:314)
... 4 more
Caused by: java.io.EOFException: SSL peer shut down incorrectly
at sun.security.ssl.InputRecord.read(InputRecord.java:505)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.
but the error comes permanently whether I start a job or not
Greetings
Markus
-
3. Re: TSSA 8.9.04 compatibility with BAO 7.9.01.001
Bill RobinsonFeb 25, 2019 8:57 AM (in response to Markus Kruse)
that log entry is from the nsh proxy. i don't think that's involved in the appserver -> bao communication.
-
4. Re: TSSA 8.9.04 compatibility with BAO 7.9.01.001
Markus Kruse Feb 25, 2019 9:05 AM (in response to Bill Robinson)well
if TSSA should be compatible with BAo 7.9.01.001 it seems that i have to open a case for it.
Hoped that I just forgot to export some certificates or things like that.