Bug 588803

Summary:	as5 plugin's getAvailability() should handle the case then AS5/AS6 instance is listening on an AS4 Server Resource's JNP URL
Product:	[Other] RHQ Project	Reporter:	Ian Springer <ian.springer>
Component:	Plugins	Assignee:	Ian Springer <ian.springer>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Corey Welton <cwelton>
Severity:	low	Docs Contact:
Priority:	low
Version:	1.3.1	CC:	ccrouch
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	2.4	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-08-12 16:56:18 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ian Springer 2010-05-04 16:28:56 UTC

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 18:47:52 UTC

Fixed by git rev 6261da7f85ffbc00386495ffdf6e080871355237.

INSTRUCTIONS FOR TESTING THE FIX
================================
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:127.0.0.1:1099/] - 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 13:21:48 UTC

QA verified.

Comment 3 Corey Welton 2010-08-12 16:56:18 UTC

Mass-closure of verified bugs against JON.