Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
MIME-Version: 1.0
In-Reply-To: <565F5866.9010505@redhat.com>
References: 
 <CAP3WMuT+n2UDudwi1WVQsSiQutvKsTfLAZxFJxh1pZoq66Bm_g@mail.gmail.com>
	<CAFitrpT8iySkPgnGXUvCffL_rmy58XUGnSBK=w=umbhnndcAdw@mail.gmail.com>
	<CAFitrpRz8kqG6h3_wUO=DHp7=-_DszD7wkeCk8Mpwcj7Fy4xqw@mail.gmail.com>
	<CAP3WMuTt9BA+SBVE1=eCMzvcH9VKQOgx3=LbtdwLH9+uAJ3Eng@mail.gmail.com>
	<565F5866.9010505@redhat.com>
Date: Wed, 2 Dec 2015 22:45:32 +0100
Message-ID: 
 <CACsaS97pftPOpAzw_xFwvFx5pJMrb51VhmSSiZuFGDzH1wg44w@mail.gmail.com>
Subject: Re: [VOTE] Release Qpid Java Components 6.0.0
From: Rob Godfrey <rob.j.godfrey@gmail.com>
To: "users@qpid.apache.org" <users@qpid.apache.org>
Content-Type: multipart/alternative; boundary=001a11c39c4e965c960525f13150

--001a11c39c4e965c960525f13150
Content-Type: text/plain; charset=UTF-8

On 2 December 2015 at 21:45, Gordon Sim <gsim@redhat.com> wrote:

