On 28 February 2018 at 12:17, Gordon Sim <[email protected]> wrote: > On 27/02/18 14:57, Oleksandr Rudyy wrote: > >> Hi all, >> >> I built a release candidate for a Qpid Broker-J 7.0.2. >> Please give it a test out and vote accordingly. >> > > +1 > > Verified hashes and signatures, built from source including tests, ran > python examples against it, ran qpid::messaging against it, ran some other > AMQP 1.0 examples against it. > > One thing to note though is that the selected_recv.py python example fails > with the broker returning an amqp:decode-error: Expected key type is > 'Filter' but got 'DescribedType'. I don't understand that error but the > protocol trace from proton is below. A variation of this in javascript > passes, where the key is jms-selector instead of just selector and the > descriptor is numeric rather than symbolic (not sure if that is the issue?). > > $ PN_TRACE_FRM=1 ./selected_recv.py [0x555941994670]: -> SASL >> [0x555941994670]: <- SASL >> [0x555941994670]:0 <- @sasl-mechanisms(64) [sasl-server-mechanisms=@PN_SY >> MBOL[:ANONYMOUS]] >> [0x555941994670]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS, >> initial-response=b"[email protected]"] >> [0x555941994670]:0 <- @sasl-outcome(68) [code=0] >> [0x555941994670]: -> AMQP >> [0x555941994670]:0 -> @open(16) >> [container-id="99957991-87b0-4e80-95ef-d346f1e42612", >> hostname="localhost", channel-max=32767] >> [0x555941994670]:0 -> @begin(17) [next-outgoing-id=0, >> incoming-window=2147483647, outgoing-window=2147483647] >> [0x555941994670]:0 -> @attach(18) >> [name="99957991-87b0-4e80-95ef-d346f1e42612-examples", >> handle=0, role=true, snd-settle-mode=2, rcv-settle-mode=0, >> source=@source(40) [address="examples", durable=0, timeout=0, >> dynamic=false, filter={:selector=@:"apache.org:selector-filter:string" >> "colour = 'green'"}], target=@target(41) [durable=0, timeout=0, >> dynamic=false], initial-delivery-count=0, max-message-size=0] >> [0x555941994670]:0 -> @flow(19) [incoming-window=2147483647, >> next-outgoing-id=0, outgoing-window=2147483647, handle=0, delivery-count=0, >> link-credit=10, drain=false] >> [0x555941994670]: <- AMQP >> [0x555941994670]:0 <- @open(16) >> [container-id="087cb095-8666-4473-bc70-f60f846f5ef7", >> max-frame-size=0, channel-max=0, idle-time-out=0, >> offered-capabilities=@PN_SYMBOL[:"ANONYMOUS-RELAY", :"SHARED-SUBS", >> :"sole-connection-for-container"], properties={:product="qpid", >> :version="7.0.2", :"qpid.build"="Unversioned directory", >> :"qpid.instance_name"="Broker", :"qpid.virtualhost_properties_ >> supported"="true"}] >> [0x555941994670]:0 <- @close(24) [error=@error(29) >> [condition=:"amqp:decode-error", description="Expected key type is >> 'Filter' but got 'DescribedType'"]] >> [0x555941994670]: <- EOS >> [0x555941994670]:0 -> @close(24) [] >> [0x555941994670]: -> EOS >> > > I would assume this is not a new error... from the looks of things this is the Broker not supporting the "apache.org:selector-filter:string" filter type, and choking on the fact in a less than graceful way. Looking at the Broker-J code in org.apache.qpid.server.protocol.v1_0.type.messaging.codec.JMSSelectorFilterConstructor it appears that the symbolic descriptor is not defined correctly there while the ulong descriptor is correct (which is why, for instance, the JMS client works).
-- Rob > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
