[ 
https://issues.apache.org/jira/browse/QPID-3212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026324#comment-13026324
 ] 

Gordon Sim commented on QPID-3212:
----------------------------------

It would appear that for some reason there is an attempt to send on a link 
whose attachment has not (yet?) been initialised correctly.

There is a 'linked' flag on the sender that is checked before sending and that 
appears only to be set after successful resolution. Resolution *should* 
initialise the attachment. However something clearly is not happening as 
expected.

hypothesis 1: somehow the linked flag is set though the resolution has not 
completed
hypothesis 2: the type is neither 'topic' nor 'queue' when do_link for the 
OutLink is called, meaning that the attachment doesn't get set up

I can't yet see how either of these could be true...

Any hints on reproducing?

> AttributeError: Attachment instance has no attribute '_routing_key'
> -------------------------------------------------------------------
>
>                 Key: QPID-3212
>                 URL: https://issues.apache.org/jira/browse/QPID-3212
>             Project: Qpid
>          Issue Type: Bug
>          Components: Python Client
>    Affects Versions: 0.8
>         Environment: machine = F14
> installed:
> qpid-cpp-server-0.8-4.fc14.i686
> python-qpid-0.8-3.fc14.noarch
> qpid-tools-0.8-4.fc14.noarch
> qpid-cpp-client-0.8-4.fc14.i686
> qpid-cpp-server-ssl-0.8-4.fc14.i686
> qpid-cpp-client-devel-0.8-4.fc14.i686
> qpid-cpp-client-ssl-0.8-4.fc14.i686
> ruby-qpid-0.8-1.fc14.i686
> The broker and client are running on the same machine.
>            Reporter: Jeff Ortel
>
> While consuming messages in a thread running inside of mod_wsgi on F14, the 
> following exception is logged over and over. The driver seems to be broken 
> until apache (the client) is restarted.  This seems to clear it up.
> TRACE:
> ================================
> 2011-04-16 17:01:41,252 [ERROR][asynctaskreplyqueue] __fetch() @
> consumer.py:90 - asynctaskreplyqueue
> Traceback (most recent call last):
>   File "/home/jdob/code/gofer/src/gofer/messaging/consumer.py", line
> 86, in __fetch
>     return self.receiver.fetch(timeout=self.WAIT)
>   File "<string>", line 6, in fetch
>   File "/usr/lib/python2.7/site-packages/qpid/messaging/endpoints.py",
> line 997, in fetch
>     self._ecwait(lambda: self.linked)
>   File "/usr/lib/python2.7/site-packages/qpid/messaging/endpoints.py",
> line 50, in _ecwait
>     result = self._ewait(lambda: self.closed or predicate(), timeout)
>   File "/usr/lib/python2.7/site-packages/qpid/messaging/endpoints.py",
> line 960, in _ewait
>     result = self.session._ewait(lambda: self.error or predicate(), timeout)
>   File "/usr/lib/python2.7/site-packages/qpid/messaging/endpoints.py",
> line 553, in _ewait
>     result = self.connection._ewait(lambda: self.error or predicate(), 
> timeout)
>   File "/usr/lib/python2.7/site-packages/qpid/messaging/endpoints.py",
> line 196, in _ewait
>     self.check_error()
>   File "/usr/lib/python2.7/site-packages/qpid/messaging/endpoints.py",
> line 189, in check_error
>     raise self.error
> InternalError: Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/qpid/messaging/driver.py",
> line 504, in dispatch
>     self.engine.dispatch()
>   File "/usr/lib/python2.7/site-packages/qpid/messaging/driver.py",
> line 808, in dispatch
>     self.process(ssn)
>   File "/usr/lib/python2.7/site-packages/qpid/messaging/driver.py",
> line 1036, in process
>     self.send(snd, msg)
>   File "/usr/lib/python2.7/site-packages/qpid/messaging/driver.py",
> line 1209, in send
>     rk = _snd._routing_key
> AttributeError: Attachment instance has no attribute '_routing_key'

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to