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

Victor Romero commented on ARTEMIS-2779:
----------------------------------------

That's interesting Justin,

In fact I got to know this from a issue in docker, where someone complained 
about it stopped working in 2.12 and I was able to reproduce.

The funny thing is that it does work with the default value in 2.11 (both 
vanilla and docker) and stops working in 2.12 (both vanilla and docker). Even 
for you, doesn't completely work, as the default configuration *://localhost* 
should be equivalent to what you wrote 
[http://localhost:8161|http://localhost:8161/] but its not. Same happen to me 
if I use *. will work in 2.11 but won't work in 2.12.

This said it could be a different issue with a different description, feel free 
to close here and I'll open another one with proper reproduction steps.

> In Artemis >= 2.12.0 jolokia won't  accept connections
> ------------------------------------------------------
>
>                 Key: ARTEMIS-2779
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2779
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.12.0, 2.13.0
>         Environment: OS: Ubuntu 20.04 LTS x86_64 
> Kernel: 5.4.0-29-generic 
> Shell: bash 5.0.16 
> Memory: 4385MiB / 32096MiB
>  
>            Reporter: Victor Romero
>            Priority: Blocker
>
>  
> In Artemis >= 2.12.0 jolokia won't accept connections, and will return the 
> following:
> {quote}{"error_type":"java.lang.Exception","error":"java.lang.Exception : 
> Origin null is not allowed to call this agent","status":403}
> {quote}
> Steps to reproduce:
> Create a vanilla 2.1[23]\{1}.0 broker instance with user admin password 
> admin. Run it, and run the following command: 
> {{curl -u admin:admin [http://localhost:8161/console/jolokia]}}
> I'm tagging as blocker as a broker without monitoring is IMHO more a problem 
> than a solution, but feel free to change.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to