Question
2
Replies
740
Views
Cts
Posted: March 19, 2019
Last activity: March 20, 2019
Closed
Information on JMS mdb listeners
Quick insight on JMS mdb listeners required.
1) Configured JMS mdb listener Point-To-Point (Not specific to individual node) with a JMS server and port. Able to listen messages.
Question: How multi nodes work here. All nodes listen to that specified queue continuously and any of the nodes failure has no impact?
2) Have multiple queues running on different jms servers and ports.
Question: To achieve this in multi node context, do we need to have the same equal no of listeners configured within PRPC.
Can a single JMS mdb configured to listen on Multiple JMS servers queues?
Any insight here or detailed document/link provided here appreciated.
Thanks.
Moderation Team has archived post,
Close popover
This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Pega deploys MDB through native application servers: https://community.pega.com/knowledgebase/articles/deploying-jms-message-driven-bean-mdb-represents-jms-mdb-listener-pega-7. For example, if you deploy an MDB in a Websphere cluster then all servers within the cluster will process messages. The onMessage is triggered by container listening to a JMS resources (e.g., queue or topic) defined by a JNDI name that the application server container can connect. In theory, you can hide all the JMS servers behind a logic JNDI resource. You only have to define one JMS MDB Listener instance, which is persisted in Pega database and available for all Pega nodes. Consult the documentation of your specific app server (We support Websphere/Weblogic/JBoss).
Hope this helps!