Couple of things: - The "addresses" command-line parameter has nothing to do with network addresses. It's for specifying broker-level addresses (i.e. a place to send messages). - You can work-around the issue by using a real address rather than 0.0.0.0. Also, there is no way for the broker to determine the proper address to be used in jolokia-access.xml if 0.0.0.0 is specified. In general, I discourage users from using 0.0.0.0 because it is ambiguous and causes problems.
Justin On Tue, Sep 18, 2018 at 6:09 AM jigar.parekh80 <[email protected]> wrote: > Hi, > > found very strange issue while configuring artemis, which blocks web > access. > When i try to create instance with option --addresses=0.0.0.0 > --http-host=0.0.0.0 cli correctly configures bootstrap.xml and broker.xml. > > it also adds http-host to jolokia-access.xml as 0.0.0.0 due to cli > implemenation as > > <allow-origin>*://${http.host}*</allow-origin> > > this will work if specific ip or domain provided but with 0.0.0.0 web > console does not connect to server as from browser it sends origin as IP > address of host which gets blocked by jolokia security. > > is there any way workaround or fix for this without manually modifying > jolokia-access.xml ? > > Regards, > Jigar > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >
