Question about ViewExpiredException

What steps does it take to reproduce the issue?
Case 1: When a user opened a tab in a browser and go to the loginpage.xhtml, and then the user opened other tabs (for example, the user opened 8 more tabs and visited xxxxx/dataverse/root in each tab) and finally returned to the login tab and click the button Username/Email in Other options, the page has no response the there is ViewExpiredException in server.log
In this case, com.sun.faces.numberOfViewsInSession and com.sun.faces.numberOfLogicalViews are 15 (the default value), and there are ViewExpiredException when the user opened 8 more tabs.

Case 2:
When a user logined to account A in a tab (tab1), and then the user opened a new tab (tab2) and login into account B. After that, the user click the logout button in tab 2, and then return to tab 1 and click the logout button in tab 1, it shows Internal Server Error - An unexpected error was encountered, no more information is available. in tab 1 and ViewExpiredException can be found the following in server.log

• When does this issue occur?
  Case 1: When user visited the loginpage in a tab, and then visited other page in Dataverse in other tabs, and then return to the tab with the loginpage
  Case 2: When user logined in different account in different tab without refreshing after a new login, and then clicked the logout button in different tab

• Which page(s) does it occurs on?
  Case 1: Login page
  Case 2: In the page for viewing Dataverse

• What happens?
  Case 1: There is no response when user clicked the button Username/Email in Other options in loginpage.xhtml. There are ViewExpiredException in server.log
  Case 2: There are ViewExpiredException in server.log

• To whom does it occur (all users, curators, superusers)?

• What did you expect to happen?

Which version of Dataverse are you using?
5.5

Any related open or closed issues to this bug report?
https://groups.google.com/g/dataverse-community/c/HfNq1lLIm74

Start by reproducing the two cases described for loginpage.xhtml and the Dataverse viewing page, then inspect the resulting ViewExpiredException entries in server.log. Review the com.sun.faces.numberOfViewsInSession and com.sun.faces.numberOfLogicalViews settings alongside the reported multi-tab login and logout flows. Done means the reported actions no longer produce an unresponsive page, Internal Server Error, or ViewExpiredException.