What is the difference between tcp notion and tibjmsnaming notion in JNDI when providing a connect URL? Which one should be used?for example:tcp://hostname:7222 or tibjmsnaming://hostname:7222
Article ID: KB0092142
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
The first one (tcp://hostname:7222) can always be used. When you provide such a URL, the client specifies which protocol (tcp or ssl) to use to connect to the server.
The second one (tibjmsnaming://hostname:7222) can be used *only* if you are doing JNDI lookups. The value can be tcp or ssl depending on your environment.
tibjmsnaming will be resolved to "tcp", unless the context property TibjmsContext.SECURITY_PROTOCOL (com.tibco.tibjms.naming.security_protocol) is defined as "ssl".
The first one (tcp://hostname:7222) can always be used. When you provide such a URL, the client specifies which protocol (tcp or ssl) to use to connect to the server.
The second one (tibjmsnaming://hostname:7222) can be used *only* if you are doing JNDI lookups. The value can be tcp or ssl depending on your environment.
tibjmsnaming will be resolved to "tcp", unless the context property TibjmsContext.SECURITY_PROTOCOL (com.tibco.tibjms.naming.security_protocol) is defined as "ssl".
Issue/Introduction
What is the difference between tcp notion and tibjmsnaming notion in JNDI when providing a connect URL? Which one should be used?for example:tcp://hostname:7222 or tibjmsnaming://hostname:7222
Feedback
Yes
No
Powered by
