Hi Shawn,
Yes, attempts to concurrently access a particular stateful session bean identity result in a
javax.ejb.ConcurrentAccessException. Technically, the spec allows the container to
serialize the concurrent requests rather than throw an exception, although the vast majority
of containers throw the exception. This is a portability issue we're planning to fix in EJB
3.1. There will likely be metadata that allows the developer to specify which behavior is
preferred.
[Message sent by forum member 'ksak' (ksak)]
http://forums.java.net/jive/thread.jspa?messageID=315049