[jira] Commented: (WICKET-3483) NullPointerException in PersistentPageManager's page cache

["Pete Questionman (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000015#comment-13000015 ] 

Pete Questionman commented on WICKET-3483:
------------------------------------------

Hi Martin,

while I think it's good to fix the NPE, I doubt that this is the real problem. Why is the page null in the first place? This happens all the time after all. When using it in production, my pagemap contains no serialised pages (they were all null), and when I then get transferred to a different node (use the always-on-feature and you get transferred often), my new node lacks the page history, and i run into page expired a lot.

I am tempted to think that returning "false" in PageManager.isReplicated() is to blame, it should probably be overridden to "true". However, then deserialisation on GAE onto fresh nodes fails altogether for other reasons :-)

Have you got a production wicket 1.5 application running on App Engine? If so, are you using the always-on-feature yet?


> NullPointerException in PersistentPageManager's page cache
> ----------------------------------------------------------
>
>                 Key: WICKET-3483
>                 URL: https://issues.apache.org/jira/browse/WICKET-3483
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-core
>    Affects Versions: 1.5-RC2
>         Environment: Google AppEngine
>            Reporter: Martin Grigorov
>            Assignee: Martin Grigorov
>             Fix For: 1.5-RC3
>
>
> From a private email to me by a user:
> Hi,
> I'm trying to use your gae-initializer to get your test application working on GAE. I'm using version 1.5-rc2 of wicket and your initializer. Using GAE sdk 1.4.2.
> I'm getting the same problem the person on the 1.5-rc1 release page was getting, and I can't get around it.
> The homepage loads, but the other page throws the same null pointer exception he was getting:
> java.lang.NullPointerException
>     at org.apache.wicket.page.PersistentPageManager$SessionEntry.findPage(PersistentPageManager.java:117)
> ....
> --------------------------------
> The problem is that org.apache.wicket.page.PersistentPageManager.SessionEntry.addPage(IManageablePage) adds even 'null' pages.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira