async table: row not found: ty

I have an AsyncTable. When the view containing the table is displayed in the browser I get in the MWS console the following lines:

(jsf : WARN) [RID:303] - row not found: ty
(jsf : WARN) [RID:303] - row not found: ty
(jsf : WARN) [RID:303] - row not found: ty
(jsf : WARN) [RID:303] - row not found: ty
(jsf : WARN) [RID:303] - row not found: ty
(jsf : WARN) [RID:303] - row not found: ty

Has anyone encountered this problem?



Did you set the “Row Java Type” field on the table’s provider?


Hi Vlad,

That was a known problem with the table control(s) in 7.x that was fixed for 8.x.

You will see that message because the async table was submitting the table ‘empty’ message as a table row when it should not have been.

Those warnings should be harmless and you can safely ignore them.


Hi Eric,

The strange thing is that when the application is under high load (a few hundred users), the message is no longer:
(jsf : WARN) [RID:303] - row not found: ty
(jsf : WARN) [RID:303] - row not found: RoleXXX

The table is used to display a list with roles (about 80). So if the users are working about 4-5 hours continuously I get a few [b]million  [/b]lines with this error in the log files. This is when the error is not harmless anymore.


Well, that is a different scenario. “RowXXX” appears to be a real row id. I wouldn’t want to speculate on what might be causing that. You may want to open an SR to get someone to take a closer look at it.

I am getting the same warning message “row not found:” in wm 8.2 during implementing
The asyc table becomes blank on the browser.

Based on what had been discussed in this thread, it was fixd in wm 8. It still occurs in my case.

Does anybody experience this? what could be a fix or workaround?



We have found that the message is logged in com.webmethods.caf.faces.component.table.html.DataTable.processValidators(FacesContext).

Basically whenever an AsyncTable content is refreshed a request with it is sent to the server for eventual changes.

Solution 1: Use suppressInputs.

It’s description says that it should contain: “List of ids of controls for which to disable validation/update processing when handling an asynchronous request (comma separated).”. Unfortunately this is deprecated now.

Solution 2: Use disjointForms
“To restrict the controls that are submitted and processed when a control is refreshed, place the control inside of a DisjointForm control; only the controls in that disjoint form will be submitted and processed.”

Hope it helps,
Vlad Turian

Hi All,

One of the Cx got several “row not found” entries in MWS log. Cx is using 9.12 and receive this warning.

2018-05-09 13:19:34 CEST (jsf:WARN) [qtp1978615214-14432] [RID:449571] - row not found: d456c5e8-153b-44e2-abb5-8c0cbbbb6c33
2018-05-09 13:19:34 CEST (jsf:WARN) [qtp1978615214-14432] [RID:449571] - row not found: e3bff900-87a4-4d43-a057-d46f42579414
2018-05-09 13:20:49 CEST (jsf:WARN) [qtp1978615214-14515] [RID:449616] - row not found: 41b09494-2f47-4030-9336-11222804d043
2018-05-09 13:20:49 CEST (jsf:WARN) [qtp1978615214-14515] [RID:449616] - row not found: 9b0bc6a1-4a1b-403e-9497-07f6d67ea364
2018-05-09 13:20:49 CEST (jsf:WARN) [qtp1978615214-14515] [RID:449616] - row not found: 357b4407-2a14-4026-99b6-854e6c016b89
2018-05-09 13:20:49 CEST (jsf:WARN) [qtp1978615214-14515] [RID:449616] - row not found: 2e96f986-fbb1-4195-aa39-1e0dd3d9c89f

As of Cx is not able to be sure if it got a business impact, because Cx does not know what’s the source of this error message.
Cx’s expectation is, that we offers any kind of analysis tools/logs/settings for further analysis, to find the source of this message.