Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Sarath Viswanath Barathi (SARATH_VISWA)
NIIT Technologies

NIIT Technologies
IN
SARATH_VISWA Member since 2012 22 posts
NIIT Technologies
Posted: Mar 14, 2017
Last activity: May 7, 2017
Posted: 14 Mar 2017 13:25 EDT
Last activity: 7 May 2017 21:39 EDT
Closed

Connect SOAP & JMS Connection Pool Handling

Hi ,

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***

To see attachments, please log in.
Data Integration
Support Case Exists

Posted: 7 years ago
Posted: 15 Mar 2017 0:17 EDT
Ankur Das (@nkur.das_GCS) Principal Software Solutions Engineer
Pegasystems Inc.
US

For Connect-SOAP, Apache HTTP Connection pool is used. 

PRPC provides the following two DSS to tune the apache connection pool.

options to set apache http connection pool size for R-C-SOAP

Owning ruleset: Pega-IntegrationEngine
Setting purpose: Axis2_Max_Connections
Value: 1000 (default)

Owning ruleset: Pega-IntegrationEngine
Setting purpose: Axis2_Max_HostConnections
Value: 100 (default)

JMS Connections are controlled via the container / application server JMS resources like TopicConnectionFactory / QueueConnectionFactory and not by PRPC code.

Hope the above information helps.

To see attachments, please log in.
Posted: 7 years ago
Posted: 15 Mar 2017 19:00 EDT
Ankur Das (@nkur.das_GCS) Principal Software Solutions Engineer
Pegasystems Inc.
US

Axis Thread management / Connection Pool was introduced in PRPC v6.3SP1 via HFis-7709. Please create a PegaSupport ticket to get the HFix package and install instructions.

To see attachments, please log in.
Posted: 7 years ago
Posted: 16 Mar 2017 0:00 EDT
Lochana Durgada Vijayakumar (Lochan_DV)
PEGA
Senior Manager, Knowledge Management
Pegasystems Inc.
IN

Hi Sharath,

Do let us know the SR number once you create it to obtain HFix-7709. We will track it through this post for you.

To see attachments, please log in.
Posted: 7 years ago
Posted: 5 May 2017 10:58 EDT
Sarath Viswanath Barathi (SARATH_VISWA)
NIIT Technologies

NIIT Technologies
IN

Hi Lochan/@nkur, I have received Hfix-7709 (SR-B47305). Can someone advise if this would address our below expectation.?

Show More

Hi Lochan/@nkur, I have received Hfix-7709 (SR-B47305). Can someone advise if this would address our below expectation.?

My understanding below.
* Whenever there is a connect(SOAP/JMS) call from PEGA, a connection is opened with integration layer (in our case its TIBCO). As soon as service is completed, connection will be closed. Connection open and closure is being taken care by PEGA. So on a given day, if there are 10,000 connect calls in total, from PEGA 10,000 connection will be opened and closed. Correct me if this is wrong.
 
Now, our expectation is to Establish a standard connection number of connections (eg..5000) And these 5000 connection should never be closed and reused for other requests.

 

 


Show Less
To see attachments, please log in.
Posted: 7 years ago
Posted: 5 May 2017 12:41 EDT
Paul Gentile (PaulGentile_GCS)
PEGA
Principal Engineer, Technical Support, 1:1 Customer Engagement
Pegasystems Inc.
US

Take a look at Java code behind invokeAxis2 activity...Pega shows you how its interacting with application server (container) to initiate connections from the JVM. Pega does not directly manage connections.

 

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice