[richfaces-issues] [JBoss JIRA] (RF-7248) a4j creates infinite HashMap.get loop

[Brian Leathem (JIRA)]

    [ https://issues.jboss.org/browse/RF-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12936721#comment-12936721 ] 

Brian Leathem commented on RF-7248:
-----------------------------------

[~xannis] unfortunately RichFaces 3 is not undergoing any more active development.  If you need legacy support for production systems please check out the WFK product from Red Hat:
http://www.redhat.com/products/jbossenterprisemiddleware/web-framework-kit/

But even there RichFaces 3 is approaching EOL.
                
> a4j creates infinite HashMap.get loop
> -------------------------------------
>
>                 Key: RF-7248
>                 URL: https://issues.jboss.org/browse/RF-7248
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-tables
>    Affects Versions: 3.3.0, 3.3.3.Final
>            Reporter: Nida Cibulskyte
>            Assignee: Nick Belaevski
>              Labels: ENT
>             Fix For: 3.3.1.SP2, 3.3.4.BETA1
>
>         Attachments: infinite_loop.JPG, screenshot-1.jpg
>
>
> Concurrent requests on a4j components causes infinite loop. While one request is being proccessed by restoreChildState method, another request is senT for proccessing. It causes the code to get stuck in hashmap.get() as the hashmap is not synchronized and causes infinite loop.
> 2009 05 25 09:41:43 ERROR demo.NameBean  - java.util.HashMap.get(HashMap.java:303)
> 2009 05 25 09:41:43 ERROR demo.NameBean  - org.ajax4jsf.component.UIDataAdaptor.restoreChildState(UIDataAdaptor.java:965)
> 2009 05 25 09:41:43 ERROR demo.NameBean  - org.ajax4jsf.component.UIDataAdaptor.restoreChildState(UIDataAdaptor.java:982)
> 2009 05 25 09:41:43 ERROR demo.NameBean  - org.ajax4jsf.component.UIDataAdaptor.restoreChildState(UIDataAdaptor.java:982)
> .......................

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira