Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-4421

jmx-console does handle glassbox MBeans correctly.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Major Major
    • No Release
    • JBossAS-4.0.5.GA
    • Web Console
    • None

    • Glassbox 2.0 Beta

    • Hide

      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;
      }

      Show
      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; }

      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).

              Unassigned Unassigned
              jnorris10 Jeremy Norris (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: