My Oracle Support Banner

Gateway Does Not Complete Process Message (Doc ID 1598455.1)

Last updated on JULY 25, 2019

Applies to:

Oracle API Gateway - Version 11.1.1.6.1 and later
Information in this document applies to any platform.

Symptoms

Problem: The Gateway does not completely process a message body, for example when a response from a back end server is processed by a connection filter.

This may cause a variety of different symptoms.

Example exceptions observed with OEG 11.1.1.6.1:

ERROR <TIMESTAMP> [<THREAD ID>] nested fault: invalid response:
java.lang.RuntimeException: invalid response
at com.vordel.dwe.http.ClientTransaction.readResponse(Native Method)
at com.vordel.circuit.net.ConnectionProcessor$State.readResponse(ConnectionProcessor.java:408)
at com.vordel.circuit.net.ConnectionProcessor$State.tryTransaction(ConnectionProcessor.java:541)
at com.vordel.circuit.net.ConnectionProcessor.invoke(ConnectionProcessor.java:650)
at com.vordel.circuit.net.ConnectToURLProcessor.invoke(ConnectToURLProcessor.java:48)
at com.vordel.circuit.InvocationEngine.invokeFilter(InvocationEngine.java:154)
at com.vordel.circuit.InvocationEngine.invokeCircuit(InvocationEngine.java:43)
at com.vordel.circuit.CircuitDelegateProcessor.invoke(CircuitDelegateProcessor.java:38)
at com.vordel.circuit.InvocationEngine.invokeFilter(InvocationEngine.java:154)
at com.vordel.circuit.InvocationEngine.invokeCircuit(InvocationEngine.java:43)
at com.vordel.circuit.CircuitDelegateProcessor.invoke(CircuitDelegateProcessor.java:38)
at com.vordel.circuit.InvocationEngine.invokeFilter(InvocationEngine.java:154)
at com.vordel.circuit.DelegatingProcessor.callCircuit(DelegatingProcessor.java:49)
at com.vordel.circuit.CircuitChainProcessor.callCircuit(CircuitChainProcessor.java:59)
at com.vordel.circuit.switchcase.SwitchProcessor.invoke(SwitchProcessor.java:47)
at com.vordel.circuit.InvocationEngine.invokeFilter(InvocationEngine.java:154)
at com.vordel.circuit.InvocationEngine.invokeCircuit(InvocationEngine.java:43)
at com.vordel.circuit.InvocationEngine.processMessage(InvocationEngine.java:229)
at com.vordel.dwe.jms.JMSConsumer.processMessage(JMSConsumer.java:108)
at com.vordel.dwe.jms.JMSConsumer.run(JMSConsumer.java:217)
at java.lang.Thread.run(Thread.java:662)

The log also might show filters corresponding to these connections as aborted, like this:

ERROR   <TIMESTAMP> [<THREAD ID>]                        Policy '<POLICY>' {
ERROR   <TIMESTAMP> [<THREAD ID>]                             Filter 'Connect to URL <VIRTUAL PATH>' Status:  ABORTED
ERROR   <TIMESTAMP> [<THREAD ID>]                         }

Attempts to write the message to file may fail; for example, only message headers may be written to file.

Changes

The problem is more likely to occur if multiple requests for the same service are processed at the same time.

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
 Additional information


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