I've given up trying to explain this. If you don't follow the spec semantics, the CCM won't understand what you are doing.
If you "cache" things outside an EJB instance you can expect the CCM to complain. Solution: Understand the spec semantics and don't try to work around them i.e. play nicely with the connection manager and pooling OR remove the CachedConnectionInterceptor View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867145#3867145 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867145 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
