What do the arguments in trace message mean: TAL-SS-10032-I RTclient {'Some_RTclient', '/foo_client', 'orion', 12345, some_user, hp700_hpux, 78} UP ?
Article ID: KB0091773
Updated On:
| Products | Versions |
|---|---|
| TIBCO SmartSockets | - |
| Not Applicable | - |
Description
Resolution:
This message is seen as part of the connection process between an RTclient and RTserver. The RTclient is identifying itself to the RTServer.
Field 1: Some_RTclient - The ident string of the RTclient – set with the API call to TipcMonSetIdentStr
Field 2: /foo_client - The unique subject of client
Field 3: orion - the node_name of the host where the RTclient resides
Field 4: 12345 - the PID of the RTclient process
Field 5: some_user – The username/ID who launched the RTclient
Field 6: hp700_hpux – The RTARCH where RTclient process resides.
Field 7: 78 - Used by Tibco internally.
This message is seen as part of the connection process between an RTclient and RTserver. The RTclient is identifying itself to the RTServer.
Field 1: Some_RTclient - The ident string of the RTclient – set with the API call to TipcMonSetIdentStr
Field 2: /foo_client - The unique subject of client
Field 3: orion - the node_name of the host where the RTclient resides
Field 4: 12345 - the PID of the RTclient process
Field 5: some_user – The username/ID who launched the RTclient
Field 6: hp700_hpux – The RTARCH where RTclient process resides.
Field 7: 78 - Used by Tibco internally.
Issue/Introduction
What do the arguments in trace message mean: TAL-SS-10032-I RTclient {'Some_RTclient', '/foo_client', 'orion', 12345, some_user, hp700_hpux, 78} UP ?
Feedback
Yes
No
Powered by
