Intermitent HTTP 408 Connection Timeout Between OSB Proxy Service Call And GWWS SALT Server In Tuxedo (Doc ID 1948006.1)

Last updated on DECEMBER 05, 2016

Applies to:

Oracle Service Architecture Leveraging Tuxedo (SALT) - Version 11.1.1.2.0 and later
Information in this document applies to any platform.

Symptoms

When some tests are performed  the OSB invokes some services exposed by SALT in Tuxedo. These tests are getting a HTTP 408 timeout randomly.

The timeout definition is:

http-response-code 408 Request Timeout
The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time.


After GWWS tracing is turned on the only additional symptom noticed in the Tuxedo ULOG is:

123456.mymach!GWWS.12345678.2468.0: TRACE:ms:SCO[4095] FSM State Transition: --WAKEUP-->Created
123456.mymach!GWWS.12345678.2468.0: TRACE:ms:SCO[4095] FSM State Transition: --Inbound-->Receive
123456.mymach!GWWS.12345678.2468.0: TRACE:ms:SCO[4095] FSM State Transition: --Found-->ParseHTTP
123456.mymach!GWWS.12345678.2468.0: TRACE:ms:SCO[4095] FSM State Transition: --Fail-->Error
123456.mymach!GWWS.12345678.2468.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->Delete
123456.mymach!GWWS.12345678.3579.0: TRACE:ms:SCO[4095] FSM State Transition: --WAKEUP-->Created
123456.mymach!GWWS.12345678.3579.0: TRACE:ms:SCO[4095] FSM State Transition: --Inbound-->Receive
123456.mymach!GWWS.12345678.3579.0: TRACE:ms:SCO[4095] FSM State Transition: --Found-->ParseHTTP
123456.mymach!GWWS.12345678.3579.0: TRACE:ms:SCO[4095] FSM State Transition: --Fail-->Error
123456.mymach!GWWS.12345678.3579.0: TRACE:ms:SCO[4095] FSM State Transition: --OK-->Delete

  

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms