PEGA Application - JMS MDB Dependency
We have 3 applications deployed in PEGA.
1 . Application A has JMS MDB Listener configured for creating case via MQ.
2 . Application B and C - does not depend on this JMS MDB.
JMS Listener is configured as per the below URL.
We would like to start up PEGA Application when the MQ server goes down so that the Applications B and C are not impacted.
Steps Followed:
Tried to modify the Application XML / Deployment descriptor as per the below article, but that does not seem to work.
We have 3 applications deployed in PEGA.
1 . Application A has JMS MDB Listener configured for creating case via MQ.
2 . Application B and C - does not depend on this JMS MDB.
JMS Listener is configured as per the below URL.
We would like to start up PEGA Application when the MQ server goes down so that the Applications B and C are not impacted.
Steps Followed:
Tried to modify the Application XML / Deployment descriptor as per the below article, but that does not seem to work.
Pegasystems Inc.
US
If I understand your issue correctly, the Pega server cannot start up when the MQ is down. Have you tried to start up MDB with delivery attribute 'active' set to false: https://access.redhat.com/documentation/en-us/jboss_enterprise_application_platform_continuous_delivery/12/html/developing_ejb_applications/message_driven_beans-1.
Accenture Technology Solutions Pte Ltd
SG
Hi Kevin,
Thanks for the reply, I followed the suggested Jboss article to set the delivery mode, however I am unable to start the PEGA application yet.
Attached the jboss-ejb3.xml for reference.
Pegasystems Inc.
US
To be sure, the Test MDB does start up (along with Pega engine) if your message provider is up and running, right? If that is the case, you might be out of luck. You can double check with Redhat. I know even in Websphere, Pega engine would not start if message broker is down. Pega depends entirely on the underlying container for MDB deployment.