Recall that the logging info is in domain.xml and that it needs to be
moved to logging.properties. That was done in UpgradeLogging the first
time that the server came up until recently. Now I see that the info is
in 2 places, domain.xml and logging.properties in the latest v3 releases.
Does that mean that if I install a v3 build that I need to run asadmin
with the --upgrade option the first time I start the domain for it to be
v3 ready?
It seems not. If not then how does the logging info get moved? It needs
to happen if the release is v2 or v3.
Carla
Jerome Dochez wrote:
> yes people have to call asadmin start-domain --upgrade over an existing
> domain installation in order to get it ready for v3.
>
> On Oct 13, 2009, at 5:55 PM, Carla Mott wrote:
>
>>
>> Hi,
>>
>> I'm looking into a bug and noticed that contents of logging.properties
>> file is incorrect. Debugging shows that UpgradeLogging service is
>> never called and therefore the values in domain.xml are not moved to
>> logging.properties. Did something change such that UpgradeLogging
>> is no longer called? the bug was filed on Fri Oct 9.
>>
>>
>> Thanks,
>> Carla
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>