Igor,
It's happening on line # 1483 of RequestCycle which corresponds to:
* Called when an unrecoverable runtime exception during request cycle
handling occurred, which
* will result in displaying a user facing error page. Clients can override
this method in case
* they want to customize logging. NOT called for {...@link
PageExpiredException page expired
* exceptions}.
*
* @param e
* the runtime exception
*/
protected void logRuntimeException(RuntimeException e)
{
log.error(e.getMessage(), e);
}
Jeremy
On Thu, Jun 18, 2009 at 11:46 AM, Igor Vaynberg <[email protected]>wrote:
> that is rather strange, there should be the stack trace. why dont you
> change your logger to show the line numbers so we can see where the
> log statement is coming from.
>
> -igor
>
> On Thu, Jun 18, 2009 at 7:53 AM, Jeremy Levy<[email protected]> wrote:
> > Per,
> > There is no stack dump, that is the entire output.
> >
> > J
> >
> > On Thu, Jun 18, 2009 at 10:48 AM, Per Lundholm <[email protected]
> >wrote:
> >
> >> No. ;-)
> >>
> >> Are you suggesting that the version of Wicket matters?
> >>
> >> How does the stack dump look in your logs?
> >>
> >> /Per
> >>
> >>
> >> On Thu, Jun 18, 2009 at 4:25 PM, Jeremy Levy<[email protected]> wrote:
> >> > I see the following a few times a day, this is with Wicket 1.3.6. It
> >> > results in a 500 being displayed to the user...
> >> >
> >> > 2009-06-18 00:53:09,485 ERROR Web [RequestCycle] :
> >> > java.lang.NullPointerException
> >> >
> >> > I realize this isn't much to go on, any ideas?
> >> >
> >> > j
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [email protected]
> >> For additional commands, e-mail: [email protected]
> >>
> >>
> >
> >
> > --
> > Jeremy Levy
> >
> > See my location in real-time:
> > http://seemywhere.com/jeremy
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
