Delayed engine startup of TIBCO BusinessEvents agent.
Article ID: KB0094075
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Description:
Delayed engine startup of TIBCO BusinessEvents agent .
Symptoms:
On startup of TIBCO BusinessEvents it take minutes to load the libraries and start the agent.
Cause:
Configuration issue
Delayed engine startup of TIBCO BusinessEvents agent .
Symptoms:
On startup of TIBCO BusinessEvents it take minutes to load the libraries and start the agent.
Cause:
Configuration issue
Issue/Introduction
Delayed engine startup of TIBCO BusinessEvents agent.
Resolution
1). Update the be-engine.tra file to load libraries by multiple loading threads.
java.property.be.catalog.loader.parallel=true
java.property.be.catalog.loader.threads=20
2). On Administrator deployment, a property in application.start.dir has been set which causes a delay with symbolic links referred due to empty homes present in the .tra file. The file is generated by admin after deployment. To avoid the issue, define dummy folders for all environment parameters.
java.property.be.catalog.loader.parallel=true
java.property.be.catalog.loader.threads=20
2). On Administrator deployment, a property in application.start.dir has been set which causes a delay with symbolic links referred due to empty homes present in the .tra file. The file is generated by admin after deployment. To avoid the issue, define dummy folders for all environment parameters.
Example.
tibco.env.PSP=\:
tibco.env.TIB_HOME=/opt/tibco/TIBCOAdmin
tibco.env.BE_HOME=/opt/tibco/TIBCOAdmin/be/5.2
tibco.env.AS_HOME=/opt/tibco/TIBCOAdmin/as/2.1
tibco.env.RV_HOME=/opt/tibco/TIBCOAdmin/tibrv/8.4
tibco.env.EMS_HOME=/opt
tibco.env.HAWK_HOME=/opt/tibco/TIBCOAdmin/hawk/5.1
tibco.env.TERR_HOME=/opt
tibco.env.FTL_HOME=/optAdditional Information
Feedback
Yes
No
Powered by
