Came across this error recently in version 11.1.1.4.0.
The error was reproduceable on screens where file uploads, downloads and deletes were occurring (via UCM) and components on the screen needed to be refreshed (partial triggers or navigation) afterwards. These actions were being applied on af:panelCollection and subsequent af:table rows.
I tried this solution but it did not work in my case. My colleague's old blog post relating to data exports was also not the solution I was looking for.
After trying several things, the solution for me was changing the af:table ContentDeilvery property from immediate to the <default> (whenAvailable).
This seems like a bug in this version but I hope this simple change will save somebody else hours of debugging.
