boot.log missing when using specialized standalone configuration

[bmsantos]

Hi,

When using a specialized standlalone configuration and no standalone directory present I get the following error:

Unable to read the logging configuration from 'file:C:\dev\server\jboss-as-7.1.1.Final\standalone/configuration/logging.properties' (java.io.FileNotFo
undException: C:\dev\server\jboss-as-7.1.1.Final\standalone\configuration\logging.properties (The system cannot find the path specified))

The server was initialized in the following way:

JBOSS_HOME\bin\standalone.bat -Djboss.server.base.dir=my-standalone-configuration-dir

And I can see the server.log in JBOSS_HOME\my-standalone-configuration-dir\log but the boot.log is missing.

The logging.properties file is avaiable in JBOSS_HOME\my-standalone-configuration-dir\configuration\logging.properties (as in the default standalone\configuration).

Any ideas on how to fix this?

Thanks

[jamezp]

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

[bmsantos]

Thanks James! You guys rock!

[bmsantos]

James,

Your solution works great on Windows but it is not working on Linux, more specifically, Red Hat Enterprise Linux 6 (Santiago)

.

[jamezp]

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

[bmsantos]

James,

Yes, that's exactly how and where I added it but to no avail.

[jamezp]

Bruno,

Hmm, that should work. You could try passing -Djboss.server.base.dir=your/dir and see if that works.

--

James R. Perkins

[bmsantos]

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".

[jamezp]

Bruno,

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

[bmsantos]

James,

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.