Hi Tim,
Thanks for the quick reply. I removed the ACCLogManager and haven't noticed any
issues. It's working well enough for me to use while testing / debugging and
that's all I'm really concerned about for now. For production I don't see it
being a problem to leave the script as is and have everything logged to the same
file.
Ryan
glassfish_at_javadesktop.org wrote:
> Hi, Ryan.
>
> Let me answer two ways. Strictly speaking, editing the script is probably officially not supported.
>
> Having said that, practically speaking, removing the logging setting should not cause any problems but this is not a scenario that's tested so please let us know what you find if you try it.
>
> Briefly, I believe the original thinking behind the ACCLogManager is to take its settings from the sun-acc.xml file (or whatever is specified as the -xml argument to the appclient command) so the log settings for the client can be managed in the same place - that XML file - as other client settings. The comments in the ACCLogManager source explain that it intentionally removes other handlers due to "double-logging" of messages that would otherwise occur. I'm not sure if that is still an issue and whether you may see that if you remove the property setting from the script.
>
> - Tim
> [Message sent by forum member 'tjquinn' (tjquinn)]
>
> http://forums.java.net/jive/thread.jspa?messageID=228829
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>