My Oracle Support Banner

Problem in BRM JCA Adapter "Org.Xml.Sax.Saxparseexception:Field 'XXX' Not Found In BRM" (Doc ID 1329651.1)

Last updated on JUNE 06, 2018

Applies to:

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

Symptoms

When trying to send message to BRM through BRMJCAAdapter, see below error:

SAX Exception when converting flist to XML:

org.xml.sax.SAXParseException: field 'CMAS_FLD_TABLAM_TEL' not found in BRM
at oracle.tip.adapter.brm.BRMXMLToFlist.processField(Unknown Source)
at oracle.tip.adapter.brm.BRMXMLToFlist.traverseFlist(Unknown Source)
at oracle.tip.adapter.brm.BRMXMLToFlist.parseDoc(Unknown Source)
at oracle.tip.adapter.brm.BRMXMLToFlist.convert(Unknown Source)
at oracle.tip.adapter.brm.BRMOpcodeCaller.convertXMLDocToFlist(Unknown Source)
at oracle.tip.adapter.brm.BRMOpcodeCaller.execOpcode(Unknown Source)
at oracle.tip.adapter.brm.BRMInteraction.callOpcode(Unknown Source)
at oracle.tip.adapter.brm.BRMInteraction.execute(Unknown Source)
at oracle_tip_adapter_brm_BRMInteraction_Proxy.execute()
atoracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:486)
at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:479)
at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:529)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:286)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:829)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:412)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:199)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3714)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1657)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:220)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:325)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5787)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1089)
at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.__createAndInvoke(CubeEngineBean.java:127)
at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.createAndInvoke(CubeEngineBean.java:170)
at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.syncCreateAndInvoke(CubeEngineBean.java:190)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
at com.evermind.server.ThreadState.runAs(ThreadState.java:693)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.TxRequiresNewInterceptor.invoke(TxRequiresNewInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterce


Note: CMAS_FLD_TABLAM_TEL is a custom field.

This is not the first time adding a custom field, it always used to work. The user changed a custom field type, kept the same name, and followed the same steps to package the new custom jar file and JCA adapter rar file, and then undeployed the old rar file and deployed the new one. But the new one is giving the above error.

Later, the user regenerated the archives of BRM and have it deployed on two servers:
Server 1 - SOA 10.1.3.4 MLR9 with Java 1.5.0_6 in OAS, on this server adapter can not recognize custom fields
Server 2 - SOA 11.1.1.3 with Java 1.6 on Weblogic, on this server the adapter works properly.

Software versions:
Oracle AIA 2.5 Communications IPS1
SOA 10.1.3.4 MLR#9
10.2.0.3 EE
ODI 10.1.3.5.3
BRM 7.4 (PS7)

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.