Why does the agent create a default transport (7500) even though the ADB sessions are configured to use non-default parameters?
Article ID: KB0087630
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for Database | - |
| Not Applicable | - |
Description
Resolution:
This is a problem with TIB/SDK 412 patch 2 on which ADB
is built. TIB/SDK 412 patch 4 has already fixed this. The TRA 1.0.3 includes SDK 4.1.2 patch 4. Please send a request to Support to get TRA 1.0.3 and fix this problem.
Following is the explanation from the readme.txt of SDK 4.1.2 patch 4:
- (C++) Fixed a defect where the Repository client would look for remote servers before checking to see if the instance was local or not. This results in a running RVD that can be undesirable in environments where executing an RVD is strictly controlled.
Current workaround: Don't use the default port 7500 in other TIBCO applications or send a request to Support to get TRA 1.0.3 and fix this problem.
This is a problem with TIB/SDK 412 patch 2 on which ADB
is built. TIB/SDK 412 patch 4 has already fixed this. The TRA 1.0.3 includes SDK 4.1.2 patch 4. Please send a request to Support to get TRA 1.0.3 and fix this problem.
Following is the explanation from the readme.txt of SDK 4.1.2 patch 4:
- (C++) Fixed a defect where the Repository client would look for remote servers before checking to see if the instance was local or not. This results in a running RVD that can be undesirable in environments where executing an RVD is strictly controlled.
Current workaround: Don't use the default port 7500 in other TIBCO applications or send a request to Support to get TRA 1.0.3 and fix this problem.
Issue/Introduction
Why does the agent create a default transport (7500) even though the ADB sessions are configured to use non-default parameters?
Feedback
Yes
No
Powered by
