qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Charles E. Rolke (Jira)" <j...@apache.org>
Subject [jira] [Created] (DISPATCH-1538) [tools] Scraper transfer and link nicknames not created in time order
Date Thu, 02 Jan 2020 15:24:00 GMT
Charles E. Rolke created DISPATCH-1538:

             Summary: [tools] Scraper transfer and link nicknames not created in time order
                 Key: DISPATCH-1538
                 URL: https://issues.apache.org/jira/browse/DISPATCH-1538
             Project: Qpid Dispatch
          Issue Type: Improvement
          Components: Tools
    Affects Versions: 1.10.0
            Reporter: Charles E. Rolke
             Fix For: 1.11.0

Transfer and link short names (transfer_1, transfer_2, ...; link_1, link_2, ...) are created
in-order as found first in log file A, then log file B, and so on. This means that if log
file A has 10,000 transfers then it consumes nicknames transfer_1..transfer_10000. The first
new transfer in log file B will be transfer_10001 despite the fact that it may have occurred
before any of the transfers in log file A.

This is obvious in the _Log data_ section as the transfers are shown in temporal order: transfer_10000
may be the first one in the section. This is confusing.

It is a bigger problem in the _Link name index_ and _Transfer name index_ sections where the
links and transfers are shown in serial order. A response transfer may be in transfer_3 while
the initiating transfer is in transfer_10001. 

Showing these sections with the serial order also being the temporal order would be a big

This message was sent by Atlassian Jira

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message