On 12/03/2015 10:03 AM, Gordon Sim wrote:
On 12/02/2015 09:45 PM, Rob Godfrey wrote:
On 2 December 2015 at 21:45, Gordon Sim <[email protected]> wrote:
From the proton python examples, I was unable to connect as that client
populates the hostname with a host and port combination, which was
causing
the broker to close the connection:
[...]
In its default configuration the Java Broker will accept any valid
hostname
or IP address as the "hostname", or the empty string, or "default". It
will not match anything containing the port number, nor will it match to
0.0.0.0. To get the Python client to work you could add the following
entry:
{
"name" : "pattern",
"virtualHostNode" : "default",
"type" : "patternMatchingAlias",
"pattern" : ".*"
}
into the list of virtualhostaliases within the AMQP port entry within the
config.json file. This will match any hostname in the open frame to the
virtual host named "default".
Yes indeed, that works perfectly, thanks!
In trying out rc5, I initially attempted to simply reuse the config.json
I had used (and edited) for rc4. However that didn't seem to work. Not
only did it not seem to recognise the extra hostname pattern I added as
you suggested, but in the web console, the 'default' virtual host wasn't
editable (double clicking didn't open the screen allowing me to add
queues etc).
I started from scratch and it all worked as expected, so not a big issue
and very possibly user error. Just noting for completeness and possibly
my education :-).
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
