Hi Fred,
Thanks for the quick response, but perhaps I never stated our problem
clearly. You are correct, the example log4j.xml file I sent along did
have the priority set to *info* and at this setting *debug* messages
would definitely be excluded from the output log. However, setting it
to *debug* had the side effect that we picked up debug messages from a
whole host of non-related libraries and frameworks that we're using,
which we're not interested in, so we opted to use a logger filter
(i.e. 'com.hp.ipg.vca.gdt.wizard' see below) to filter out only the
*debug* messages in the named package.
Given this configuration, we pick up all the *debug* messages from
this package in our server-side code, however, we see no *debug*
messages making their way from the client-side to the server log file
even though our client-side code is packaged in the same manner (i.e.
'com.hp.ipg.vca.gdt.wizard').
We do see *debug* messages in the GWT Development console under the
'Application' tab, so clearly the messages are being logged, however,
it appears that something on the server side is filtering them out.
<!--Print only messages of level warn or above in the package com.foo
-->
<logger name="com.hp.ipg.vca.gdt.wizard">
<level value="debug"/>
</logger>
<root>
<priority value="debug" />
<appender-ref ref="ConsoleAppender" />
<appender-ref ref="GDTFileAppender" />
<appender-ref ref="FileAppender" />
</root>
On Mon, Feb 8, 2010 at 11:03 AM, Fred Sauer <[email protected]> wrote:
> In your log4j.xml you have
> <priority value="info" />
> and
> <param name="threshold" value="info" />
> Fred
>
> On Mon, Feb 8, 2010 at 9:06 AM, jd <[email protected]> wrote:
>>
>> First, I'd like to say nice job and *thanks* to Allen for making this
>> library available!
>>
>> Second, here's our situation, I've setup gwt-log with remote logging
>> as follows in our GWT application:
>>
>> Application.gwt.xml
>>
>> ...
>> ...
>> <inherits name="com.allen_sauer.gwt.log.gwt-log-DEBUG" />
>> <set-property name="log_RemoteLogger" value="ENABLED" />
>> <set-property name="log_DivLogger" value="DISABLED" />
>> <set-configuration-property name="log_pattern" value="%d [%t] %p -
>> %m
>> %n" />
>> ...
>> ...
>>
>> web.xml
>> ...
>> ...
>> <servlet>
>> <servlet-name>gwt-log-remote-logger-servlet</servlet-name>
>> <servlet-
>> class>com.allen_sauer.gwt.log.server.RemoteLoggerServiceImpl</servlet-
>> class>
>> </servlet>
>>
>> <servlet-mapping>
>> <servlet-name>gwt-log-remote-logger-servlet</servlet-name>
>>
>> <url-pattern>/com.hp.ipg.vca.gdt.wizard.Application/gwt-log</url-
>> pattern>
>> </servlet-mapping>
>> ...
>> ...
>>
>>
>> log4j.xml
>> ...
>> ...
>> <appender name="ConsoleAppender"
>> class="org.apache.log4j.ConsoleAppender">
>> <layout class="org.apache.log4j.SimpleLayout" />
>> </appender>
>>
>> <appender name="FileAppender"
>> class="org.apache.log4j.FileAppender">
>> <param name="File" value="${logs.dir}/gdt-wizard.log" />
>> <param name="Append" value="false" />
>> <layout class="org.apache.log4j.PatternLayout">
>> <param name="ConversionPattern" value="%d [%t] %p -
>> %m%n" />
>> </layout>
>> </appender>
>>
>> <appender name="GDTFileAppender"
>> class="org.apache.log4j.RollingFileAppender">
>> <param name="maxFileSize" value="100KB" />
>> <param name="maxBackupIndex" value="5" />
>> <param name="File"
>> value="${logs.dir}/gdt-wizard-rolling.log" />
>> <param name="threshold" value="info" />
>> <layout class="org.apache.log4j.PatternLayout">
>> <param name="ConversionPattern" value="%d{ABSOLUTE} %5p
>> %c{1}:%L - %m%n" />
>> </layout>
>> </appender>
>>
>> <root>
>> <priority value="info" />
>> <appender-ref ref="ConsoleAppender" />
>> <appender-ref ref="GDTFileAppender" />
>> <appender-ref ref="FileAppender" />
>> </root>
>> ...
>> ...
>>
>> In our GWT Application.java (the class that implements the GWT
>> EntryPoint interface) we've setup the '
>> Log.setUncaughtExceptionHandler();' we output the sample test messages
>> as illustrated in the getting started guide.
>>
>> ...
>> ...
>> Log.debug("This is a 'DEBUG' test message");
>> Log.info("This is a 'INFO' test message");
>> Log.warn("This is a 'WARN' test message");
>> Log.error("This is a 'ERROR' test message");
>> Log.fatal("This is a 'FATAL' test message");
>> ...
>> ...
>>
>> In the GWT Development console we see the full compliment of these
>> messages displayed as expected, however, on the *server-side* of the
>> equation our logs display ALL but the "This is a 'DEBUG' test
>> message".
>>
>> So it would appear as though the DEBUG messages are being captured and
>> routed to the server via the GWT-LOG Remote Logging facilities,
>> however, it appears they are being stripped.
>>
>> Any thoughts?
>>
>> Thanks in advance for any tips or pointers.
>>
>>
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "gwt-log" group.
>> To post to this group, send email to [email protected].
>> To unsubscribe from this group, send email to
>> [email protected].
>> For more options, visit this group at
>> http://groups.google.com/group/gwt-log?hl=en.
>>
>
>
>
> --
> Fred Sauer
> Developer Advocate
> Google Inc.
> 1600 Amphitheatre Parkway
> Mountain View, CA 94043
> [email protected]
>
> --
> You received this message because you are subscribed to the Google Groups
> "gwt-log" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/gwt-log?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"gwt-log" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/gwt-log?hl=en.
