Messages posted by: ted.goddard  XML
Profile for ted.goddard -> Messages posted by ted.goddard [874] Go to Page: Previous  1, 2, 3 , ... 57, 58, 59 Next 
Author Message
Do you refer directly to org.icepush.util.ExtensionRegistry in your code or web.xml? Also, remove any servlet references to ICEpush if you have them in your web.xml.

It might be useful to post your web.xml here.
Do you have the complete stack trace?
ICEpush can actually handle that number of users easily -- the question would be sufficient memory for a JSF application of that scale.

WebSocket features will likely be introduced first for HTML 5 development with BridgeIt rather than JSF development with ICEfaces. (Where we can introduce new APIs outside the JSF request/response model.)

Do you have an application that would benefit specifically from WebSocket? The main advantage with the HTTP strategy with ICEpush is that it has the widest browser and network infrastructure support (some firewalls will block WebSocket). Since the PushRenderer API would remain the same, there would be little visible difference to the application developer.
One easy way is to remove icepush.jar from your application (if you are not using push).
Is the network connection dropping because of network conditions (lost wifi signal, or something), or do the Push updates never occur when you are using PortableRenderer?

PortableRenderer is just an Object reference that persists beyond the PushContext (which is tied to the FacesContext) so using it does not affect anything related to network activity. So, if PortableRenderer is not working under good network conditions, it likely means you are obtaining the PortableRenderer instance from a non-JSF thread.

The use of PortableRenderer does not affect the heartbeat (<noop/>) behaviour, but you must be sure to obtain the PortableRenderer instance from a JSF thread before storing it for use by other threads.
You can detect this at the bean level with WindowScope: http://www.icesoft.org/wiki/display/ice/window+scope
org.icepush.pushIdTimeout configures PushID expiry. This is mostly an implementation detail, but the configuration is made available to solve unforeseen problems (such as PushIDs not being cleaned up as expected).

Is the auction sample working for you?

Are you using PushRenderer.addCurrentSession(groupname)
and PushRenderer.render(groupname) in your bean?
A fix for the id being set on the body has been checked in:


Since manually setting the id did not fix your problem, however, there may be a different root cause. I would recommend including an h:panelGroup just inside the body with a manually set id or try simplifying the page until the problem goes away to try to isolate it. You may also want to contact product.support@icesoft.com for individual help resolving the problem.
ICEmobile-SX includes a new "Open in" feature for downloads which may be useful. Could you provide more details on the workflow for the user to download and interact with the file on the iPad?
We will need to investigate this further. In the meantime, it may help to manually set an ID on the body <h:body id="mybody">. Which version of JSF are you using?
This will require investigation by product.support@icesoft.com since the conflict is with commercial code from Oracle.
Good suggestion; I've added the configuration to our wiki page.
Do you see the same logging with


added to the Faces Servlet declaration?
Profile for ted.goddard -> Messages posted by ted.goddard [874] Go to Page: Previous  1, 2, 3 , ... 57, 58, 59 Next 
Go to:   
Powered by JForum 2.1.7ice © JForum Team