[
https://issues.apache.org/jira/browse/CAMEL-11140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicola Ferraro resolved CAMEL-11140.
------------------------------------
Resolution: Fixed
Added JMX information about subscriptions and removed the same information from
camel subscribers (i.e. when camel consumes items from a reactive streams),
since a CamelSubscription can be linked only to a CamelPublisher and not to a
CamelSubscriber, so previous JMX data on camel subscribers was always empty.
Added tests and fixed tck tests that were not closing the context.
I've renamed CamelSubscriber into ReactiveStreamsCamelSubscriber and pulled it
out of the "engine" package because it's generic and will be used presumably by
all engines.
> camel-reactive-streams - Add uuid for CamelSubscription
> -------------------------------------------------------
>
> Key: CAMEL-11140
> URL: https://issues.apache.org/jira/browse/CAMEL-11140
> Project: Camel
> Issue Type: Improvement
> Components: camel-reactive-streams
> Reporter: Claus Ibsen
> Assignee: Nicola Ferraro
> Fix For: 2.20.0
>
>
> A subscription do not have any kind of unique identifier? I wonder if
> it would make sense to include such in CamelSubscription. For example
> this can aid during debugging / logging / statistics. For example for
> the latter I would like to be able to use JMX tabular data to output a
> table with details about all the subscriptions and their state.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
