JBoss AS 7 plug-in for JBoss ON reports inconsistent version information for application server resource depending on connection state
Issue
- JBoss Enterprise Application Platform (EAP) targets which had a version other than
EAP 6.0.0.GAbecame broken. - Identical resources report different version strings such as
EAP 6.0.0.GA,EAP 6.0,EAP 6.0.CustomApp. - How does the agent determine the version of the running JBoss instance?
- Is the version determined by directory name?
- Version string changes for the same resource
Environment
- JBoss Operations Network (ON) 3.1.1, 3.1.2
- JBoss Application Server (AS) 7 plug-in for JBoss ON
- JBoss AS resource in any of the following states:
- Inventory status of
NEW - Inventory status of
COMMITTED
- Inventory status of
- JBoss AS resource's version string (as seen in the resource detail page) changes from:
EAP 6.0toEAP 6.0.0.GAEAP 6.0.0.GAtoEAP 6.0EAP <suffix of your JBOSS_HOME direcotry name>to or from any of the above
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.