Skip to main content

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.



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

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

******************************************************************************************************************************************
Labels:

Comments

Post a Comment

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...
Post a Comment
Read more

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...
Post a Comment
Read more

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. *********************************************************************************************...
Post a Comment
Read more