XML Gateway Fails to Initialize with Error 'java.lang.InstantiationException' after Application Of Critical Patch Update CPU Patch 20406628 (Doc ID 2017115.1)

Last updated on APRIL 04, 2025

Applies to:

Symptoms

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:

<Note 418926.1> - How to Configure OTA For XML Gateway in Release 12 (Doc ID 418926.1)

select * from v$session where action like'OXTA%';

Still does not return a row indicating OTA did not come up.

You have worked through:

<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 :

$LOG_HOME/ora/10.1.3/j2ee/oafm/oafm_<default_group_x>/log.xml

 <MSG_TEXT>Exception encountered:</MSG_TEXT>
  <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

Changes

 Installed E-Business Suite 12.1 Critical Patch Update (CPU) for April 2015 (<Patch 20406628>).  XML Gateway was functioning prior to this patch.

Cause