Re: [JBoss-user] Deadlock with Oracle and Jboss 2.2.1

[Jose R. D. <jd...@ar...>]

Hi Danch

    Sorry, but I don´t understand you, what do you mean with "more traditional
deadlock scenario hunting"? What can I try?

    And a second question, although there was several instances of a bean,
wouldn´t the container (JBoss 2.2.1) serialize all the database access?

    Thanks a lot

             Jose R. Díaz


danch wrote:

> If it's called ~5 times a second there's a good possibility (depending
> on how long the methods take to execute) that more than one instance of
> the bean would be executing at the same time. Are these different
> methods, and if so do they perform their accesses in different orders?
> that would deadlock pretty easily.
>
> You might try bean-managed transactions, but I'd perform more
> traditional deadlock scenario hunting first.
>
> -danch
>
> Jose Ramon Diaz wrote:
>
> > Hi,
> >
> >     We have a Stateless bean with JBoss 2.2.1. This EJB makes deletes
> > and updates of several rows, inserts and selects in a table, and selects
> > in other three tables.
> >     That table is only accessed from that EJB. This EJB is called 5 or 6
> > times/second. This table usually contains about 200 or 250 rows.
> >     Our problem is that Oracle is detecting deadlocks. If we access that
> > table only from that EJB, isn´t it supposed to be serialized every
> > transaction? Why is Oracle detecting a deadlock?
> >     We have configured the EJB as a container managed transaction. Would
> > it be better to be a Bean managed transaction and to make the commits
> > and rollback on our own explicitly?
> >
> >     Thanks
> >
> >             Jose R. Díaz
> >
> >
> >
> > _______________________________________________
> > JBoss-user mailing list
> > JBo...@li...
> > https://lists.sourceforge.net/lists/listinfo/jboss-user
> >