Inbound AS2 messages fail to process with a java exception in the bcce-is logs

Inbound AS2 messages fail to process with a java exception in the bcce-is logs

book

Article ID: KB0072416

calendar_today

Updated On:

Products Versions
TIBCO BusinessConnect Container Edition 1.1.1

Description

During an inbound AS2 transaction, messages fail to get processed with the following java error in the bcce-is logs:
<<<
java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at com.tibco.ax.engine.job.Job.process(Job.java:178)
    at com.tibco.ax.engine.job.Job.run(Job.java:287)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NoClassDefFoundError: com/tibco/tibrv/TibrvException
    at com.tibco.ax.ezcomm.inbound.impl.EZIBBMHService.getBoInterceptor(EZIBBMHService.java:1000)
    at com.tibco.ax.ezcomm.inbound.impl.EZIBBMHService.handleAsyncMessage(EZIBBMHService.java:977)
    at com.tibco.ax.fw.runtime.inbound.impl.IBBMHService.processMsg(IBBMHService.java:300)
    at com.tibco.ax.fw.runtime.inbound.impl.DMZInboundJob.ibbmhProcess(DMZInboundJob.java:466)
    ... 9 more
Caused by: java.lang.ClassNotFoundException: com.tibco.tibrv.TibrvException
    at java.net.URLClassLoader.findClass(Unknown Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    ... 13 more
>>>

Environment

All platforms

Resolution

- To overcome this issue, please verify whether the protocol's jar file (for eg. bcce-ezcomm-1.1.1.jar) is present under the following path: bcce-is/bcce-is-version/lib/ in the image.

- After adding the jar file, rebuild the image, and.then redeploy and restart bcce-is and retry the transaction.

Issue/Introduction

Inbound AS2 messages fail to process with a java exception in the bcce-is logs