Bug 1003018

Summary:	Switchyard subsystem should be offilne when connection settings are invalid
Product:	[JBoss] JBoss Operations Network	Reporter:	Libor Zoubek <lzoubek>
Component:	Plugin -- SOA 6	Assignee:	kconner
Status:	CLOSED NOTABUG	QA Contact:	Mike Foley <mfoley>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	JON 3.2	CC:	theute
Target Milestone:	---
Target Release:	JON 3.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-10-04 07:04:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Libor Zoubek 2013-08-30 13:46:38 UTC

Description of problem: Currently user has no way to find out that connection settings for SwitchYard subsystem are correct or not. 


Version-Release number of selected component (if applicable):
RHQ 4.9-master SwitchYard plugin master

How reproducible: always


Steps to Reproduce:
1.create rhqadmin:rhqadmin mgmt user for your SOA instance
2.import it to JON (import must work out-of-box)
3.go to SwitchYard's connection settings and change username to foo

Actual results: SwitchYard subsystem stays UP


Expected results: SwitchYard subsystem must appear DOWN, because when connection settings are wrong, it cannot detect any new applications or push metrics to JON server.


Additional info:

Comment 1 Libor Zoubek 2013-08-30 14:09:14 UTC

It looks like switchyard plugin does not respect connection settings changes.

It does respect it when: I change it to wrong settings, then I restart agent. Then SwitchYard subsystem is DOWN, when I update settings to correct ones, subsystem goes up.

In other cases - when I change from correct to incorrect settings, it does not have any effect.

Comment 2 Libor Zoubek 2013-10-04 07:04:23 UTC

This is no longer valid for JON 3.2.ER2 because switchyard plugin was migrated from MBeans to DMR, so there are no additional connection settings for switchyard subsystem anymore.