Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-4886

Admin Console relies specific library directories

    XMLWordPrintable

    Details

    • Affects:
      Release Notes
    • Release Notes Text:
      Hide
      The ApplicationServerDiscoveryComponent class does not use JBoss variables because the paths are hardcoded to the jar files. If JBoss library locations and the JBoss variables for the libraries (jboss.lib.url, jboss.common.lib.url and jboss.server.lib.url) were changed, the JBoss Admin Console failed to open. This issue is resolved by adding BootstrapAction.createPluginContainerConfiguration() to the Admin Console.
      Show
      The ApplicationServerDiscoveryComponent class does not use JBoss variables because the paths are hardcoded to the jar files. If JBoss library locations and the JBoss variables for the libraries (jboss.lib.url, jboss.common.lib.url and jboss.server.lib.url) were changed, the JBoss Admin Console failed to open. This issue is resolved by adding BootstrapAction.createPluginContainerConfiguration() to the Admin Console.
    • Release Notes Docs Status:
      Documented as Resolved Issue
    • Docs QE Status:
      ON_QA

      Description

      If the JBoss library locations are altered and the JBoss variables for the libraries (jboss.lib.url,jboss.common.lib.url and jboss.server.lib.url) are made consistent with the library locations the JBoss Admin Console cannot be opened.

      Investigations shows
      This is because the ApplicationServerDiscoveryComponent class don't use JBoss variables and instead hard coded the path to jar files:
      See at the end of ApplicationServerDiscoveryComponent:
      CLIENT_JARS = Arrays.asList(new String[]

      { "client/jbossall-client.jar", "client/trove.jar", "client/javassist.jar", "common/lib/jboss-security-aspects.jar", "lib/jboss-managed.jar", "lib/jboss-metatype.jar", "lib/jboss-dependency.jar" }

      );
      AS6_CLIENT_JARS = new ArrayList(CLIENT_JARS);
      AS6_CLIENT_JARS.add("lib/jboss-classpool.jar");
      AS6_CLIENT_JARS.add("lib/jboss-classpool-scoped.jar");

      And it seems still the case in the trunk: http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=blob;f=modules/plugins/jboss-as-5/src/main/java/org/rhq/plugins/jbossas5/ApplicationServerDiscoveryComponent.java

        Gliffy Diagrams

          Attachments

            Issue Links

            is blocked by

            Bug - A problem which impairs or prevents the functions of the product. EMBJOPR-329 jboss-as-5 plugin: reliance on hard-coded app server library paths

            • Critical - An upcoming version that is affected by this issue cannot be released until it's addressed. A critical bug is one that crashes the application, causes loss of data or severe memory leak.
            • Coding In Progress

              Activity

                People

                • Assignee:
                  ozizka Ondrej Zizka
                  Reporter:
                  ShaunA Shaun Appleton
                  Writer:
                  Rebecca Newton
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: