You mean cache not pool. Regards, Adrian
On Wed, 2004-02-04 at 16:28, Stephane Nicoll wrote: > Typical case is as follows: > > you start a JTA transaction, then pool an important number of entity bean > (let's say a findAll() or something). The entity bean pool is then full so it > starts putting entity bean in the passivate state but it can't because those > are still enlisted 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 passivate due to ctx lock > > > 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 trials. > We use <commit-option>D</commit-option> with a refresh rate of 30 seconds > (the container tries to passivate bean instances then) and > encounter the same warning message if a client currently calls a bean method. > > My questions is: How is such a situation resolved? Tries the container again > and when? Can it be that a bean instance is never > passivated (refreshed) if sequently passivation trials are unsuccessful or > are passivation trials enqueued or reminded with a flag > in something associated with the instance (ctx?) so that instances are > definitely passivated by the container right after the > locking invocation returns? > > Thanks, > S. Pohl > > > -----UrsprÃngliche Nachricht----- > > Von: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Auftrag von Marek > > Lange > > Gesendet: Mittwoch, 4. Februar 2004 15:21 > > An: JBoss User > > Betreff: [JBoss-user] Unable to passivate due to ctx lock > > > > > > After switching from 3.0.6 to 3.2.3 we experience warning messages in > > our logfiles: > > > > WARN [org.jboss.ejb.plugins.AbstractInstanceCache] Unable to > > passivate > > due to ctx lock, id=127.0.0.1:1099:dq6o9s7q-x > > > > This seems to be a problem to passivate (a stateful session?) bean. > > Looking into the code, the context of the bean seems to be locked: > > > > protected boolean canPassivate(EnterpriseContext ctx) > > { > > if (ctx.isLocked()) > > { > > // The context is in the interceptor chain > > return false; > > } > > ... > > > > Is there a way to discover what is holding the lock on the > > context? What > > is the impact of that warning for our application? > > > > Thanks, > > > > -marek > > > > > > > > ------------------------------------------------------- > > The SF.Net email is sponsored by EclipseCon 2004 > > Premiere Conference on Open Tools Development and Integration > > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > > http://www.eclipsecon.org/osdn > > _______________________________________________ > > JBoss-user mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user -- xxxxxxxxxxxxxxxxxxxxxxxx Adrian Brock Director of Support Back Office JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
