I did follow this thread 'cause we're facing the same problems.

I did c/o hibernate trunk this morning, but i still get (With jboss-cache  
1.3.0.SP2) these strange don't kno
w how to handle messages (when using OPTIMISTIC cache locking)


  | 2006-05-31 09:23:44,254 INFO  
[org.jboss.cache.interceptors.OptimisticNodeInterceptor] CRUD Method 
_put(GlobalTransaction:<null>:311, 
/de/eyetea/hfax/entity/auktion/Car2Auktion/de.eyetea.hfax.entity.auktion.Car2Auktion#80339,
 item, 
CacheEntry(de.eyetea.hfax.entity.auktion.Car2Auktion)[EYETEA,null,null,2006-05-30
 
21:48:08.132,0,null,BID,null,null,80827,1000,null,null,false,80338,56384,80339,80339],
 true, 0) called - don't know how to handle!
  | 

With PESIMISTIC cache locking we still get Exceptions like
2006-05-31 09:39:06,580 ERROR [org.jboss.cache.lock.IdentityLock] write lock 
for 
/de/eyetea/hfax/entity/auktion/Gebot/de.eyetea.hfax.entity.auktion.Gebot#80821 
could not be acquired after 0 ms. Locks: Read lock owners: {}
  | Write lock owner: GlobalTransaction:<null>:175
  |  (caller=GlobalTransaction:<null>:168, lock info: write 
owner=GlobalTransaction:<null>:175 ([EMAIL PROTECTED]))
  | 

Note that the we have 
anonymous wrote : 5000

in jboss-service.xml, but the exceptions says "0 ms".

We're using jboss cache as a "standalone" .sar / mbean, could this be the 
reason for this behaviour?



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

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


-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to