Hi,
I'm on a customer site just now and this is a problem that they've been facing for some time; it happens only randomly.
One thing that stands out as being unusual here with their RFC calls is that they've used the NWDS import wizard to generate proxy classes and handle the BAPI calls.... rather than just using the getDefaultJcoConnection() method to get a reference to the function, set input params directly and execute the function.
They do use the defaultJcoConnection; using the generated proxy classes they set the JcoClient for something called the messageSpecifier... that's the only reference they have to the defaultJcoConnection.
object.messageSpecifier.setJcoClient(this.getDefaultJCoConnection().getJCoClient());
So I don't really know if the defaultJcoConnection is being used for the execute or not....
Could this be the reason that the JCO_ERROR_CONCURRENT_CALL exception occurs?
Thanks for your time and help,
Patrick.
Edited by: Patrick O'Neill on Jun 23, 2009 2:15 PM