> Try ensuring that your parser access is synchronized and then perform a load test.
Thanks for your suggestion. I assume you refer to the parser in the WS client stack on the client end.
I'm using NetBeans, which generates client stubs using JAX-WS RI.
I'm boarding the WebServices train 10 years late, so I would assume the default client library shipped with JDK6 does not exhibit such a threading problem.
Do you mean I should ensure synchronization of [i]our own code[/i] accessing the web service? I think this part is OK (each thread in the load test client uses its own port instance).
Did I misunderstand you, and did you have anything else in mind?
[Message sent by forum member 'jduprez' (jduprez)]
http://forums.java.net/jive/thread.jspa?messageID=352467