JBossAS resource type is for JBoss AS 3.2.x/4.x server. This causes confusing log messages to be generated when requested as an optional plugin, e.g.: Optional plugin [JBossAS] was requested by plugins [[Hibernate]] but it does not exist in the dependency graph yet and will be ignored. See the IRC log bellow. (23:29:42) smcgowan: 2009-11-02 16:36:09,886 INFO [org.rhq.core.pc.PluginContainer] (http-127.0.0.1-8080-2) Initializing Plugin Container v1.3.0.EmbJopr.1.3.0-4... (23:29:42) smcgowan: 2009-11-02 16:36:11,841 INFO [org.rhq.core.clientapi.agent.metadata.PluginDependencyGraph] (http-127.0.0.1-8080-2) Optional plugin [JBossAS] was requested by plugins [[Hibernate]] but it does not exist in the dependency graph yet and will be ignored (23:29:42) smcgowan: 2009-11-02 16:36:13,364 INFO [org.rhq.core.clientapi.agent.metadata.PluginMetadataParser] (http-127.0.0.1-8080-2) There is no resource type named [JBossAS Server] from a plugin named [JBossAS]. This is probably because that plugin is missing. Resource Type [Hibernate Statistics] will not have that missing type as a possible parent. 23:30 (23:30:23) smcgowan: we had many changed w.r.t. Hibernate in Branch_5_x so looking to understand if this is a regression or we previsoulsy included Hibernate support (23:31:09) ips: smcgowan: i think that's actually ok. hibernate should still work (23:31:47) ips: hibernate plugin defines the hibernate resource type itself as having two possible parent resource types - JBoss AS Server or JBoss AS5 Server (23:32:10) ips: it's just saying it can't support the former bc the jboss-as plugin isn't included (23:32:29) ips: but the latter should still work since the jboss-as-5 plugin -is- included (23:39:33) ozizka: ips, could the name be something like JBossAsLegacy or similar, to make it less confusing? 23:40 (23:40:39) ips: ozizka: you mean the resource type name? (23:40:45) ozizka: Yes (23:41:11) ozizka: Or, is the "JBoss AS Server" for JBoss AS 4? (23:41:26) ips: yeah, it is (23:41:34) ozizka: Bingo :) (23:41:41) ozizka: ips: BTW, Since when will RHQ and Jopr be available only via Git? Can you let me in (23:41:45) ips: it's kind of confusing because it's really JBoss AS 3.2.x/4.x Server :) (23:41:50) ozizka: with my account, ozizka? (23:42:19) ozizka: Ok, let's create a jira issue for the res type name (23:42:32) ips: unfortunately, the resource type names are used as keys, so we can't easily change it as this point
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2482
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs. keyword: new = Tracking + FutureFeature + SubBug
making sure we're not missing any bugs in rhq_triage
Closing per triage