[
https://issues.apache.org/jira/browse/ARTEMIS-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495110#comment-16495110
]
ASF GitHub Bot commented on ARTEMIS-1895:
-----------------------------------------
GitHub user cshannon opened a pull request:
https://github.com/apache/activemq-artemis/pull/2116
ARTEMIS-1895 - Add duplicate metadata failure callback to
ActiveMQServerPlugin
Add a callback on duplicate metadata which will allow extra functionality
to be added.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cshannon/activemq-artemis ARTEMIS-1895
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/2116.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2116
----
commit afba4982b661759b3e7f1c6a2e4095fbc4c5a1dd
Author: Christopher L. Shannon (cshannon) <christopher.l.shannon@...>
Date: 2018-05-30T12:50:05Z
ARTEMIS-1895 - Add duplicate metadata failure callback to
ActiveMQServerPlugin
Add a callback on duplicate metadata which will allow extra
functionality to be added.
----
> Add duplicate metadata failure callback to ActiveMQServerPlugin
> ---------------------------------------------------------------
>
> Key: ARTEMIS-1895
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1895
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 2.6.0
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Priority: Minor
> Fix For: 2.7.0
>
>
> I have a usecase where it would be useful to have a callback as part of the
> plugin api when there is duplicate session metadata detected (ie duplicate
> clientId). This new callback will allow a user to add custom handling such
> as logging, etc.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
