Concurrent access to stateful beans

svetzal Jul 17, 2006 1:46 PM

Hi Folks,

We're readying a CRM application that uses Seam heavily, and are going through some of our lingering issues, one of which is the current access to stateful beans problem.

I've found first mention to it here: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=70595

It's attached to a rejected JIRA issue here:
http://jira.jboss.com/jira/browse/EJBTHREE-313

I tend to agree that Seam is trying to do something here that the EJB3 spec does not allow. It would be most useful for us if Seam could serialize the requests so that they do not hit the same component concurrently when the user gets impatient and clicks links twice, or (painful) double-clicks everything in the UI.

Is/has this been addressed? Is there a JIRA issue I missed that covers this?

I suppose we could pretty up the exceptions, but I'd really rather have a proper solution.

We're currently using Seam 1.0.1.GA and JBoss 4.0.4.GA with EJB3 RC8.

Thanks!

Steve

1. Re: Concurrent access to stateful beans

gavin.king Jul 17, 2006 1:58 PM (in response to svetzal)

I actually managed to sneak something into the EJB3 spec at the last minute to make it possible to detect a concurrentaccessexception. So the current issue is here:

http://jira.jboss.com/jira/browse/JBSEAM-95

I suggest that you simply add your own handling for this exception in a servlet filter or something.
Actions
2. Re: Concurrent access to stateful beans

svetzal Jul 17, 2006 3:50 PM (in response to svetzal)

Yeah, in thinking further on this issue really serializing requests would be evil.

What we really want to do is keep the browser from submitting subsequent requests. Sounds like a JSF hack to me right now.
Actions
3. Re: Concurrent access to stateful beans

denis-karpov Jul 19, 2006 5:02 AM (in response to svetzal)

I use this solution:
http://jira.jboss.com/jira/browse/JBSEAM-183
Actions

Go to original post