Failed to create BE instance error occurs in TIBCO BusinessEvents Enterprise Administrator Agent.
Article ID: KB0076563
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
Description
While deploying the TIBCO BusinessEvents application from TEA admin, the error "Failed to create BE instance " occurs.
The issue was because of referencing global variable in the logging (roles) section of the CDD
The error occurs when global variable was defined in the Log configuration roles section in the cdd file.
eg:
+++
<roles>%%Logger/Log_Level%%</roles>
+++
The issue was because of referencing global variable in the logging (roles) section of the CDD
The error occurs when global variable was defined in the Log configuration roles section in the cdd file.
eg:
+++
<roles>%%Logger/Log_Level%%</roles>
+++
Issue/Introduction
Failed to create BE instance error occurs in TIBCO BusinessEvents Enterprise Administrator Agent.
Environment
TIBCO BusinessEvents Enterprise Edition 5.x
All Operating Systems
Resolution
Log configurations roles are controlled and managed using TIBCO BusinessEvents Enterprise Administrator Agent.
The Log configuration roles should defined directly without using any global variables reference.
For example :
<roles>*:info</roles> or
<roles>*:debug</roles>
Using BE-TEA Agent, one can change the log level of an instance.
In TEA UI , select the Application and then select the Instance ==> Log Levels
The Log configuration roles should defined directly without using any global variables reference.
For example :
<roles>*:info</roles> or
<roles>*:debug</roles>
Using BE-TEA Agent, one can change the log level of an instance.
In TEA UI , select the Application and then select the Instance ==> Log Levels
Feedback
Yes
No
Powered by
