Skip to main content

Tibco BW Error "Exception in parse eval: [Ljava.lang.Object;@****]"


Issue: Exception in parse eval: [Ljava.lang.Object;@124bf39b

******************************************************************************************************************************************
Complete Error:

<?xml version = "1.0" encoding = "UTF-8"?>
<ns0:ErrorReport xmlns:ns0 = "http://www.tibco.com/pe/EngineTypes">
<StackTrace>Job-6000 Error in [Processes/ABC.process/Header Group/RenderE1EDL20]
Exception in parse eval: [Ljava.lang.Object;@124bf39b.
at com.tibco.plugin.parse.RenderActivity.eval(Unknown Source)
at com.tibco.pe.plugin.Activity.eval(Unknown Source)
at com.tibco.pe.core.TaskImpl.eval(Unknown Source)
at com.tibco.pe.core.Job.a(Unknown Source)
at com.tibco.pe.core.Job.k(Unknown Source)
at com.tibco.pe.core.JobDispatcher$JobCourier.a(Unknown Source)
at com.tibco.pe.core.JobDispatcher$JobCourier.run(Unknown Source)
caused by: java.io.IOException
at com.tibco.plugin.parse.RenderActivity.eval(Unknown Source)
at com.tibco.pe.plugin.Activity.eval(Unknown Source)
at com.tibco.pe.core.TaskImpl.eval(Unknown Source)
at com.tibco.pe.core.Job.a(Unknown Source)
at com.tibco.pe.core.Job.k(Unknown Source)
at com.tibco.pe.core.JobDispatcher$JobCourier.a(Unknown Source)
at com.tibco.pe.core.JobDispatcher$JobCourier.run(Unknown Source)
</StackTrace>
<Msg>Exception in parse eval: [Ljava.lang.Object;@124bf39b.</Msg>
<FullClass>com.tibco.plugin.parse.BadDataFormatException</FullClass>
<Class>BadDataFormatException</Class>
<ProcessStack>Processes/ABC/ABC.process/REST Dispatch and Reply>Processes/ABC/ABC.process/ABC Group/SegmentCreation_ABC>Processes/ABC/ABC.process/Header Group/RenderE1EDL20</ProcessStack>
<MsgCode>BW-PARSE-100002</MsgCode>
<Data>
<BadDataFormatException>
<msg>Exception in parse eval: [Ljava.lang.Object;@124bf39b.</msg>
<msgCode>BW-PARSE-100002</msgCode>
</BadDataFormatException>
</Data>
</ns0:ErrorReport>

******************************************************************************************************************************************
Resolution:
Go to the Data Format and check the Field Offsets. There will be some fields for which the start and end is not defined. Define the start and end positions properly and test again.

******************************************************************************************************************************************
Details:
The error defines that there is an issue with the data format. So check the data format definition. For me some new fields got added in SAP which were fetched when I refreshed the schema on upgrading the code. For these fields, start and end were zero so it caused this error.

So this occurs when new fields get added in data format schema for which the start and end is not defined. This may happen when we refresh SAP schema and some new fields are added at sap end which are not known to us. While upgrading as well some new fields may get added that are not required for business but are there in SAP and can get added to data format.
So set the fields with proper line length, start and end and your issue will be resolved.

******************************************************************************************************************************************
Note: If you see this error in any other case then do share the details with me . :-)

******************************************************************************************************************************************



Comments

Popular posts from this blog

Tibco Rendezvous (RV): Transport and More

Transport: It is the mechanism for sending and delivering messages. There are three main parameters in Tibco RV for transport: network, daemon and service. Service is specific to programs. Multiple programs may be running on a network. Each program has a different service. There can be many services running under a daemon for different programs. Network parameter specifies the interface for multicast communication from a program. A specific network should be selected for  outbound multicast Rendezvous communications. Daemon specifies the port where RV daemon runs. RV communicates through this daemon and hence remote daemon must be specified to support network communications. Tibrvsend and Tibrvlisten: Every Tibco RV installation provides these two utilities for sending and receiving messages on any multicast network. Sample for testing these utilities: tibrvlisten.exe -service 7576 -network 10.21.6.38 -daemon tcp:7500 "TEST" tibrvsend.exe -s...

Tibco Rendezvous (RV): Features and More

Features of Tibco RV: Decoupling and Data Independence : In RV the applications are loosely coupled and RV has self-describing data that makes it easy for the applications to share data. Location Transparency : RV is based upon subject based addressing. The data/messages are sent and received over subject; hence the programs can communicate without knowing the network details. Architectural Emphasis on Information Sources and Destinations : RV provides efficient solutions for developing distributed system by emphasis on identifying sources and destinations of information. Reliable Delivery: RV provides reliable delivery of messages and without the need of network details. The information like network details and packet transfer are hidden. Certified Message Delivery: Some applications require more assurance for message delivery. For this RV provides Certified Message (CM) delivery which sends the confirmation for the messages received. Distribu...

How to add JCO Trace?

Requirement: To debug an issue and to check the data flowing through Tibco R3 adapter enable SAP JCo trace. Once the trace is enable it creates JCo tracing files in the specified location. These files have details of the JCo library, versions and JCo paths. It will show a complete trace log of the fields/segments in the adapter and it's tables and the input/output data that is flowing through the adapter. ************************************************************************************************************************************************ Steps: Add below properties in the adr3.tra file to enable SAP JCo trace: ===== java.property.jco.trace_level=8 java.property.jco.trace_path=<The path of the directory where the JCo trace file will be generated> ===== Restart the SAP adapter instance. Once you test, the JCo files will be created in the specified location. *********************************************************************************************...