After updating from BusinessEvents(BE) v4.0 to BusinessEvents(BE) v4.0.1 during startup a Resource$IOWrappedException for JMS is thrown.
Article ID: KB0089964
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Resolution:
Description:
============
After updating from BusinessEvents(BE) v4.0 to BusinessEvents(BE) v4.0.1 during startup a Resource$IOWrappedException for JMS is thrown.
Environment:
==========
TIBCO BusinessEvents Studio
Symptoms:
=========
1). During startup of BE, the foillowing message is printed in the log -
<Resource$IOWrappedException: Unresolved reference 'JMS' > occured.
2). Also, BE starts fine but no longer not communicates via JMS.
Cause:
=====
EAR was not rebuilt with version 4.0.1 when BE is upgraded from 4.0.0 to 4.0.1 .
Resolution:
==========
After EAR is rebuilt with the current installed version (i.e. 4.0.1), BE will start processing messages correctly.
Description:
============
After updating from BusinessEvents(BE) v4.0 to BusinessEvents(BE) v4.0.1 during startup a Resource$IOWrappedException for JMS is thrown.
Environment:
==========
TIBCO BusinessEvents Studio
Symptoms:
=========
1). During startup of BE, the foillowing message is printed in the log -
<Resource$IOWrappedException: Unresolved reference 'JMS' > occured.
2). Also, BE starts fine but no longer not communicates via JMS.
Cause:
=====
EAR was not rebuilt with version 4.0.1 when BE is upgraded from 4.0.0 to 4.0.1 .
Resolution:
==========
After EAR is rebuilt with the current installed version (i.e. 4.0.1), BE will start processing messages correctly.
Issue/Introduction
After updating from BusinessEvents(BE) v4.0 to BusinessEvents(BE) v4.0.1 during startup a Resource$IOWrappedException for JMS is thrown.
Feedback
Yes
No
Powered by
