Admin Console should provide a way for specifying additional logger that
is not in the logging.properties file. We have that feature in v2.
I have just logged
http://java.net/jira/browse/GLASSFISH-16190 so that
user doesn't need to use CLI to do it.
thanks
Anissa.
On 3/10/11 6:54 AM, Tom Mueller wrote:
> Any log level that the system knows about can be managed from the
> admin console via the Logging screen within the Configurations
> section. However, to get a new log level added to the list, it is
> necessary to run the "asadmin set-log-levels" command. For example,
> of the logger used by your application is com.example.app1, then run:
>
> asadmin set-log-levels com.example.app1=INFO
>
> From then on, the com.example.app1 log setting will show up on the
> console and can be managed from there. If you have your application
> deployed to a cluster, then using the --target option for
> set-log-levels to set it for the appropriate cluster.
>
> Tom
>
>
> On 3/9/2011 6:10 PM, forums_at_java.net wrote:
>> hi all,
>>
>> we are doveloping a webapplication, where we use some webservices.
>>
>> we need to be able to controll the logging option from the glassfih
>> admin
>> console, this mean (our wish ) all the configuration files should be
>> red from
>> the war files and added to the logger settings automatically when the
>> war
>> file deployed.
>>
>> is this possible ?????
>>
>>
>>
>> best regards
>>
>> Yahya
>>
>>
>> --
>>
>> [Message sent by forum member 'yahya_h']
>>
>> View Post: http://forums.java.net/node/779787
>>
>>