Normally, each request gets its own instance of an ActionBean class so you don't have to worry about synchronization in the ActionBean itself. It is possible that your ActionBean uses another class that is not thread-safe.
If you use @SessionScope, then one instance of the ActionBean class is created per session so thread-safety is a bit of a concern there. -Ben On Mon, May 25, 2009 at 9:13 AM, Laurent Perez <[email protected]> wrote: > Hi > > I'm trying to figure out an error "randomly" repeating itself on a > production system, which I can't reproduce locally. Stripes version is > 1.5. > > I believe this may be linked to concurrency issues, however, I'm not > sure if this could happen : are ActionBean expected to be thread-safe > ? By thread-safe, I mean can I run into unexpected problems whenever > two different browsers hit the same method of an ActionBean ? Is the > ActionBeanContext safe, too ? > > If so, is it meaningfull to synchronize "sensitive" Resolutions, as in > public synchronized Resolution process() {....}, or would it make no > difference ? > > Thanks > laurent >
------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com
_______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
