Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XFormsReplicationTest occasionally getting stuck #6236

Open
avernet opened this issue Mar 22, 2024 · 4 comments
Open

XFormsReplicationTest occasionally getting stuck #6236

avernet opened this issue Mar 22, 2024 · 4 comments

Comments

@avernet
Copy link
Collaborator

avernet commented Mar 22, 2024

  • This is happening both on Travis and locally.
  • To reproduce locally, run orbeonWarJS / testOnly *XFormsReplicationTest.
  • When it gets stuck, it is always in the same place:
    • after shutting down B, in updateWindowsAndAssert,
    • when doing the updateWindow on window B.
  • The request reaches the Tomcat A, since we've shut down B.
  • When this fails
    • We get the following log (enabled dev logging): TomcatA-failure-log.txt.
    • We see the request for quantity = 50.
    • We are restoring the dynamic state, but then throw an "Got unexpected request sequence number".
@avernet
Copy link
Collaborator Author

avernet commented Mar 22, 2024

  • The issue still happens occasionally after uncommenting the await(delay(5.seconds)) we had before shutting down B.
    • In orbeon-war/js/src/test/resources/resources/config/ehcache.xml, we set the property replicateAsynchronously=false.
    • The issue still happens in about 50% of the runs after increasing the delay to 20 seconds, which makes me think that the issue is unrelated to this.

@avernet
Copy link
Collaborator Author

avernet commented Mar 22, 2024

@ebruchez
Copy link
Collaborator

Curious: I can't see the code that updates the dynamic state after every request when replication is enabled. However, this works in some cases!

  • find code that updates the dynamic state after every request
  • check if somehow we might not store the newer sequence number associated with the latest dynamic state

@ebruchez
Copy link
Collaborator

We can do this locally, as it appears to happen about 50% of the time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Orbeon Forms 2023.1.3
Awaiting triage
Orbeon Forms 2024.1
Awaiting triage
Development

No branches or pull requests

2 participants