essage-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, February 04, 2004 4:00 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-user] Unable to passivate due to ctx lock
>
>
> Hello,
>
> for me, it seems that such a ctx is locked when an i
in the JTA transaction you created.
Solution is to increase the pool size (see container configuration).
Regards,
Stephane
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 04, 2004 4:00 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] Unable to passiv
On Wed, 2004-02-04 at 14:59, [EMAIL PROTECTED] wrote:
> Hello,
>
> for me, it seems that such a ctx is locked when an invocation is currently active in
> a bean instance. We encounter such a warning
> message if the container tries to passivate such an instance. It depends on the time
> methods
Hi,
I've had a search through this list's archives, and haven't found a
definite resolution to this issue.
We're seeing this warning on a very low-traffic site, and while it hasn't
caused any significant issues so far I don't want to run into the memory
leakage problems reported elsewhere.
A rum
Marek,
You aren't perchance using Handle.getEJBObject() in your client app/webapp are you?
If so, search this mailing lists archive for my prior post about Handle.getEJBObject().
I think that there may be a new bug introduced in the 3.2 series that causes an
additional
extra ref lock on the sta
Hello,
for me, it seems that such a ctx is locked when an invocation is currently active in a
bean instance. We encounter such a warning
message if the container tries to passivate such an instance. It depends on the time
methods need to execute and the frequency of
invocations and passivation t
Alex, I'm using BMP's.
The id's displayed in the warn message is valid. The record definitely exist in
database.
Cheers,
Magesh
On 6/25/03 12:01 PM, Alexey Loubyansky <[EMAIL PROTECTED]> wrote:
>Hello Magesh,
>
>Wednesday, June 25, 2003, 1:33:27 PM, Magesh Prabhu wrote:
>
>MP> I'm getting this
Hello Magesh,
Wednesday, June 25, 2003, 1:33:27 PM, Magesh Prabhu wrote:
MP> I'm getting this following warning. I went in to all my entity beans to check if
I'm doing any naughtly stuff with entity context. Everything looks fine. Could anybody
suggest me what could be
MP> the possible reason f
The instances are locked and can't be passivated (evicted from the
cache). Could you provide deployment info on the entities that can't be
passivated?
Specifically, do you have foreign keys mapped to CMP fields?
alex
Wednesday, June 18, 2003, 6:13:39 PM, Davide Pozza wrote:
DP> Can anyone tell
