My Oracle Support Banner

OEG Policy Studio Connection Problem In OEG Update After Changing Server Socket Connection Timeout Field in Policy Studio Preferences (Doc ID 1524028.1)

Last updated on OCTOBER 07, 2022

Applies to:

Oracle API Gateway - Version 11.1.1.4.0 to 11.1.1.6.1 [Release 11gR1]
Information in this document applies to any platform.

Symptoms

OEG Policy Studio suddenly fails to connect to the Gateway.  Policy Studio throws exceptions and/or crashes.  An already running and connected Policy Studio instance cannot deploy to the Gateway anymore.  The problem persists after restarting Policy Studio.  The problem can show up regardless whether Policy Center is used or not.

Example error messages by Policy Studio:

AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.SocketTimeoutException: Read timed out
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
at org.apache.axis.transport.http.HTTPSender.readHeadersFromSocket(HTTPSender.java:569)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:142)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
at org.apache.axis.client.Call.invoke(Call.java:2748)
at org.apache.axis.client.Call.invoke(Call.java:2424)
at org.apache.axis.client.Call.invoke(Call.java:2347)
at org.apache.axis.client.Call.invoke(Call.java:1804)
at com.vordel.pd.generated.DeploymentServiceSoapBindingStub.getProcessDetailsForID(DeploymentServiceSoapBindingStub.java:3804)
at com.vordel.pd.client.axis.AxisPolicyDirector.getProcessDetailsForID(AxisPolicyDirector.java:298)
at com.vordel.client.gui.policystudio.manager.ManagerRCP$7.run(ManagerRCP.java:1209)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)

{http://xml.apache.org/axis/}hostname:myhost
[...]
java.net.SocketTimeoutException: Read timed out
at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
at org.apache.axis.transport.http.HTTPSender.invoke(HTT

 

Example error messages in Gateway's trace file:

DEBUG   <TIMESTAMP> [<THREAD ID>] opdb commit loop: sleep for max 5000ms
FATAL   <TIMESTAMP> [<THREAD ID>] Failed relaying content (send failed)
ERROR   <TIMESTAMP> [<THREAD ID>] java exception running circuit:
java.lang.RuntimeException: send failed
        at com.vordel.dwe.NativeContentSource.relayN(Native Method)
        at com.vordel.dwe.NativeContentSource.relay(NativeContentSource.java:38)
        at com.vordel.mime.Body.write(Body.java:368)
        at com.vordel.dwe.http.ServerTransaction.sendResponse(Native Method)
        at com.vordel.dwe.http.HTTPPlugin.invokeDispose(HTTPPlugin.java:310)
        at com.vordel.dwe.http.HTTPPlugin.invoke(HTTPPlugin.java:131)

ERROR  <TIMESTAMP> [<THREAD ID>] error handling connection: connection closed

 

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
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.