Confirmed that fault is mine!
For anyone who has a similar issue, my problem was that uncaught
exceptions were being thrown on the server-side and disappearing into
the ether.
Solution was to override doUnexpectedFailure() in my implementation of
RemoteServiceServlet.
So:
@Override
protected void doUnexpectedFailure(Throwable e) {
logger.log(Level.ERROR, "Error invoking remote method", e);
}
On Aug 12, 4:24 pm, nullPainter <[email protected]> wrote:
> Hmm, actually... I suspect my problem may actually lie with my log4j
> (mis)configuration, as all server side exceptions are appearing on the
> console instead of in the log4j log files.
>
> So, you may (probably) ignore me! :)
>
> M
>
> On Aug 12, 4:08 pm, nullPainter <[email protected]> wrote:
>
>
>
> > Hi,
>
> > Apologies if this has been addressed before as it's fairly
> > straightforward issue, but I can't get stack traces to log using gwt-
> > log in combination with log4j.
>
> > In my log4j log, I get a very brief exception:
> > gwt-log 2010-08-12 16:03:04,634 -- FATAL -- Uncaught Exception:
>
> > with the stack trace itself on the console. I would prefer to have the
> > stack trace instead in the log rather than in a separate stdout file.
>
> > I may be barking up the wrong tree, but in ServerLogImplLog4J.log(),
> > the following line is used to do the actual logging:
> > logger.log(Level.toLevel(mapGWTLogLevelToImplLevel(record.getLevel())),
> > record.getMessage());
>
> > Shouldn't this instead be something like:
> > logger.log(Level.toLevel(mapGWTLogLevelToImplLevel(record.getLevel())),
> > record.getMessage(), getThrowable());
>
> > Or is this by design?
--
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.
