This content has been marked as final.
Show 4 replies
-
1. Re: no concurrent calls on stateful beans exception
pualsa Jun 25, 2004 5:59 AM (in response to mcdan)May be you have a cyclic invocation: Bean1 -> Bean2 -> Bean1
If this is the case then try to make Bean1 reentrant (but be careful this allows multithreading on the bean) -
2. Re: no concurrent calls on stateful beans exception
mcdan Jun 25, 2004 6:50 AM (in response to mcdan)"pualsa" wrote:
May be you have a cyclic invocation: Bean1 -> Bean2 -> Bean1
If this is the case then try to make Bean1 reentrant (but be careful this allows multithreading on the bean)
That's not the case, because then I would have a 'caused by' in the exceptions stack trace that would point to a line in Bean2.
How can I make a bean reentrant without switching to a stateless bean? Is this possible? -
3. Re: no concurrent calls on stateful beans exception
pualsa Jun 25, 2004 11:17 AM (in response to mcdan)Sorry, I was wrong: reantrant is applicable only to Entity beans - server will throw another exception.
-
4. Re: no concurrent calls on stateful beans exception
ramesh4u Jun 14, 2006 3:06 AM (in response to mcdan)I am also getting the same error. Can anyone help me to resolve this issue