Bug #2313
Unexpected Exception about introspection
Status: | New | Start date: | 06/03/2015 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | Python | |||
Target version: | rsb-0.18 |
Description
I got an unexpected traceback on console when using a simple python RSB tool:
Exception in thread Thread-13: Traceback (most recent call last): File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner self.run() File "/usr/lib/python2.7/threading.py", line 763, in run self.__target(*self.__args, **self.__kwargs) File "/vol/csra/releases/trusty/lsp-csra-nightly/lib/python2.7/site-packages/rsb_python-0.12.0-py2.7.egg/rsb/util.py", line 326, in __worker self.__delFunc(receiver.receiver, message) File "/vol/csra/releases/trusty/lsp-csra-nightly/lib/python2.7/site-packages/rsb_python-0.12.0-py2.7.egg/rsb/eventprocessing.py", line 135, in __deliver action(event) File "/vol/csra/releases/trusty/lsp-csra-nightly/lib/python2.7/site-packages/rsb_python-0.12.0-py2.7.egg/rsb/patterns/__init__.py", line 326, in _handleRequest self.informer.publishEvent(reply) File "/vol/csra/releases/trusty/lsp-csra-nightly/lib/python2.7/site-packages/rsb_python-0.12.0-py2.7.egg/rsb/__init__.py", line 1425, in publishEvent % (event.scope, event, self.scope)) ValueError: Scope Scope[/__rsb/introspection/hosts/74938b09ed902fb7ea2dcd25556c0708/25912/echo/] of event Event[id = EventId(UUID('0d8b3a49-4fca-41d3-b7f7-91f871b546f2'), 158590), scope = 'Scope[/__rsb/introspection/hosts/74938b09ed902fb7ea2dcd25556c0708/25912/echo/]', data = 'None', type = '<type 'NoneType'>', method = 'REPLY', metaData = MetaData[create = 1433321961.33, send = 1433321961.33, receive = 1433321961.34, deliver = 1433321961.34, userTimes = {'request.send': 1433321961.332422, 'request.receive': 1433321961.342748}, userInfos = {}], causes = [EventId(UUID('0d8b3a49-4fca-41d3-b7f7-91f871b546f2'), 158590)]] is not a sub-scope of this informer's scope Scope[/__rsb/introspection/hosts/74938b09ed902fb7ea2dcd25556c0708/26077/echo/].
I cannot reproduce this exception as it only occurred once. I hope you can use this information...
History
#1 Updated by J. Wienke almost 8 years ago
Are you using multiprocessing?
#2 Updated by N. Köster almost 8 years ago
no, it was a very basic 1 file simple receiver for images - no multiprocessing involved
#3 Updated by J. Wienke almost 8 years ago
Hm the only way apart from multiprocessing which could explain this would be a UUID clash. Two processes must have had the same UUID for a contained participant. Quite unlikely, but I cannot see any other explanations for this behavior. Basically, the PID of the process differed despite the UUID being the same.
Jan, any further ideas?
#4 Updated by J. Wienke almost 8 years ago
Jan, do you have an idea how to explain this?
#5 Updated by J. Moringen over 7 years ago
- Target version changed from rsb-0.13 to rsb-0.14
#6 Updated by J. Moringen about 7 years ago
- Target version changed from rsb-0.14 to rsb-0.15
#7 Updated by J. Moringen over 6 years ago
- Target version changed from rsb-0.15 to rsb-0.16
#8 Updated by J. Moringen about 6 years ago
- Target version changed from rsb-0.16 to rsb-0.17
#9 Updated by J. Moringen over 5 years ago
- Target version changed from rsb-0.17 to rsb-0.18