Question

2
Replies
63
Views
SAIKATROY Member since 2012 8 posts
Accenture
Posted: June 1, 2018
Last activity: June 7, 2018
Closed

JMS explorer causing Requestor lock exception in PEGA 7.3.1 personal edition

When clicked on down arrow in the connection factory dropdown or browse message option in the window that opens on click of JMS explorer button from JNDI server rule, the request was taking forever to complete. The personal edition installed on JBoss EAP 7 didn't have proper ActiveMQ/ JMS configuration done on JBoss, but my concern is the request to populate the JMS values is taking forever to complete and I needed to close the window forcefully. After that when I clicked on other links from developer portal or try to refresh the portal, I am getting requestor lock exception because the request opened on the JMS explorer window was still running in background and holds lock on requestor.

So, my question is how to timeout the request in JMS explorer window in case of any misconfiguration which causes JMS values to not get populated and avoids potential requestor lock exception?

***Edited by Moderator Marissa to update platform capability***

Data Integration
Moderation Team has archived post
Share this page LinkedIn