[
https://issues.jboss.org/browse/AS7-5600?page=com.atlassian.jira.plugin.s...
]
Nicholas DiPiazza updated AS7-5600:
-----------------------------------
Description:
I am specifying a journal-directory as an absolute path.
<journal-directory path="C:/JBoss/jboss-journal" />
This worked on JBoss 7.1.1.Final which uses HornetQ 2.2.13.
I moved to the latest snapshot from Hudson which is currently jboss-as-7.2.0.Alpha1 /
HornetQ 2.2.21.
It will append the path to the JBoss data directory. Thus I get this error: Cannot open
file
"C:\JBoss\server-backup\jboss-as-7.2.0.Alpha1-SNAPSHOT\standalone\data\C:\JBoss\jboss-journal\server.lock"
was:
I am specifying a journal-directory as an absolute path.
<journal-directory path="C:/JBoss/jboss-journal" />
This worked on WJBoss 7.1.1.Final which uses HornetQ 2.2.13.
I moved to the latest snapshot from Hudson which is currently Ijboss-as-7.2.0.Alpha1.
It will append the path to the JBoss data directory. Thus I get this error: Cannot open
file
"C:\JBoss\server-backup\jboss-as-7.2.0.Alpha1-SNAPSHOT\standalone\data\C:\JBoss\jboss-journal\server.lock"
journal-directory paths are not appended correctly in messaging
subsystem
-------------------------------------------------------------------------
Key: AS7-5600
URL:
https://issues.jboss.org/browse/AS7-5600
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.2.0.Alpha1
Environment: AS7 upstream. I tested this on Windows XP only so far.
Reporter: Nicholas DiPiazza
Assignee: Jeff Mesnil
I am specifying a journal-directory as an absolute path.
<journal-directory path="C:/JBoss/jboss-journal" />
This worked on JBoss 7.1.1.Final which uses HornetQ 2.2.13.
I moved to the latest snapshot from Hudson which is currently jboss-as-7.2.0.Alpha1 /
HornetQ 2.2.21.
It will append the path to the JBoss data directory. Thus I get this error: Cannot open
file
"C:\JBoss\server-backup\jboss-as-7.2.0.Alpha1-SNAPSHOT\standalone\data\C:\JBoss\jboss-journal\server.lock"
--
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