[
https://issues.apache.org/jira/browse/TAPESTRY-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567788#action_12567788
]
Robert Zeigler commented on TAPESTRY-2037:
------------------------------------------
Sorry, focus on this issue has been scattered; it happens often enough to be
annoying, but not often enough to be top priority for me.
In terms of the "easy to recreate", it still isn't so. That the trivial app
recreated the issue suggests that the issue isn't (necessarily) my application
code. However, the occurrence of the error in the trivial app is still few and
far between, so "proving fixed" proves difficult.
I can say that in 5.0.10-SNAPSHOT, I'm still seeing this issue on a dual-core
box running debian linux on tomcat 4.1.
> 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.11
>
>
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
