qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Lugtu <clu...@microsoft.com>
Subject RE: Help with Proton-c 0.9.1 and Qpid 0.32 Java Broker
Date Mon, 18 May 2015 22:58:26 GMT
Thanks again Rob.

Unfortunately nothing much changed. I'm not seeing any logs from the framer.  I'm also continuing
to get the same assert.

2015-05-18 15:57:14,356 INFO  [IoReceiver - /0:0:0:0:0:0:0:1:51932] (stats.StatisticsCounter)
- Resetting statistics for counter: messages-delivered-0-13
2015-05-18 15:57:14,356 INFO  [IoReceiver - /0:0:0:0:0:0:0:1:51932] (stats.StatisticsCounter)
- Resetting statistics for counter: data-delivered-0-14
2015-05-18 15:57:14,356 INFO  [IoReceiver - /0:0:0:0:0:0:0:1:51932] (stats.StatisticsCounter)
- Resetting statistics for counter: messages-received-0-15
2015-05-18 15:57:14,356 INFO  [IoReceiver - /0:0:0:0:0:0:0:1:51932] (stats.StatisticsCounter)
- Resetting statistics for counter: data-received-0-16



-----Original Message-----
From: Rob Godfrey [mailto:rob.j.godfrey@gmail.com] 
Sent: Monday, May 18, 2015 9:05 AM
To: users@qpid.apache.org
Subject: Re: Help with Proton-c 0.9.1 and Qpid 0.32 Java Broker

Is it possible you to turn on frame debug logging in the Java Broker...

Adding something like the following:

    <logger additivity="true" name="FRM">

        <level value="debug"/>

    </logger>

to the log4j.xml for the broker should do it.


I'm guessing that proton is trying to send to some address on the broker that isn't an already
defined queue or exchange.  In this case the broker will be responding to the client to say
that no such address exists.

Having the log details should make this clear though,

-- Rob

On 18 May 2015 at 17:46, Carlos Lugtu <clugtu@microsoft.com> wrote:
> Thanks for the response. Now I'm getting this from proton when I run 
> the following command
>
> .\send.exe -a amqp://anonymous:@localhost:5672 hello
>
> Assertion failed: n == PN_EOS, file 
> qpid-proton-0.9.1-rc1\proton-c\src\transport\transport.c, line 1599
>
> If I switch back to the password authentication I see the same thing. This happens on
both send and recv.
>
> On the broker I get the following logs:
> 2015-05-18 08:45:03,693 INFO  [IoReceiver - /0:0:0:0:0:0:0:1:46494] 
> (stats.StatisticsCounter) - Resetting statistics for counter: 
> messages-delivered-7-33
> 2015-05-18 08:45:03,693 INFO  [IoReceiver - /0:0:0:0:0:0:0:1:46494] 
> (stats.StatisticsCounter) - Resetting statistics for counter: 
> data-delivered-7-34
> 2015-05-18 08:45:03,693 INFO  [IoReceiver - /0:0:0:0:0:0:0:1:46494] 
> (stats.StatisticsCounter) - Resetting statistics for counter: 
> messages-received-7-35
> 2015-05-18 08:45:03,693 INFO  [IoReceiver - /0:0:0:0:0:0:0:1:46494] 
> (stats.StatisticsCounter) - Resetting statistics for counter: 
> data-received-7-36
>
> So something different is going on, but I'm still not sure where the failure is.
>
> Can anyone reproduce this simple test?
>
> Thanks in advance for your help.
>
> C
>
>
> -----Original Message-----
> From: Rob Godfrey [mailto:rob.j.godfrey@gmail.com]
> Sent: Monday, May 18, 2015 3:01 AM
> To: users@qpid.apache.org
> Subject: Re: Help with Proton-c 0.9.1 and Qpid 0.32 Java Broker
>
> OK - so for Carlos, if he wants to use anonymous with proton 0.9.1 he 
> could use
>
> amqp://anonymous:@localhost:5672
>
> (where anonymous could actually be substituted by any non-zero length 
> string)
>
> -- Rob
>
> On 18 May 2015 at 11:56, Gordon Sim <gsim@redhat.com> wrote:
>> On 05/18/2015 10:19 AM, Rob Godfrey wrote:
>>>
>>> Does the proton client support Anonymous SASL, or would Carlos need 
>>> to set up some user/password database on the server side (i.e. is 
>>> supplying a user/password just to force the client into doing SASL 
>>> negotiation)?
>>
>>
>> Sorry, I guess I didn't actually answer the question!
>>
>> In 0.8 and earlier, messenger always used a SASL layer, with 
>> ANONYMOUS being the default unless a username was supplied. In 0.9 
>> and 0.9.1, a SASL layer is only used if a username is specified. If 
>> there is no password specified, then ANONYMOUS is chosen, else PLAIN.
>>
>> In the next release, 0.10, for linux at least there is cyrus SASL 
>> support which if built may alter the picture as well (it appears to 
>> choose the first suitable mechanism offered by the peer/broker).
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org For 
>> additional commands, e-mail: users-help@qpid.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org For 
> additional commands, e-mail: users-help@qpid.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org For 
> additional commands, e-mail: users-help@qpid.apache.org
>

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


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

Mime
View raw message