You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Robert Zeigler (JIRA)" <de...@tapestry.apache.org> on 2008/03/10 16:45:46 UTC
[jira] Commented: (TAPESTRY-2037) NullPointerException caused by
many rapid page refreshes
[ https://issues.apache.org/jira/browse/TAPESTRY-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577044#action_12577044 ]
Robert Zeigler commented on TAPESTRY-2037:
------------------------------------------
Long delay; apologies. After upgrading to 5.0.11-SNAPSHOT, there were various things that needed changing, and new features that needed to be added, so it took a while to put an app where I frequently see this exception onto the boxes where I see it. I was able to put that up over the weekend. Crossing my fingers that the NPE go away; typically, I see several per day. Ironically, the next two weeks will be slow in terms of app usage. If I see the NPE again, I'll comment (so we know it's not fixed). During a typical-usage day, I see the NPE several times. So if I haven't seen it after the end of three weeks, I think it's fair to call it fixed.
Crossing my fingers.
> NullPointerException caused by many rapid page refreshes
> --------------------------------------------------------
>
> Key: TAPESTRY-2037
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2037
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core, tapestry-ioc
> Affects Versions: 5.0.7
> Environment: jdk 1.5
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Critical
> Fix For: 5.0.12
>
>
> This was reported on the mailing list.
> In certain places, hitting the refresh button rapidly can cause a null pointer exception.
> It is believed this is related to a JDK 1.5 bug:
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6550283
> Tapestry makes a few uses of ThreadLocal that are consistent with this pattern. ThreadLocals are used to connect service proxies to perthread scope services.
> We will locate all useages of ThreadLocal and, alas, synchronize access to them.
> More discussion: http://markmail.org/message/7bwztu66paz2cfqm
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org