[JBoss-user] [EJB/JBoss] - Unable to passivate due to ctx lock

2005-10-05 Thread sraghavan
I get the following error in my jboss, while trying to save data to the mysql 
database: 

WARN [org.jboss.ejb.plugins.AbstractInstanceCache] Unable to passivate due to 
ctx lock, 

(followed by the id of the entity bean primarykey )

jboss 3.2.3, mysql 4.0
please help

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3899260#3899260

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3899260


---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user


[JBoss-user] [EJB/JBoss] - Unable to passivate due to ctx lock

2005-09-30 Thread JasonNorth
We are getting the following error:

[org.jboss.ejb.plugins.AbstractInstanceCache] Unable to passivate due to ctx 
lock, id=X

This error starts happens after more than 1 day of normal activity where the 
jboss process goes from using an average of 1% CPU usage to 90% CPU usage.

Is this because a stateful session is locked out for some reason and can not be 
passivated?  Why would this cause the CPU usage to go so high?

JBoss version:   4.0.1 SP1
Java version:   1.5.0_03
OS:  Solaris 9 (Sparc)  8 Processors, 16GB RAM

We have about 10 - 15 concurrent users.

Any help much appreciated!



View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3898249#3898249

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3898249


---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user


[JBoss-user] [EJB/JBoss] - Unable to passivate due to ctx lock

2005-07-22 Thread blackandwhite
In my server.log, I find a lot of WARN:
anonymous wrote : 2005-07-18 00:32:02,156 WARN  
[org.jboss.ejb.plugins.AbstractInstanceCache] Unable to passivate due to ctx 
lock

who can tell me why and help me to resolv this problem, thx!

My standardjboss.xml, it is default:

anonymous wrote :
  | 
  |   
  |  Standard CMP 2.x EntityBean
  |  false
  |  
entity-rmi-invoker
  |  false
  |  
  | org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor
  | org.jboss.ejb.plugins.LogInterceptor
  | org.jboss.ejb.plugins.SecurityInterceptor
  | org.jboss.ejb.plugins.TxInterceptorCMT
  | org.jboss.ejb.plugins.MetricsInterceptor
  | org.jboss.ejb.plugins.EntityCreationInterceptor
  | org.jboss.ejb.plugins.EntityLockInterceptor
  | org.jboss.ejb.plugins.EntityInstanceInterceptor
  | org.jboss.ejb.plugins.EntityReentranceInterceptor
  | org.jboss.resource.connectionmanager.CachedConnectionInterceptor
  | org.jboss.ejb.plugins.EntitySynchronizationInterceptor
  | org.jboss.ejb.plugins.cmp.jdbc.JDBCRelationInterceptor
  |  
  |  
org.jboss.ejb.plugins.EntityInstancePool
  |  
org.jboss.ejb.plugins.InvalidableEntityInstanceCache
  |  
org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager
  |  
org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock
  |  
  | 
org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy
  | 
  |50
  |100
  |300
  |600
  |400
  |60
  |1
  |0.75
  | 
  |  
  |  
  | 100
  |  
  |  B
  |   

OS: Win2000 sp4
RAM: 2G
JBOSS 3.2.1 with jetty

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3886053#3886053

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3886053


---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user


[JBoss-user] [EJB/JBoss] - Unable to passivate due to ctx lock

2005-01-14 Thread natebowler
I've got a stateful session bean, and after using it, I see the folling 
messages repeated in the logs:

