You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Kent Tong <SM...@cpttm.org.mo> on 2011/11/03 10:47:00 UTC

what could have caused this: a page ID in listener URL getting a wrong page instance

Hi,

My users are frequently getting "internal errors" after a few minutes
of inactivity. From the log I can see that mostly this is caused by:

org.apache.wicket.WicketRuntimeException: component foo not found
on page XYZ[id = 3], listener interface...

The weird thing is that there is no "foo" component on page XYZ, but
it is on page ABC. It means that while the browser believes that page
3 is an instance of ABC, actually it is an instance of XYZ.

What could have caused this? I know this is a long shot, but just to
see if there is any (remote) ideas. I can rule out session expiration
as it only took a few minutes to occur.

We're using Wicket 1.4.9.

Thanks in advance!

-- 
Kent Tong
Useful & FREE software at http://www2.cpttm.org.mo/cyberlab/freeware

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: what could have caused this: a page ID in listener URL getting a wrong page instance

Posted by Martijn Dashorst <ma...@gmail.com>.
Upgrade to latest in 1.4.x. AFAIK there were some issues with session
sharing due to lingering thread locals.

Martijn

On Thu, Nov 3, 2011 at 10:47 AM, Kent Tong <SM...@cpttm.org.mo> wrote:
> Hi,
>
> My users are frequently getting "internal errors" after a few minutes
> of inactivity. From the log I can see that mostly this is caused by:
>
> org.apache.wicket.WicketRuntimeException: component foo not found
> on page XYZ[id = 3], listener interface...
>
> The weird thing is that there is no "foo" component on page XYZ, but
> it is on page ABC. It means that while the browser believes that page
> 3 is an instance of ABC, actually it is an instance of XYZ.
>
> What could have caused this? I know this is a long shot, but just to
> see if there is any (remote) ideas. I can rule out session expiration
> as it only took a few minutes to occur.
>
> We're using Wicket 1.4.9.
>
> Thanks in advance!
>
> --
> Kent Tong
> Useful & FREE software at http://www2.cpttm.org.mo/cyberlab/freeware
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org