Jack Van Ooststroom added a comment - 15/Mar/16 8:15 AM Sending core/src/main/java/org/icefaces/impl/push/servlet/ICEpushResourceHandler.java Transmitting file data . Committed revision 48512.

Jack Van Ooststroom added a comment - 15/Mar/16 8:36 AM First of all the .icepush requests when using ICEfaces are ending in .icepush.xml.jsf and will result in getting the FacesServlet to get initiated. When this occurs, the ICEpushResourceHandler gets asked if this request is to be considered a "resource request", which gets confirmed. Finally, the ICEpushResourceHandler gets asked to handle the "resource request" as it confirmed it to be a "resource request". However, the ICEpushResourceHandler has not set-up the MainServlet just yet and as a result will let the wrapped ResourceHandler handle the "resource request" causing it to return the 404 Not Found. The ICEpushResourceHandler is registered as a PhaseListener interested in the PhaseId.RESTORE_VIEW . When this occurs within the JSF lifecycle upon getting its beforePhase(PhaseEvent) method invoked, the MainServlet is instantiated. If the first request received is a .icepush request this will not happen and as a result will return the 404 Not Found. A new getMainServlet() method has been introduced in the ICEpushResourceHandlerImpl class functioning as a sort of getInstance() method. This piece of code is guarded by a lock to ensure the MainServlet only gets initiated once. This method is now used throughout the various methods within the ICEpushResourceHandlerImpl , including the beforePhase(PhaseEvent) method, to ensure the MainServlet gets initiated even before or without invoking the beforePhase(PhaseEvent) method. I successfully tested this in a number of scenarios using the Emporium sample: Open the Emporium sample. Open the Emporium sample; initiate a separate create-pushid.icepush request. Initiate a separate create-pushid.icepush request. Initiate a separate create-pushid.icepush request; open the Emporium sample. Marking this one as FIXED.