Skip to main content

Posts

Tibco R3 Adapter Error: java.lang.NullPointerException

Issue:   After upgrading the code to 7.2.0 it starts giving error like below Server Exception: Gateway Host: USMTGFCV6574D Gateway Service: sapgw02 Program ID: TIBSAP02 Error Message: java.lang.NullPointerException ****************************************************************************************************************************************** Complete Error: 2019 Mar 29 01:42:25:109 GMT -0700 Tibco_R3Adapter-Tibco_Outbound_R3Adapter Info [Application] AER3-000084 Received IDOC Name/Number/Receiving Partner: IDOCNEW-Offer03/000000101654285343/TIBSAP02, Count: 1 2019 Mar 29 01:42:25:341 GMT -0700 Tibco_R3Adapter-Tibco_Outbound_R3Adapter Info [Adapter] AER3-000091 Total IDOCs processed: 1 2019 Mar 29 01:42:25:342 GMT -0700 Tibco_R3Adapter-Tibco_Outbound_R3Adapter Info [Adapter] AER3-000199 Transaction rolled back 0A16A13406905C9DCF7D033D 2019 Mar 29 01:42:25:344 GMT -0700 Tibco_R3Adapter-Tibco_Outbound_R3Adapter Warn [Adapter] AER3-970276 Server Exception: Gatewa...

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. *********************************************************************************************...

Tibco BW Error: The markup in the document following the root element must be well-formed

Issue:  An error occurred while parsing:  The markup in the document following the root element must be well-formed ****************************************************************************************************************************************** Complete Error: <?xml version = "1.0" encoding = "UTF-8"?> <ns0:ErrorReport xmlns:ns0 = "http://www.tibco.com/pe/EngineTypes"> <StackTrace>Job-24000 Error in [Processes/Offer/NewOfferAdd.process/Parse XML] An error occurred while parsing:  The markup in the document following the root element must be well-formed.. at com.tibco.plugin.xml.XMLParseActivity.for(Unknown Source) at com.tibco.plugin.xml.XMLParseActivity.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$JobCour...

Tibco R3 Adapter Error : Mismatch found for service: ****, thread count: *, connection count: *

Issue: Mismatch found for service: OfferModfiyServer, thread count: 1, connection count: 30 ****************************************************************************************************************************************** Resolution: For all Inbound Adapter Configurations in code, go to Advanced Tab and configure ThreadCount.  It is better to configure a GV and use in all the adapter configurations. ****************************************************************************************************************************************** Details: The error defines that there is an mismatch in the number of threads and the number of connections used in client connection pool. Here, in my case it says connection count is 30 but the thread count is 1. So I configured the thread count to be 30 and the issue is resolved. ******************************************************************************************************************************...

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.Rende...

Tibco Rendezvous (RV): Monitoring and Troubleshooting

Once the setup is done, the most important thing is to monitor the connections, communication, transfer of messages and to troubleshoot the issues. This can be done through the means listed below. Monitoring and Troubleshooting: Below are the means available for monitoring and assessment: Rendezvous performance assessment software: It is a tool that measures the performance of RV in a running situation and provides a detailed output report. It consists of two executable programs: Rvperfm and rvperfs : These are the performance assessment tools which measures their capacity to receive messages as part of overall network performance. Rvperfm sends messages to the network and reports the statistics to stdout. Rvperfs listens for messages from rvperfm, gathers and reports statistics to rvperfm at the end of each run. Latency assessment software (rvlat): It is a latency assessment tool that measures the message latency that is the total time taken to send a m...

Tibco Rendezvous (RV): Virtual Circuit, Fault Tolerance and Current Value Cache

Virtual Circuit: Virtual circuit (VC) provides exclusive communication between two nodes. Only the two nodes can communicate with each other. The sender can only send messages to opposite node and the receiver can receive messages only from the opposite node. If there is a requirement where transport should be done among specific nodes and no other listener should get the information then VC should be used. Fault Tolerance: When the active program fails, the fault tolerance software directs one of the backup programs to become active and start processing. To configure programs in FT mode below parameters must be configured: Active Goal: It defines the total  number of active members. For example: If the active goal is set as 4, there will be 4 active members those have the highest ranks among all the members. Rank: Each program has a unique rank. If a program has N rank and another program has N+1 rank, then N is a higher rank than N+1. It determines the membe...