ICEpush
  1. ICEpush
  2. PUSH-115

Verify Servlet 3.0 support on GlassFish

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 2.0-Beta
          • Fix Version/s: 2.0.1
          • Component/s: Push Library
          • Labels:
            None
          • Environment:
            ICEfaces, GlassFish 3.0.1

            Description

            If Servlet 3.0 support is enabled in an ICEfaces push application:

                <servlet>
                    <servlet-name>Faces Servlet</servlet-name>
                    <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
                    <load-on-startup>1</load-on-startup>
                    <async-supported>true</async-supported>
                </servlet>

            Running on GlassFish 3.0.1 results in:


            Caused by: java.lang.IllegalStateException: Not Suspended
            at com.sun.grizzly.tcp.Response.resume(Response.java:752)
            at org.apache.catalina.connector.Request.asyncComplete(Request.java:3782)
            at org.apache.catalina.connector.AsyncContextImpl.complete(AsyncContextImpl.java:223)
            at org.icepush.servlet.AsyncAdaptingServlet$AsyncRequestResponse.respondWith(AsyncAdaptingServlet.java:66)
            at org.icepush.BlockingConnectionServer.respondIfPendingRequest(BlockingConnectionServer.java:196)

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Ted Goddard added a comment -

              This should likely be fixed for ICEfaces 2.0.1.

              Show
              Ted Goddard added a comment - This should likely be fixed for ICEfaces 2.0.1.
              Hide
              Permalink
              Mircea Toma added a comment -

              ICEpush running on Glassfish 3.0.1/Mac works well. I can see 'Servlet 3.0 AsyncContext environment' message in the logs which confirms that async features are used.

              Show
              Mircea Toma added a comment - ICEpush running on Glassfish 3.0.1/Mac works well. I can see 'Servlet 3.0 AsyncContext environment' message in the logs which confirms that async features are used.
              Hide
              Permalink
              Ken Fyten added a comment -

              Support reports the issue still occurs after approx. 30 secs of operation. Please investigate.

              Show
              Ken Fyten added a comment - Support reports the issue still occurs after approx. 30 secs of operation. Please investigate.
              Hide
              Permalink
              Mircea Toma added a comment -

              Investigated. Ran ICEpush's 'basic' and 'auction' tests configured with async. support. Both ran fine without any issues.

              Show
              Mircea Toma added a comment - Investigated. Ran ICEpush's 'basic' and 'auction' tests configured with async. support. Both ran fine without any issues.
              Hide
              Permalink
              Arran Mccullough added a comment -

              Attached my test case where I see the issue. This is using the ICEfaces 2.0 release code and also not overriding the Glassfish JSF jars. I did test with the 2.0 trunk jars and over rode the GLassfish jars with the JSF jars in the trunk and I could still see the issue.

              The exception occurs after some time, I found it usually occurs after connecting two clients to the application.

              Show
              Arran Mccullough added a comment - Attached my test case where I see the issue. This is using the ICEfaces 2.0 release code and also not overriding the Glassfish JSF jars. I did test with the 2.0 trunk jars and over rode the GLassfish jars with the JSF jars in the trunk and I could still see the issue. The exception occurs after some time, I found it usually occurs after connecting two clients to the application.
              Hide
              Permalink
              Mircea Toma added a comment -

              It turns out that this issue is caused by the changes introduced by MOBI-1 and it wasn't specific only to Glassfish server.

              Show
              Mircea Toma added a comment - It turns out that this issue is caused by the changes introduced by MOBI-1 and it wasn't specific only to Glassfish server.

                People

                • Assignee:
                  Mircea Toma
                  Reporter:
                  Ted Goddard
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: