Skip to content

bug #4106 : Take into account the change in the session management service #160

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

Merged
merged 1 commit into from
Jan 11, 2013

Conversation

mmoqui
Copy link
Member

@mmoqui mmoqui commented Jan 10, 2013

This pull request is sync with the one in the Silverpeas Core project for the same branch name.

@buildhive
Copy link

Silverpeas » Silverpeas-Components #7 FAILURE
Looks like there's a problem with this pull request
(what's this?)

@NicolasEYSSERIC
Copy link
Member

This pull request does not fix associated bug...

@mmoqui
Copy link
Member Author

mmoqui commented Jan 10, 2013

In effect, the HornetQ server seams to be stopped (and thus all the JMS topics and queues are unregistered in the JNDI service) when the session management service is in shutdown ! It is surprised it is not stopped once all the applications are done.
So, the service management service shutdown is now hooked directly to the runtime shutdown, so that the HornetQ JBoss adapter isn't yet stopped at this time.

@ehsavoie
Copy link
Member

In English please ;)
In fact, the HornetQ server seems to stop (and thus all the JMS topics and queues are unregistered from the JNDI service) when the session management service is shutting down ! It is surprising that it is not stopped once all the applications have stopped.
The service management service shutdown is now hooked directly to the runtime shutdown, so that it can stop while the HornetQ JBoss adapter has already stopped.

@NicolasEYSSERIC NicolasEYSSERIC merged commit 326fb16 into Silverpeas:components-5.11.x Jan 11, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants