My Oracle Support Banner

iPayment Auth Out Of Sync With FDC - iPayment Times Out (Doc ID 1099053.1)

Last updated on MARCH 11, 2019

Applies to:

Oracle Payments - Version 11.5.10.2 to 11.5.10.3 [Release 11.5]
Information in this document applies to any platform.

Symptoms

Find that iPayment authorizations with FDC are sometimes going out of sync. When this occurs, iPayment times out. iPayment never syncs up until Apache is bounced.

Auth works fine until a point when one of the auths fails with timeout exception. After this failure, all subsequent auths fail until Apache is bounced. FDC did receive the transaction and was able to authorize the transaction, but from the iPayment logs it appears that even though there was a response, it still did not update the response and instead considered it as timed out. The associated auth record in IBY_TRXN_SUMMARIES_ALL has status 9. An extract of an example iPayment log looks like this:

Mar 1, 2010 5:45:37 PM
iby.net.NetUtils.writeHttpPost]:phase 3: writing POST body

Mar 1, 2010 5:45:37 PM
iby.exception.Log.debug.generic]:written:=

>>> then there is a time gap of 50 seconds

Mar 1, 2010 5:46:27 PM
iby.net.NetUtils.writeHttpPost]:bytes read in response=789

iby.net.NetUtils.writeHttpPost]:closing socket

iby.net.NetUtils.parseHttpResponse]:raw response:

<MessageStatus>IO_ERROR</MessageStatus>
<ErrorCode>Time Out - Response not received </ErrorCode>

As a result of this, customer's credit cards are having a funds hold due to the authorization being successful in FDC but this is not reflected in iPayment due to the timeout error.

Changes

 

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


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