Bill,

Thanks for the help. My responses to your questions are below:

- What is your primary key class?

public class UserPK implements java.io.Serializable 
{
        public Integer id = null;

        public int hashCode()
        {
                return (this.getClass().getName()+
                " id="+id+
                "").hashCode();
        }

        public boolean equals(Object t_UserPK)
        {
                if(! (t_UserPK instanceof UserPK)) return false;
                UserPK t_CompareUserPK = (UserPK)t_UserPK;
                if(t_CompareUserPK.id == null) {
                        if(id != null) return false;
                }
                else
                        if(!t_CompareUserPK.id.equals(id))
                        return false;
                return true;
        }
}

- Are you using custom container configurations?  Make sure that you have
the correct interceptor chain.  If you have a custom config, please post 
it.

I haven't made any changes to standardjboss.xml. Using the one that ships 
with JBoss 3.0

- Did you change the locking-policy?  What did you change it to?

No changes to this either.

Thanks,
Todd

> -----Original Message-----
> From: <EMAIL: PROTECTED>
> [mailto:<EMAIL: PROTECTED>]On Behalf Of Todd Huss
> Sent: Monday, June 17, 2002 8:53 PM
> To: <EMAIL: PROTECTED>
> Subject: [JBoss-user] JBoss 3.0 and Transaction attribute RequiresNew
>
>
> I have a stateful session bean (with all methods having transaction
> attributes set to "Required") making calls into an entity bean with
> transaction attribute "RequiresNew". When the stateful session bean 
calls
> the method on the entity bean I get the exception:
>
> java.lang.IllegalStateException: removing bean lock and it has tx set!
>         at
> org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.removeRef(Queu
> edPessimisticEJBLock.java:469)
>         at
> org.jboss.ejb.BeanLockManager.removeLockRef(BeanLockManager.java:7
> 8)
> at
> org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInter
> ceptor.java:124)
> ...
> ..
> .
>
> Does anyone have a suggestion why I'm getting this error message or how 
to
> troubleshoot it? I'm upgrading to 3.0 from JBoss 2.4.4 and this
> error did not
> occur in 2.4.4.
>
> Thanks for any suggestions,
> Todd


----------------------------------------------------------------------------
                   Bringing you mounds of caffeinated joy
                      >>>     http://thinkgeek.com/sf    <<<

_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to