We are using ICEfaces 1.7.2 together with Spring Web Flow.

If we just add our EAR file to the WAS server, all is well, furthermore we can make changes to our application and then just republish it. But....if we introduce some sort of error, say referencing a bean that does not exist, like so:

<ice:outputText value="#{boom.bang}" />

where boom is a Spring Bean defined like so:

<bean id="boom" class="im.so.not.here" />

(in case you couldn't tell...no, there is no class named im.so.not.here :-)

our application fails.....of course. If we correct the error and wish to republish our application, we can not do so. RAD just hangs with "Publishing to WebSphere Application Server 6.0" stuck on 100%.

If we cancel our publishing attempt and try to stop the server, it appears to be stopped alright, but when looking at the process manager in Windows we can see that it is not. The only thing to do (as far as we can see) is to terminate the WAS server process in the process manager.

The only line in the console that seems to hint anything is this:

[11-11-08 09:03:11:662 CET] 00000048 MainSessionBo W com.icesoft.faces.webapp.http.servlet.MainSessionBoundServlet$2 run [1] views have accumulated updates

Which is shown when trying to publish both with and without errors. When publishing with errors, this is the last line shown.

To me it seems like something is not terminated properly when an error occurs (this is just wild guessing).

And one final observation. We did not have this problem when using ICEfaces 1.7.1

I admit, it's not much to go from, but if you have any further questions or comments, do not hesitate to contact me.