Last activity: 7 May 2017 21:39 EDT
Connect SOAP & JMS Connection Pool Handling
We are using TIBCO as middleware in our application to access external service via Connect-SOAP and Connect-JMS methods.
TIBCO team had reported that PEGA is opening multiple connections and which is causing overhead on the TIBCO side.
I would like to understand how connection are configured and managed within PEGA. As far as I am aware we don't have connection pool setting for connect requestors like we have for database.
Please share your thoughts.
***Updated by moderator: Lochan to add SR details***