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

@Listener methods called after SessionListener.sessionRemoved #754

Closed
boris-petrov opened this Issue Nov 16, 2017 · 6 comments

Comments

Projects
None yet
2 participants
@boris-petrov

boris-petrov commented Nov 16, 2017

For the same ServerSession.getId, I receive a SessionListener.sessionRemoved notification and after that a @Listener method is called.

Is this expected? If not, could it be my mistake somewhere? If yes, why?

@sbordet

This comment has been minimized.

Show comment
Hide comment
@sbordet

sbordet Nov 16, 2017

Member

Which CometD version ?
How much after ?
The session is removed because of server-side expiration (the timeout parameter will be true) ?

Member

sbordet commented Nov 16, 2017

Which CometD version ?
How much after ?
The session is removed because of server-side expiration (the timeout parameter will be true) ?

@boris-petrov

This comment has been minimized.

Show comment
Hide comment
@boris-petrov

boris-petrov Nov 16, 2017

Sorry, should have put the version. The latest - 3.1.3. The SessionListener.sessionRemoved callback is invoked in the middle of some @Listener notifications so it is pretty much immediately after the sessionRemoved that the listener is invoked. I'll put some logging and will tell you whether its because of a timeout.

boris-petrov commented Nov 16, 2017

Sorry, should have put the version. The latest - 3.1.3. The SessionListener.sessionRemoved callback is invoked in the middle of some @Listener notifications so it is pretty much immediately after the sessionRemoved that the listener is invoked. I'll put some logging and will tell you whether its because of a timeout.

@boris-petrov

This comment has been minimized.

Show comment
Hide comment
@boris-petrov

boris-petrov Nov 16, 2017

OK, the timeout parameter is true which is kind of strange as the session was created around a second before that, a few @Listeners were invoked and then the SessionListener.sessionRemoved... any ideas on how to approach this?

boris-petrov commented Nov 16, 2017

OK, the timeout parameter is true which is kind of strange as the session was created around a second before that, a few @Listeners were invoked and then the SessionListener.sessionRemoved... any ideas on how to approach this?

@sbordet

This comment has been minimized.

Show comment
Hide comment
@sbordet

sbordet Nov 16, 2017

Member

It's unlikely that the session is expired on server if it's created around a second before.
I need server-side DEBUG logs, please attach them here.

Member

sbordet commented Nov 16, 2017

It's unlikely that the session is expired on server if it's created around a second before.
I need server-side DEBUG logs, please attach them here.

@boris-petrov

This comment has been minimized.

Show comment
Hide comment
@boris-petrov

boris-petrov Nov 16, 2017

OK, I'll need some time for that, I'll try to do it in the next few... weeks probably.

boris-petrov commented Nov 16, 2017

OK, I'll need some time for that, I'll try to do it in the next few... weeks probably.

@sbordet

This comment has been minimized.

Show comment
Hide comment
@sbordet

sbordet Sep 4, 2018

Member

Closing as no further activity. Please open another issue if this is still a problem for you, but I do need DEBUG logs to understand what's going on.

Member

sbordet commented Sep 4, 2018

Closing as no further activity. Please open another issue if this is still a problem for you, but I do need DEBUG logs to understand what's going on.

@sbordet sbordet closed this Sep 4, 2018

@sbordet sbordet modified the milestone: 3.1.5 Sep 4, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment