In Siebel 23.X When Trying To Deploy A New Siebel Server From SMC An Error Message Is Being Reported: "com.siebel.opcgw.cloudgateway.CGServer: Error : could not read the packet"
(Doc ID 3004774.1)
Last updated on FEBRUARY 26, 2024
Applies to:
Siebel CRM - Version 23.8 and laterInformation in this document applies to any platform.
Symptoms
In Siebel version 23.X when attempting to deploy a Siebel server from SMC into the "cloudgateway.log" file the following error occurs:
ERROR
-----------------------
[ERROR] 2024-01-25 14:33:31.613 [https-jsse-nio-8090-exec-5] CG_LOGGER - com.siebel.opcgw.cloudgateway.config.GatewayClusterResource: Gateway Cluster deployment not configured
[ERROR] 2024-01-25 14:33:31.614 [https-jsse-nio-8090-exec-5] CG_LOGGER - com.siebel.opcgw.cloudgateway.config.GatewayClusterResource: End :GET on gatewaycluster deployment
[ERROR] 2024-01-25 14:35:32.033 [Thread-2] CG_LOGGER - com.siebel.opcgw.cloudgateway.CGSSLCommServer: SSL handshake failed:Connection reset
[ERROR] 2024-01-25 14:35:32.033 [Thread-2] CG_LOGGER - com.siebel.opcgw.cloudgateway.CGSSLCommServer:
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:210) ~[?:1.8.0_361]
at java.net.SocketInputStream.read(SocketInputStream.java:141) ~[?:1.8.0_361]
at sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:475) ~[?:1.8.0_361]
at sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:469) ~[?:1.8.0_361]
at sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:159) ~[?:1.8.0_361]
at sun.security.ssl.SSLTransport.decode(SSLTransport.java:111) ~[?:1.8.0_361]
at sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1320) ~[?:1.8.0_361]
at sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1233) ~[?:1.8.0_361]
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:417) ~[?:1.8.0_361]
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:389) ~[?:1.8.0_361]
at com.siebel.opcgw.cloudgateway.CGSSLCommServer.accept(CGSSLCommServer.java:123) [opcgw.jar:?]
at com.siebel.opcgw.cloudgateway.CGServer.run(CGServer.java:59) [opcgw.jar:?]
at java.lang.Thread.run(Thread.java:750) [?:1.8.0_361]
Additionally to previous errors in same "cloudgateway.log" file there is another raised error when a packet is readout:
[ERROR] 2024-01-25 14:55:59.621 [Thread-31] CG_LOGGER - com.siebel.opcgw.cloudgateway.CGServer:
java.io.IOException: could not read the packet
at com.siebel.opcgw.cloudgateway.CGPacket.readPacket(CGPacket.java:52) ~[opcgw.jar:?]
at com.siebel.opcgw.cloudgateway.CGSSLCommServer.read(CGSSLCommServer.java:140) ~[opcgw.jar:?]
at com.siebel.opcgw.cloudgateway.CGServer$1.run(CGServer.java:86) [opcgw.jar:?]
at java.lang.Thread.run(Thread.java:750) [?:1.8.0_361]
[ERROR] 2024-01-25 14:55:59.634 [Thread-31] CG_LOGGER - com.siebel.opcgw.cloudgateway.CGServer: Error : could not read the packet
The environment behavior can be reproduced by blocking the Siebel default ports in the local firewall.
Changes
The environment behavior is reported after installing a new Siebel environment.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |