-
1. Re: jboss3.0 IllegalStateException: removing bean lock and i
andrewlau4 Jul 15, 2002 4:06 AM (in response to andrewlau4)Hi,
After I changed something that is totally unrelated to ejb relationship, I no longer see the problem. Seems that I have somehow fixed the problem(?)
I am afraid I have done something wrong and the problem is just hidden for now and will appear again later. I would appreciate if somebody can give me some insight about what can cause this exception.
Any help is very much appreciated. Thank you very much!
Andrew -
2. Re: jboss3.0 IllegalStateException: removing bean lock and i
dsundstrom Jul 15, 2002 3:44 PM (in response to andrewlau4)This exception is always caused by a bad custom primary key class. Check that the hashCode and equals functions follow the rules.
-
3. Re: jboss3.0 IllegalStateException: removing bean lock and i
andrewlau4 Jul 15, 2002 5:04 PM (in response to andrewlau4)Hi Dain,
Thank you very much for your reply. I didn't use custom primary key class. I used java.lang.Integer for all my primary key class.
This exception happens sometimes but not every time.
Any idea? Thanks!
Andrew -
4. Re: jboss3.0 IllegalStateException: removing bean lock and i
dsundstrom Jul 15, 2002 6:57 PM (in response to andrewlau4)What version of JBoss 3.0 are you using? Try using the 3.0.1 release.
-
5. Re: jboss3.0 IllegalStateException: removing bean lock and i
andrewlau4 Jul 16, 2002 2:00 PM (in response to andrewlau4)Hi Dain,
Thanks!
I tried jboss 3.0.1 and get the same exception. But I found a quick solution for now. The IllegalStateException exception only happens when I call EJBLocalObject remove() method. Now I changed my code so it calls EJBLocalHome remove() method instead. Since then, it is working fine so far.
But I am still wondering what is the difference? I think the two remove() method should do the same thing.
Any idea?
Thank you very much!
Andrew -
6. Re: jboss3.0 IllegalStateException: removing bean lock and i
dsundstrom Jul 16, 2002 3:30 PM (in response to andrewlau4)Can you please post a bug report on this at SourceForge, and Bill Burke will take a look at it.