ICEfaces-EE
  1. ICEfaces-EE
  2. IPCK-29

Support for WebLogic NIO features in EPS

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.8.2 Beta
    • Fix Version/s: 1.8.2.GA
    • Component/s: Enterprise Push Server
    • Labels:
      None
    • Environment:
      WebLogic 10.3

      Description

      It would be a useful enhancement to EPS throughput performance if EPS could be configured to optional use the Weblogic Future Response Servlet or Abstract Asynchronous Servlet for NIO operations when running on WebLogic 10.3.2 server.

        Activity

        Hide
        Ken Fyten added a comment -
        Show
        Ken Fyten added a comment - Related forum thread: http://www.icefaces.org/JForum/posts/list/0/15207.page#57983
        Hide
        Ted Goddard added a comment -
        Show
        Ted Goddard added a comment - http://download.oracle.com/docs/cd/E13222_01/wls/docs100/javadocs/weblogic/servlet/http/AbstractAsyncServlet.html#doRequest(weblogic.servlet.http.RequestResponseKey ) If we return true from doRequest(), the request is parked. Later we call notify() to unpark the request.
        Hide
        Jack Van Ooststroom added a comment -

        The AbstractAsyncServlet abstract class is now extended by and the FutureResponseModel interface is implemented by the WebLogicAdaptingServlet. The WebLogicAdaptingServlet can handle the blocking HTTP requests (/block/receive-updated-views) using WebLogic's ARP mechanism. In order to do so the WebLogicAdaptingServlet needs to be configured in the EPS' web.xml as follows:

        <servlet>
        <servlet-name>WebLogic Adapting Servlet</servlet-name>
        <servlet-class>com.icesoft.faces.push.server.arp.internal.WebLogicAdaptingServlet</servlet-class>
        <load-on-startup>1</load-on-startup>
        </servlet>

        <servlet-mapping>
        <servlet-name>WebLogic Adapting Servlet</servlet-name>
        <url-pattern>/block/receive-updated-views/*</url-pattern>
        </servlet-mapping>

        The servlet mapping must precede the Push Servlet's servlet mapping in order to ensure the handling of the blocking HTTP requests by the WebLogicAdaptingServlet.

        In addition the build.xml of EPS contains a target to build EPS for this environment:

        ant weblogic-arp.weblogic-jms

        This target ensures the inclusion of the servlet and servlet mapping as described earlier in EPS' web.xml.

        Marking this one as FIXED.

        Show
        Jack Van Ooststroom added a comment - The AbstractAsyncServlet abstract class is now extended by and the FutureResponseModel interface is implemented by the WebLogicAdaptingServlet. The WebLogicAdaptingServlet can handle the blocking HTTP requests (/block/receive-updated-views) using WebLogic's ARP mechanism. In order to do so the WebLogicAdaptingServlet needs to be configured in the EPS' web.xml as follows: <servlet> <servlet-name>WebLogic Adapting Servlet</servlet-name> <servlet-class>com.icesoft.faces.push.server.arp.internal.WebLogicAdaptingServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet-mapping> <servlet-name>WebLogic Adapting Servlet</servlet-name> <url-pattern>/block/receive-updated-views/*</url-pattern> </servlet-mapping> The servlet mapping must precede the Push Servlet's servlet mapping in order to ensure the handling of the blocking HTTP requests by the WebLogicAdaptingServlet. In addition the build.xml of EPS contains a target to build EPS for this environment: ant weblogic-arp.weblogic-jms This target ensures the inclusion of the servlet and servlet mapping as described earlier in EPS' web.xml. Marking this one as FIXED.

          People

          • Assignee:
            Jack Van Ooststroom
            Reporter:
            Ken Fyten
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: