[jira] Closed: (TAPESTRY-2037) NullPointerException caused by many rapid page refreshes

["Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>]

     [ https://issues.apache.org/jira/browse/TAPESTRY-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAPESTRY-2037.
------------------------------------------

    Resolution: Fixed

Really, this was fixed in 5.0.11, but we're accepting Robert's observations as proof it's really gone.

> 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