My Oracle Support Banner

BRM JCA Adapter Error: "Exception occured during invocation of JCA binding" (Doc ID 1535830.1)

Last updated on JULY 31, 2020

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Information in this document applies to any platform.


After upgraded to Billing and Revenue Management (BRM) 7.4 Patch-Set (PS) 16, the BRM J2EE Connector Architecture (JCA) Adapter on Oracle service-oriented architecture (SOA) 11g stopped working with custom fields.


NOTE: All OPCODE callers without custom fields worked successful. All these calls with custom fields on SOA 10g worked fine.

The user has followed the workaround as suggested in the Note 1329651.1 "Problem In BRM JCA Adapter "Org.Xml.Sax.Saxparseexception:Field 'XXX' Not Found In BRM", but it did not help.

The user has recompiled the customfields.jar with BRM JDK and recompiled the source classes with SOA JDK (same JDK version 1.6 on the BRM system and SOA system), but this was still not working.


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

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