[ 
https://issues.apache.org/jira/browse/TAPESTRY-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662757#action_12662757
 ] 

michael wasserman commented on TAPESTRY-2723:
---------------------------------------------

The line numbers may be off due to debugging code that we've placed in the 
source.

The exception is being thrown at the following lines in the getComponent() 
method:

if (result == null)
            throw new 
ApplicationRuntimeException(Tapestry.format("no-such-component", this, id),
                    this, null, null);

The problem is that result is never set because the _components HashMap is null.


We believe we may have found a solution to this problem.
By placing the line "_pageSpecificationResolver.resolve(_cycle, 
pageKey.getPageName());"
from PageSource.makeObject(Object key) in a synchronize block we have so far 
been unable to recreate the exception.
We are intending to test more aggressively on Monday/Tuesday and will report 
our findings then.

> Compenents that should be found are not found during page loading
> -----------------------------------------------------------------
>
>                 Key: TAPESTRY-2723
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2723
>             Project: Tapestry
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: 4.1.6
>         Environment: Windows XP Service pack 3 - 1.86 GHz, 3 GB of ram - 
> JBoss - Tapestry 4.1.6
>            Reporter: michael wasserman
>            Assignee: Andreas Andreou
>         Attachments: StackTrace.txt
>
>
> When AbstractComponent.getComponents(String) is called the HashMap 
> "_components" is unexpectedly null, causing an ApplicationRuntimeException 
> which indicates that the given component (id passed as parameter to 
> getComponents(String)), does not exist. We have confirmed that in every 
> instance the given component does exist in the given page.  
> This problem happens randomly on a variety of pages.  
> This could be an indication of a thread safety problem in the PageLoader 
> class. We can duplicate the problem, (unreliably), via our selenium test 
> suite.  

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