|No. You can't have two clients calling beanA simultaneously. That would |imply two threads of execution for one tx, which is not possible. :-P rickard... we have been there before remember ??? :P it is possible... hence the test failure marc | |Or do you mean clientA call beanA, return, clientB call beanA, return? In |that case it is valid, but then it is not locked when clientB call comes in |so no problem! | |> this test does more than is needed. In fact does wrong stuff... |> (invalidates the above scenario) | |No, as above. | |> marc (yes? see it? I am completely off-base?) | |AFAIK you're off-base. | |/Rickard | | | |
- Re: [jBoss-Dev] Release lock bug ... Rickard Oberg
- RE: [jBoss-Dev] Release lock bug ... marc fleury
- RE: [jBoss-Dev] Release lock bug ... marc fleury
- Re: [jBoss-Dev] Release lock bug ... Rickard Oberg
- RE: [jBoss-Dev] Release lock bug ... marc fleury
- Re: [jBoss-Dev] Release lock bug ... Rickard Oberg
- RE: [jBoss-Dev] Release lock bug ... marc fleury
- Re: [jBoss-Dev] Release lock bug ... Rickard Oberg
- RE: [jBoss-Dev] Release lock bug ... marc fleury
- Re: [jBoss-Dev] Release lock bug ... Rickard Oberg
- Re: [jBoss-Dev] Release lock bug ... marc fleury
- Re: [jBoss-Dev] Release lock bug ... Rickard Oberg
- Re: [jBoss-Dev] Release lock bug in JDK? Fixed ? Sebastien Alborini
- Re: [jBoss-Dev] Release lock bug in JDK? Fixed ? Sebastien Alborini
