You are viewing a plain text version of this content. The canonical link for it is here.

Posted to gitbox@activemq.apache.org by GitBox <gi...@apache.org> on 2020/04/02 18:35:01 UTC

[GitHub] [activemq-artemis] franz1981 commented on issue #3059: NO-JIRA stop PagingManager after RemotingService to let it finish send notifications

franz1981 commented on issue #3059: NO-JIRA stop PagingManager after RemotingService to let it finish send notifications
URL: https://github.com/apache/activemq-artemis/pull/3059#issuecomment-608032547
 
 
   That's good: it means that we are:
   1) assuming some order on components shutdown that I'm not honoring with my change
   2) replication behaviour are wrongly relying on such ordering (maybe not flushing tasks?)
   In both cases I think that is dangerous to commit this fix, but I would like to investigate what's going on anyway, maybe it can be improved by making explicit what we now assume implicitly...

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services