[
https://issues.apache.org/jira/browse/AMQ-9333?focusedWorklogId=886909&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-886909
]
ASF GitHub Bot logged work on AMQ-9333:
---------------------------------------
Author: ASF GitHub Bot
Created on: 24/Oct/23 09:08
Start Date: 24/Oct/23 09:08
Worklog Time Spent: 10m
Work Description: jbonofre commented on PR #1097:
URL: https://github.com/apache/activemq/pull/1097#issuecomment-1776818048
NB: I have to double check the Jolokia authentication and configuration
loading.
Issue Time Tracking
-------------------
Worklog Id: (was: 886909)
Time Spent: 20m (was: 10m)
> Upgrade to jolokia 2.0.0-M4
> ---------------------------
>
> Key: AMQ-9333
> URL: https://issues.apache.org/jira/browse/AMQ-9333
> Project: ActiveMQ
> Issue Type: Dependency upgrade
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 6.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Jolokia 2.x supports Jakarta Servlet API. So instead of completely remove
> Jolokia from ActiveMQ 6.0.0, I propose to use Jolokia 2.0 even if it's not
> yet a GA release.
>
> Furthermore, jolokia has been removed from main (due to Jakarta namespace),
> but we still have:
>
> {code:java}
> INFO | ActiveMQ Jolokia REST API available at
> http://127.0.0.1:8161/api/jolokia/ {code}
>
>
> in the log. That's no accurate.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
