Re: [paho-dev] Basic test failing

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [paho-dev] Basic test failing

From: Nicolas Jouanin <nico@xxxxxxxxxxxxxxx>
Date: Mon, 27 Jul 2015 22:15:41 +0200
Delivered-to: paho-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/paho-dev>
List-help: <mailto:paho-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/paho-dev>, <mailto:paho-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/paho-dev>, <mailto:paho-dev-request@eclipse.org?subject=unsubscribe>

For information, I’ve release HBMQTT 0.4 which pass all broker conformance tests successfully.

Le 27 juil. 2015 à 13:15, Nicolas Jouanin <nico@xxxxxxxxxxxxxxx> a écrit :

Hi,

I manages to fix this issue. Now I’m investigating the problem I mentioned in a previous post : offline_message_queuing_test working alone but not in the test suite.
Thanks again.

Le 27 juil. 2015 à 12:18, Ian Craggs <icraggs@xxxxxxxxxxxxxxxxxxxxxxx> a écrit :

Hi Nicolas,

from that trace, it looks like the client is sending a PUBREL for msgid 4, but not getting a PUBCOMP, nor receiving a PUBLISH? The trace looks like it might be incomplete though. This is the sequence of packets which are sent and received by the Python test broker (python3 startbroker.py) when running the same test:

