Problem: Sharing session between two different Web browser & Web Appn'

Question

I�m facing a strange scenario here and would appreciate any inputs which could resolve this issue.
I have two webapplications (EAR�s) on two different machine and different WebSphere application server. I have �WebAppA� [on machine A, WAS A] which opens in parent window and expects to pass some info in the FORM submission with request parameter to �WebAppB� [on machine B, WAS B] which opens in a child window browser on clicking submit button from �WebAppA�.
Now the WebAppA is required to wait till the response come from WebAppB after certain functionality and once the function of retrieval is over by WebAppB, it sent back the response data back to WebAppA FORM, which finally submits this form after getting the response data from WebAppB. Now the response to WebAppA [which is in machine A, WAS A] from WebAppB is a pure POST request on complete URL and set of request parameters with values.
Now what is happening is that, when a User A fills the form on WebAppA and submits the data to WebAppB, on response it gets the data of some other User request, for example day of UserB or UserC.
Now when I do the test on my development environment, where its just me or some other 2-3 users accessing it I don�t face any problem. I get the response for the request I have submitted�.PERFECT. On production I have issue where users are getting data as response of other users.
I suspect since the response is submitted to the form page of WebAppA its unable to synchronize to which user it belongs to. May be that�s the reason when I test it on development with single or 2-3 users its behaving fine. I hope I could put my question properly to you. I don�t know what can resolve this or what is the actual cause? Is there a proper way to implement this? Please any suggestion or inputs are appreciated.

Answer 1

Thanks Amittev,
That's the problem for me. Actually this is a part of integration with third party application (which is loaded in child window - WebAppB). So as per the functionality there is no reference or trace of the user in the parent window at first instance. Anyone can come to parent window and initiatate a process. Its only when the data comes back from child window (which is the WebAppB), that parent window application (WebAppA) take the response and proceed further. Now here is what I'm facing problem. the user who initiated the process by clicking on the submit buttom of Parent window is not getting his response, but of some other user. This is not happening with every user and at all time. But were sparingly and rarely, but enough to bring headache to our department now.
Now I suspect that, since there is a parent/child browser functionality here the session which is started by parent is not synced with child where the WebAppB is loaded and responds the response to WebAppA. The WebAppB makes a POST request submission to the WebAppA thru the child window and the session here is missing synchronization, I believe. I will appreciate some inputs and resolution to this problem. Thanks.