Thanks Fred.  I now see the exception and stack.  The stack traces will
always have "Unknown" class names in production mode, right?  Only in hosted
mode can we expect more meaningful class names?

Also... please let me know when the next "official" release will be that
will include the fix.

Thanks again,

Eric

2010-07-20 06:40:18,216 ERROR [gwt-log](http-0.0.0.0-8001-6) Null Pointer
test Caused by: java.lang.NullPointerException: THis is an NPE
java.lang.NullPointerException: THis is an NPE
 at Unknown.CAc(Unknown source:0)
 at Unknown.K2b(Unknown source:0)
 at Unknown.AEb(Unknown source:0)
 at Unknown.PC(Unknown source:0)
 at Unknown.yG(Unknown source:0)
 at Unknown.cG(Unknown source:0)
 at Unknown.Y9(Unknown source:0)
 at Unknown.zC(Unknown source:0)
 at Unknown.Q9(Unknown source:0)
 at Unknown.deb(Unknown source:0)
 at Unknown.Bbb(Unknown source:0)
 at Unknown.U0(Unknown source:0)
 at Unknown.anonymous(Unknown source:0)
 at Unknown.xu(Unknown source:0)
 at Unknown.anonymous(Unknown source:0)
 at Unknown.jw(Unknown source:0)
 at Unknown.Mdb(Unknown source:0)
 at Unknown.deb(Unknown source:0)
2010-07-20 06:40:29,043 FATAL [gwt-log](http-0.0.0.0-8001-6) Uncaught
Exception Caused by: java.lang.NullPointerException: THis is an uncaught NPE
java.lang.NullPointerException: THis is an uncaught NPE
 at Unknown.CAc(Unknown source:0)
 at Unknown.O2b(Unknown source:0)
 at Unknown.AEb(Unknown source:0)
 at Unknown.PC(Unknown source:0)
 at Unknown.yG(Unknown source:0)
 at Unknown.cG(Unknown source:0)
 at Unknown.Y9(Unknown source:0)
 at Unknown.zC(Unknown source:0)
 at Unknown.Q9(Unknown source:0)
 at Unknown.deb(Unknown source:0)
 at Unknown.Bbb(Unknown source:0)
 at Unknown.U0(Unknown source:0)
 at Unknown.anonymous(Unknown source:0)
 at Unknown.xu(Unknown source:0)
 at Unknown.anonymous(Unknown source:0)
 at Unknown.jw(Unknown source:0)
 at Unknown.Mdb(Unknown source:0)
 at Unknown.deb(Unknown source:0)


On Mon, Jul 19, 2010 at 10:23 PM, Fred Sauer <[email protected]> wrote:

> Thanks Eric!
>
> I used to pass the throwable to the server, but it appears that code was
> lost in the LogRecord changes I made at around r436.
>
> Thanks to you, however, they're back as of r506. Mind giving the attached
> file a try?
>
> Thanks
> Fred
>
>
> On Sat, Jul 17, 2010 at 10:13 AM, EricB. <[email protected]> wrote:
>
>> This is production mode, release 3.0.1.   (By the way, I really like
>> the library... I find it incredibly useful and usable....thanks very
>> much for developing, putting it out there, and supporting it.)
>>
>> Just looking at the code, it seems that, in
>> com.allen_sauer.gwt.log.server.ServerLogImplLog4J, there is no use of
>> the exception which is on the on the LogRecord.  It just sends through
>> the message:
>>  public void log(LogRecord record) {
>>    Set<Entry<String, String>> set = record.getMapEntrySet();
>>    for (Entry<String, String> entry : set) {
>>      MDC.put(entry.getKey(), entry.getValue());
>>    }
>>
>> logger.log(Level.toLevel(mapGWTLogLevelToImplLevel(record.getLevel())),
>> record.getMessage());
>>    for (Entry<String, String> entry : set) {
>>      MDC.remove(entry.getKey());
>>    }
>>  }
>>
>> Thanks,
>>
>> Eric
>>
>> On Jul 16, 3:03 pm, Fred Sauer <[email protected]> wrote:
>> > That's not expected.
>> >
>> > What's the version of gwt-log you are using?
>> >
>> > Is this development mode or production mode?
>> >
>> >
>> >
>> >
>> >
>>   > On Fri, Jul 16, 2010 at 9:53 AM, EricB. <[email protected]> wrote:
>> > > Here's what's in my GWT Code:
>> > > Log.error("Log error", new NullPointerException("Test NPE"));
>> >
>> > > Here's what's in server log:
>> > > 2010-07-16 09:49:48,934 ERROR [gwt-log](http-0.0.0.0-8001-4) Log error
>> >
>> > > There entry in the server log doesn't mention anything about the
>> > > exception that was thrown nor anything about the stack in which it was
>> > > thrown.  Is that as expected?
>> >
>> > > Thanks,
>> >
>> > > Eric
>> >
>> > > --
>> > > 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] Hide quoted text -
>> >
>> > - Show quoted text -
>>
>> --
>>  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]<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].
For more options, visit this group at 
http://groups.google.com/group/gwt-log?hl=en.

Reply via email to