[jira] [Commented] (AMQ-9565) Micrometer not working out of the box

["Jean-Baptiste Onofré (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMQ-9565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17895032#comment-17895032 ] 

Jean-Baptiste Onofré commented on AMQ-9565:
-------------------------------------------

ActiveMQ {{lib/camel}} folder doesn't contain all jar files. So, depending of your Camel routes (components, EIPs, ... you are using), you have to add extra jar files in the {{lib/camel}} folder.

It's not an ActiveMQ or Camel bug, it's just that you have to populate the classpath with the expected jar files.

> Micrometer not working out of the box
> -------------------------------------
>
>                 Key: AMQ-9565
>                 URL: https://issues.apache.org/jira/browse/AMQ-9565
>             Project: ActiveMQ Classic
>          Issue Type: Bug
>          Components: Camel
>    Affects Versions: 6.1.3
>            Reporter: Doug Whitfield
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>             Fix For: 6.2.0, 6.1.4
>
>
> We see there is a new version of Camel and have updated the routes. 5.17 was Camel 2.25 and now we are on 4.4.
> We are seeing this ‘micrometer’ error on the router logs–
> WARN | Setup of JMS message listener invoker failed for destination 'cons.interfaces.virtual.t.notif' - trying to recover. Cause: io/micrometer/observation/Observation | org.apache.camel.component.jms.DefaultJmsMessageListenerContainer | Camel (camel_t_notif_interfaces) thread #934 - JmsConsumer[cons.interfaces.virtual.t.notif]
> We were able to fix this with the following:
> We were able to fix this issue now by importing some more jars that were needed for the micrometer to work as expected:
>  
> *_micrometer-commons-1.13.4.jar_*
> *_micrometer-core-1.13.4.jar_*
> *_micrometer-observation-1.13.4.jar_*
> It seems like these jars should be automatically pulled if we are going to get an error if they aren't there.
> Is this an ActiveMQ bug or a Camel bug? Did we just miss this being documented somewhere?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@activemq.apache.org
For additional commands, e-mail: issues-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact