More clearly there is one and first successful update of outtext on problematic system (after page is loaded).
After that all the responses come as I described under And extract of the log output where Ajax functionality is broken.
Any messages in server log?
Nick, no error messages if you mean that. I enabled DEBUG level in log4j.properties.
The application log is attached.
application.log.zip 10.5 K
I also want to clarify how main page(template) is organized.
<f:view contentType="text/html" encoding="UTF-8" viewId="mainView">
1 of 1 people found this helpful
does it start work when you set ajaxRendered=”true” of a4j:outputPanel?
Are you using Spring WebFlow?
Yes, I tried that before and this specific case works. But I am not fully satisified with this solution
due to numerous side effects. For example, I have to click 2-3 times tab header to switch to another tab.
So my question was to understand the Ajax behavior. From what I see the Ajax request goes normally
to server. And response is also returned. So the communication is not broken. But why the response is not
valid so there is no refresh of UI pages?
Yes, I am using Spring Web Flow 2.0.5.
Unfortunatelly has no tests with such configuration. Would you able to create sample for us? It would be very helpfull for investigation.
Yes, I will create and send it.
I also seem to fixed the issue because I had to use the last solution - reboot the server and Ajax features work properly. How the question remains open - what was the issue with Ajax that cannot be fixed by restarting Tomcat but by restarting the server? Also the more informative debug log would be helpful.
Thanks Sergey, looking forward for receiving test project!