TIBCO BusinessEvents (BE) engine takes lot of time to start when you use JNDI lookup and set com.tibco.tibjms.connect.attempts property in CDD.
Article ID: KB0093997
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Resolution:
This solution applies to scenario where you have JMS reconnection parameters set in your CDD and you are using JNDI look-ups in your JMS connection. The cause of the issue is using the property "com.tibco.tibjms.connect.attempts" when you have JNDI lookups in your JMS connection configuration. After removing JNDI lookup from your JMS connection, the engines startup fine. So, to resolve the issue, either use the other JMS re-connection property property "be.jms.reconnect.timeout" to manage your JMS reconnect behavior or remove the JNDI lookups from your code. We feel the first option is easier and does not involve any project changes.
Issue/Introduction
TIBCO BusinessEvents (BE) engine takes lot of time to start when you use JNDI lookup and set com.tibco.tibjms.connect.attempts property in CDD.
Feedback
Yes
No
Powered by
