JCo destinations 7.3 for aRFC2

[Former Member]

Hello,

Currently i have some problems with the destinations that are used by aRFC2 models in a WebDynpro Java application.

That problem that we have is that after some days, suddenly in the log i can see that the JCo can't be created because max limit was reached.

And after this even after the sessions are closed (thinking that the current sessions will be removed from the pool) , it doesn't work anymore.

And only way to solve the problem is to re-create them.

The destinations are maintained from NWA Destinations : Destinations.

This is how the destinations were defined:

1) MODEL DATA

Connection and transport:

Load balancing: No

Target host

System number

System ID

SNC - Inactive

Logon data:

Authentication scheme: Current user (Logon ticket)

Language: en

Client

Repository Connection Destination Name: RFC_METADATA related to this model;

Specific data:

Pooled connection mode enabled;

Max Connections: 10

Pool size: 5

Max wait time in ms: 10000

2) META-DATA

Connection and transport:

Load balancing: No

Target host

System number

System ID

SNC - Inactive

Logon data:

Authentication scheme: Technical user

Language: EN

Client

Repository Connection Destination Name: This Destination

Specific data:

Pooled connection mode enabled;

Max Connections: 10

Pool size: 5

Max wait time in ms: 10000

Any help will be appreciated.

Thank you for reading this message.

Regards,

Cristi

[Former Member · Accepted solution]

Can you provide full log with errors for analysis? Try to increase the maximum connections parameter for Pool Settings.

[Former Member]

Thank you very much for support.

I am waiting for person responsible to test the application so we can reproduce the error.

When i will reproduce the error i will apply the suggestions and also add the logs here.

Thank you very much once again!!!

[Former Member]

Hi,

Rather than increasing the connection we need to check why the connection are not getting cleared off.

Once the connection has reached 100 it will still be an issue.

Thanks

Rishi Abrol

[Reagan]

Hello

Rather than increasing the connection we need to check why the connection are not getting cleared off.

The system is not going to keep all the connections open when they are not needed.

Maximum Pool Size - The pool keeps as many JCo connections open as you defined for the maximum pool size and these connections do not have to be newly created.

At present it is set to 5. I didn't suggest to increase or change it from the present settings.

If the number of Maximum Connections is higher than the number of Maximum Pool Size, the JCo connections that are not needed are immediately closed.

What I suggested is to increase the Maximum Connections.

By doing this the system will be able to open more connections (up to 100). That doesn't mean that those connections will be left open throughout the runtime of the application.

Maximum Connections. This is the maximum number of connections that can be set up at runtime.

Once the connection has reached 100 it will still be an issue.

If the application needs more connections than defined for Maximum Connections, the required connections are sent to a queue and can only be opened when other JCo connections are closed.

Again there are parameters like:

Connection Timeout (sec.) - Specifies the time after which an opened connection that is not needed is closed.

Maximum Waiting Time (sec.) - Specifies the maximum time to open a connection in the pool when the capacity of the pool is exhausted

Have a look at this link:

http://help.sap.com/saphelp_nw04/helpdata/en/3a/3b1b40fcdd8f5ce10000000a155106/content.htm

The information provided above are from the above link.

Regards

RB

[Former Member]

Please note this is not Nw 04 its NW7.3 system...

[Reagan]

Good Day

Please note this is not Nw 04 its NW7.3 system

Did you read my reply or just chose to reply with that statement ?

Note that my reply clarifies how the Maximum Pool Size and the Maximum Connections work for the JCo connections.

Regards

RB

[Reagan]

Hello

Specific data:
Pooled connection mode enabled;
Max Connections: 10
Pool size: 5
Max wait time in ms: 10000

Max Connections: 10

Increase this to 100

Regards

RB

[anja_engelhardt2]

moved to SAP NetWeaver Application Server by moderator

[Former Member]

Hi,

As the connection are created between the abap and the java so i think this is due to the connection between the two system.

For this you need to set the parameter CPIC_MAX_CONV at os level for sidadm for both the system.

1507034 - Max number of gateway connections / Maximum number of conversations exceeded

Thanks

Rishi Abrol

[Former Member]

Hello,

Thank you for your message.

I don't think that is the solution since the other pages that are not using those JCo are working, and they are between same systems.

Regards,

Cristi

[Former Member]

Hi,

Thanks for the clarification.

It looks to be issue with the Java support pack.

1630240 - Portal runtime error after installing or upgrading to SAP NW 7.30 SPS05

Note 1725337 - Web Dynpro Console CheckApplication is not displaying data

Note 1878985 - SAP NetWeaver AS Java 7.30 SP9 List of corrections

Can you please check if you have affected support pack.

Thanks

Rishi Abrol