Troubleshooting
Problem
Changes were made on IBM Sterling Integrator in the customer override property file for ciphers and secure protocol .
After recycling IBM Sterling Integrator to put the changes into affect, Control Center could no longer attach to B2Bi.
Symptom
B2B ccinteropt logs showed no SOA Requests from IBM Control Center.
IBM Control Center Engine logs showed a handshake error on the initial connection attempt to B2Bi.
CGIS048E Error getting data from server.
Reason: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Message send failed
at com.sterlingcommerce.scc.agent.services.node.gis.GISUtil.getResults(GISUtil.java:461)
at com.sterlingcommerce.scc.agent.services.node.gis.GISNodeService.getResults(GISNodeService.java:2100)
at com.sterlingcommerce.scc.agent.services.node.gis.GISNodeService.setConsolidatedStatus(GISNodeService.java:1056)
at com.sterlingcommerce.scc.agent.services.node.gis.GISNodeService.signOn(GISNodeService.java:1402)
at com.sterlingcommerce.scc.agent.services.node.gis.GISTask.perform(GISTask.java:47)
at com.sterlingcommerce.scc.agent.services.node.Task.run(Task.java:92)
at java.util.TimerThread.mainLoop(Timer.java:566)
at java.util.TimerThread.run(Timer.java:516)
Caused by: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Message send failed
at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:161)
at com.sterlingcommerce.scc.agent.services.node.gis.GISUtil.getSOAPResponse(GISUtil.java:707)
at com.sterlingcommerce.scc.agent.services.node.gis.GISUtil.access$000(GISUtil.java:56)
at com.sterlingcommerce.scc.agent.services.node.gis.GISUtil$ResponseSetter.run(GISUtil.java:621)
Caused by: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Message send failed
at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:294)
at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:157)
... 3 more
Caused by: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
at com.ibm.jsse2.k.a(k.java:42)
at com.ibm.jsse2.k.a(k.java:37)
at com.ibm.jsse2.av.b(av.java:549)
at com.ibm.jsse2.av.a(av.java:715)
at com.ibm.jsse2.av.i(av.java:574)
at com.ibm.jsse2.av.a(av.java:280)
at com.ibm.jsse2.av.startHandshake(av.java:431)
at com.ibm.net.ssl.www2.protocol.https.c.afterConnect(c.java:167)
at com.ibm.net.ssl.www2.protocol.https.d.connect(d.java:62)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1346)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1321)
at com.ibm.net.ssl.www2.protocol.https.b.getOutputStream(b.java:53)
at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:249)
... 4 more
at com.sterlingcommerce.scc.agent.services.node.gis.GISUtil.getResults(GISUtil.java:461)
at com.sterlingcommerce.scc.agent.services.node.gis.GISNodeService.getResults(GISNodeService.java:2100)
at com.sterlingcommerce.scc.agent.services.node.gis.GISNodeService.setConsolidatedStatus(GISNodeService.java:1056)
at com.sterlingcommerce.scc.agent.services.node.gis.GISNodeService.signOn(GISNodeService.java:1402)
at com.sterlingcommerce.scc.agent.services.node.gis.GISTask.perform(GISTask.java:47)
at com.sterlingcommerce.scc.agent.services.node.Task.run(Task.java:92)
at java.util.TimerThread.mainLoop(Timer.java:566)
at java.util.TimerThread.run(Timer.java:516)
Caused by: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Message send failed
at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:161)
at com.sterlingcommerce.scc.agent.services.node.gis.GISUtil.getSOAPResponse(GISUtil.java:707)
at com.sterlingcommerce.scc.agent.services.node.gis.GISUtil.access$000(GISUtil.java:56)
at com.sterlingcommerce.scc.agent.services.node.gis.GISUtil$ResponseSetter.run(GISUtil.java:621)
Caused by: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Message send failed
at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:294)
at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:157)
... 3 more
Caused by: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
at com.ibm.jsse2.k.a(k.java:42)
at com.ibm.jsse2.k.a(k.java:37)
at com.ibm.jsse2.av.b(av.java:549)
at com.ibm.jsse2.av.a(av.java:715)
at com.ibm.jsse2.av.i(av.java:574)
at com.ibm.jsse2.av.a(av.java:280)
at com.ibm.jsse2.av.startHandshake(av.java:431)
at com.ibm.net.ssl.www2.protocol.https.c.afterConnect(c.java:167)
at com.ibm.net.ssl.www2.protocol.https.d.connect(d.java:62)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1346)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1321)
at com.ibm.net.ssl.www2.protocol.https.b.getOutputStream(b.java:53)
at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:249)
... 4 more
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"ARM Category":[{"code":"a8m3p000000GoRnAAK","label":"Advanced Communications-\u003ETroubleshooting"}],"ARM Case Number":"TS009794181","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2.6;6.0.0;6.1.0"},{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS9GLA","label":"IBM Control Center"},"ARM Category":[{"code":"a8m0z000000cx9aAAA","label":"B2B"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1.1;6.1.2;6.1.3"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
23 June 2026
UID
ibm16599233