[
http://jira.jboss.com/jira/browse/JBAS-4421?page=all ]
Jeremy Norris updated JBAS-4421:
--------------------------------
Workaround Description:
This is a hack until this is resolved properly, but allows you still still use the
jmx-console for MBean names without '%' in them.
deploy/jmx-console.war/displayMBeans.jsp: line 47 insert the following:
if (properties.contains("%")) {
continue;
}
jmx-console does handle glassbox MBeans correctly.
--------------------------------------------------
Key: JBAS-4421
URL:
http://jira.jboss.com/jira/browse/JBAS-4421
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.5.GA
Environment: Glassbox 2.0 Beta
Reporter: Jeremy Norris
Glassbox 2.0 Beta on JBoss 4.0.5.
When the jmx-console main page is loaded, it stack traces when visiting many of the
glassbox MBeans.
ie:
java.lang.IllegalArgumentException: URLDecoder: Illegal hex characters in escape (%)
pattern - For input string: "'""
at java.net.URLDecoder.decode(URLDecoder.java:173)
at java.net.URLDecoder.decode(URLDecoder.java:83)
...
Problems occur with MBean names that look like this:
resource0="jdbc:mysql://<server>:3306/<schema_name>",resource1="SHOW
FULL COLUMNS FROM `table_name` FROM `schema_name` LIKE '%'",topic=stats
The problem is the '%' character is not being handled correctly by the jmx
console. Even though this is a unusual name for an MBean, I think it's legal (This
particular MBean name example is coming from some hibernate DDL generation stuff on
initialization that glassbox is instrumenting, but this is not important right now).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira