Bug 1148903

Summary:	RHQ server plugin: JDBC store columns (3) were NOT applied from RHQ console
Product:	[JBoss] JBoss Data Grid 6	Reporter:	Tomas Sykora <tsykora>
Component:	JON Plugin	Assignee:	William Burns <wburns>
Status:	CLOSED UPSTREAM	QA Contact:	Martin Gencur <mgencur>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.4.0	CC:	jdg-bugs, ttarrant
Target Milestone:	CR1
Target Release:	6.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-02-10 03:43:11 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 Tomas Sykora 2014-10-02 15:25:27 UTC

https://issues.jboss.org/browse/ISPN-4799

These 3 column properties:

Data Column
Id Column
Timestamp Column

while being configured in JON interface are _NOT_ added into server configuration file accordingly.

Comment 2 William Burns 2014-10-03 19:42:31 UTC

There is at least 1 issue I have found: JDG 6.4 doesn't currentlly support the database type in either the reader or writer xml code so it is not possible to set this value currently.  So either it needs to be added to the server or removed from the plugin for JDG 6.4

Just glancing at the code the keyed-tables should work properly for both writing and reading so I am not quite sure what is up there.  It worked fine for me on community ISPN and RHQ, but I have to test further with JDG and JON, as there might have been something that didn't merge properly.

Tomas can you provide the version of JON you are using just so I can make sure I am on the same thing?  Thanks.

Comment 3 Tomas Sykora 2014-10-06 12:12:07 UTC

Hi Will,

this is JDG 6.4.ER1 + JON 3.3 ER4

This is link for JON 3.3 ER4 build: https://brewweb.devel.redhat.com//buildinfo?buildID=388959

Version :	
3.3.0.ER04
Build Number :	
99d2107:d7c537e

Comment 4 William Burns 2014-10-06 12:34:04 UTC

Looking closer JDG still uses the old way of setting the database type, which means the plugin needs to be changed specifically for JDG as ISPN is fine.

I will confirm the table issue as it may be JDG specific as well, but I will update as I find out.

Tomas, thanks for the version information.

Comment 5 JBoss JIRA Server 2016-08-02 11:37:51 UTC

Tristan Tarrant <ttarrant> updated the status of jira ISPN-4799 to Closed

Comment 6 Red Hat Bugzilla 2025-02-10 03:43:11 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.