Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours
Bug 588803 - as5 plugin's getAvailability() should handle the case then AS5/AS6 instance is listening on an AS4 Server Resource's JNP URL
as5 plugin's getAvailability() should handle the case then AS5/AS6 instance i...
Product: RHQ Project
Classification: Other
Component: Plugins (Show other bugs)
All All
low Severity low (vote)
: ---
: ---
Assigned To: Ian Springer
Corey Welton
Depends On:
  Show dependency treegraph
Reported: 2010-05-04 12:28 EDT by Ian Springer
Modified: 2013-08-05 20:36 EDT (History)
1 user (show)

See Also:
Fixed In Version: 2.4
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-08-12 12:56:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ian Springer 2010-05-04 12:28:56 EDT
When it detects a server from a different config path is listening on the server's JNP URL, it should also log an error, rather than a debug message (though this error should be throttled, since getAvailablity() is called frequently.
Comment 1 Ian Springer 2010-05-04 14:47:52 EDT
Fixed by git rev 6261da7f85ffbc00386495ffdf6e080871355237.

1) inventory an EAP 4.x instance and verify it is green in the GUI
2) stop the EAP 4.x instance
3) start up an EAP 5.0 or AS 6.0 instance on the same bind address as the EAP 4.x instance
4) run the 'avail' Agent prompt command to kick off a full availability scan
5) verify that an error message similar to the following is logged to the Agent log:

[ERROR] Availability check for JBoss AS Resource with configPath [/opt/jboss-eap-4.3/jboss-as/server/production] has connected to a different running JBoss AS instance which is installed at [/opt/jboss-as-6.0/server/default] using namingURL [jnp:] - returning AvailabilityType.DOWN..."

6) run the 'avail' Agent prompt command a second time to kick off another full availability scan
7) verify that the error message is not logged again
8) go to the GUI and verify the Resource is red
Comment 2 Corey Welton 2010-05-19 09:21:48 EDT
QA verified.
Comment 3 Corey Welton 2010-08-12 12:56:18 EDT
Mass-closure of verified bugs against JON.

Note You need to log in before you can comment on or make changes to this bug.