2.0.3 On Thu, Apr 29, 2010 at 9:42 AM, ravirocks <[email protected]> wrote:
> Thanks Fred for such a quick response! You rock!!!! > > Meanwhile, I was able to get around it via following code: > > Log.getSystemLogger().setCurrentLogLevel(LogUtil.stringToLevel(logLevel)); > > instead of: > > Log.setCurrentLogLevel(LogUtil.stringToLevel(logLevel)); > > We are tied to a third party gwt library that ties to us to GWT 1.7. > So not sure if I can use the build below (since it could be based on > GWT 1.7+). What GWT version is the build based on? > > Thank you again! > > Regards, > Ravi Hasija > > Fred Sauer wrote: > > Ravi, > > > > This has always bugged me. Thanks for reporting it. I'm no longer > forwarding > > these message to the server as of r466. > > > > See the attached build and let me know how it works. > > > > Fred > > > > > > On Wed, Apr 28, 2010 at 1:14 PM, ravirocks <[email protected]> > wrote: > > > > > Hi, > > > > > > We are using gwt-log library's remote logging facility and we have the > > > following settings: > > > > > > <inherits name="com.allen_sauer.gwt.log.gwt-log-TRACE"/> > > > <set-property name="log_WindowLogger" value="DISABLED"/> > > > <set-property name="log_DivLogger" value="DISABLED"/> > > > <set-property name="log_RemoteLogger" value="ENABLED" /> > > > > > > However at main module load time I am changing the log level > > > programmatic-ally to INFO. It is logging the following message in the > > > server logs: > > > > > > 28 Apr 2010 15:49:45,126 FATAL [btpool0-4] (ServerLogImplLog4J.java: > > > 48) - [127.0.0.1] [CLIENT] Temporarily setting the current (runtime) > > > log level filter to 'OFF'. > > > > > > Is there a way this message be not logged as FATAL. This is generating > > > an email to the QA and we will like to avoid that by logging the same > > > message as INFO or DEBUG. Is it possible to log the message above at > > > debug/info level? Is there a way to change the log level at run time > > > and not log this message as FATAL. > > > > > > Please advice. > > > > > > Regards, > > > Ravi H > > > > > > -- > > > 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]<gwt-log%[email protected]> > <gwt-log%[email protected]<gwt-log%[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]<gwt-log%[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]<gwt-log%[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.
