[JBoss JIRA] Created: (JGRP-803) CLONE -Use the correct MBeanServer if multiple MBeanServers are present
8:42 p.m.
CLONE -Use the correct MBeanServer if multiple MBeanServers are present
-----------------------------------------------------------------------
Key: JGRP-803
URL: https://jira.jboss.org/jira/browse/JGRP-803
Project: JGroups
Issue Type: Bug
Affects Versions: 2.2.8, 2.2.9, 2.2.9.1, 2.2.9.2
Reporter: Robert Buck
Assignee: Bela Ban
Fix For: 2.3
Current code is
ArrayList servers=MBeanServerFactory.findMBeanServer(null);
if(servers != null && servers.size() > 0) {
return (MBeanServer)servers.get(0);
}
This takes the first server it find. However, if we run JBoss (which has its own
MBeanServer) inside of JDK 5 (which also has an MBeanServer), we have multiple servers.
The code needs to be changes to accommodate that
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:48 p.m.
New subject: [JBoss JIRA] Updated: (JGRP-803) CLONE -Use the correct MBeanServer if multiple MBeanServers are present
[
https://jira.jboss.org/jira/browse/JGRP-803?page=com.atlassian.jira.plugi...
]
Robert Buck updated JGRP-803:
-----------------------------
Description:
The prior bug did not fix the issue of running the cache under jboss when the following
options are present:
set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote
The code is presently as follows (which is incorrect, by the way):
{code}
157 List servers=MBeanServerFactory.findMBeanServer(null);
158 if(servers == null || servers.size() == 0)
159 throw new Exception("TreeCacheView.init(): no MBeanServers
found");
{code}
TreeCacheView fails to deploy because it is using the wrong MBeanServer. Rather than doing
the above, you should either do something like:
{code}
import org.jboss.mx.util.MBeanServerLocator;
...
// find the local MBeanServer
MBeanServer server = MBeanServerLocator.locateJBoss();
{code}
, or you should do something like this:
{code}
public static MBeanServer getDefaultMBeanServer() {
return findMBeanServer("jboss");
}
private static MBeanServer findMBeanServer(String agentId) {
List servers = MBeanServerFactory.findMBeanServer(null);
if (servers != null && servers.size() > 0) {
for (Object object : servers) {
MBeanServer server = (MBeanServer) object;
if (server.getDefaultDomain().equals(agentId)) {
return server;
}
}
}
return null;
}
{code}
The reason is because with Java 5, when the "-Dcom.sun.management.jmxremote"
switch is turned on, the default platform MBeanServer is the zeroth instance rather than
"jboss".
To test, deploy the tree cache view, and start JBoss with the JAVA_OPTS mentioned above.
was:
Current code is
ArrayList servers=MBeanServerFactory.findMBeanServer(null);
if(servers != null && servers.size() > 0) {
return (MBeanServer)servers.get(0);
}
This takes the first server it find. However, if we run JBoss (which has its own
MBeanServer) inside of JDK 5 (which also has an MBeanServer), we have multiple servers.
The code needs to be changes to accommodate that
CLONE -Use the correct MBeanServer if multiple MBeanServers are
present
-----------------------------------------------------------------------
Key: JGRP-803
URL: https://jira.jboss.org/jira/browse/JGRP-803
Project: JGroups
Issue Type: Bug
Affects Versions: 2.2.8, 2.2.9, 2.2.9.1, 2.2.9.2
Reporter: Robert Buck
Assignee: Bela Ban
Fix For: 2.3
The prior bug did not fix the issue of running the cache under jboss when the following
options are present:
set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote
The code is presently as follows (which is incorrect, by the way):
{code}
157 List servers=MBeanServerFactory.findMBeanServer(null);
158 if(servers == null || servers.size() == 0)
159 throw new Exception("TreeCacheView.init(): no MBeanServers
found");
{code}
TreeCacheView fails to deploy because it is using the wrong MBeanServer. Rather than
doing the above, you should either do something like:
{code}
import org.jboss.mx.util.MBeanServerLocator;
...
// find the local MBeanServer
MBeanServer server = MBeanServerLocator.locateJBoss();
{code}
, or you should do something like this:
{code}
public static MBeanServer getDefaultMBeanServer() {
return findMBeanServer("jboss");
}
private static MBeanServer findMBeanServer(String agentId) {
List servers = MBeanServerFactory.findMBeanServer(null);
if (servers != null && servers.size() > 0) {
for (Object object : servers) {
MBeanServer server = (MBeanServer) object;
if (server.getDefaultDomain().equals(agentId)) {
return server;
}
}
}
return null;
}
{code}
The reason is because with Java 5, when the "-Dcom.sun.management.jmxremote"
switch is turned on, the default platform MBeanServer is the zeroth instance rather than
"jboss".
To test, deploy the tree cache view, and start JBoss with the JAVA_OPTS mentioned above.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:52 p.m.
New subject: [JBoss JIRA] Updated: (JGRP-803) CLONE -Use the correct MBeanServer if multiple MBeanServers are present
[
https://jira.jboss.org/jira/browse/JGRP-803?page=com.atlassian.jira.plugi...
]
Robert Buck updated JGRP-803:
-----------------------------
Fix Version/s: (was: 2.3)
Affects Version/s: (was: 2.2.8)
(was: 2.2.9)
(was: 2.2.9.1)
(was: 2.2.9.2)
Description:
The prior bug did not fix the issue of running the cache under jboss when the following
options are present:
set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote
The code is presently as follows (which is incorrect, by the way):
{code}
157 List servers=MBeanServerFactory.findMBeanServer(null);
158 if(servers == null || servers.size() == 0)
159 throw new Exception("TreeCacheView.init(): no MBeanServers
found");
{code}
TreeCacheView fails to deploy because it is using the wrong MBeanServer. Rather than doing
the above, you should either do something like:
{code}
import org.jboss.mx.util.MBeanServerLocator;
...
// find the local MBeanServer
MBeanServer server = MBeanServerLocator.locateJBoss();
{code}
, or you should do something like this:
{code}
public static MBeanServer getDefaultMBeanServer() {
return findMBeanServer("jboss");
}
private static MBeanServer findMBeanServer(String agentId) {
List servers = MBeanServerFactory.findMBeanServer(null);
if (servers != null && servers.size() > 0) {
for (Object object : servers) {
MBeanServer server = (MBeanServer) object;
if (server.getDefaultDomain().equals(agentId)) {
return server;
}
}
}
return null;
}
{code}
The reason is because with Java 5, when the "-Dcom.sun.management.jmxremote"
switch is turned on, the default platform MBeanServer is the zeroth instance rather than
"jboss".
See:
http://fisheye.jboss.com/browse/JBossCache/core/support-branches/1.4.1.SP...
To test, deploy the tree cache view, and start JBoss with the JAVA_OPTS mentioned above.
was:
The prior bug did not fix the issue of running the cache under jboss when the following
options are present:
set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote
The code is presently as follows (which is incorrect, by the way):
{code}
157 List servers=MBeanServerFactory.findMBeanServer(null);
158 if(servers == null || servers.size() == 0)
159 throw new Exception("TreeCacheView.init(): no MBeanServers
found");
{code}
TreeCacheView fails to deploy because it is using the wrong MBeanServer. Rather than doing
the above, you should either do something like:
{code}
import org.jboss.mx.util.MBeanServerLocator;
...
// find the local MBeanServer
MBeanServer server = MBeanServerLocator.locateJBoss();
{code}
, or you should do something like this:
{code}
public static MBeanServer getDefaultMBeanServer() {
return findMBeanServer("jboss");
}
private static MBeanServer findMBeanServer(String agentId) {
List servers = MBeanServerFactory.findMBeanServer(null);
if (servers != null && servers.size() > 0) {
for (Object object : servers) {
MBeanServer server = (MBeanServer) object;
if (server.getDefaultDomain().equals(agentId)) {
return server;
}
}
}
return null;
}
{code}
The reason is because with Java 5, when the "-Dcom.sun.management.jmxremote"
switch is turned on, the default platform MBeanServer is the zeroth instance rather than
"jboss".
To test, deploy the tree cache view, and start JBoss with the JAVA_OPTS mentioned above.
CLONE -Use the correct MBeanServer if multiple MBeanServers are
present
-----------------------------------------------------------------------
Key: JGRP-803
URL: https://jira.jboss.org/jira/browse/JGRP-803
Project: JGroups
Issue Type: Bug
Reporter: Robert Buck
Assignee: Bela Ban
The prior bug did not fix the issue of running the cache under jboss when the following
options are present:
set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote
The code is presently as follows (which is incorrect, by the way):
{code}
157 List servers=MBeanServerFactory.findMBeanServer(null);
158 if(servers == null || servers.size() == 0)
159 throw new Exception("TreeCacheView.init(): no MBeanServers
found");
{code}
TreeCacheView fails to deploy because it is using the wrong MBeanServer. Rather than
doing the above, you should either do something like:
{code}
import org.jboss.mx.util.MBeanServerLocator;
...
// find the local MBeanServer
MBeanServer server = MBeanServerLocator.locateJBoss();
{code}
, or you should do something like this:
{code}
public static MBeanServer getDefaultMBeanServer() {
return findMBeanServer("jboss");
}
private static MBeanServer findMBeanServer(String agentId) {
List servers = MBeanServerFactory.findMBeanServer(null);
if (servers != null && servers.size() > 0) {
for (Object object : servers) {
MBeanServer server = (MBeanServer) object;
if (server.getDefaultDomain().equals(agentId)) {
return server;
}
}
}
return null;
}
{code}
The reason is because with Java 5, when the "-Dcom.sun.management.jmxremote"
switch is turned on, the default platform MBeanServer is the zeroth instance rather than
"jboss".
See:
http://fisheye.jboss.com/browse/JBossCache/core/support-branches/1.4.1.SP...
To test, deploy the tree cache view, and start JBoss with the JAVA_OPTS mentioned above.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:54 p.m.
New subject: [JBoss JIRA] Closed: (JGRP-803) CLONE -Use the correct MBeanServer if multiple MBeanServers are present
[
https://jira.jboss.org/jira/browse/JGRP-803?page=com.atlassian.jira.plugi...
]
Robert Buck closed JGRP-803.
----------------------------
Resolution: Won't Fix
wrong project, sorry.
CLONE -Use the correct MBeanServer if multiple MBeanServers are
present
-----------------------------------------------------------------------
Key: JGRP-803
URL: https://jira.jboss.org/jira/browse/JGRP-803
Project: JGroups
Issue Type: Bug
Reporter: Robert Buck
Assignee: Bela Ban
The prior bug did not fix the issue of running the cache under jboss when the following
options are present:
set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote
The code is presently as follows (which is incorrect, by the way):
{code}
157 List servers=MBeanServerFactory.findMBeanServer(null);
158 if(servers == null || servers.size() == 0)
159 throw new Exception("TreeCacheView.init(): no MBeanServers
found");
{code}
TreeCacheView fails to deploy because it is using the wrong MBeanServer. Rather than
doing the above, you should either do something like:
{code}
import org.jboss.mx.util.MBeanServerLocator;
...
// find the local MBeanServer
MBeanServer server = MBeanServerLocator.locateJBoss();
{code}
, or you should do something like this:
{code}
public static MBeanServer getDefaultMBeanServer() {
return findMBeanServer("jboss");
}
private static MBeanServer findMBeanServer(String agentId) {
List servers = MBeanServerFactory.findMBeanServer(null);
if (servers != null && servers.size() > 0) {
for (Object object : servers) {
MBeanServer server = (MBeanServer) object;
if (server.getDefaultDomain().equals(agentId)) {
return server;
}
}
}
return null;
}
{code}
The reason is because with Java 5, when the "-Dcom.sun.management.jmxremote"
switch is turned on, the default platform MBeanServer is the zeroth instance rather than
"jboss".
See:
http://fisheye.jboss.com/browse/JBossCache/core/support-branches/1.4.1.SP...
To test, deploy the tree cache view, and start JBoss with the JAVA_OPTS mentioned above.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5904
days inactive
5904
days old
3 comments
1 participants
participants (1)
-
Robert Buck (JIRA)