Posted: 29 May 2019 11:33 EDT Last activity: 4 Nov 2019 4:37 EST
JMS Connection pooling on Tomcat
Our Pega Application 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 IBM WebSphere MQ and the performance is also poor. Earlier we had Websphere application platform which had an inbuilt connection pooling mechanism. Now, after migrating to Tomcat, we had a major problem on the number of connections that can be open and need to implement connection pooling for the queuing mechanism.
Is there any hotfix or solution available for JMS connection pooling on Tomcat server? How can we achieve JMS connection pooling on Tomcat ? (Apart from using Enterprise application server for Pega EAR file deployment).
***Edited by Moderator Marissa to update platform capability tags****
In general, Pega has no plan to provide any JMS connection pool implementation. If your backend message provider is still MQ, check IBM MQ for JMS APIs (also may need customization) or other vendors (e.g., Spring). Tomcat has a good integration with ActiveMQ (open source project). What is your use case with MQ within Pega? (e.g., Connect-JMS)
Initially we had WebSphere application platform where we had IBM WebSphere MQ for queuing mechanism to read and post messages. Recently, we migrated to Tomcat application server, and Tomcat doesn't support the JMS-MDB listener queuing mechanism nor connection pooling. As a result, we modified the context.xml and web.xml to integrate with the existing IBM Websphere MQ using JMS listeners, but now, trying to achieve connection pooling mechanism, as it is opening numerous connections while reading the messages and degrading the performance of the processing.
Also, IBM MQ 7.0 has depreciated functions for connection pooling. So we are trying to use Spring Jar. Can you help us to know how to wrap around Spring and IBM MQ with PRPC.
Unable to implement the following article directly in PRPC -
Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write Post button here. Once created, please reply here with the URL of the new post.
You may also refer this discussion link as a reference in the new thread.