[jboss-as7-dev] Logging Subsystem Changes

[James Perkins]

On 11/26/2012 10:13 PM, Stuart Douglas wrote:
>
>
> James Perkins wrote:
>> Mainly because the logging.properties is overwritten so it would only be
>> there on the very first boot. After that everything is written to the
>> server.log. Also resolving determining the path was an issue IIRC.
>
> Assuming of course that the first boot succeeds :-) Trying to figure 
> out why your new install won't boot sounds like it might be a problem.
>>
>> Note too this is only on the very first boot and a clean install. On the
>> next boot the JVM parameters and what not will be written out to the
>> server.log file.
>
> So this means that after the first start the logging.properties will 
> be modified? Shouldn't we be trying to ship a logging.properties that 
> corresponds to the default standalone.xml settings? Or does the lack 
> of expressions mean that we now have to write absolute paths to this 
> file?
I'm trying to remember what the issue was with keeping the file handler 
in the initial properties. It was almost a year ago I was working on 
this. I almost think it may have been something with the 
jboss.server.log.dir system property. Since a while ago we changed that 
to get resolved in the scripts, it might not really be an issue at all. 
I'll test it today and see if we can get that working.

We still wouldn't end up with a separate boot log, but everything would 
be logged into server.log from the start.
>
> Stuart
>
>>
>> On 11/26/2012 03:38 PM, Andrig Miller wrote:
>>> Why are we getting rid of the boot.log?
>>>
>>> We depend on that for information from the customer in support, and 
>>> I certainly have used it many times just to see that my changes like 
>>> JVM parameters, etc. are what I was expecting.  Most production 
>>> systems won't even have the CONSOLE to log to, so this information 
>>> is just being lost.
>>>
>>> Andy 
>>

-- 
James R. Perkins
JBoss by Red Hat