Bug 1002976 - JDBC object store does not change LOG_STORE_TYPE attribute
Summary: JDBC object store does not change LOG_STORE_TYPE attribute
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Transaction Manager
Version: 6.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER4
: EAP 6.2.0
Assignee: Ivo Studensky
QA Contact: Ondrej Chaloupka
Russell Dickenson
URL:
Whiteboard:
Depends On: 971358
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-30 11:56 UTC by Ivo Studensky
Modified: 2013-12-15 16:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-15 16:17:55 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-1765 0 Major Resolved JDBC object store does not change LOG_STORE_TYPE attribute 2013-12-06 10:26:53 UTC

Description Ivo Studensky 2013-08-30 11:56:06 UTC 
Description of problem:
The transaction subsystem when set up to the JDBC object store should keep a note about it in the log-store-type attribute, like the HornetQ object store does. It seems not to be consistent when the latter fills this attribute, but the former does not.

This bugzilla is a clone of WFLY-1765 for EAP.
Comment 1 Ivo Studensky 2013-09-26 14:05:32 UTC 
Relevant PR:

https://github.com/jbossas/jboss-eap/pull/470
Comment 5 Ondrej Chaloupka 2013-12-06 10:06:51 UTC 
The log-store attribute is correctly changed when store is put to jdbc object one.
Verified EAP 6.2.0.CR3
Note You need to log in before you can comment on or make changes to this bug.