Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 957994

Summary:	Change H2 database from in-memory to persistent mode for Overlord
Product:	[JBoss] JBoss Fuse Service Works 6	Reporter:	Jiri Pechanec <jpechane>
Component:	Configuration	Assignee:	Gary Brown <gbrown>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jiri Pechanec <jpechane>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.0.0 GA	CC:	dlesage, gbrown, jsedlace, kconner, ncross, soa-p-jira
Target Milestone:	DR6
Target Release:	6.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	The data in the gadget server database is not persistent. Users need to re-configure their gadget settings every time they restart the gadget server.	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 Jiri Pechanec 2013-04-30 04:31:41 UTC

Gadget server currently uses datasource configured in gs-ds.xml. It is configured using 

jdbc:h2:mem:gadget-server;DB_CLOSE_DELAY=-1

connection string which means that the data in database are not peristent and are removed after server restart.

I think this is not good solution especially for the gadget server as a user that configures its gadgets, plays with Overlord, adds new account etc. needs to do this after every server restart.

Thus I propose either to change DS to persistent mode or provide a hint to user to do this on his own as the current setup is very confusing and inconvenient.

Comment 1 JBoss JIRA Server 2013-06-10 10:48:50 UTC

Gary Brown <gary> updated the status of jira RTGOV-196 to Closed

Comment 2 Jiri Sedlacek 2013-07-01 11:25:15 UTC

verified in DR6