Our enterprise app which used SIBus route for internal messaging, was asked to be changed to work with MDB using WebSphere MQ(external messaging requirement had also come up).
This application uses ejb-2.1, and is now deployed on WAS-126.96.36.199, and is configured to use JMS-Activation to work with the WMQ destination. Our customer initially did not have the WMQ infrastructure, so with the WAS configuration(JMS-Activation) done(JMS Resources) for our app, the app wouldn't start as the JMS Activation enabling failed. To correct this, we had suggested using WAS_EndpointInitialState(value as INACTIVE) JMS Activation custom property referring http://www.ibm.com/developerworks/websphere/library/techarticles/1104_madgula/1104_madgula.html?ca=drs.
Are there other ways to help protect the app deployed from failing to start up, because the JMS destination(WMQ) is unavailable, that is, ways to make the app independent(with respect to app start) of the JMS resources it use? In Messaging Listener Port based WAS configuration, it had the "Maximum number of retries" option, what is its equivalent in JMS Activation specification, that is, how message sending failure is to be handled?
This topic has been locked.
1 reply Latest Post - 2012-05-04T12:30:11Z by SystemAdmin
Pinned topic JMS Activation specifications, WMQ and app-packaging
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-05-04T12:30:11Z at 2012-05-04T12:30:11Z by SystemAdmin