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

Fixed - Inconsistent MaxInactiveInterval Setting in Sessions in multi-node #6478

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

seakider
Copy link
Contributor

@seakider seakider commented Mar 9, 2025

…-node

Signed-off-by: seakider <seakider@gmail.com>
@mrniko mrniko added this to the 3.46.0 milestone Mar 10, 2025
@mrniko mrniko added the bug label Mar 10, 2025
…-node

Signed-off-by: seakider <seakider@gmail.com>
@@ -263,7 +263,7 @@ private void fastPut(String name, Object value) {
return;
}
m.fastPut(name, value);
if (readMode == ReadMode.MEMORY && this.broadcastSessionUpdates) {
if (readMode == ReadMode.REDIS || this.broadcastSessionUpdates) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we need to change readMode here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are two instances of the application in ReadMode.REDIS mode. Instance a calls setMaxInactiveInterval, and instance b calls getMaxInactiveInterval to get a value that is not the value set by instance a.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

condition should remain unchanged and getMaxInactiveInterval() should be overridden like getIdleTimeInternal()

@seakider seakider requested a review from mrniko March 12, 2025 14:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

2 participants