-
1. Re: Running multiple standalone instances of JBOSS on the same machine fails due to HornetQ FileLockNodeManager
ctomc May 9, 2012 10:00 AM (in response to newway)1 of 1 people found this helpfulhi,
in messeging subsystem add:
<journal-directory path="${hornetq.dir:data/messaging}" relative-to="jboss.server.base.dir" />
and then you can run server with:
standalone -Dhornetq.dir=data/server1
or configure it manualy.
--
tomaz
-
2. Re: Running multiple standalone instances of JBOSS on the same machine fails due to HornetQ FileLockNodeManager
newway May 9, 2012 11:19 AM (in response to ctomc)Thanks for you help - this helped me to solve the problem - but not exactly as you described the solution
Tomaz Cerar wrote:
hi,
in messeging subsystem add:
<journal-directory path="${hornetq.dir:data/messaging}" relative-to="jboss.server.base.dir" />
...
When I try to use the suggestion you gave I get the following error
WARN [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-4) can't open file C:\JBOSS7\standalone\${hornetq.dir:data\messaging}\server.lock: java.io.IOException: The filename, directory name, or volume label syntax is incorrect at java.io.WinNTFileSystem.createFileExclusively(Native Method) [rt.jar:1.6.0_16] at java.io.File.createNewFile(File.java:883) [rt.jar:1.6.0_16] ...
I changed it to
<journal-directory path="${hornetq.dir}/data/messaging" relative-to="jboss.server.base.dir" />
and I pass the hornetq.dir - but it looks like it is not being used and I get a folder with the name ${hornetq.dir} under the standalone folder
so I configured the name manually - without passing it as a variable.
(This is actually interesting that I don't manage to configure some of the things in the standalone xml using variables and some i mange - for example I pass -Dmy.app.root - I manage to instruct the deployment scanner to look there - but when I try to configure the log to the same place it just create a folder called ${my.app.root})
thanks,
Noa
-
3. Re: Running multiple standalone instances of JBOSS on the same machine fails due to HornetQ FileLockNodeManager
ctomc May 9, 2012 11:38 AM (in response to newway)1 of 1 people found this helpfulHi,
yes this can be a problem, the trick is that not every attribute supports expressions, we added support for many attributes in 7.1 but still not everything is covered.
can you create jira issue for this, so we can make sure it gets addressed in future versions.
--
tomaz