Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Shrikant Pustode (shrikantbp)
Amazon

Amazon
US
shrikantbp Member since 2014 25 posts
Amazon
Posted: Sep 12, 2017
Last activity: Sep 19, 2017
Posted: 12 Sep 2017 15:59 EDT
Last activity: 19 Sep 2017 13:33 EDT
Closed

JMS Listener - Run only one requestor at a time?

Hi,

We have configured a JMS MDB listener for a topic. It is targeted on one WebLogic backend node. JMS service package requestor pool limit is 10.

When server is restarted, Pega starts multiple requestors for JMS listener and picks up multiple JMS messages from topic.

We want to be able to pick up only one message from topic at a time. Pega doesn't seem to have any such setting or any control to stop creating multiple requestors at a time.

Any suggestions who we can ensure only one JMS listener requestor is created and only one message is processed?

Thanks,

Shrikant

To see attachments, please log in.
Data Integration

Posted: 7 years ago
Posted: 13 Sep 2017 2:06 EDT
Penchalanarasimhulu Vendipalli (Narasimha522)
PEGA
Senior Technical Solutions Engineer
Pegasystems Inc.
IN

this is expected behaviour as the topic contains multiple messages then App Server creates multiple MDB Listener instances to process simultaneously the messages. in case if you want to achieve i.e one MDB at a time you need to push one message at a time to topic or decrease the requestor pool size to 1 and in that scenario you may face performance issue hope this information helps you.

 

Thanks,

Narasimha

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice