+1. The same problem you had re: the Cached Connection Manager exists for a JBoss Cache
instance if the ClusteredSingleSignOn valve is used. There's a longstanding hack in
the ClusteredSingleSignOn that gets around the problem, but it would be nice to get rid of
it.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059624#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...