ICEfaces
  1. ICEfaces
  2. ICE-9151

Sample apps - Server Internal Errors when using Myfaces 2.1.11 JSF

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.3
    • Fix Version/s: EE-3.3.0.GA_P02
    • Component/s: Sample Apps
    • Labels:
      None
    • Environment:
      Icefaces3 trunk revision #34307 (built with Myfaces JSF)
      Server: tomcat6/7
      Browser: FF3.6, IE7 & GoogleChrome25
    • Assignee Priority:
      P1

      Description

      1. In showcase, there is a Server Internal Error popup when navigating to the Overview page of each ACE component - see attached screen shot; the other pages of each ACE component are not accessible.

      The server log has many occurrences of this error:
      10-Apr-2013 10:25:38 AM org.apache.myfaces.context.servlet.ServletExternalContextImpl setResponseContentType
      SEVERE: Cannot set content type. Response already committed

      Also visible in tomcat terminal window but not found in the logs:
      java.lang.IllegalStateException: component with duplicate id "j_id__v_17" found
              at org.apache.myfaces.view.facelets.compiler.CheckDuplicateIdFaceletUtil
      s.checkIdsStatefulComponents(CheckDuplicateIdFaceletUtils.java:54)
              at org.apache.myfaces.view.facelets.compiler.CheckDuplicateIdFaceletUtil
      s.checkIdsStatefulComponents(CheckDuplicateIdFaceletUtils.java:75)
              at org.apache.myfaces.view.facelets.compiler.CheckDuplicateIdFaceletUtil
      s.checkIdsStatefulComponents(CheckDuplicateIdFaceletUtils.java:66)
              at org.apache.myfaces.view.facelets.compiler.CheckDuplicateIdFaceletUtil
      s.checkIdsStatefulComponents(CheckDuplicateIdFaceletUtils.java:35)
              at org.apache.myfaces.view.facelets.DefaultFaceletsStateManagementStrate
      gy.saveView(DefaultFaceletsStateManagementStrategy.java:549)
              at org.apache.myfaces.application.StateManagerImpl.saveView(StateManager
      Impl.java:188)
              at javax.faces.application.StateManager.getViewState(StateManager.java:2
      53)
              at org.icefaces.impl.context.DOMPartialViewContext.renderState(DOMPartia
      lViewContext.java:619)
              at org.icefaces.impl.context.DOMPartialViewContext.processPartial(DOMPar
      tialViewContext.java:247)
              at javax.faces.component.UIViewRoot.encodeChildren(UIViewRoot.java:421)
              at javax.faces.component.UIComponentBase.encodeAll(UIComponentBase.java:
      532)
              at org.apache.myfaces.view.facelets.FaceletViewDeclarationLanguage.rende
      rView(FaceletViewDeclarationLanguage.java:1981)
              at org.apache.myfaces.application.ViewHandlerImpl.renderView(ViewHandler
      Impl.java:285)
              at org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderRes
      ponseExecutor.java:116)
              at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:
      241)
              at javax.faces.webapp.FacesServlet.service(FacesServlet.java:199)
              at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
      icationFilterChain.java:305)


      2. basic application:
      All browsers: Test Basic Application - A similar error message is displayed on the page when clicking on "Show/ Hide" button. Terminal window shows an error (not found in server logs):
      INFO: MyFaces Unified EL support disabled
      java.lang.IllegalStateException: component with duplicate id "j_id__v_6" found
              at org.apache.myfaces.view.facelets.compiler.CheckDuplicateIdFaceletUtil
      s.checkIdsStatefulComponents(CheckDuplicateIdFaceletUtils.java:54)
              at org.apache.myfaces.view.facelets.compiler.CheckDuplicateIdFaceletUtil
      s.checkIdsStatefulComponents(CheckDuplicateIdFaceletUtils.java:75)
              at org.apache.myfaces.view.facelets.compiler.CheckDuplicateIdFaceletUtil
      s.checkIdsStatefulComponents(CheckDuplicateIdFaceletUtils.java:66)
              at org.apache.myfaces.view.facelets.compiler.CheckDuplicateIdFaceletUtil
      s.checkIdsStatefulComponents(CheckDuplicateIdFaceletUtils.java:35)
              at org.apache.myfaces.view.facelets.DefaultFaceletsStateManagementStrate
      gy.saveView(DefaultFaceletsStateManagementStrategy.java:549)
              at org.apache.myfaces.application.StateManagerImpl.saveView(StateManager
      Impl.java:188)
             ....................

      3. fajax:
      All browsers: fajax1 - Error message renders on the page when clicking on "Toggle test 1" or any button on the page. Terminal window shows a similar " java.lang.IllegalStateException: component with duplicate id" error.

      4. elementUpdate:
      All browsers: Input Elements Common - Error message renders on the page when clicking on "value" or any other button, and a " java.lang.IllegalStateException: component with duplicate id" error occurs in Tomcat terminal window.
                          Input Elements Individual - Error message renders on the page when clicking on "update" button, and a " java.lang.IllegalStateException: component with duplicate id" error occurs in Tomcat terminal window.

        Activity

        Hide
        Deryk Sinotte added a comment -

        Looks like this might be a known problem with the 2.1.11 release. A quick Google search turns up this:

        http://www.mail-archive.com/users@myfaces.apache.org/msg59471.html

        which seems to indicate a change between 2.1.10 and 2.1.11 introduced this behaviour. The change is suspected to be a part of this ticket:

        https://issues.apache.org/jira/browse/MYFACES-3665

        So while we might be able to change something in our app to get around this, we'll need to go back to 2.1.10 for the release.

        Show
        Deryk Sinotte added a comment - Looks like this might be a known problem with the 2.1.11 release. A quick Google search turns up this: http://www.mail-archive.com/users@myfaces.apache.org/msg59471.html which seems to indicate a change between 2.1.10 and 2.1.11 introduced this behaviour. The change is suspected to be a part of this ticket: https://issues.apache.org/jira/browse/MYFACES-3665 So while we might be able to change something in our app to get around this, we'll need to go back to 2.1.10 for the release.
        Hide
        Deryk Sinotte added a comment -

        The problem has been noted by others and a ticket with test case has been opened:

        https://issues.apache.org/jira/browse/MYFACES-3709

        Show
        Deryk Sinotte added a comment - The problem has been noted by others and a ticket with test case has been opened: https://issues.apache.org/jira/browse/MYFACES-3709
        Hide
        Ken Fyten added a comment -

        Resolved via update to MyFaces JSF 2.1.15.

        Show
        Ken Fyten added a comment - Resolved via update to MyFaces JSF 2.1.15.

          People

          • Assignee:
            Deryk Sinotte
            Reporter:
            Carmen Cristurean
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: