'The request could not be handled' error on the UI after updating Table Options in RSA Governance & Lifecycle
a day ago
Article Number
000073897
Applies To
  • RSA Governance & Lifecycle 8.0.0 P09
Issue

When a user navigates on the UI to any of the pages that lists a table of data (e.g., Users > Users, Requests > Requests, Rules > Definitions, Reports > Tabular, etc.), clicks on the gear icon on top-right of the table to open the Table Options, and updates any option, such as, Rows/Page value, the UI shows the following error on saving changes to the Table Options:

The request could not be handled

An error similar to the following (depending on the affected UI page) is logged in the aveksaServer.log:

03/24/2026 14:59:54.718 ERROR (default task-4405) [com.aveksa.gui.core.MainManager] 
java.lang.ClassCastException: java.lang.Integer cannot be cast to java.lang.String
	at com.aveksa.gui.components.table.core.TableModel.init(TableModel.java:1552) ~[classes:?]
	at com.aveksa.gui.components.table.core.TableModel.print(TableModel.java:1431) ~[classes:?]
	at com.aveksa.gui.components.table.core.TableModel.print(TableModel.java:1423) ~[classes:?]
	at com.aveksa.gui.pages.admin.monitor.datarun.summary.DataRunsHistoryPageView.printContent(DataRunsHistoryPageView.java:47) ~[classes:?]
    ...
	...
03/24/2026 14:59:54.720 ERROR (default task-4405) [com.aveksa.gui.core.MainManager] 192.168.26.100 invalid request: https://acm-host.domain.net/aveksa/main?ReqType=GetPartial&PageID=DataRunsHistoryPageData&BreadcrumbLevel=0&isAjax=false

NOTE: The above error only affects those user(s) who apply changes to the Table Options.

Cause

This is a known issue in RSA Governance & Lifecycle 8.0.0 P09.

Resolution

This issue has been fixed in the following version/patch:

  • RSA Governance & Lifecycle 8.0.0 P10
Workaround

For RSA Governance & Lifecycle 8.0.0 P09, a workaround is available to fix the problem for the affected user(s).  Please contact RSA Technical Support and reference this KB article to obtain the workaround which includes updating the table options configuration for the affected user(s) in the database.