Ken Giusti created DISPATCH-1459:
------------------------------------

             Summary: Python3: exception thrown when processing MAUs
                 Key: DISPATCH-1459
                 URL: https://issues.apache.org/jira/browse/DISPATCH-1459
             Project: Qpid Dispatch
          Issue Type: Bug
          Components: Routing Engine
    Affects Versions: 1.9.0
         Environment: 3 router mesh configuration with test client that 
generates a large # of subscriptions.

Configurations and client attached.

Run like this:

(in build directory)

 

rm Router*.log; qdrouterd -c 
/home/kgiusti/work/dispatch/qpid-dispatch/BUILD/RouterA.conf & sleep 2; 
qdrouterd -c /home/kgiusti/work/dispatch/qpid-dispatch/BUILD/RouterB.conf & 
sleep 2; qdrouterd -c 
/home/kgiusti/work/dispatch/qpid-dispatch/BUILD/RouterC.conf & sleep 2; 
~/tmp/test-receiver -a 127.0.0.1:28782 &

 

Monitor logs until traceback is hit.
            Reporter: Ken Giusti
             Fix For: 1.10.0
         Attachments: RouterA.conf, RouterB.conf, RouterC.conf, test-receiver.c

While running an address load test with system python == 3.7.4:

2019-10-24 09:22:56.131966 -0400 ROUTER (error) Exception in control message 
processing
Traceback (most recent call last):
 File 
"/home/kgiusti/work/dispatch/qpid-dispatch/python/qpid_dispatch_internal/router/engine.py",
 line 163, in handleControlMessage
 msg = MessageMAU(body)
 File 
"/home/kgiusti/work/dispatch/qpid-dispatch/python/qpid_dispatch_internal/router/data.py",
 line 267, in __init__
 self.mobile_seq = LONG(_seq)
 File 
"/home/kgiusti/work/dispatch/qpid-dispatch/python/qpid_dispatch_internal/compat/__init__.py",
 line 136, in LONG
 return int(i)
TypeError: int() argument must be a string, a bytes-like object or a number, 
not 'NoneType'
 
(/home/kgiusti/work/dispatch/qpid-dispatch/python/qpid_dispatch_internal/router/engine.py:176)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to