INFO 20150727 110533 in: Connects(DUP=False, QoS=0, Retain=False, ProtocolName=MQTT, ProtocolVersion=4, CleanSession=True, WillFlag=False, KeepAliveTimer=0, ClientId=myclientid, usernameFlag=False, passwordFlag=False)
INFO 20150727 110533 out: Connacks(DUP=False, QoS=0, Retain=False, Session present=False, ReturnCode=0)
INFO 20150727 110533 in: Subscribes(DUP=False, QoS=1, Retain=False, MsgId=2, Data="" 2)])
INFO 20150727 110533 out: Subacks(DUP=False, QoS=0, Retain=False, MsgId=2, Data="" class="">INFO 20150727 110533 in: Publishes(DUP=False, QoS=0, Retain=False, TopicName='TopicA', Payload=b'qos 0')
INFO 20150727 110533 out: Publishes(DUP=False, QoS=0, Retain=False, TopicName='TopicA', Payload=b'qos 0')
INFO 20150727 110533 in: Publishes(DUP=False, QoS=1, Retain=False, MsgId=3, TopicName='TopicA', Payload=b'qos 1')
INFO 20150727 110533 out: Publishes(DUP=False, QoS=1, Retain=False, MsgId=1, TopicName='TopicA', Payload=b'qos 1')
INFO 20150727 110533 out: Pubacks(DUP=False, QoS=0, Retain=False, MsgId 3
INFO 20150727 110533 in: Publishes(DUP=False, QoS=2, Retain=False, MsgId=4, TopicName='TopicA', Payload=b'qos 2')
INFO 20150727 110533 out: Pubrecs(DUP=False, QoS=0, Retain=False, MsgId=4)
INFO 20150727 110533 in: Pubacks(DUP=False, QoS=0, Retain=False, MsgId 1
INFO 20150727 110534 in: Pubrels(DUP=False, QoS=1, Retain=False, MsgId=4)
INFO 20150727 110534 out: Publishes(DUP=False, QoS=2, Retain=False, MsgId=2, TopicName='TopicA', Payload=b'qos 2')
INFO 20150727 110534 out: Pubcomps(DUP=False, QoS=0, Retain=False, MsgId=4)
INFO 20150727 110534 in: Pubrecs(DUP=False, QoS=0, Retain=False, MsgId=2)
INFO 20150727 110534 out: Pubrels(DUP=False, QoS=1, Retain=False, MsgId=2)
INFO 20150727 110534 in: Pubcomps(DUP=False, QoS=0, Retain=False, MsgId=2)
INFO 20150727 110535 in: Disconnects(DUP=False, QoS=0, Retain=False)

(Remember this is the server side of the exchange)

Ian

On 07/23/2015 09:41 PM, Nicolas Jouanin wrote:
Hi,

My broker implementation currently fails basic testing fails with error :
Traceback (most recent call last):
File "client_test.py", line 106, in basic_test
   aclient.disconnect()
File "/Users/nico/Dev/beerfactory/org.eclipse.paho.mqtt.testing/interoperability/mqtt/client/main.py", line 189, in disconnect
   assert self.__receiver.outMsgs == {}, self.__receiver.outMsgs
AssertionError: {4: Publishes(DUP=False, QoS=2, Retain=False, MsgId=4, TopicName='TopicA', Payload=b'qos 2')}
test suite failed

As I understand this means that all messages have not been sent on disconnect. What is strange in that debugging message flows seems OK except that the test client doesn’t return PUBREL message and my broker waits for it to send the pubcomp. Here is the output of client_test.py with debug logging level. Any idea why the client_test doesn’t send PUBREL back ?

hostname localhost port 1883
clean up starting
DEBUG:mqtt-client:out: b'\xe0\x00'
clean up finished
Basic test starting
DEBUG:mqtt-client:out: b'\x10\x16\x00\x04MQTT\x04\x02\x00\x00\x00\nmyclientid'
DEBUG:mqtt-client:initializing receiver
DEBUG:mqtt-client:out: b'\xe0\x00'
DEBUG:mqtt-client:out: b'\x10\x16\x00\x04MQTT\x04\x02\x00\x00\x00\nmyclientid'
DEBUG:mqtt-client:initializing receiver
DEBUG:mqtt-client:out: b'\x82\x0b\x00\x02\x00\x06TopicA\x02'
DEBUG:mqtt-client:out: b'0\r\x00\x06TopicAqos 0'
DEBUG:mqtt-client:out: b'2\x0f\x00\x06TopicA\x00\x03qos 1'
DEBUG:mqtt-client:out: b'4\x0f\x00\x06TopicA\x00\x04qos 2'
DEBUG:mqtt-client:in :Pubacks(DUP=False, QoS=0, Retain=False, MsgId 3
DEBUG:mqtt-client:in :Pubrecs(DUP=False, QoS=0, Retain=False, MsgId=4)
DEBUG:mqtt-client:out: Pubrels(DUP=False, QoS=1, Retain=False, MsgId=4)
DEBUG:mqtt-client:in :Subacks(DUP=False, QoS=0, Retain=False, MsgId=2, Data="" class="">DEBUG:mqtt-client:disconnecting {} {4: Publishes(DUP=False, QoS=2, Retain=False, MsgId=4, TopicName='TopicA', Payload=b'qos 2')}
DEBUG:mqtt-client:disconnecting {} {4: Publishes(DUP=False, QoS=2, Retain=False, MsgId=4, TopicName='TopicA', Payload=b'qos 2')}
DEBUG:mqtt-client:disconnecting {} {4: Publishes(DUP=False, QoS=2, Retain=False, MsgId=4, TopicName='TopicA', Payload=b'qos 2')}
DEBUG:mqtt-client:disconnecting {} {4: Publishes(DUP=False, QoS=2, Retain=False, MsgId=4, TopicName='TopicA', Payload=b'qos 2')}
DEBUG:mqtt-client:disconnecting {} {4: Publishes(DUP=False, QoS=2, Retain=False, MsgId=4, TopicName='TopicA', Payload=b'qos 2')}
DEBUG:mqtt-client:disconnecting {} {4: Publishes(DUP=False, QoS=2, Retain=False, MsgId=4, TopicName='TopicA', Payload=b'qos 2')}
DEBUG:mqtt-client:disconnecting {} {4: Publishes(DUP=False, QoS=2, Retain=False, MsgId=4, TopicName='TopicA', Payload=b'qos 2')}
DEBUG:mqtt-client:disconnecting {} {4: Publishes(DUP=False, QoS=2, Retain=False, MsgId=4, TopicName='TopicA', Payload=b'qos 2')}
DEBUG:mqtt-client:disconnecting {} {4: Publishes(DUP=False, QoS=2, Retain=False, MsgId=4, TopicName='TopicA', Payload=b'qos 2')}
DEBUG:mqtt-client:disconnecting {} {4: Publishes(DUP=False, QoS=2, Retain=False, MsgId=4, TopicName='TopicA', Payload=b'qos 2')}
DEBUG:mqtt-client:disconnecting {} {4: Publishes(DUP=False, QoS=2, Retain=False, MsgId=4, TopicName='TopicA', Payload=b'qos 2')}
DEBUG:mqtt-client:disconnecting {} {4: Publishes(DUP=False, QoS=2, Retain=False, MsgId=4, TopicName='TopicA', Payload=b'qos 2')}
DEBUG:mqtt-client:disconnecting {} {4: Publishes(DUP=False, QoS=2, Retain=False, MsgId=4, TopicName='TopicA', Payload=b'qos 2')}
DEBUG:mqtt-client:disconnecting {} {4: Publishes(DUP=False, QoS=2, Retain=False, MsgId=4, TopicName='TopicA', Payload=b'qos 2')}
DEBUG:mqtt-client:disconnecting {} {4: Publishes(DUP=False, QoS=2, Retain=False, MsgId=4, TopicName='TopicA', Payload=b'qos 2')}
DEBUG:mqtt-client:disconnecting {} {4: Publishes(DUP=False, QoS=2, Retain=False, MsgId=4, TopicName='TopicA', Payload=b'qos 2')}
DEBUG:mqtt-client:disconnecting {} {4: Publishes(DUP=False, QoS=2, Retain=False, MsgId=4, TopicName='TopicA', Payload=b'qos 2')}
DEBUG:mqtt-client:disconnecting {} {4: Publishes(DUP=False, QoS=2, Retain=False, MsgId=4, TopicName='TopicA', Payload=b'qos 2')}
DEBUG:mqtt-client:disconnecting {} {4: Publishes(DUP=False, QoS=2, Retain=False, MsgId=4, TopicName='TopicA', Payload=b'qos 2')}
DEBUG:mqtt-client:disconnecting {} {4: Publishes(DUP=False, QoS=2, Retain=False, MsgId=4, TopicName='TopicA', Payload=b'qos 2')}
Traceback (most recent call last):
File "client_test.py", line 106, in basic_test
   aclient.disconnect()
File "/Users/nico/Dev/beerfactory/org.eclipse.paho.mqtt.testing/interoperability/mqtt/client/main.py", line 189, in disconnect
   assert self.__receiver.outMsgs == {}, self.__receiver.outMsgs
AssertionError: {4: Publishes(DUP=False, QoS=2, Retain=False, MsgId=4, TopicName='TopicA', Payload=b'qos 2')}
test suite failed

_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/paho-dev

--
Ian Craggs
icraggs@xxxxxxxxxx                 IBM United Kingdom
Paho Project Lead; Committer on Mosquitto

_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/paho-dev

_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/paho-dev

References:
- [paho-dev] Basic test failing
  - From: Nicolas Jouanin
- Re: [paho-dev] Basic test failing
  - From: Ian Craggs
- Re: [paho-dev] Basic test failing
  - From: Nicolas Jouanin

Prev by Date: Re: [paho-dev] Basic test failing
Next by Date: [paho-dev] Wrong Design Pattern in ClientState.checkForActivity()
Previous by thread: Re: [paho-dev] Basic test failing
Next by thread: [paho-dev] Wrong Design Pattern in ClientState.checkForActivity()
Index(es):
- Date
- Thread

Breadcrumbs