ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Valentin Kulichenko <valentin.kuliche...@gmail.com>
Subject MBean naming
Date Sun, 19 Apr 2015 23:07:43 GMT
Guys,

I created ticket https://issues.apache.org/jira/browse/IGNITE-766 based on
this forum post:
http://apacheignite.readme.io/v1.0/discuss/551db8b0a7e98017009e3e97

Currently we append class loader hash and JVM ID only in pair,
if IGNITE_MBEAN_APPEND_JVM_ID system property is set. But I believe that in
most cases we're dealing with different application instances loaded by
different class loader, but not with different JVMs (and such deployment is
pretty typical, at least for WebLogic).

So I suggest to ALWAYS append class loader hash, while JVM ID will still be
appended only if system property is set. In this case the property will be
very rarely used, but we can leave it to be on the safe side.

This change will allow to avoid such questions from WebLogic users, who
have to use this not-very-well-documented workaround.

Any objections?

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message