/commented by valentin kulichenko/ Eric,
This is a known issue with clustered WebLogic environment. WebLogic shares one MBean server across instances of one application and this causes a name collision in Ignite MBeans. You can set the following system property to solve the issue (it will append class loader hash code and JVM id to each MBean name to avoid such collisions): */-DIGNITE_MBEAN_APPEND_JVM_ID=true/* ----- /This post is migrated from now discontinued Apache Ignite forum at http://apacheignite.readme.io/v1.0/discuss/ -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Running-multiple-NEAR-ONLY-caches-in-same-JVM-for-production-redeployment-tp97p98.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
