It is a deadlock problem. We could not figure out why it was happening inspite of the
synchronized block. Is there any stratey we can follow to avoid such an issue while using
the JBoss Cache in high performance environment.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030474#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...