[jboss-jira] [JBoss JIRA] (AS7-5661) CLONE - Absolute path in attribute "path" in paging-directory, bindings-directory, journal-directory and large-messages-directory elements is always taken as relative path
Jeff Mesnil (JIRA)
jira-events at lists.jboss.org
Mon Oct 1 10:10:03 EDT 2012
[ https://issues.jboss.org/browse/AS7-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Mesnil resolved AS7-5661.
------------------------------
Resolution: Duplicate Issue
this issue has been fixed in AS7-5600
> CLONE - Absolute path in attribute "path" in paging-directory, bindings-directory, journal-directory and large-messages-directory elements is always taken as relative path
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-5661
> URL: https://issues.jboss.org/browse/AS7-5661
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Miroslav Novak
> Assignee: Jeff Mesnil
> Fix For: 7.1.4.Final (EAP)
>
>
> When HornetQ journal is specified using absolute paths then it's treated as relative path:
> {code}
> <hornetq-server>
> ...
> <paging-directory path="/home/jbossqa/hornetq_eap6_testsuite/journal_A/paging"/>
> <bindings-directory path="/home/jbossqa/hornetq_eap6_testsuite/journal_A/bindings"/>
> <journal-directory path="/home/jbossqa/hornetq_eap6_testsuite/journal_A/journal"/>
> <large-messages-directory path="/home/jbossqa/hornetq_eap6_testsuite/journal_A/large-messages"/>
> ...
> </hornetq-server>
> {code}
> Server log:
> {code}
> 15:29:07,418 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-7) live server is starting with configuration HornetQ Configuration (clustered=true,backup=false,sharedStore=true,journalDirectory=/home/jbossqa/hornetq_eap6_testsuite/server1/jboss-eap-6.0/standalone/data//home/jbossqa/hornetq_eap6_testsuite/journal_A/journal,bindingsDirectory=/home/jbossqa/hornetq_eap6_testsuite/server1/jboss-eap-6.0/standalone/data//home/jbossqa/hornetq_eap6_testsuite/journal_A/bindings,largeMessagesDirectory=/home/jbossqa/hornetq_eap6_testsuite/server1/jboss-eap-6.0/standalone/data//home/jbossqa/hornetq_eap6_testsuite/journal_A/large-messages,pagingDirectory=/home/jbossqa/hornetq_eap6_testsuite/server1/jboss-eap-6.0/standalone/data//home/jbossqa/hornetq_eap6_testsuite/journal_A/paging)
> {code}
> Definition of "directoryType" from jboss-as-messaging_1_2.xsd:
> {code}
> <xs:complexType name="directoryType">
> <xs:annotation>
> <xs:documentation>
> <![CDATA[
> A directory location configuration.
> The "path" attribute denotes a relative or absolute filesystem pathname where the directory should be
> located.
> The "relative-to" attribute references a global path configuration in the domain model, defaulting
> to the JBoss Application Server data directory (jboss.server.data.dir). If the value of the "path" attribute
> does not specify an absolute pathname, it will treated as relative to this path.
> ]]>
> </xs:documentation>
> </xs:annotation>
> <xs:attribute name="relative-to" type="xs:string" default="jboss.server.data.dir" />
> <xs:attribute name="path" type="xs:string" />
> </xs:complexType>
> {code}
> It seems that detection that given string in path attribute is absolute path is not correct.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list