Bug 886126

Summary:	Datasource JNDI change takes too long to be propagated to JON server
Product:	[JBoss] JBoss Operations Network	Reporter:	Jakub Cechacek <jcechace>
Component:	Plugin -- JBoss EAP 5	Assignee:	Thomas Segismont <tsegismo>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mike Foley <mfoley>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	JON 3.1.2	CC:	jkudrnac, lfuka, myarboro, rhatlapa, tsegismo
Target Milestone:	ER01
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:		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 Jakub Cechacek 2012-12-11 15:12:20 UTC

This issue is probably related to https://bugzilla.redhat.com/show_bug.cgi?id=886119


If you change JNDI name of some Datasource from lets say "foo" to "bar" two things happen 

1) Because datasource type resources are being referenced by JNDI instead of Resource Name (key?) the old "foo" resource will become dead but still visible in inventory of EAP server resource. 

2) After some time (probably when discovery -f is performed on agent side) new child resource of name "bar" appears in inventory

Comment 1 Radim Hatlapatka 2012-12-17 13:57:38 UTC

Till JON runs check for changes the resource with old name (JNDI name) is visible in JON, which makes it confusing for customer. The workaround is to run discovery manually (on the agent run discovery -f, or the agent's manual discovery operation).

The datasource resource should be rather associated with its resource name, if it is specified during its creation, it would prevent this kind of errors as having two datasources at the same time when one is invalid and second is valid.

Comment 3 Thomas Segismont 2013-07-25 16:08:42 UTC

Fixed in master

commit 4ab947d9c450a94601055509cb9c4240b0652210
Author: Thomas Segismont <tsegismo>
Date:   Thu Jul 25 18:06:07 2013 +0200

In EAP5, JNDI name is the key of Datasource and Connection Factory managed components. Consequently, there is no way to change the JNDI name of such components without creating a new managed component, which will in the end be discovered by RHQ.

So in RHQ, jndi-name config property is now marked as read-only (it will still be required when creating a Datasource or a Connection Factory).

Comment 4 Larry O'Leary 2013-09-06 14:30:31 UTC

As this is MODIFIED or ON_QA, setting milestone to ER1.

Comment 5 Libor Fuka 2013-09-25 12:11:57 UTC

VERIFIED with JON 3.2.0.ER1 and EAP 5.2.0.GA
You can't change JNDI name of DataSource, JNDI Name is read-only attribute