NETWORK CONNECTION INTERRUPTED ICEFACES HOW TO
NETWORK CONNECTION INTERRUPTED ICEFACES CODE
NETWORK CONNECTION INTERRUPTED ICEFACES PC

Since it is part of a JSF/HTTP request, you cannot call portableRenderer.

This is a backing bean method called by some UI event (e.g. Public void someBeanMethod(ActionEvent evt) PushRenderer.addCurrentSession('fullFormGroup') PI33193, Enabling the same interceptor in different. It doesn't matter where you define the PortableRenderer, as long as it's before it's used. The plug-in connection to the application server can fail if it is interrupted during the initial connect. This method is called by the constructor. I haven't tested it, and I wrote it in gedit so it might have a syntax error or two, but it should at least get you started in the right direction.

NETWORK CONNECTION INTERRUPTED ICEFACES CODE

I can't reveal the explicit source code I've used, but this is a boiled-down version that doesn't reveal any confidential information.

NETWORK CONNECTION INTERRUPTED ICEFACES HOW TO

PortableRenderer = PushRenderer.getPortableRenderer() įor the threading part, I used implements Runnable on my class, and for handling multiple threads in a single class, I followed this StackOverflow post: How to deal with multiple threads in one class? My PortableRenderer is declared as PortableRender portableRenderer and in my init() method (called by the class constructor) contains: PushRenderer.addCurrentSession('fullFormGroup') Once the main thread kicks off both execution and polling threads, it terminates and it completes the original HTTP request. I now have three threads in my backing bean- one for executing the long operation, one for polling the status, and one 'main' thread for spawning the new threads and returning UI control to the client browser. Multithreading was the missing link, in conjunction with PushRenderer and PortableRenderer (see ). It seems like it would work, but I don't want to spend time hacking together such an inelegant solution when I would hope that there is a more elegant solution built into JSF/ICEfaces.Īm I missing something, or is resorting to ugly hacks the only way to achieve the desired behavior? One possible solution that comes to mind is to have an invisible button somewhere that is automatically 'pressed' by the bean when step 1 of the long operation completes, and by clicking it, it calls step 2, and so on and so forth. I have tried using FacesContext.getCurrentInstance().renderResponse() and other functions, such as PushRenderer.render(String ID) to force XmlHttpRequest to initialize early, but no matter what, the appearance of the component does not change until the Java code finishes executing. However, since the component is only updated at the render response phase, it doesn't show any output until the Java methods have finished executing, and it shows it all changes accumulated at once. The problem is, I have a long file-copy operation to perform, and I would like the the inputText component to show a periodic status update. However, it seems that the change in variable isn't 'noticed' by the component until the end of the JSF cycle (which, from my basic understanding, is the render response phase). In theory, variable value is programmatically modified, and the component sees the change and updates its appearance/properties accordingly. Ken Fyten VP Product Development ICEsoft Technologies, Inc.I have an ICEfaces web app which contains a component with a property linked to a backing bean variable.

if you are still on the 3.3.0 open source release. If the front end was open and the user filling out the form, the connection could be lost in as little as 4 minutes.

NETWORK CONNECTION INTERRUPTED ICEFACES PC

I would also strongly recommend using the ICEfaces EE 3.3 release to ensure you have the latest fixes, etc. Before I modified the registry and followed the instructions in the KB article I posted, the PC would not even go to sleep. Once the end of the list is reached the bridge will give up trying to establish the connection, and an Network Connection Interrupted (NCI) message will be displayed (unless disabled). Once a network error is detected new connection is initiated, if again no response is received the second multiplying factor is used and so on. A network error is detected when the bridge does not receive a response in the amount of time resulted from multiplying the first factor in the list with the current heartbeat timeout. For example: - (since 4.1, EE 3.3.0.GA_P04) A space separated list of integer heartbeat timeout multiplication factors. You might try adjusting some of the ICEpush configuration parameters to see if it helps. Generally speaking, if you are seeing sporadic NCI popups when using push/asynchronous mode it is due to something in the network infrastructure that is either killing the push connections prematurely or possibly stripping out required header parameters.

Network connection interrupted icefaces