Navigation Menu

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

hazelcast web session replication doesn't replicate when shutdown #3362

Closed
bilalyasar opened this issue Aug 22, 2014 · 4 comments
Closed

hazelcast web session replication doesn't replicate when shutdown #3362

bilalyasar opened this issue Aug 22, 2014 · 4 comments
Assignees
Labels
Milestone

Comments

@bilalyasar
Copy link
Contributor

full story is here: https://groups.google.com/forum/#!topic/hazelcast/H1FWmMgBdz4
when server goes to shutdown, our architecture couldn't get whether this process is shutdown or timeout.
so in some cases replication doesn't work.

    @Test
    public void test() throws Exception {
        CookieStore cookieStore = new BasicCookieStore();
        executeRequest("write", serverPort1, cookieStore);
        server1.restart();
        assertEquals("value",executeRequest("read", serverPort2, cookieStore));
    }
@bilalyasar bilalyasar added this to the 3.4 milestone Aug 22, 2014
@serkan-ozal serkan-ozal self-assigned this Sep 2, 2014
@serkan-ozal
Copy link
Contributor

The issue is caused by destroying session.

When the session on server1 is destroyed, its entries (key and values) are removed from distributed map via "DestroySessionEntryProcessor" and "InvalidateSessionAttributesEntryProcessor" processor in "destroySession" method. So the second one cannot find it in both of its local map (since it is not requested from server2 before server1 is restarted) and in distributed map.

https://github.com/hazelcast/hazelcast/blob/master/hazelcast-wm/src/main/java/com/hazelcast/web/WebFilter.java#L363

@eladh
Copy link

eladh commented Oct 20, 2014

Hi.

Our Software update procedure includes Current / New Tomcat servers .
When deploying new Software update we shutting down one of the servers - but its graceful shutdown and not by sending kill signal to the process.

Any workaround for this issue / or fix estimation ?

thanks,
elad.

@mesutcelik
Copy link

What you can do for now is :

  • block all incoming requests to one Tomcat instance i.e. configuring load balancer
  • wait until all sessions are expired or migrated to the other Tomcat instance.
  • upgrade Tomcat server and restart
  • configure load balancer to direct requests to the new server.
  • redo the same operations to all the other Tomcat instances.

@mesutcelik mesutcelik modified the milestones: 3.5, 3.4 Nov 26, 2014
@bilalyasar bilalyasar modified the milestones: 3.6, 3.5 May 12, 2015
@mesutcelik mesutcelik modified the milestones: Backlog, 3.6 Oct 12, 2015
@kobalski kobalski self-assigned this Dec 17, 2015
@kobalski kobalski modified the milestones: 3.6, Backlog Dec 17, 2015
@mesutcelik mesutcelik modified the milestones: 3.5.5, 3.6 Dec 17, 2015
kobalski pushed a commit to kobalski/hazelcast that referenced this issue Dec 18, 2015
kobalski pushed a commit to kobalski/hazelcast that referenced this issue Dec 18, 2015
kobalski pushed a commit to kobalski/hazelcast that referenced this issue Dec 18, 2015
kobalski pushed a commit to kobalski/hazelcast that referenced this issue Dec 21, 2015
kobalski pushed a commit to kobalski/hazelcast that referenced this issue Dec 21, 2015
kobalski pushed a commit to kobalski/hazelcast that referenced this issue Dec 21, 2015
@mesutcelik
Copy link

fixed by #7112

@mmedenjak mmedenjak added the Source: Internal PR or issue was opened by an employee label Aug 8, 2021
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

6 participants