Web Dynpro application with 15+ Adaptive RFCs..... after 11 all RFCs fail.

[Former Member]

I have developed a 7 page application that calls 15 or so RFCs (for field validation and population of Search-Helps). The wierd thing is that after the application has called 11 RFCs (all going through the same destination to the same backend system), all other subsequent RFCs will fail. I can re-order the RFCs completely and all RFCs after the 11 call will fail. Independently in separate applications all of the RFCs (15+) all function as expected.

The error message in Default Trace is simply:

Could not create JCOClientConnection for logical System: 'WD_MODELDATA_DEST' etc etc

It is as though there is maximum number of connections that can open between the application and the backend system via the JCO connection. Do I need to clean up the connections after each call? Or can I configure this maxiumum number of connections in the JCo configuration?

If anyone has had an similar experiences as this, please let me know. Much appreciated and points will be awarded for responses that tackle this specific issue.

Thanks

Adrian

[Former Member · Accepted solution]

<b>Hi

I think your JCo Connection pool will be setted to handle maximum of 11 Connections and You can solve your problem by extending the no of connections in the Connection Pool which is in Content Administrator.

Regards

Chandran</b>

[Former Member · Accepted solution]

Thanks for the response. I have actually 'worked around' the limit just now by shifting around the model design. In one page I have 6 RFCs calls, I have reimported all the RFCs into ONE model (rather than separate models). By doing this only one JCO connection is used for all 6 of these RFCs, so obviously more efficient.

My question now, is when during the lifecycle of the application are these JCo connections released? And how can I monitor these connections ? Thanks

[Former Member · Accepted solution]

Hi Adrian,

Here is a link for /thread/418808 [original link is broken] for monitoring the JCo connections.

You can get the help regarding WebDynPro Console from WebDynpro Content Administrator link, which I have given above.

Also see<a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/85a483cb-0d01-0010-2990-c5168f01ce8a">JCo quick summary</a>.

[Former Member · Accepted solution]

<b><b>Hi Adrian

During the Life cycle of your application Your connection will be Released when it is inactive for particular Time (The inactive time limit will be specified in the JCo Pool Settings that would be in milli seconds)

The RFC Connection can be Monitored using the Gateway process .

There are Some Predefined Connections in the Gatewway Process and each connection Requires approximately 200Kb of Memory.

So the memory cosumption of the Gateway process is proportional to the number of Active RFC Connection.

For More Details Check This

<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/85a483cb-0d01-0010-2990-c5168f01ce8a">JCo Connection Pools</a>

Regards

Chandran S</b>

[Former Member]

Adrian, if you have 1 model to each RFC you have to change it and put all RFCs in a unique model.

See this document

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/11c3b051-0401-0010-fe9a-9eabd9c2...

[Former Member]

Hi Adrian,

I think while creating Jco connection they should have mentioned number of connection as 11.please check in the content administrator.