On Tue, 2003-07-29 at 15:54, Alexey Loubyansky wrote:
> Hello Davide,
>
> let's consider a simple case. There are two entity beans BeanA and
> BeanB. And two threads/transactions T1 and T2 accessing these beans.
>
> Accessing in the same order:
> T1: -> BeanA -> BeanB
> T2: -> BeanA -> BeanB
>
>
On Tue, 2003-07-29 at 14:57, Alexey Loubyansky wrote:
> ID> the code is from xpetstore (this is not the code which fails, but is
> ID> similar). As you can see it does nothing more than create a regular
>
> Are you jeering? You offer to find a bug in a code that does not fail?
> Some threads are
]
Betreff: Re: Re[2]: [JBoss-user] Application deadlock detected: Two or
moretransactions contention.
Hi Alexey,
On the previous post you say:
> Some threads are accessing the same set of beans in different order.
Many times reading other posts or the JBoss documentation, I've found
Hi Alexey,
On the previous post you say:
> Some threads are accessing the same set of beans in different order.
Many times reading other posts or the JBoss documentation, I've found this phrase, but
I can't understand it very well...
What's the meaning of the "entity beans ordered access" (see "J
On Tue, 2003-07-29 at 10:53, Alexey Loubyansky wrote:
> Hello Ittay,
>
> the deadlock, probably, occurs in value object creation. So, pay
> attention to it or post more details/code snippets.
ok. sorry if i've sent too little information. here is a code snippet of
how a value object is created. i