WARN  [AbstractInstanceCache.tryToPassivate()]: Unable to passivate due to ctx 
lock, id=e3ypkkzl-8
WARN  [AbstractInstanceCache.tryToPassivate()]: Unable to passivate due to ctx 
lock, id=e3ypklco-9
WARN  [AbstractInstanceCache.tryToPassivate()]: Unable to passivate due to ctx 
lock, id=e3ypkllu-a
WARN  [AbstractInstanceCache.tryToPassivate()]: Unable to passivate due to ctx 
lock, id=e3ypkm0b-c
WARN  [AbstractInstanceCache.tryToPassivate()]: Unable to passivate due to ctx 
lock, id=e3ypkm8n-d
WARN  [AbstractInstanceCache.tryToPassivate()]: Unable to passivate due to ctx 
lock, id=e3ypkmha-e
WARN  [AbstractInstanceCache.tryToPassivate()]: Unable to passivate due to ctx 
lock, id=e3ypkmp2-f
WARN  [AbstractInstanceCache.tryToPassivate()]: Unable to passivate due to ctx 
lock, id=e3ypkmwv-g
WARN  [AbstractInstanceCache.tryToPassivate()]: Unable to passivate due to ctx 
lock, id=e3ypkn7f-h
WARN  [AbstractInstanceCache.tryToPassivate()]: Unable t
o passivate due to ctx lock, id=e3ypkneo-i

The stateful session bean I am using is pretty straightforward, as is the use 
case.

Could someone explain what this means and if there is anything I can do to 
avoid this warning? 

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862204#3862204

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862204


---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user


[JBoss-user] [EJB/JBoss] - "Unable to passivate due to ctx lock" and jboss stops respon

2004-05-17 Thread RichBolen
We're having an issue with JBoss 3.2.3 on Win 2000 server.  It appears to be related 
to "Unable to passivate due to ctx lock" appearing in the log files.  Our jboss server 
stops responding to client requests and we get thousands of these "Unable..." messages 
in our logs.   When the server is working, we don't see any of these messages. 

Does anyone know if there's a clear connection between these messages and the server 
not responding to client requests?  Is it a configuration problem?

Our app uses 2 stateful session beans (and one stateless).  Our cache limit is 100 
for stateful beans.  

I've seen various posts about the "unable to passivate" messages but no clear solution.

I've enabled trace logging on "org.jboss.ejb.plugins" to see what we find.

Rich  

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3835201#3835201

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3835201


---
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


[JBoss-user] [EJB/JBoss] - unable to passivate due to ctx lock

2004-04-14 Thread erikdhansen
I'm running into a problem since upgrading from JBoss 3.2.1 to 3.2.3 with warnings: 
Unable to passivate due to ctx lock.  I've seen a lot of other people with questions 
about this, but haven't been able to find much in the way of answers, yet.

I have a stateful bean which acts as a page iterator for entity beans.  The client 
creates the stateful bean which calls methods on a stateless bean which in turn uses a 
finder method to retrieve a collection of entity beans.  

The stateless bean then returns to the stateful bean a collection of data objects 
which the stateful bean holds onto.

The client then invokes methods in the stateful bean to navigate through the 
collection of data objects.

If the passivation time expires for the stateful bean, I can see JBoss trying to 
passivate the stateful bean, but fails: Unable to passivate due to ctx lock and 
references the stateful bean (id=).

If my stateful bean is holding data objects copied from entity beans by the stateless 
bean (session facade for the entites) why is the stateful failing to passivate?  
Shouldn't the entity beans retrieved by the stateless bean be released when the 
stateless bean invocation completes?

Any information would be greatly appreciated.  Thanks.


View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3830561#3830561

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3830561


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user


[JBoss-user] [EJB/JBoss] - Unable to passivate due to ctx lock

2004-03-15 Thread hswac
Hi,

we've problems with stateful session beans, user transactions and passivation.

When a stateful session bean instance is part of a user transaction and JBoss
tries to passivate this bean we got the warning "Unable to passivate due to ctx lock". 
This is ok, because beans cannot be passivated when they are part of a transaction. 
But when I access the bean afterwards, JBoss tries to activate the bean but can't do 
this because the bean wasn't passivated at all.
We got the following exception:

java.rmi.NoSuchObjectException: Could not activate; failed to restore state; Cau
sedByException is:
C:\Programme\jboss-3.2.2\server\default\tmp\sessions\MyBean-d
ruw1307-8v\druw5s8a-b5.ser (Das System kann die angegebene Datei nicht finden)

For me, this seems to be a bug in JBoss, because JBoss tries to activate a bean which 
was never passivated. We're using JBoss 3.2.2.

Any comments or hints? Thanks in advance.
Helmut


http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3825751#3825751";>View 
the original post

http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3825751>Reply 
to the post


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user