Bug 1017011

Summary: Adding possibility to change type of object store to JDBC one under the Transaction subsytem
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Ondrej Chaloupka <ochaloup>
Component: Web ConsoleAssignee: Harald Pehl <hpehl>
Status: CLOSED NOTABUG QA Contact: Jakub Cechacek <jcechace>
Severity: medium Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.2.0CC: brian.stansberry, hbraun, hpehl, jkudrnac, myarboro
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-02 14:13:46 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Ondrej Chaloupka 2013-10-09 07:09:15 UTC 
Web console currently contains item "Use HornetQ Store?" under tab Common.
This allows user change the object store which will be used for saving information about on-fly transactions.

The EAP 6.2.0 comes with new type of object store - JDBC object store. I suppose that adding such configuration option would be logical step.

The JDBC object store needs to be referenced to existing datasource and its settings have following limitations:
 - it has to be standard datasource (not the xa one)
 - the datasource *has to* be set as jta=false (otherwise the server even fails to start)
 - the server has to be restarted for the jdbc object store would be activated  (reload is not enough)
Comment 1 Ondrej Chaloupka 2013-10-10 14:11:51 UTC 
I've got one more idea about this - when JDBC object store is set then hornetq object store has to be deactivated. Maybe there could be better to have radio buttons with file system/hornetq/jdbc object stores. But this is just an idea.
Comment 2 Heiko Braun 2014-07-02 14:07:02 UTC 
Please use the community Jira for feature requests next time.
Comment 3 Heiko Braun 2014-07-02 14:13:46 UTC 
The JDBC store config seems to be more complex than just a the data source name. Please create feature request in the community Jira and outline the complete use case and everything impact/constraint it might have on the hornetq store configuration option.

I am going to close this one.
Comment 4 JBoss JIRA Server 2015-11-04 10:37:30 UTC 
Heiko Braun <ike.braun> updated the status of jira HAL-444 to Coding In Progress
Comment 5 JBoss JIRA Server 2015-11-23 08:59:25 UTC 
Heiko Braun <ike.braun> updated the status of jira HAL-444 to Resolved
Comment 6 JBoss JIRA Server 2015-11-23 08:59:32 UTC 
Heiko Braun <ike.braun> updated the status of jira HAL-444 to Reopened
Comment 7 JBoss JIRA Server 2015-11-23 08:59:38 UTC 
Heiko Braun <ike.braun> updated the status of jira HAL-444 to Closed