Pega is hosted on Tomcat Tomcat does not have inbuilt JMS connection pooling and PEGA also does not provide connection pooling. Due, to this pega is opening lot of connections to the Tibco EMS server and the performance is also poor. We had a major Incident during the last disaster recovery test and now have restrictions on the number of connections that can be open and to implement connection pooling.
User has the following questions.
1. Is there any hotfix available for JMS connection pooling? 2. When can the fix be provided? 3. What are the alternatives? (Apart from Deploying to Enterprise Appication server)
***Moderator Edit-Vidyaranjan: Updated SR details***
Thanks Abhinav. We have Pega 7.2.1 hosted on Tomcat, and without JMS connection pooling, Pega is opening lot of connections to the Websphere IBM MQ server and the performance is weak when there is large volume of request. Hope the enhancement request works on Pega 7.2.1.