Maximum no. 300 of systems reached

[aneeth_gajapathi]

Hi,

Could someone help me with this issue please?

Our business users access Enterprise Portal to run BW Reports. This creates a new RFC connection in the BW ABAP backend and I could see the connection in the SM04 and SMGW screens. However some of these connections are not closed. They remain there forever until it reaches the maximum number of RFC connections and no users could run reports anymore.

Also, from the SMGW screen, when I click on "Go To > Logged on Clients", I could see list of clients, some of which are few days old. Even these are not closed and at some point they reach the maximum limit and below errors start appearing in SM21:

Maximum no. 300 of systems reached

As a workaround, we are currently doing an "End Session" in SM04 and "Delete Client" in SMGW I don't want to increase the count in the parameters for maximum RFC's or maximum Clients' because if the connections are not closed, they would reach maximum limit again. I would like to understand why these connections are not closed.

Another interesting thing is our users also connect to ERP and SRM exactly the same way and we don't have any problems there.

In fact in those system's SM21 logs I could see these messages:

HTTP/RFC session has been deleted following timeout.

I don't see similar messages in BW.

Your help will be much appreciated.

Thanks.

Aneeth

[aneeth_gajapathi · Accepted solution]

Sorry for the delay in updating this thread. After various investigations, I understood that the BW reports in our Portal system is using Bex Web Explorer. The way it makes connections to ABAP BW is different to normal http connections. I found note 1600085 which has recommended settings for systems like this. I followed it and now the connections are properly closed.

Thanks to everyone who helped.

[isaias_freitas · Accepted solution]

Happy to hear it!

[aneeth_gajapathi]

Thanks Ramkrishna.

I followed 1660720 and got confirmation that the SRA knows about the session on the server side .
. I'll check with other notes tomorrow and get back to you.

By the way, I am the Basis Team

Thanks once again

[aneeth_gajapathi]

Thanks Isaias. As you know, Visual Administrator is quite complex. So if you remember the precise instruction about Jco Timeout, that will be brilliant. Thanks anyway.

[isaias_freitas]

Hello!

I found the SAP note 2005477. It seems that it is not at the Visual Admin .

The parameters that would be interesting for this thread would be:

• jco.destination.expiration_time: Timeout period after which pooled idle connections can be closed (the default value is 600000ms, or 10minutes).
• jco.destination.expiration_check_period: Regular time interval for checking if pooled connections have expired and will be closed.

Regards,

Isaías

[aneeth_gajapathi]

Thanks Isaias and sorry for the delay in getting back to you.

I checked the above note and I think it is not applicable in my case because I found out that our Portal uses BI component - Bex Web Explorer to connect to BW. I don't think it uses the Jco Destination. However I have logged this issue with SAP and investigating it further. I'll post the outcome here.

Thanks for your help anyways.

[isaias_freitas]

Hello Aneeth,

Sorry for not having a more precise instruction set, but you would need to set/change the "JCO timeout" at the Portal end.

I believe this can be done at the Visual Administrator.

The Java-stack of the Portal has to close idle / unnecessary RFC connections to the BW.

I hope this helps, or that someone with Java-stack knowledge replies this thread!

Regards,

Isaías

[Former Member]

hi aneeth,

Please do refer to below links which can help you out for the session management and log off any old session.

1660720 - Session remains open after the logoff on enterprise portal

1717945 - Portal Logoff Does Not Logoff the Backend When Using HTTP Security Session Management

And for below OSS note there are few parameter checks in backend and backend services so you might need to get the help from your basis team to check on the Session managment in BAckend ABAP system and parameters.

1322944 - ABAP: HTTP security session management

1777513 - WebGUI logoff does not work

Let us know if this helps you.

Regards,

Ram

[isaias_freitas]

Hi,

And for below OSS note there are few parameter checks in backend and backend services so you might need to get the help from your basis team to check on the Session managment in BAckend ABAP system and parameters.

There is no parameter at an ABAP system that would terminate idle RFC sessions.

The RFC caller must close the RFC session explicitly.

Regards,

Isaías

[Former Member]

Hi Isaias,

We can set below parameter in the backend (ABAP) side icf/user_recheck which can check the connection is alive or not based on user sessions.

Regards,

Ram

[isaias_freitas]

Hello Ram,

"icf/..." is for ICF sessions -> HTTP.

This thread is about RFC sessions .

Regards,

Isaías