BE 3.0 Decision Manager fails to communicate with RMS and also error Unhandled event loop exception is thrown in Decision Manager stack trace.
Article ID: KB0091734
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Resolution:
1. Search for file (using windows explorer) "commons-codec-1.3.jar".
2. Make sure only one jar is in the machine/classpath and that too in location "C:\tibco\tpcl\5.5\lib\httpclient_3.0".
3. If you found this jar at other locations, try to move it away from the classpath.
4. Also if "commons-codec-1.3.jar" is not found at location ""C:\tibco\tpcl\5.5\lib\httpclient_3.0\", copy this jar in this
directory and remove this jar from any other location in <TIBCO_HOME> directory.
After following these steps, restart RMS and Decision Manager and then DM will be able to communicate to RMS.
1. Search for file (using windows explorer) "commons-codec-1.3.jar".
2. Make sure only one jar is in the machine/classpath and that too in location "C:\tibco\tpcl\5.5\lib\httpclient_3.0".
3. If you found this jar at other locations, try to move it away from the classpath.
4. Also if "commons-codec-1.3.jar" is not found at location ""C:\tibco\tpcl\5.5\lib\httpclient_3.0\", copy this jar in this
directory and remove this jar from any other location in <TIBCO_HOME> directory.
After following these steps, restart RMS and Decision Manager and then DM will be able to communicate to RMS.
Issue/Introduction
BE 3.0 Decision Manager fails to communicate with RMS and also error Unhandled event loop exception is thrown in Decision Manager stack trace.
Feedback
Yes
No
Powered by
