ICEfaces
  1. ICEfaces
  2. ICE-5879

Glimmer sample failures with Tomcat 7.0.0

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0-Beta1
    • Fix Version/s: 2.0-Beta1
    • Component/s: Sample Apps
    • Labels:
      None
    • Environment:
      Glimmer revision: 21856
      Server: Tomcat 7.0.0
      Browser: FF3.6

      Description

      1. Compat Showcase
      - Rich text: Error message displays on the page - Could not find resource at /component-showcase/icefaces/resource//LTQ5MTYyMDg1Mw==/editor/fckeditor.html
      - Menu bar: no sub menu is displayed
      - Split pane panel: divider is not draggable

      2. NullPointerException was seen a couple of times when testing compat showcase and compat auction, but could not reproduce when reran.
      com.sun.faces.application.view.FaceletViewHandlingStrategy handleRenderException
      SEVERE: Error Rendering View[/auctionMonitor.xhtml]
      java.lang.NullPointerException
          at org.icefaces.event.WindowAndViewIDSetup$1.encode(WindowAndViewIDSetup.java:52)
          at org.icefaces.event.UIOutputWriter.encodeBegin(UIOutputWriter.java:32)
          at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1611)
          at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1616)
          at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1616)
          at org.icefaces.context.DOMPartialViewContext.processPartial(DOMPartialViewContext.java:151)

      com.sun.faces.application.view.FaceletViewHandlingStrategy handleRenderException
      SEVERE: Error Rendering View[/showcase.xhtml]
      SEVERE: Error Rendering View[/showcase.xhtml]
      java.lang.NullPointerException
              at org.icefaces.event.WindowAndViewIDSetup$1.encode(WindowAndViewIDSetup.java:52)
              at org.icefaces.event.UIOutputWriter.encodeBegin(UIOutputWriter.java:32)
              at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1611)
              at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1616)

        Activity

        Hide
        Joanne Bai added a comment -
        • Menu bar: the sub menu does not display
        • Split pane panel: the divider is not draggable

        Those two failures in compat showcase are current glimmer regressions. Only Rich Text seems specific to Tomcat 7.

        Show
        Joanne Bai added a comment - Menu bar: the sub menu does not display Split pane panel: the divider is not draggable Those two failures in compat showcase are current glimmer regressions. Only Rich Text seems specific to Tomcat 7.
        Hide
        Ted Goddard added a comment -

        RichText problem is also reproducible with Tomcat 6. It appears to be a transient problem, may require clearing the browser cache to reproduce.

        Show
        Ted Goddard added a comment - RichText problem is also reproducible with Tomcat 6. It appears to be a transient problem, may require clearing the browser cache to reproduce.
        Hide
        Ted Goddard added a comment -

        This bug is not yet fixed, but the component-showcase application should now work reliably. The WeakHashMap in DynamicResourceDispatcher.java has been replaced with a HashMap. Unfortunately, this results in the accumulation of some dynamically registered resources (such as with the chart demo).

        The reason that the WeakHashMap is not effective here is because the WeakHashMap uses weakly held keys. When the key can be garbage collected, then the WeakHashMap breaks the reference to the value. This essentially introduces random behavior into resource garbage collection because the lifetime of the key (often a dynamically generated path) is not strongly associated with the lifetime of the resource being served.

        See ICE-5787 for additional discussion on resource dispatching.

        Show
        Ted Goddard added a comment - This bug is not yet fixed, but the component-showcase application should now work reliably. The WeakHashMap in DynamicResourceDispatcher.java has been replaced with a HashMap. Unfortunately, this results in the accumulation of some dynamically registered resources (such as with the chart demo). The reason that the WeakHashMap is not effective here is because the WeakHashMap uses weakly held keys . When the key can be garbage collected, then the WeakHashMap breaks the reference to the value. This essentially introduces random behavior into resource garbage collection because the lifetime of the key (often a dynamically generated path) is not strongly associated with the lifetime of the resource being served. See ICE-5787 for additional discussion on resource dispatching.
        Hide
        Ted Goddard added a comment -

        Please verify that the RichText problems are now fixed in the trunk.
        This bug can be closed if the reported problems are not Tomcat 7 specific.

        Show
        Ted Goddard added a comment - Please verify that the RichText problems are now fixed in the trunk. This bug can be closed if the reported problems are not Tomcat 7 specific.
        Hide
        Joanne Bai added a comment -

        Glimmer revision 21886
        Browsers: FF3.6, IE8

        Rich text in compat showcase is verified working properly upon reload using both Tomcat 6.0.26 and Tomcat 7

        Show
        Joanne Bai added a comment - Glimmer revision 21886 Browsers: FF3.6, IE8 Rich text in compat showcase is verified working properly upon reload using both Tomcat 6.0.26 and Tomcat 7

          People

          • Assignee:
            Joanne Bai
            Reporter:
            Joanne Bai
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: