ICEfaces
  1. ICEfaces
  2. ICE-3132

Failed to notify listener: problem when using multiple FF2 windows on Tomcat6 or Jboss4.2 NIO

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.7
    • Fix Version/s: 1.8RC1, 1.8
    • Component/s: Framework
    • Labels:
      None
    • Environment:
      ICEfaces asynchronous applications w/ Tomcat 6 w/ optional NIO configured (or JBoss 4.2.2 with optional NIO configured).
    • Workaround Exists:
      Yes
    • Workaround Description:
      Do not configure NIO for Tomcat / JBoss 4.2.2, use ICEfaces AHS config. instead or plain old blocking IO.

      Description

      When testing auctionMonitor on Tomcat6.o NIO or JBoss4.2 NIO following fails:

      1) 3 FF2 windows- clocks stop ticking

      2) Opera 2 tabs + 1 IE window same problem

      SEVERE: Failed to notify listener: com.icesoft.faces.context.View$3@13c296b
      java.lang.NullPointerException
              at org.apache.catalina.connector.CometEventImpl.getHttpServletResponse(C
      ometEventImpl.java:112)
              at com.icesoft.faces.webapp.http.servlet.TomcatPushServlet$EventResponde
      r.run(TomcatPushServlet.java:295)
              at com.icesoft.faces.webapp.http.core.ViewQueue.put(ViewQueue.java:17)
              at com.icesoft.faces.context.View$3.run(View.java:76)
              at com.icesoft.faces.context.View.broadcastTo(View.java:195)
              at com.icesoft.faces.context.View.put(View.java:170)
              at com.icesoft.faces.webapp.http.core.ReceivePing.service(ReceivePing.ja

      NOTE: 3+ IE7 windows running auctionMonitor work fine.

      Also when the JBoss4.2 server is first started Following message is seen in the logs:
      2008-06-03 11:03:47,553 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing:

      --- Packages waiting for a deployer ---
      org.jboss.deployment.DeploymentInfo@2a24ff8e { url=file:/C:/MyDownloads/JBoss/jboss-4.2.2.GA-NIO/server/default/deploy/WEB-INF/web.xml }
        deployer: null
        status: null
        state: INIT_WAITING_DEPLOYER
        watch: file:/C:/MyDownloads/JBoss/jboss-4.2.2.GA-NIO/server/default/deploy/WEB-INF/web.xml
        altDD: null
        lastDeployed: 1212512627522
        lastModified: 1212512627522
        mbeans:

      This could have something to do with the changes that were made in the web.xml file for the work around being used for Jboss server as mentioned in the configuration notes:
      " Note: There is a known issue with JBoss 4.2 whereby the default JBoss ReplyHeaderFilter will fail with this configuration. A work-around is to disable the ReplyHeaderFilter via the following configuration change in the ../server/default/deploy/jboss-web.deployer/conf/web.xml file:"

        Activity

        There are no subversion log entries for this issue yet.

          People

          • Assignee:
            Unassigned
            Reporter:
            Mandeep Hayher
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: