voyent
Messages posted by: jack.van.ooststroom  XML
Profile for jack.van.ooststroom -> Messages posted by jack.van.ooststroom [158] Go to Page: 1, 2, 3  ...  9, 10, 11 Next 
Author Message
Hello Fredrik,

Thank you for pointing this out. The fix to PUSH-381 should effectively avoid getting into the endless loop you described. When invoking org.icefaces.application.PortableRenderer.render(group) where the group argument is set to null it should now result in an IllegalArgumentException to be thrown.

Regards,
Hello Rohit,

Just to answer a few of your questions.

Only ICEfaces-EE is supported in cluster/fail-over environments.

ViewScoped beans reside in the session, thus in the case of a fail-over the session gets replicated, if configured correctly, including any ViewScoped beans as long as they are Serializable.

Are you using Push?

Regards,
Hello,

Have you tried to use Apache 2's mod_proxy_balancer instead of mod_jk?

Regards,
Hi,

I'm not sure what you mean by "to work with it". Once Tomcat 7 is configured correctly to use SSL, you can access your ICEfaces application either using HTTP (port 8080) or HTTPS (port 8443).

If you want to enforce HTTPS to be used when accessing your ICEfaces application, you can add the following to your web.xml:

Code:
 <security-constraint>
     <web-resource-collection>
         <url-pattern>/*</url-pattern>
     </web-resource-collection>
     <user-data-constraint>
         <transport-guarantee>CONFIDENTIAL</transport-guarantee>
     </user-data-constraint>
 </security-constraint>

I hope this helps.

Regards,
Can you try one of the stock sample applications shipped with ICEfaces 3.0.1, like auction, auctionMonitor or showcase?

I haven't been able to reproduce this using one of our stock sample applications on GlassFish Server 3.1.2. When building them please ensure to use the web-profile Ant target as it will result in the Mojarra libraries not being added to the resulting .war file.

Thanks,
I'd like to suggest using MyFaces 2.1.x on JBoss AS 5.x. The MyFaces libraries and its dependents can be included in the ICEfaces application's web archive. Additionally, add the following to the web.xml:
Code:
     <context-param>
         <param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-name>
         <param-value>true</param-value>
     </context-param>
Hope this helps.

Regards,
Hello,

What do you use to do the reverse proxying? Can you share the reverse proxy configuration with us?

Regards,
Hello,

It indeed looks like Tomcat 6 NIO is not supported by the AJP connector: Advanced IO and Tomcat. Tomcat 7 NIO does seem to be supported by the AJP connector: Connector Comparison

Please be advised that Push Server does not support Tomcat NIO. The Enterprise Push Server (EPS) does.

Regards,
Hello Naren,

Could you attach a simplified testcase that exhibits the issue? At this point I'd think we should try to look into the root cause before potentially porting the ContextEventRepeater over to ICEfaces 2.

Thanks,
Hello Naren,

ICEfaces 2 currently does not have the ContextEventRepeater or a replacement, as there hasn't been a need for it so far. On which events does your application depend on in order to gracefully shutdown upon session expiry?

Regards,
Hello,

Clusters, session replication and fail-over, are supported by the ICEfaces-EE product [link]. For Server Push applications the ICEfaces-EE product includes the Enterprise Push Server (EPS) to support these environments.

Regards,
Hello Ed,

The intent of the Grizzly Compat library is probably best explained here: http://jfarcand.wordpress.com/2008/07/01/porting-and-compiling-your-glassfish-v2-comet-application-to-v3/

Basically, in order for our code to be compatible with both GlassFish V2 and V3 environments we included the Grizzly Compat library to build against and to include in the WEB-INF/lib directory. If your targeted platform is V2 I don't think it's necessary to include it. But then again there's no harm in including it either and makes applications more compatible.

Regards,
The related JIRA mentioned earlier in this thread has been marked fixed: http://jira.icefaces.org/browse/ICE-5082

Its fix versions are 1.8.2-EE-GA_P01 and 1.8.3.

Regards,
Looking at the logs it looks like Push Server is not deployed (correctly). When Push Server is deployed and the application server starts up, you should see something like the following in your logs:

Code:
 Apr 22, 2010 2:04:15 PM org.icefaces.push.server.PushServlet init
 INFO: 
 ICEsoft Technologies, Inc.
 ICEfaces Push Server x.x.x x
 Build number: x
 Revision: x
 

Please make sure the Push Server is deployed correctly. I tried deploying the Push Server both through Tomcat's administration console and by copying the push-server.war manually into the [tomcat-home]/webapps directory.

Please note that the Push Server needs to be deployed and started up first before the ICEfaces application is exercised for the first time. The ICEfaces application upon receiving its very first request during its run-time will try to detect the Push Server. If the Push Server is found it will use it for the remainder of its run-time. If the Push Server is not found it will use the traditional Push environment for the remainder of its run-time instead.

Hope this helps.

Regards,
Hello,

A couple of questions:

  • Can you post your application's web.xml?
  • Can you post your logs?
  • Are you using HTTP or HTTPS to access your application?

    Regards,
  •  
    Profile for jack.van.ooststroom -> Messages posted by jack.van.ooststroom [158] Go to Page: 1, 2, 3  ...  9, 10, 11 Next 
    Go to:   
    Powered by JForum 2.1.7ice © JForum Team