anonymous wrote : 
  | 
  | Regarding those pessimistic locking errors: they seem to be suppressed in 
the way that they don't cause any malfunctioning, but why are they logged as 
ERROR? JBossCache 1.2.4 at least logged just the error alone, without the stack 
trace, but 1.3 logs the entire stack, which is really inappropriate for 
expected behaviour. Can this be switched off somehow?
  | 

This is what I mean.  They should be suppressed in 1.3.x, rather than 
embellished.  This is expected behaviour.



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

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


-------------------------------------------------------
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