Hello, maybe this could not be the right place where to ask similar information Any advice regarding where to ask for support on this matter?
Thanks in advance *Distinti Saluti / *Kind Regards M.G. Il giorno mar 6 feb 2024 alle ore 14:22 Marco Garavello < [email protected]> ha scritto: > Hello again, > > to whom reads this I propose this very fast test, as statistic and > learning, which could help me a lot: can you please execute this command on > the VM where your primary AMQ instance is running > > "curl -v http://localhost:8161/api/jolokia"; > > and post here the HTTP status code you receive? > > > *Distinti Saluti / *Kind Regards > M.G. > > > > Il giorno ven 2 feb 2024 alle ore 08:48 Marco Garavello < > [email protected]> ha scritto: > >> Hello everybody, >> >> is there someone here who has got experience configuring Jolokia auth on >> ActiveMQ? >> I'm facing issue as my previous mail - summarizing I have got 2 >> independent AMQ brokers running v5.17.2, and querying >> http://localhost:8161/api/jolokia on one broker I receive " *HTTP/1.1 >> 200 OK* ", while on the other I get " *HTTP/1.1 401 Unauthorized* " >> The goal is to obtain 200 on both of them. Any advice? >> >> Thank you so much in advance! >> >> *Distinti Saluti / *Kind Regards >> M.G. >> >> >> >> Il giorno lun 29 gen 2024 alle ore 11:22 Marco Garavello < >> [email protected]> ha scritto: >> >>> Hello everybody, >>> >>> I'm new here, so excuse me if I will not adhere completely to the best >>> practices of this mailing list. I'll do my best! >>> >>> I've got a strange issue: doing "curl -v >>> http://localhost:8161/api/jolokia"; on an Ubuntu VM with ActiveMQ >>> v5.17.2 running, I receive this >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> ** Trying 127.0.0.1:8161...* Connected to localhost (127.0.0.1) port >>> 8161 (#0)> GET /api/jolokia HTTP/1.1> Host: localhost:8161> User-Agent: >>> curl/7.81.0> Accept: */*>* Mark bundle as not supporting multiuse< HTTP/1.1 >>> 401 Unauthorized< WWW-Authenticate: basic realm="ActiveMQRealm"< >>> Cache-Control: must-revalidate,no-cache,no-store< Content-Type: >>> text/html;charset=iso-8859-1< Content-Length: 377<<html><head><meta >>> http-equiv="Content-Type" >>> content="text/html;charset=ISO-8859-1"/><title>Error 401 >>> Unauthorized</title></head><body><h2>HTTP ERROR 401 >>> Unauthorized</h2><table><tr><th>URI:</th><td>/api/jolokia</td></tr><tr><th>STATUS:</th><td>401</td></tr><tr><th>MESSAGE:</th><td>Unauthorized</td></tr><tr><th>SERVLET:</th><td>-</td></tr></table></body></html>* >>> Connection #0 to host localhost left intact* >>> >>> >>> BUT, if I do the same command on another Ubuntu VM with ActiveMQ v5.17.2 >>> running (but with different configuration, of course), I receive this >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> ** Trying 127.0.0.1:8161...* TCP_NODELAY set* Connected to localhost >>> (127.0.0.1) port 8161 (#0)> GET /api/jolokia HTTP/1.1> Host: >>> localhost:8161> User-Agent: curl/7.68.0> Accept: */*>* Mark bundle as not >>> supporting multiuse< HTTP/1.1 200 OK< Date: Mon, 29 Jan 2024 10:11:55 GMT< >>> X-FRAME-OPTIONS: SAMEORIGIN< Content-Type: text/plain;charset=utf-8< >>> Cache-Control: no-cache< Pragma: no-cache< Expires: Mon, 29 Jan 2024 >>> 09:11:55 GMT< Transfer-Encoding: chunked* >>> *[...]* >>> >>> >>> So the question is: which configuration should I modify to control this >>> different behaviour? >>> I already get through all the configuration files, making diff, setting >>> things etc but still I'm not able to let the 1st machine answer 200 to my >>> request, as the 2nd machine does. >>> >>> Please advise >>> Have a good day! >>> >>> >>> >>> *Distinti Saluti / *Kind Regards >>> M.G. >>> >>
