-
1. Re: boot.log missing when using specialized standalone configuration
jamezp Nov 28, 2012 2:20 PM (in response to bmsantos)In the JBOSS_HOME\bin\standalone.conf.bat file set the JBOSS_BASE_DIR environment variable.
set "JBOSS_BASE_DIR=C:\dev\server\jboss-as-7.1.1.Final\my-standalone-configuration-dir"
--
James R. Perkins
-
2. Re: boot.log missing when using specialized standalone configuration
bmsantos Nov 29, 2012 2:54 PM (in response to bmsantos)Thanks James! You guys rock!
-
3. Re: boot.log missing when using specialized standalone configuration
bmsantos Nov 29, 2012 4:05 PM (in response to jamezp)James,
Your solution works great on Windows but it is not working on Linux, more specifically, Red Hat Enterprise Linux 6 (Santiago)
.
-
4. Re: boot.log missing when using specialized standalone configuration
jamezp Nov 29, 2012 4:07 PM (in response to bmsantos)You just need to set the evironment variable in the standalone.conf for Linux.
export JBOSS_BASE_DIR="/opt/jboss/my-standalone-configuration-dir"
--
James R. Perkins
-
5. Re: boot.log missing when using specialized standalone configuration
bmsantos Nov 30, 2012 10:17 AM (in response to jamezp)James,
Yes, that's exactly how and where I added it but to no avail.
-
6. Re: boot.log missing when using specialized standalone configuration
jamezp Nov 30, 2012 12:55 PM (in response to bmsantos)Bruno,
Hmm, that should work. You could try passing -Djboss.server.base.dir=your/dir and see if that works.
--
James R. Perkins
-
7. Re: boot.log missing when using specialized standalone configuration
bmsantos Nov 30, 2012 1:31 PM (in response to jamezp)James,
Yes, that is exactly how I have been starting the server, by passing the java land "jboss.server.base.dir" property to standalone.sh
From the beggining that I was surprised to see that passing this property was not enough for JBoss to find the default log directory.
By the way, the "standalone" directory was removed and it is not present. The only directory present is "
my-standalone-configuration-dir
". -
8. Re: boot.log missing when using specialized standalone configuration
jamezp Nov 30, 2012 1:34 PM (in response to bmsantos)1 of 1 people found this helpfulBruno,
On Windows it's a bit of a challenge to parse the incoming parameters which is why it doesn't work right on there. On Linux it should work. I had a look at the bash script and it first looks for the system property being passed then checks the environment variable. I'm not sure why adding it to standalone.conf wouldn't work.
--
James R. Perkins
-
9. Re: boot.log missing when using specialized standalone configuration
bmsantos Nov 30, 2012 1:44 PM (in response to bmsantos)1 of 1 people found this helpfulJames,
Got it!
The issue was that I was only setting:
-Djboss.server.base.dir=
my-standalone-configuration-dir
And, by passing the full path as:
-Djboss.server.base.dir=$JBOSS_HOME/
my-standalone-configuration-dir
It works just fine!
I was assuming that by the fact that JBoss succeeds in finding the "standalone.xml" configuration file that it would also know where to drop the logs (maybe this is little bug).
And, just in case someone else finds the same issue, the environment variable JBOSS_BASE_DIR is not required when the java property is set.
James, again, thanks for your help.