You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2008/01/19 00:03:39 UTC
[jira] Reopened: (TAPESTRY-2037) NullPointerException caused by
many rapid page refreshes
[ https://issues.apache.org/jira/browse/TAPESTRY-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reopened TAPESTRY-2037:
--------------------------------------------
Please go into your logs and capture the full exception.
Be careful ... fundamental bugs like this can throw exceptions while reporting an exception, try to get the true, deepest, most underlying cause exception.
> 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.8
>
>
> 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
Re: [jira] Reopened: (TAPESTRY-2037) NullPointerException caused by many rapid page refreshes
Posted by Robert Zeigler <ro...@scazdl.org>.
I have a decorator around exception handling that grabs the exception
and reports the entire set of nested exceptions. But I'll double check
my code to be sure. :)
Robert
On Jan 18, 2008, at 1/185:03 PM , Howard M. Lewis Ship (JIRA) wrote:
>
> [ https://issues.apache.org/jira/browse/TAPESTRY-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Howard M. Lewis Ship reopened TAPESTRY-2037:
> --------------------------------------------
>
>
> Please go into your logs and capture the full exception.
>
> Be careful ... fundamental bugs like this can throw exceptions while
> reporting an exception, try to get the true, deepest, most
> underlying cause exception.
>
>> 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.8
>>
>>
>> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org