concurrent calls to stateful session beans

[andrewtv]

Hope this doesn't sound too idiotic, but I'm running into an issue where some concurrent calls to a EJB 3.0 SFSB cause EJBExceptions on local interfaces, and am wondering if there is any way to automatically have these calls act single threaded (instead of wrapping calls externally), or alternatively to allow concurrent access. I tried synchronizing the public methods on the SFSB pojo but that didn't seem to do the trick, I still seem to get this exception. Manual external synchronization should work, though just wondering if there was a cleaner solution.

[bdecoste]

Concurrent calls to a session bean instance are not allowed via the spec. Are you sharing a SFSB handle (proxy) between multiple threads?

[andrewtv]

Understood. Perhaps if there was a way to single thread access to the bean automatically as if all calls were synchronized, I suppose this is what I'm looking for -- perhaps this is more of a locking strategy. I have a web tier in which parts get composed in mutiple threads, but would like to continue using the sfsb, though I suppose another alternative would be to just switch to a plain session bean.

[bdecoste]

If there is no state between calls, then a stateless bean is the way to go. Access to a SFSB instance should be locked (via the StatefulSessionInterceptor) to force single threaded access. Could you please post a full stack trace?

[bill.burke]

no, multi threaded access to a SFSB will throw an exception by default as per the spec...

@org.jboss.annotation.ejb.SerializedConcurrentAccess will block on co

[andrewtv]

Thanks, I'll try this