Hi,
We're using JCA connections (JCO under the hood) to connect from the portal to an ECC back-end using SSO. Normally everything works fine, and we can call bapis and get the data back to the portal. The requests are coming from a browser initially and these are being reformatted into JCA calls by a DC, and the results reformatted into JSON and returned to the browser.
However, if the application on the browser submits a second request before the first one has returned, we get a 'double response' back at the browser for one call, and nothing in the second one (or vice versa). This appears to be related to the JCA/JCO connection since I have proved that if the requests just get information from the portal everything is fine, ie. the portal can cope with multiple requests from the same http session. It is worth stressing that the requests destined for the back-end have to overlap for the problem to occur - sequential bapi calls are fine.
In the JCA/JCO situation, I would have thought that each request would get it's own thread on the portal server, and each of these thread's would run through the same code independently and get an independent connection to the back end (note that I do not have any static objects that could affect this) ? They obviously don't because of the mashed up response - anyone got any idea why ?
Thanks for your attention,
Nick