-
30. Jopr and JBoss AS 5.1.0
meghasuresh May 9, 2011 7:58 PM (in response to ips)Hi,
I am new to JBoss and just installed my first JBoss EAP 5.1 version. I had set up a cluster of JBoss servers successfully but I had noticed that i cannot manage both the instances with one single Admin console. I have then noticed this Forum and understood jopr is not supported with 5.1.
Are there any solutions found that can help setting up jopr or I would need to upgrade to 6.0?
-
31. Jopr and JBoss AS 5.1.0
ips May 9, 2011 8:05 PM (in response to meghasuresh)As I stated in my first post on this thread, EAP 5.1 is supported, but AS 5.1 is not.
supported: EAP 5.0.x, EAP 5.1.x, AS 6.0.x, AS 6.1.x
not supported: AS 5.0.x
-
32. Jopr and JBoss AS 5.1.0
meghasuresh May 9, 2011 8:09 PM (in response to ips)Great thanks very much Ian. I will now look around for the documentation to install and enable this plug in
-
33. Jopr and JBoss AS 5.1.0
ips May 9, 2011 9:30 PM (in response to meghasuresh)It's the jboss-as-5 plugin and is included with the RHQ distribution.
-
34. Re: Jopr and JBoss AS 5.1.0
cristivlc Jul 22, 2011 1:07 AM (in response to ips)Hi
I need to use JBOSS 5.1 and I want to modify the plugin sources too, but I am new to RHQ Project. Can somebody explain how is done?
What I tried is to clone with GIT all RHQ sources and execute: mvn -Penterprise,dev -DskipTests -Ddbsetup install
But it stops after 10 minutes with an error saying there is a problem with a jar file.
Also, I am wondering if there is an Eclipse project or something like that. And is possible to compile only the plugin, not the entire server?Thank you very much,
Cristi
-
35. Re: Jopr and JBoss AS 5.1.0
mazz Jul 22, 2011 9:17 AM (in response to cristivlc)Basic build notes: http://rhq-project.org/display/RHQ/Building+RHQ
Advanced Build Notes: http://rhq-project.org/display/RHQ/Advanced+Build+Notes
Yes, the eclipse project files are checked into git. Eclipse notes: http://rhq-project.org/display/RHQ/Eclipse+Tips
If you have your own custom plugin, you can just build that and not have the source, all RHQ artifacts are in the jboss maven repo. But to compile the RHQ base plugins, I believe you need to have the full source. I've never tried to just build the RHQ plugin by themselves without also buildign the core RHQ as well.
-
36. Re: Jopr and JBoss AS 5.1.0
sergio.tondin Sep 20, 2011 10:05 AM (in response to swiderski.maciej)It would be possible to make the download has rhq with support for JBoss 5.1GA? thanks
-
37. Re: Jopr and JBoss AS 5.1.0
ips Sep 20, 2011 2:04 PM (in response to sergio.tondin)The RHQ dev team has no plans to add support for AS 5.x at this time. However, if Cristi or someone else from the community can get AS 5.1 discovery and management working by modifying either the jboss-as or jboss-as-5 plugin, they can submit a patch, and I can merge it into the code base if it looks good.
-
38. Re: Jopr and JBoss AS 5.1.0
sergio.tondin Oct 6, 2011 12:43 PM (in response to ips)If it were possible to do this you would be grateful. -
39. Re: Jopr and JBoss AS 5.1.0
will.tatam Mar 3, 2012 12:37 PM (in response to swiderski.maciej)I have an working build for RHQ 4.2.0 if anyone needs it. Built using changes mentioned in thread plus change to JBossASServerComponent
Messageme if you need it
-
40. Re: Jopr and JBoss AS 5.1.0
conor.williams Mar 5, 2012 11:18 AM (in response to will.tatam)i had upgraded to the EE Enterprise Edition
-
41. Re: Jopr and JBoss AS 5.1.0
blaffitte Mar 5, 2012 5:23 PM (in response to swiderski.maciej)For people who needs to monitor JBoss AS 5.1.0.GA servers I made a patch based on jboss-as-5 3.0.1.GA rhq plugin.
This patch do not permit to manage completly AS 5.1.0.GA servers but it help a lot for basic monitoring tasks.
diff --git a/modules/enterprise/server/sars/pom.xml b/modules/enterprise/server/sars/pom.xml
index 3e4e5be..96a1e55 100644
--- a/modules/enterprise/server/sars/pom.xml
+++ b/modules/enterprise/server/sars/pom.xml
@@ -41,7 +41,7 @@
<pluginRepository>
<id>jboss-deprecated-repository</id>
<name>JBoss Deprecated</name>
- <url>https://repository.jboss.org/maven2/</url>
+ <url>https://repository.jboss.org/nexus/content/repositories/deprecated</url>
<snapshots>
<enabled>false</enabled>
</snapshots>
diff --git a/modules/plugins/jboss-as-5/pom.xml b/modules/plugins/jboss-as-5/pom.xml
index 6754dcd..a11c077 100644
--- a/modules/plugins/jboss-as-5/pom.xml
+++ b/modules/plugins/jboss-as-5/pom.xml
@@ -13,7 +13,7 @@
</parent>
<groupId>org.jboss.on</groupId>
- <artifactId>jopr-jboss-as-5-plugin</artifactId>
+ <artifactId>jopr-jboss-as-510-plugin</artifactId>
<packaging>jar</packaging>
<name>RHQ JBossAS 5.x Plugin</name>
diff --git a/modules/plugins/jboss-as-5/src/main/java/org/rhq/plugins/jbossas5/ApplicationServerDiscoveryComponent.java b/modules/plugins/jboss-as-5/src/main/java/org/rhq/plugins/jbossas5/ApplicationServerDiscoveryComponent.java
index 2a403fa..896792d 100644
--- a/modules/plugins/jboss-as-5/src/main/java/org/rhq/plugins/jbossas5/ApplicationServerDiscoveryComponent.java
+++ b/modules/plugins/jboss-as-5/src/main/java/org/rhq/plugins/jbossas5/ApplicationServerDiscoveryComponent.java
@@ -89,17 +89,15 @@ public class ApplicationServerDiscoveryComponent implements ResourceDiscoveryCom
private static final Map<JBossProductType, ComparableVersion> MINIMUM_PRODUCT_VERSIONS = new HashMap(3);
static {
- MINIMUM_PRODUCT_VERSIONS.put(JBossProductType.AS, new ComparableVersion("5.2.0.Beta1"));
- MINIMUM_PRODUCT_VERSIONS.put(JBossProductType.EAP, new ComparableVersion("5.0.0.Beta"));
- MINIMUM_PRODUCT_VERSIONS.put(JBossProductType.EWP, new ComparableVersion("5.0.0.CR1"));
- MINIMUM_PRODUCT_VERSIONS.put(JBossProductType.SOA, new ComparableVersion("5.0.0.Beta"));
+ MINIMUM_PRODUCT_VERSIONS.put(JBossProductType.AS, new ComparableVersion("5.1.0.GA"));
}
private static final List<String> CLIENT_JARS = Arrays.asList(
// NOTE: The jbossall-client.jar aggregates a whole bunch of other jars from the client dir via its
// MANIFEST.MF Class-Path.
"client/jbossall-client.jar", "client/trove.jar", "client/javassist.jar",
- "common/lib/jboss-security-aspects.jar", "lib/jboss-managed.jar", "lib/jboss-metatype.jar",
+ "common/lib/jboss-security-aspects.jar", "common/lib/hibernate-core.jar", "common/lib/jboss-profileservice.jar",
+ "lib/jboss-managed.jar", "lib/jboss-metatype.jar", "lib/jboss-reflect.jar",
"lib/jboss-dependency.jar");
private static final List<String> AS6_CLIENT_JARS = new ArrayList<String>(CLIENT_JARS);
diff --git a/modules/plugins/jboss-as-5/src/main/java/org/rhq/plugins/jbossas5/connection/RemoteProfileServiceConnectionProvider.java b/modules/plugins/jboss-as-5/src/main/java/org/rhq/plugins/jbossas5/connection/RemoteProfileServiceConnectionProvider.java
index d90f5a2..028e4fe 100644
--- a/modules/plugins/jboss-as-5/src/main/java/org/rhq/plugins/jbossas5/connection/RemoteProfileServiceConnectionProvider.java
+++ b/modules/plugins/jboss-as-5/src/main/java/org/rhq/plugins/jbossas5/connection/RemoteProfileServiceConnectionProvider.java
@@ -106,9 +106,8 @@ public class RemoteProfileServiceConnectionProvider extends AbstractProfileServi
this.initialContext = createInitialContext(env);
ProfileService profileService = (ProfileService) lookup(this.initialContext, PROFILE_SERVICE_JNDI_NAME);
- ManagementView managementView = (ManagementView) lookup(this.initialContext, MANAGEMENT_VIEW_JNDI_NAME);
- DeploymentManager deploymentManager = (DeploymentManager) lookup(this.initialContext,
- DEPLOYMENT_MANAGER_JNDI_NAME);
+ ManagementView managementView = (ManagementView) profileService.getViewManager(); // lookup(this.initialContext, MANAGEMENT_VIEW_JNDI_NAME);
+ DeploymentManager deploymentManager = (DeploymentManager) profileService.getDeploymentManager(); // lookup(this.initialContext, DEPLOYMENT_MANAGER_JNDI_NAME);
AbstractProfileServiceConnection profileServiceConnection;
if (this.principal != null) {
diff --git a/modules/plugins/jboss-as-5/src/main/resources/META-INF/rhq-plugin.xml b/modules/plugins/jboss-as-5/src/main/resources/META-INF/rhq-plugin.xml
index 5ca45a1..bb3f7ff 100644
--- a/modules/plugins/jboss-as-5/src/main/resources/META-INF/rhq-plugin.xml
+++ b/modules/plugins/jboss-as-5/src/main/resources/META-INF/rhq-plugin.xml
@@ -931,9 +931,9 @@
-<plugin name="JBossAS5" displayName="JBoss Application Server 5.x" package="org.rhq.plugins.jbossas5"
+<plugin name="JBossAS51" displayName="JBoss Application Server 5.x" package="org.rhq.plugins.jbossas5"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- description="Supports management and monitoring of JBoss AS from version EAP 5"
+ description="Supports management and monitoring of JBoss AS from version 5.1.x"
xmlns="urn:xmlns:rhq-plugin"
xmlns:c="urn:xmlns:rhq-configuration">
diff --git a/pom.xml b/pom.xml
index ea21cc6..6b0f9fc 100644
--- a/pom.xml
+++ b/pom.xml
@@ -823,7 +823,7 @@ version is changed the versions of each of these should be validated and updated
<repository>
<id>jboss-deprecated-repository</id>
<name>JBoss Deprecated</name>
- <url>https://repository.jboss.org/maven2/</url>
+ <url>https://repository.jboss.org/nexus/content/repositories/deprecated</url>
<releases>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
-
42. Re: Jopr and JBoss AS 5.1.0
will.tatam Mar 6, 2012 6:06 AM (in response to blaffitte)Your patch to fix the as5 plugin is smaller than mine to get the as4 plugin to connect to 5.1
What bits at broken still im your updated plugin? For mine, it fails to get the state of entity homes
-
43. Re: Jopr and JBoss AS 5.1.0
blaffitte Mar 6, 2012 12:13 PM (in response to will.tatam)I haven't test it on EJB and all deployment parts, my needs are to monitor JVM, servers, datasources and application, but in my investigations I found that profileService isn't has mature as EAP version.
I think that your problem come from this difference of profileservice version between AS and EAP.
One solution could be to replace EJB monitoring through profileservice by a JMX monitoring one...
-
44. Re: Jopr and JBoss AS 5.1.0
rbattenfeld Mar 8, 2012 1:47 PM (in response to blaffitte)Hi
I was able to manage that rhq is reqognizing jboss 6.1. See more here https://community.jboss.org/thread/196288
Perhaps this solution works for jboss 5.1 as well. I think the change is high.
Regards,
Ralf