Are there any news on this issue?
The JIRA entry
has been rejected, because concurrent calls on stateful session beans are not allowed by the EJB specification. The double click problem however stays.
Has anybody found a good workaround for this?
I haven't even been able to write a decent error page for the exception, because the behavior is hard to reproduce, and thus the error page is hard to test. Also, the exception which shloud be caught can be different, although the cause is always javax.ejb.EJBException
It should be very easy to write an errorpage. The root cause exception is always a ConcurrentAccessException.