When processing an inbound EDI file, the following exception is thrown:java.lang.NullPointerException at com.tibco.ax.tibedi.parser.EDINodeStoreFactory.getInstance . Edi node corrupted
book
Article ID: KB0090524
calendar_today
Updated On:
Products
Versions
TIBCO BusinessConnect EDI Protocol Powered by Instream
-
Not Applicable
-
Description
Resolution: Description: ============ When processing an inbound EDI file, the following exception is thrown: java.lang.NullPointerException at com.tibco.ax.tibedi.parser.EDINodeStoreFactory.getInstance . Edi node corrupted
Environment: ========== BC EDI 6.x , applicable to all Operating Systems
Symptoms: ========= When posting an inbound file , you could see the EDI node is invalid . The following exception is thrown in the interior logs
"java.lang.NullPointerException at com.tibco.ax.tibedi.parser.EDINodeStoreFactory.getInstance (EDINodeStoreFactory.java:83) at com.tibco.ax.tibedi.parser.EDINode.getStore(EDINode.java:49) at com.tibco.ax.tibedi.parser.EDINode.toStore"
Cause: ===== After an upgrade from an older environments BC 5.x/EDI 5.X to BC 6.x ( EDI version may be the same) the "edi.node.store.impl" property might not have been properly updated during the migration.
Resolution: ========= Under System Settings->tibEDI property "edi.node.store.impl" is string and should be a value of "ehcache". Even if it is set to "ehcache", the user may need to click on the drop down , select 'ehcache" again and click on the "Save" button. This insures that the right value is saved in the BC configuration store.
Issue/Introduction
When processing an inbound EDI file, the following exception is thrown:java.lang.NullPointerException at com.tibco.ax.tibedi.parser.EDINodeStoreFactory.getInstance . Edi node corrupted