Products | Versions |
---|---|
TIBCO BusinessEvents Enterprise Edition | - |
Not Applicable | - |
Resolution
======
This may be due to some custom JAR files in the TRA classpath, which has a different implementation of a third party component, such as the log4j utility. To isolate the issue, we suggest you have your custom JAR files in a different directory structure so that it is not included in your deployed projects. It is easy to do a test by excluding these files from loading by changing the classpath in the .TRA files. The other possibility is due to the Security policy in your JRE. Make the appropriate changes to your JRE securtiy/policy files to avoid this issue.