XML Gateway Fails to Initialize with Error 'java.lang.InstantiationException' after Application Of Critical Patch Update CPU Patch 20406628
Last updated on NOVEMBER 01, 2017
Applies to:Oracle XML Gateway - Version 12.0.6 to 12.1.3 [Release 12 to 12.1]
Oracle E-Business Suite Technology Stack - Version 12.0.6 to 12.1.3 [Release 12.0 to 12.1]
Oracle E-Business Suite Integrated SOA Gateway - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
After installation of the E-Business Suite 12.1 Critical Patch Update (CPU) for April 2015 (<Patch 20406628>), XML Gateway is no longer functioning. Relevant services start up with no problem, but the ../webservices/ECXOTAInbound url is no longer available because OTA is not up. You have verified that the ASADMIN account is unlocked and have applied the correct ASADMIN password to the j2ee oafm system-jazn-data.xml file. You have also reviewed all relevants notes, eg:
Still does not return a row indicating OTA did not come up.
You have worked through:
<Note 1267410.1> - OXTA Not Starting In R12
<Note 1087499.1> - Cannot Start OXTA After Upgrade To R12.1.x
After enable logging for OAFM by following <Note 419839.1> - How to enable Apache, OC4J and OPMN logging in Oracle Applications R12', the following is observed in :
<SUPPL_DETAIL><![CDATA[java.lang.InstantiationException: Application: oafm is in failed state as initialization failed
Caused by: java.lang.InstantiationException: Error occurred initializing connectors. Exception is: Exception creating connection pool. Exception: oracle.oc4j.sql.DataSourceException: Exception setting the property 'dbcFile' on the DataSource. Exception: java.lang.reflect.InvocationTargetException
Installed E-Business Suite 12.1 Critical Patch Update (CPU) for April 2015 (<Patch 20406628>). XML Gateway was functioning prior to this patch.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms