User conected with R3 without logging off

[Former Member]

Hello Experts,

I have same WebDynpro ABAP and Web Dynpro Java from ESS in the Portal.

When the users access to these aplications to consult information from R3, in this system appears a lot of RFC connections (Transaction SMGW) created by these consults.

There are more of 500 connections and this causes R3 is down.

I need that, when the users don't use more these application, the RFC session in R3 closing automatically.

How can I do this?

Thanks and regards.

Mariano

[hemanth2]

Dear Mariano,

Hope you are doing good.

This issue needs detailed investigation.

It would be useful to know the function module which was called when the connections where left open. For that please can

you check the Note 780817. The connection pool should not be relied on for terminating the backend sessions. The application itself should be terminating the backend sessions. Often times when the the JCo sessions are failing to close it is because there is an exception occurring during the call to terminate the session.

Do the below for more info:

- Reproduce the issue if necessary

- Trigger 3 thread dumps on the j2ee server nodes

- Check SM04 and SMGW transaction details to see user sessions and gateway connections

- Capture the active defaultTraces covering the period when jco Pool connection were used and returned to the pool and this should provide more info on the application responsible.

Hopefully there are some exceptions thrown in the defaultTrace that explain why the backend sessions were not closed.

Also, carefully go through the documents below in order to properly configure your JCOs. If necessary, remove

them and recreate in the correct way:

JCo Quick Summary

[http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/85a483cb-0d01-0010-2990-c5168f01ce8a]

How to Configure the JCo Destination Settings

[http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3103eb90-0201-0010-71af-be6f4a6f61d1]

You will have to calculate the maximum number of JCo connections to each application based on Models and users. If you don't

manage to solve the issue even after carefully readjusting your JCO settings as per these information then, please set Maximum Pool Size to 100 and decrease Connection Timeout and Maximum Waiting Time to a value around 50.

Thank you and have a nice day :).

_____________

Kind Regards,

Hemanth

SAP AGS