We are currently developing a spring web application with jax-rpc access to our DAOs.
The client and server are the same apps except for one being configured to use jdbc directly and the other to use jax-rcp to connect to the jdbc webapp.
We used the jpetstore example as guideline for the jax-rpc part.
Our tests showed some strange behaviour when accessing the client with multiple users. It looks like the jax-rpc response from the server cannot be associated with the originating request.
For example: Client A requests data from the webservice. Before the response for client A is back client B requests some other data. In our case the response for client B is much faster generated by the server so it's send back before the response for client A. What happens now is that client A gets the response for client B resulting in errors like wrong serializer or other strange xml parsing errors.
The only solution we found so far is making it synchronized. But this is not an option because of the poor performance.
Is there way way to make the jax-rpc calls behave like ordinary java method calls (the response knows which request triggered it)?