> On 12/02/2015 03:22 PM, Oleksandr Rudyy wrote:
>
>> Robbie,
>>
>> Thanks a lot for pointing out that source release bundle is not available
>> in staging repo. I created 6.0.0 RC4 source bundle and put it together
>> with
>> binary bundles into dev area of the dist repo under:
>>
>> https://dist.apache.org/repos/dist/dev/qpid/java/6.0.0-rc4/
>>
>
> Every compile dok, tests ran. I untarred the broker tarball, ran a broker,
> configured it to accept anonymous on port 5672 and then tried to connect
> from some other clients.
>
> From qpid::messaging (c++) over AMQP 1.0 I could send and receive messages
> though there is an alarming error from qpid-send or the drain examples
> which appears to be due to an out of order detach from the broker (the
> client doesn't explicitly detach, it just closes the session:
>
>   <- AMQP
>>   -> AMQP
>> 0 -> @open(16) [container-id="b379d7dc-7d2a-419b-aea4-a8fc85923e5f",
>> channel-max=32767, properties={:"qpid.client_process"=:spout,
>> :"qpid.client_pid"=4112, :"qpid.client_ppid"=12984}]
>> 0 <- @open(16) [container-id="282a59cd-7875-4ede-8807-48dcc79fd3c7",
>> max-frame-size=32768, channel-max=255, idle-time-out=0,
>> properties={:product="qpid", :version="6.0.0", :"qpid.build"="Unversioned
>> directory", :"qpid.instance_name"="Broker"}]
>> 0 -> @begin(17) [next-outgoing-id=0, incoming-window=2147483647,
>> outgoing-window=2147483647]
>> 0 <- @begin(17) [remote-channel=0, next-outgoing-id=0,
>> incoming-window=2048, outgoing-window=2048]
>> 0 -> @attach(18) [name="amq.topic_e62ca481-0877-4a82-9fee-31f5dc1642a7",
>> handle=0, role=false, snd-settle-mode=2, rcv-settle-mode=0,
>> source=@source(40) [address="amq.topic", durable=0, timeout=0,
>> dynamic=false], target=@target(41) [address="amq.topic", durable=0,
>> timeout=0, dynamic=false], initial-delivery-count=0]
>> 0 <- @attach(18) [name="amq.topic_e62ca481-0877-4a82-9fee-31f5dc1642a7",
>> handle=0, role=true, snd-settle-mode=2, rcv-settle-mode=0,
>> source=@source(40) [address="amq.topic", durable=0, timeout=0,
>> dynamic=false], target=@target(41) [address="amq.topic", durable=0,
>> timeout=0, dynamic=false]]
>> 0 <- @flow(19) [next-incoming-id=0, incoming-window=2048,
>> next-outgoing-id=0, outgoing-window=2048, handle=0, delivery-count=0,
>> link-credit=20000, echo=false]
>> Message(properties={spout-id:5928f636-ecd6-4171-a07d-aefab6892b7f:0},
>> content='abc')
>> 0 -> @transfer(20) [handle=0, delivery-id=0,
>> delivery-tag=b"\x00\x00\x00\x00", message-format=0, settled=false,
>> more=false] (93)
>> "\x00Sp\xc0\x04\x02BP\x00\x00Ss\xd0\x00\x00\x00\x0c\x00\x00\x00\x04@
>> @@\xa1\x03abc\x00St\xc13\x02\xa1\x08spout-id\xa1&5928f636-ecd6-4171-a07d-aefab6892b7f:0\x00Sw\xa1\x03abc"
>> 0 <- @disposition(21) [role=true, first=0, last=0, settled=true,
>> state=@accepted(36) []]
>> 0 -> @end(23) []
>> 0 -> @close(24) []
>>   -> EOS
>> 0 <- @end(23) []
>> 0 <- @detach(22) [handle=0, closed=true]
>>   <- EOS
>>
>
> The end comes before the detach which leads the client to complain. Not
> a huge issue in itself and it can be avoided if the client explicitly
> detaches (i.e. closes the sender/receiver) before ending (i.e. closing)
> the session.
>


OK - I'll look at this one.


>
> 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:
>
> [0x1705190]:  <- AMQP
>> [0x1705190]:  -> AMQP
>> [0x1705190]:0 -> @open(16)
>> [container-id="94292005-d76e-41be-837e-c6d52bd5c8ae",
>> hostname="localhost:5672", channel-max=32767]
>> [0x1705190]:0 -> @begin(17) [next-outgoing-id=0,
>> incoming-window=2147483647, outgoing-window=2147483647]
>> [0x1705190]:0 -> @attach(18)
>> [name="94292005-d76e-41be-837e-c6d52bd5c8ae-examples", handle=0, role=true,
>> snd-settle-mode=2, rcv-settle-mode=0, source=@source(40)
>> [address="examples", durable=0, timeout=0, dynamic=false],
>> target=@target(41) [durable=0, timeout=0, dynamic=false],
>> initial-delivery-count=0]
>> [0x1705190]:0 -> @attach(18)
>> [name="94292005-d76e-41be-837e-c6d52bd5c8ae-examples", handle=1,
>> role=false, snd-settle-mode=2, rcv-settle-mode=0, source=@source(40)
>> [durable=0, timeout=0, dynamic=false], target=@target(41)
>> [address="examples", durable=0, timeout=0, dynamic=false],
>> initial-delivery-count=0]
>> [0x1705190]:0 -> @flow(19) [incoming-window=2147483647,
>> next-outgoing-id=0, outgoing-window=2147483647, handle=0, delivery-count=0,
>> link-credit=10, drain=false]
>> [0x1705190]:0 <- @open(16)
>> [container-id="282a59cd-7875-4ede-8807-48dcc79fd3c7", max-frame-size=0,
>> channel-max=0, idle-time-out=0, properties={:product="qpid",
>> :version="6.0.0", :"qpid.build"="Unversioned directory",
>> :"qpid.instance_name"="Broker"}]
>> [0x1705190]:0 <- @close(24) [error=@error(29)
>> [condition=:"amqp:not-found", description="Unknown hostname in connection
>> open: 'localhost:5672'"]]
>> [0x1705190]:  <- EOS
>> ERROR:root:Unknown hostname in connection open: 'localhost:5672'
>> [0x1705190]:0 -> @close(24) []
>> [0x1705190]:  -> EOS
>>
>
> The c messenger works ok provided you set the address to the right
> hostname. The send example used 0.0.0.0 as default which again is rejected
> as invalid.
>
>

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".

-- Rob

>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>

--001a11c39c4e965c960525f13150--