Too many connections/Sessions at R/3 due to ESS

[Former Member]

Hi Friends,

We are implementing the ESS 50.4. We come across a typical scenario as below:

We’ve encountered a condition in EP where too many sessions in R/3 and ITS are being created.

As the ESS user clicks and launches multiple transactions in the portal, each is creating a separate session in R/3.

This causes multiple problems, including possible record locking and memory & other resource consumption in the backend R/3 system.

Please advise/solution if anyone have encountered this issue and know of configuration that addresses it.

Thanks & Regards,

Raghavendra Pothula

• points assured

[Former Member]

Hi Umair & Raghavendra,

We r also encountering the same problem and not yet found any appr soln.

Our case is peculiar one . For ESS services only one sesssion is being created.But problem is with the "My first days" services.Here multiple sessions are opened in R/3 and results in Lock. Why this is happening for this service only ?

If u come across any soln it wud be great helpful to us.

Rgds,

J

[Former Member]

hello J,

I too am facing the same problem as users,

Can you update how did u solve th problem.

thank you,

V Kumar

[Former Member]

Hi Raghavendra,

We encountered this issue with our implementation as well...we had to check a few things:

1-Make sure you're custom code is closing the JCO connections, if any. If you have just a few custom iViews, try to not use them and see if the sessions still hang.

2-The DSM Terminator has to be configured or it will not close sessions from different domains (or subdomains), because of the javascript origin policy. Read more details on this here: http://help.sap.com/saphelp_erp2004/helpdata/en/ca/a9a7408f031414e10000000a1550b0/frameset.htm

3-Make sure the Business Package is compatible and tested with the R/3 version you've got.

4-Configure and fine tune session management, JCO connection pooling and such settings via the J2EE visual administrator.

For instance, try the JCO Pool Configuration settings

Maximum Pool Size = 15

Maximum Connections = 30

Connection Timeout (Sec.) = 2

Maximum Wait Time (Sec.) = 4

The following document is an excellent resource for these performance tuning settings for the Portal:

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b601a14c-0601-0010-909c-ddc...

5-If you have a java iView calling a BSP iView or a Web Dynpro iView or vice versa, sometimes it causes sessions to not release properly. Try a simple scenario taking out custom iViews and adding them one-by-one.