-
Bug
-
Resolution: Done
-
Major
-
EAP 5.0.1
-
EAP 5.0.1
-
Release Notes
-
-
Documented as Resolved Issue
-
ON_QA
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[]
);
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