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

Howard M. Lewis Ship updated TAPESTRY-2037:
-------------------------------------------

    Description: 
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

  was:
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.

        Summary: NullPointerException caused by many rapid page refreshes  
(was: NullPointerException caused by many page refreshes)

> 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
>
> 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]

Reply via email to