We continued our investigations further and we figured that if we assign ids to component the ajax request starts working. This is still very confusing but we stumbled upon the migration document of richfaces. At the moment we are using richfaces 3.3.3 with JSF 1.2
The problem occurred due to specific usage of the dynamic id generation implementing JSF 1.2. In case of simultaneous request processing, the id of the command component becomes out-of-sync with id of the same component on the page. After that any Ajax requests of the component with old id is not processed.
For further details please refer http://docs.jboss.org/richfaces/latest_3_3_X/en/migrationguide/html/RichFacesMigrationIssues31to32.html
The cause that is mentioned exactly matches ours.
Can anyone please let us know the following
1> Is the anomaly/defect/bug fixed in JSF 2.0 implementation
2> Even though we assign ids to certain components, if we have rich datatable, filters are not working. Can anyone please let us know how we can get around this problem
3> Is there any defect id/bug id associated with this?
Any help is appreciated