Nicklas Karlsson added a comment - 26/Nov/10 1:12 AM This might be a general push-in-single-method problem since I can reproduce it with a outputText in the same manner.

Deryk Sinotte added a comment - 26/Nov/10 3:20 PM I think this might be more of a usage issue. I recommend taking a look at the following class in the Component Showcase demo: org.icefaces.application.showcase.view.bean.examples.component.progressBar.OutputProgressController To simulate a long-runnning process and modify the status of the progress bar, there is a TimerTask created in the startLongProcress() [sic] method: public void startLongProcress(ActionEvent event) { Timer timer = new Timer(true); timer.scheduleAtFixedRate( new LongOperationRunner(timer, outputProgressModel), 0, PROCCESS_SLEEP_LENGTH ); } The LongOperationRunner is an inner class that handles updating the progress bar status values and calling the render request: public void run() { if (0 == percentComplete) { ouputProgressModel.setPogressStarted(true); } ouputProgressModel.setPercentComplete(percentComplete); SessionRenderer.render("progressExample"); if (percentComplete >= 100) { ouputProgressModel.setPogressStarted(false); timer.cancel(); } percentComplete += 10; } The way the attached test case runs, it only runs once, stopping the actual request thread for 5 seconds (to simulate some work being done during the request). You'll need to offload the progress updating and pushing as outlined in the Component Showcase example.