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

Hibernate Session cache causing workflow issues #87

Open
bjagg opened this issue Nov 29, 2018 · 1 comment
Open

Hibernate Session cache causing workflow issues #87

bjagg opened this issue Nov 29, 2018 · 1 comment
Labels

Comments

@bjagg
Copy link
Member

bjagg commented Nov 29, 2018

Latest fixes have highlighted an issue with session caching in Admin UI.

Example 1:

  1. As admin, add a new shared calendar feed.
  2. Observe on the admin calendar list that the new feed appears.
  3. Return to 'View Calendars'
  4. Observe that the new feed is missing in view preferences.
  5. Log out and back in as admin
  6. Observe the new feed is present in view preferences.

Example 2:

  1. Delete a shared calendar feed in the Admin calendar page.
  2. Observe that the deleted calendar is still listed.
  3. Attempt to delete the calendar and observe that a error is thrown.

Flushing the EhCache does not correct this caching issue. This led me to believe it is in the Hibernate Session (as opposed to Http session). Transactions may not be set up correctly. Some experimentation with flushing and clearing the template in HibernateCalendarStore did not seem to help. Might be that the action request that does the updates but the call to get the calendar feeds is in the redirect. Also worth noting is that adding a new feed seems to manifest differently than deleting a feed!

@bjagg bjagg added the bug label Nov 29, 2018
@cbeach47
Copy link

Similar to Example 2, this has also been experienced with the following:

  1. Delete a shared calendar feed in the Admin calendar page.
  2. Observe that the deleted calendar is still listed.
  3. Attempt to delete the calendar and observe that nothing appears to happen - no error, or reaction from the page. logging back in nor clearing the cache helps

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants