Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Help Configuring JCo connection

I have written a Web Dynpro application that generates an Event Details report from EH&S. This application uses many RFCs (> 20) to compile this very large list of data.

Our landscape is setup so that not every portal user has a backend (R/3) account, therefore we cannot use SSO for our JCo connections, as the portal login user may or maynot have a backend account with those credentials. We have setup a single backend technical user which is the account used for the JCo connection username/password setup anytime this application is run.

My question is this...as we could have 100s of users trying to retrieve various Event Reports at the same time, is there a guide somewhere telling me what I should set maximum connections and maximum pool size to based on the number of RFCs being called and expected simultaneous user count?

Also, it appears that by default the system uses 10 millisecond for connection timeout and 30 milliseconds for maximum wait time. These values seem far too small, and also they seem like they should be the same value...

Any help would be greatly appreciated. Once the number of users starts to grow over just a dozen or so I get periodic JCo connection errors.

Former Member
Former Member replied

Hi Tom,

You are right. If max. no of connections established then you get

JCO.maximum pool size reached

so to avoid this we need to do 2 steps.

1. Increase the max. poolsize to 100 or 200

You can leave other setttings as they are or change according to your requirement.

2.In the Web Dynpro application,

in each RFC execte method, add the following code after

wdContext.current<RFC>_InputElement().modelObject().execute():
wdContext.current<RFC>_InputElement().modelObject().modelInstance().disconnectIfAlive();

Since there are too many RFCs and so many users you can use different JCo destination to a set 4-5 RFC models. Say you have 20 RFCs. 1-5 RFCs - set1 JCOs, 6-10 RFCs - set2 JCOs 11-15 RFCs - set3 JCOs 16-20 RFCs - set4 JCOs. Like this also you can improve performance and decrease the chance to reach max. pool size.

Regards,

Siva

0 View this answer in context

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question