Hi! You are correct in assuming that the threading issue arises on the client side (in our struts action) which had created one instance of the sei which it shared between calling threads. The actual web-service endpoint is deployed as a stateless session-bean under jbossws on another machine and is thread-safe.
We solved the problem by creating a dynamic proxy for the sei that in its InvocationHandler used commons-pool to hold a pool of sei:s which it used for dispatching the invocations. This solution had the advantage of not requiring any changes to the struts action (it uses the dynamic proxy instead) and seems to work just fine under multiple threads.. Maybe there is a better/easier way? regards, /Ole View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873906#3873906 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873906 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
