[
https://issues.apache.org/jira/browse/DISPATCH-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487820#comment-15487820
]
Gordon Sim commented on DISPATCH-502:
-------------------------------------
The issue here seems to be that the create request message results in a
qdr_action_t being enqueued for processing by the core thread. That action has
a qd_field_iterator_t for the name (and some other stuff). However after the
action is enqueued, some object that owns the data the name iterator is
pointing into is freed (qd_field_iterator_t representing the
application-properties - which contains the name - is being freed in
qdr_management_agent_on_message, not sure if that is relevant or if it is
something higher up). This means that the name field may be overwritten before
the core thread processes it, so when it does, it gets a bad name.
> Seeing unexpected values in management query response
> -----------------------------------------------------
>
> Key: DISPATCH-502
> URL: https://issues.apache.org/jira/browse/DISPATCH-502
> Project: Qpid Dispatch
> Issue Type: Bug
> Reporter: Ulf Lilleengen
> Attachments: router.log
>
>
> We've been debugging an issue where we are getting some strange results from
> a management query for the router addresses.
> We've been able to capture the offending (we think) frame, maybe you can tell
> whether this is a correct frame or not:
> {noformat}
> [0x7f1cb8025ea0]:0 -> @transfer(20) [handle=1, delivery-id=9,
> delivery-tag=b"\x09\x00\x00\x00\x00\x00\x00\x00", message-format=0,
> settled=true, more=false] (547)
> "\x00Ss\xd0\x00\x00\x00G\x00\x00\x00\x06@@\xa19amqp:/_topo/0/Router.qdrouterd-3ysq1/temp.CKP6RovAXu+Q6mB@@\xa1\x0210\x00St\xd1\x00\x00\x00)\x00\x00\x00\x04\xa1\x11statusDescription\xa1\x02OK\xa1\x0astatusCodeR\xc8\x00Sw\xd1\x00\x00\x01\x9b\x00\x00\x00\x04\xa1\x0eattributeNames\xd0\x00\x00\x00U\x00\x00\x00\x08\xa1\x04name\xa1\x08identity\xa1\x04type\xa1\x06prefix\xa1\x0cdistribution\xa1\x08waypoint\xa1\x0cingressPhase\xa1\x0begressPhase\xa1\x07results\xd0\x00\x00\x01\x1f\x00\x00\x00\x03\xd0\x00\x00\x00X\x00\x00\x00\x08\xa1\x07myqueue\xa1\x013\xa1.org.apache.qpid.dispatch.router.config.address\xa1\x07myqueue\xa1\x08balancedAT\x00T\x01\xd0\x00\x00\x00W\x00\x00\x00\x08\xa1\x06CREATE\xa1\x014\xa1.org.apache.qpid.dispatch.router.config.address\xa1\x07anycast\xa1\x08balancedBT\x00T\x00\xd0\x00\x00\x00]\x00\x00\x00\x08\xa1\x09broadcast\xa1\x015\xa1.org.apache.qpid.dispatch.router.config.address\xa1\x09broadcast\xa1\x09multicastBT\x00T\x00
> {noformat}
> I'll attach the full log. We're working on a reproducer. Right now, we see
> this 1/5 times when deploying the router, so it seems to be a bit timing
> dependent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]