application deadlocks

[vivek.chaudhri]

Hello:

I am using JBoss 3.0.0 and using CMP as my persistence mechanism on Oracle 8.1.7. I mark all my getter methods to be read-only on jboss.xml. I see deadlocks when accessing getter methods. I am not sure what will be causing this. I thought that marking the method read-only would solve deadlock problems. The stack trace for the deadlock says that the deadlock is happening when executing a getter method which I said I tagged them as read-only.

Could anyone please enlighten me what I may be doing wrong. Is there any other way to change the locking mechanism. In the stack trace I also see that I am using pessimistic locking. Is there a way I an tell the container to use optimistic locking. If so, would that solve my deadlock problems. Also I am using commit-option A. That should have resulted in less situation for deadlocks but I am not seeing that. In my application I am mosting doing reads and do very few writes to the database.

All help will be greatly appreciated.

Thanks
Vivek

[pranav]

Why are you making the getXXX() methods as read only...

Pranav

[vivek.chaudhri]

I am setting them as read-only because I do not want them to participate in the transaction, and because these methods do not modify data.

Thanks
Vivek

[adrian.brock]

Try a more recent version of jboss, there were
bugs in the original application deadlock detection.

Also a read-only method does lock the bean for the
duration of the invocation. If you have already taken
a write lock on the bean, if will still do a full lock.

Regards,
Adrian