I have read the JBossCacheAndWAS Wiki on how to accomplish this and I have a concern with this approach. Moving the JBoss Cache JARs to the %WAS_ROOT%/lib/ext directory requires overriding the WebSphere JMX JAR jmxc.jar in $WAS_ROOT%/lib. I believe this would interfere with WebSphere and the administration console, not to mention resistance from the infrastructure folks.
Is this the only option? What would prevent the cache and/or JGroups channel from shutting down cleanly when the application class loader is shutting down? Am I correct that there is still a cache or channel which was loaded from the old application class loader still being notified of broadcasts from the new application? Why would this situation lock up the application server process? Alternatively, is there any plan to remove the dependency on JBoss JMX, as the JMX capability is not used outside of JBoss AS? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3944668#3944668 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3944668 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
