Bug 1393936

Summary: Element relative-to not applicable to leveldb-store
Product: [JBoss] JBoss Data Grid 6 Reporter: Rafael Chies <rchies>
Component: DocumentationAssignee: Christian Huffman <chuffman>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.6.0CC: chuffman, jdg-bugs, rchies
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Build Name: 23149, Administration and Configuration Guide-6.6 Build Date: 08-09-2016 09:25:13 Topic ID: 41565-775568 [Specified]
Last Closed: 2019-01-30 19:50:20 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:
Attachments:
Description Flags
Standalone configuration none

Description Rafael Chies 2016-11-10 16:34:03 UTC 
Doc: Administration Guide
Title: Cache Store Configuration Details (Remote Client-Server Mode)

The doc says "The relative-to parameter specifies the base directory to store the cache state. This value defaults to jboss.server.data.dir".

I tried to use this relative-to parameter, but it's not valid. When I start JDG the following error is raised: "Message: JBAS014788: Unexpected attribute 'relative-to' encountered"
Comment 2 Christian Huffman 2016-11-30 20:33:47 UTC 
Rafael,

I tested this on a JDG 6.6 server using the following configuration:

        <subsystem xmlns="urn:infinispan:server:core:6.4" default-cache-container="local">
            <cache-container name="local" default-cache="default" statistics="true">
                <local-cache name="default" start="EAGER">
                    <file-store name="myFileStore"
                        passivation="true"
                        purge="true"
                        relative-to="jboss.server.config.dir"
                        path="store"
                        max-entries="10000"
                        fetch-state="true"
                        preload="false" />
                    <locking acquire-timeout="30000" concurrency-level="1000" striping="false"/>
                    <transaction mode="NONE"/>
                </local-cache>
            </cache-container>
        </subsystem>

This started successfully for me.  

In addition, checking the schemas ($JDG_SERVER/docs/schema/jboss_infinispan_core_6_4.xsd) the `relative-to` attribute is listed here as well.

Can you provide the full configuration where this was encountered?
Comment 3 Rafael Chies 2016-12-02 18:57:29 UTC 
Hi Christian, thanks for analyzing this.
You have tested the single file store. The unexpected behavior that I mentioned was related to the leveldb-store (look the case title). I'm attaching here an example of standalone.xml with your configuration, but changing the file-store element by leveldb-store. Using this XML configuration you probably are going to face the same issue.

Thanks,
Comment 4 Rafael Chies 2016-12-02 18:58:11 UTC 
Created attachment 1227458 [details]
Standalone configuration
Comment 5 Christian Huffman 2019-01-30 19:50:20 UTC 
I'm closing this issue out due to age. If it persists, file a corresponding JIRA.