I am creating an application that will send java objects via the TIB.Is it better to create and destroy transports when sending objects or to create one transport and leave it open for the duration of the application?
Article ID: KB0089852
Updated On:
| Products | Versions |
|---|---|
| TIBCO Rendezvous | - |
| Not Applicable | - |
Description
Resolution:
We do not recommend creating (and destroying) a transport for each message published, instead client application should try to reuse the connection.
It is up to the application developer to determine how they want connections reused. We do recommend that connections be "long-lived" though since it is generally not a good practice to create the connection, create a transport, send a message, and then close everything down. It is much more efficient for resources to be re-used as much as possible.
We do not recommend creating (and destroying) a transport for each message published, instead client application should try to reuse the connection.
It is up to the application developer to determine how they want connections reused. We do recommend that connections be "long-lived" though since it is generally not a good practice to create the connection, create a transport, send a message, and then close everything down. It is much more efficient for resources to be re-used as much as possible.
Issue/Introduction
I am creating an application that will send java objects via the TIB.Is it better to create and destroy transports when sending objects or to create one transport and leave it open for the duration of the application?
Feedback
Yes
No
Powered by
