JCO_ERROR_CONCURRENT_CALL: Concurrent call.

[Former Member]

Hi SAP Experts

Does anyone know how I can kill a concurrent thread session in Portal without restarting the system? Our users are getting the following error:

Exception caught: com.sap.mw.jco.JCO$Exception: (132) JCO_ERROR_CONCURRENT_CALL: Concurrent call. Connection currently used in another thread.

Thanks in advance

Frederico

[former_member304001 · Accepted solution]

Have u checked SAP Note : 545014

and also check this link

http://help.sap.com/saphelp_nw04/helpdata/en/f6/daea401675752ae10000000a155106/frameset.htm

may be helpful for u

Regards

Krishna.

[Former Member]

It's been quite a while since the last post, but another advice won't hurt.

     I was facing the same error when trying to call 15~16 ajax calls from web at the same time. First 2 calls could get a response, while others getting server error(500). After investigating "Logs and Traces" section of Enterprise Portal, JCO_ERROR_CONCURRENT_CALL exception was the cause.

     Solution was, simply putting *synchronized* declaration to the method i used to create jco connections.

     Sample Java Method:

private synchronized getDataFromRfc(){
     // code that connects to rfcs with sapjco
}

    About synchronized declaration from official java documentation:

    Synchronized Methods (The Java™ Tutorials > Essential Classes > Concurre...

[Former Member]

Hi Frederico,

//getting Connection from pool

m_JCO_Client = m_JCO_PoolEntry.getJCOClient();

...

m_JCO_Client.connect();

There can be a possibility like, m_JCO_Client is defined as class member. If two threads make a change on m_JCO_Client, it could happen that the method connect will be called twice on the same client.

Hope this helps,

Regards,

Shailesh Nagar

[Former Member]

Hi,

Exception JCo.Exception with the group JCO_ERROR_CONCURRENT_CALL) is triggered if it you try to use a connection to send a call from various different threads at the same time. This new exception prevents follow on errors if an application executes simultaneous concurrent calls. If this exception is triggered, you must check and correct the application that uses JCo. Install the latest version of the Java Connector

Hope it helps.

Regards,

Mona