[SME-Comments] Customer How to resolve "RuntimeBootsrtap:sInit java.lang.NoClassDefFoundError: com/foresight/jinstreamapi/jNInStreamMsg" error?
Article ID: KB0086401
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessConnect EDI Protocol Powered by Instream | - |
| Not Applicable | - |
Description
Resolution:
Description:
============
How do I resolve "RuntimeBootsrtap:sInit java.lang.NoClassDefFoundError: com/foresight/jinstreamapi/jNInStreamMsg" error?
Environment:
============
TIBCO BusinessConnect EDI Protocol Version 6.x
Symptoms:
=========
When testing an inbound or outbound EDI transaction, the following error occurs. This is applicable to X12 also.
RuntimeBootsrtap:sInit Error initializing installed 'EDIFACT' protocol, from 'tibEDI' plugin with Runtime extension 'com.tibco.ax.tibedi.runtime.EDIBootStrapExtension'
[...]
RuntimeBootsrtap:sInit java.lang.NoClassDefFoundError: com/foresight/jinstreamapi/jNInStreamMsg
[...]
Cause:
======
During start up, the BC engine is not picking up the Instream and Translator API Jar files.
Resolution:
===========
Add the instreamapi.jar and fstransapi.jar files in to tibco.env.CUSTOM_EXT_PREPEND_CP (See the example below - modify it accordingly) in the deployed BC interior tra file. After confirming that the issue is resolved, make the same modification in the TIBCO_HOME/bin/bcengine.tra file. The next time the BC application is deployed, it will pick up these values automatically.
tibco.env.CUSTOM_EXT_PREPEND_CP=%TPCL_HOME%/lib/httpclient_3.0%PSP%%TPCL_HOME%/tomcat/common/lib/mail.jar%PSP%%TIB_HOME%/instream/8.3/java/instreamapi.jar%PSP%%TIB_HOME%/translator/3.3/java/fstransapi.jar
Description:
============
How do I resolve "RuntimeBootsrtap:sInit java.lang.NoClassDefFoundError: com/foresight/jinstreamapi/jNInStreamMsg" error?
Environment:
============
TIBCO BusinessConnect EDI Protocol Version 6.x
Symptoms:
=========
When testing an inbound or outbound EDI transaction, the following error occurs. This is applicable to X12 also.
RuntimeBootsrtap:sInit Error initializing installed 'EDIFACT' protocol, from 'tibEDI' plugin with Runtime extension 'com.tibco.ax.tibedi.runtime.EDIBootStrapExtension'
[...]
RuntimeBootsrtap:sInit java.lang.NoClassDefFoundError: com/foresight/jinstreamapi/jNInStreamMsg
[...]
Cause:
======
During start up, the BC engine is not picking up the Instream and Translator API Jar files.
Resolution:
===========
Make sure that the edi.tra file in \\tibco\bc\6.x\protocols\tibedi\bin\ has the correct Instream and Translator version references.Verify that the instreamapi.jar and fstransapi.jar files are included in "tibco.env.CUSTOM_EXT_PREPEND_CP" variable of edi.tra file.After updating this edi.tra file, you can redeploy the BC application in the administrator GUI and retest it. When you redeploy the BC application, it will read the edi.tra file and add the Instream and Translator references in BC interior server tra file.
If the problem still persists, try the following.
Add the instreamapi.jar and fstransapi.jar files in to tibco.env.CUSTOM_EXT_PREPEND_CP (See the example below - modify it accordingly) in the deployed BC interior tra file. After confirming that the issue is resolved, make the same modification in the TIBCO_HOME/bin/bcengine.tra file. The next time the BC application is deployed, it will pick up these values automatically.
tibco.env.CUSTOM_EXT_PREPEND_CP=%TPCL_HOME%/lib/httpclient_3.0%PSP%%TPCL_HOME%/tomcat/common/lib/mail.jar%PSP%%TIB_HOME%/instream/8.3/java/instreamapi.jar%PSP%%TIB_HOME%/translator/3.3/java/fstransapi.jar
Issue/Introduction
[SME-Comments] Customer
How to resolve "RuntimeBootsrtap:sInit java.lang.NoClassDefFoundError: com/foresight/jinstreamapi/jNInStreamMsg" error?
Feedback
Yes
No
Powered by
