Question
AMERICAN EXPRESS
US
Last activity: 11 Apr 2017 19:59 EDT
REST Connector Connection pool settings inside pega or application server
The application has REST connectors to publish message on solace queue using POST method. The solace has configuration to set max connection size. Once reached max size, solace is not accepting more connections.
Could we configure max connection limit in side pega application. At run time, before publishing message, Pega should be able to verify how many connections already opened before publishing message on solace queue. It would be able to publish later by queue items.
Please respond what options we have to configure the max connection limit either on pega or application server hosted the pega applications.
***Moderator Edit: Vidyaranjan | Tagged SRExists***
Pegasystems Inc.
IN
Hi Radhakrishnaraj,
Once the service package is created , you can go to the pooling tab of the service package and configure.
Hope this helps.
AMERICAN EXPRESS
US
HI Abhishek,
The service package would allow to configure connection settings for Services (Rest, soap, etc) developer inside pega application to server external customers. Here we are looking for max connections to be established by pega application to service on external server.
1) Pega's REST connector => The Pega application would publish message on solace queue using this connector.
2) Solace Queue => This queue has max connections configuration similar to how service package has max connections inside pega.
Due to multi-node environment and heavy traffic during peak hours, there are number of REST connections establishing between Pega application and solace queue. Even Solace queue was already configured huge number as max connections, however connection count reaching the max configuration during peak hours and creating production support incidents due to out of connections available.
To handle the situation better, we would like avoid connections when it reach certain limit. we are looking for options.
Q1) Check the number of connections already established on the queue already. How to find count of live connections established by node where the current thread running to solace queue? How to find count of live connections from all nodes (in multi node environment)?
HI Abhishek,
The service package would allow to configure connection settings for Services (Rest, soap, etc) developer inside pega application to server external customers. Here we are looking for max connections to be established by pega application to service on external server.
1) Pega's REST connector => The Pega application would publish message on solace queue using this connector.
2) Solace Queue => This queue has max connections configuration similar to how service package has max connections inside pega.
Due to multi-node environment and heavy traffic during peak hours, there are number of REST connections establishing between Pega application and solace queue. Even Solace queue was already configured huge number as max connections, however connection count reaching the max configuration during peak hours and creating production support incidents due to out of connections available.
To handle the situation better, we would like avoid connections when it reach certain limit. we are looking for options.
Q1) Check the number of connections already established on the queue already. How to find count of live connections established by node where the current thread running to solace queue? How to find count of live connections from all nodes (in multi node environment)?
Q2) Can we set a max connection size setting in pega ? This would allow to avoid unnecessary calls to service systems and avoid production support incidents due to connection not available
Q3) Can we set a max connector size setting in IBM WebSphere Application Server?
Please let me know.