In an application, when maxQueueLength is set in both Global variables in Project code and in application.tra ofTIBCO BusinessWorks ProcessMonitor,which value is picked up?
Article ID: KB0092519
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessWorks ProcessMonitor | - |
| Not Applicable | - |
Description
Resolution:
For a
deployed application, if the global variable for maxQueueLength is set
(assume nJAMS/MemoryManagement/maxQueueLength=100) in Project code and the same property is also set in application.tra in TIBCO BusinessWorks ProcessMonitor to
another value (say JAMS/MemoryManagement/maxQueueLength=50), then the application.tra value is picked up. In this case, the value 50 will be picked up.
Consider the following cases:
Case 1: If an application is running from TIBCO Designer, that is, you are triggering jobs from Designer, and the global variable value for maxQueueLength is not defined, it will take a default value of 20.
Case 2: If an application is running from TIBCO Designer (jobs are being triggering from Designer), and the global variable value for maxQueueLength is set to a particular value, say 100, this length will be chosen as maxQueueLength.Case 3: If the application is a deployed application, and if the global variable value for maxQueueLength is set to a particular value in application.tra, say 100, that length is chosen as maxQueueLength.
Case 4: However, if the application is a deployed application, and if the global variable value for maxQueueLength in TIBCO Designer is set to a particular value, say 100, and nJAMS/MemoryManagement/maxQueueLength in application.tra is set to another value (say 50), then the value 50 is chosen as maxQueueLength.
Issue/Introduction
In an application, when maxQueueLength is set in both Global variables in Project code and in application.tra ofTIBCO BusinessWorks ProcessMonitor,which value is picked up?
Feedback
Yes
No
Powered by
