Bug 1019012 - The location of the log depends on type of used object store
Summary: The location of the log depends on type of used object store
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Documentation
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: GA
: EAP 6.3.0
Assignee: Misha H. Ali
QA Contact: Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-15 00:04 UTC by Ondrej Chaloupka
Modified: 2014-08-14 15:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Build Name: 14875, Development Guide-6.2-1 Build Date: 02-10-2013 13:20:00 Topic ID: 4307-459932 [Latest]
Last Closed: 2014-06-28 15:27:10 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Ondrej Chaloupka 2013-10-15 00:04:08 UTC 
Title: Handle a Heuristic Outcome in a Transaction

Please add not that location of the transaction log depends on used object store and on the settings of the object-store-relative-to and object-store-path configuration paramters.

For file system ones - standard shadow log and hornetq - the default directory location is ok. When you use jdbc object store then the location of the log is in a DB.
Comment 2 Scott Mumford 2014-02-26 05:13:42 UTC 
Moving to ON_QA.

The changes should be available for review on the documentation stage within an hour or so from this comment.

http://documentation-devel.engineering.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/
Comment 3 Scott Mumford 2014-02-26 05:15:44 UTC 
Moving to ON_QA.

The changes should be available for review on the documentation stage within an hour or so from this comment.

http://documentation-devel.engineering.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/
Comment 4 Ondrej Chaloupka 2014-02-26 08:17:33 UTC 
Perfect, thanks.
Note You need to log in before you can comment on or make changes to this bug.