ICEfaces
  1. ICEfaces
  2. ICE-2896

Fatal render failures in log when doing inter-portlet communication (IPC) with ICEfaces Ajax Push and Liferay Portal

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Duplicate
    • Affects Version/s: 1.7RC1
    • Fix Version/s: 1.7
    • Component/s: None
    • Labels:
      None
    • Environment:
      Liferay 4.4.2 + Tomcat 6.0.16 bundle + ICEfaces 1.7RC1

      Description

      Attached you will find a portle which is a sample that I developed for Liferay Portal that demonstrates inter-portlet communication with ICEfaces Ajax Push.

      Although it is only one .WAR, it contains two portlets: Customers and Bookings

      To reproduce the problems:

      1. Download and Install the Liferay 4.4.2 + Tomcat 6.0.16 bundle
      2. Run the bundle, which will create a $HOME/liferay/deploy folder
      3. Download the sample-icefaces-ipc-ajax-push-portlet.war attached to this ticket and copy to $HOME/liferay/deploy
      5. Start IE7
      6. Login as test@liferay.com with password test
      7. Position the mouse over the "Welcome" dock in the upper right hand corner
      8. Navigate to "My Places > My Community > Private Pages"
      9. Add a page named "IPC"
      10. Under the "Add Content" menu, expand the "Samples" category
      11. Add the "Sample ICEfaces IPC - Customers" portlet
      12. Under the "Add Content" menu, expand the "Samples" category
      13. Add the "Sample ICEfaces IPC - Bookings" portlet
      14. Click on a customer, note in the Tomcat log:
      ERROR [CustomerTable:92] fatal render failure for viewNumber 1
      15. Click on the Home tab
      16. Click back on the IPC tab, and note in the Tomcat log
      ERROR [CustomerTable:92] fatal render failure for viewNumber 1
      ERROR [CustomerTable:92] fatal render failure for viewNumber 3

      And if you keep repeating steps 15 and 16, more and more output occurs in the Tomcat log.

      Also, it seems like sometimes I have to click twice on a customer before the Ajax Push server initiated rendering takes place.



        Activity

        Hide
        Neil Griffin added a comment -

        Another bug that might be related is when I pick a date in Bookings portlet, then I have to click twice on the next customer before it will render.

        Show
        Neil Griffin added a comment - Another bug that might be related is when I pick a date in Bookings portlet, then I have to click twice on the next customer before it will render.
        Hide
        Deryk Sinotte added a comment -

        I have replicated both issues with 1.7 RC1

        1) The FatalRenderingException seems to be caused by improper bean disposal which has been fixed (http://jira.icefaces.org/browse/ICE-2904). When I updated the case to use the latest code from the repository head, it went away. We can consider this issue fixed.

        2) Occasionally, clicking on one of the Customer buttons in the first portlet doesn't appear to trigger a render. Clicking a second time appears to work. However, I also waited for the next heartbeat and that ALSO worked. So it appears that the framework knows that a change is pending but doesn't send it as a response to the initial click. This one will need further investigation as it doesn't happen all the time.

        Show
        Deryk Sinotte added a comment - I have replicated both issues with 1.7 RC1 1) The FatalRenderingException seems to be caused by improper bean disposal which has been fixed ( http://jira.icefaces.org/browse/ICE-2904 ). When I updated the case to use the latest code from the repository head, it went away. We can consider this issue fixed. 2) Occasionally, clicking on one of the Customer buttons in the first portlet doesn't appear to trigger a render. Clicking a second time appears to work. However, I also waited for the next heartbeat and that ALSO worked. So it appears that the framework knows that a change is pending but doesn't send it as a response to the initial click. This one will need further investigation as it doesn't happen all the time.
        Hide
        Neil Griffin added a comment -

        Thanks Derek – Fixing the usability problem with having to click on the item twice is something that IMHO can wait for ICEfaces 1.7.1

        Show
        Neil Griffin added a comment - Thanks Derek – Fixing the usability problem with having to click on the item twice is something that IMHO can wait for ICEfaces 1.7.1
        Hide
        Deryk Sinotte added a comment -

        I'm closing this as duplicate as part of the previous case (ICE-2904) mentioned where beans weren't being disposed properly and opening a separate case for the issue of the updates not always being applied.

        Show
        Deryk Sinotte added a comment - I'm closing this as duplicate as part of the previous case ( ICE-2904 ) mentioned where beans weren't being disposed properly and opening a separate case for the issue of the updates not always being applied.

          People

          • Assignee:
            Unassigned
            Reporter:
            Neil Griffin
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: