-
1. Re: Web Sphere: javax.ejb.ConcurrentAccessException: TX_METHOD_READY: wrong transaction
sashkanem May 31, 2010 2:59 AM (in response to daniele4)First off all you had better use global queue enabled for richfaces (in case you use it), to avoid lots of parallel AJAX requests from page.
In your seam component methods where you access SFSB methods, all methods must be marked synchronized, to avoid concurrent access to SFSB, that is prohibited.
-
2. Re: Web Sphere: javax.ejb.ConcurrentAccessException: TX_METHOD_READY: wrong transaction
daniele4 May 31, 2010 8:35 AM (in response to daniele4)I've made your suggestion and it's works better now, but sometimes i still get the exception. How can i catch it?
thanks
-
3. Re: Web Sphere: javax.ejb.ConcurrentAccessException: TX_METHOD_READY: wrong transaction
sashkanem May 31, 2010 9:12 AM (in response to daniele4)I don't think it would be right to catch that exception, you have to just avoid such situations to happen.
You have to avoid concurrent access to same instance of SFSB methods.
-
4. Re: Web Sphere: javax.ejb.ConcurrentAccessException: TX_METHOD_READY: wrong transaction
daniele4 May 31, 2010 9:28 AM (in response to daniele4)I know you are right but i dont't know to avoid it!
I already follow your suggestion.any other ideas?
thanks -
5. Re: Web Sphere: javax.ejb.ConcurrentAccessException: TX_METHOD_READY: wrong transaction
sashkanem May 31, 2010 9:31 AM (in response to daniele4)Does the exception still happen in the method that you marked synchronized?
-
6. Re: Web Sphere: javax.ejb.ConcurrentAccessException: TX_METHOD_READY: wrong transaction
daniele4 May 31, 2010 10:18 AM (in response to daniele4)yes it does!
I've made a workaround cathing the exception with pages.xml (you just seen another post about it).