Skip to Content
avatar image
Former Member

SAP NW JRA configuration for JCO

We are trying to use SAP JRA to manage the JCO connection pools to R3 as specified in http://help.sap.com/saphelp_nw04/helpdata/EN/c9/5e84429069de54e10000000a155106/frameset.htm

When we run a load test with 3 users, after some time we find that no connections are returned. We get the below exception.

"Cannot get connection for 10 seconds - Possible reasons: 1) Connections are cached within SystemThread(can be any server service or any code invoked within SystemThread in the SAP J2EE Engine), 2) The pool size of adapter "job/SAPJRAFactory" is not enough according to the current load of the system or 3) The specified time to wait for connection is not enough according to the pool size and current load of the system. In case 1) the solution is to check for cached connections using the Connector Service list-conns command, in case 2) to increase the size of the pool and in case 3) to increase the time to wait for connection property. In case of application thread, there is an automatic mechanism which detects unclosed connections and unfinished transactions"

If we close connection explicitly, getting following exception.

"com.sap.mw.jco.jra.JRA$ResourceException: Connection handle is already closed and no longer associated with a managed connection

at com.sap.mw.jco.jra.JRA$ConnectionImpl.assertConnection(JRA.java:4080)

at com.sap.mw.jco.jra.JRA$ConnectionImpl.close(JRA.java:4281)"

Pls provide some insight on how to configure the SAP JRA, so that connections are returned as and when requested based on the size of the pool.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Mar 10, 2009 at 08:47 AM

    "Connection handle is already closed and no longer associated with a managed connection"

    Read note 1083348 and update your JRA connector.

    Sébastien.

    Add comment
    10|10000 characters needed characters exceeded