[jira] [Commented] (DISPATCH-1141) Add an event API in the router core to more cleanly support module interactions
[ https://issues.apache.org/jira/browse/DISPATCH-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16648437#comment-16648437 ] ASF subversion and git services commented on DISPATCH-1141: --- Commit a357dfa3ef0aaf01a7e88d96e443ff68b00355d2 in qpid-dispatch's branch refs/heads/master from [~tr...@redhat.com] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=a357dfa ] DISPATCH-1141 - Consolidated address to link/connection binding, wired in the core address events > Add an event API in the router core to more cleanly support module > interactions > --- > > Key: DISPATCH-1141 > URL: https://issues.apache.org/jira/browse/DISPATCH-1141 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Router Node >Reporter: Ted Ross >Assignee: Ted Ross >Priority: Major > Fix For: 1.5.0 > > > Router core modules are reactive and respond to changes in connection, link, > and address state. This improvement provides an event API that can be used > by modules to register for events that are of interest. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8248) qpid-config lists deleted exchange
[
https://issues.apache.org/jira/browse/QPID-8248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16648241#comment-16648241
]
ASF subversion and git services commented on QPID-8248:
---
Commit f264cc6c0f27635b784d602d6ff85df09742cbe0 in qpid-cpp's branch
refs/heads/master from Gordon Sim
[ https://git-wip-us.apache.org/repos/asf?p=qpid-cpp.git;h=f264cc6 ]
QPID-8248: fix resetting of pointer for certain compilers
> qpid-config lists deleted exchange
> --
>
> Key: QPID-8248
> URL: https://issues.apache.org/jira/browse/QPID-8248
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
>Affects Versions: qpid-cpp-1.38.0
>Reporter: Gordon Sim
>Assignee: Gordon Sim
>Priority: Major
> Fix For: qpid-cpp-1.39.0
>
>
> In AMQP 0-10, the last exchange to which a message is sent is cached for
> improved performance. However this means that the exchange object will not be
> freed when deleted from the registry until all references to it are freed.
> To reproduce:
> {noformat}
> 1. qpid-config add exchange foo
> 2. qpid-send -a foo --content-stdin
> 3. enter some text to send a message
> 4. in another console qpid-config dell exchange foo
> 5. qpid-config exchanges
> {noformat}
> Should not see the deleted exchange in step 5.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1142) Edge Router Module - Connection manager to select the active uplink
[ https://issues.apache.org/jira/browse/DISPATCH-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-1142. Resolution: Fixed > Edge Router Module - Connection manager to select the active uplink > --- > > Key: DISPATCH-1142 > URL: https://issues.apache.org/jira/browse/DISPATCH-1142 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Router Node >Reporter: Ted Ross >Assignee: Ted Ross >Priority: Major > Fix For: 1.5.0 > > > An edge router may have multiple "edge-uplink" connections to interior > routers. The edge router must designate exactly one of these connections as > the active uplink and leave the others unused but ready as alternates to > serve as the new active if the current active is lost. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1141) Add an event API in the router core to more cleanly support module interactions
[ https://issues.apache.org/jira/browse/DISPATCH-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-1141: --- Fix Version/s: (was: Backlog) 1.5.0 > Add an event API in the router core to more cleanly support module > interactions > --- > > Key: DISPATCH-1141 > URL: https://issues.apache.org/jira/browse/DISPATCH-1141 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Router Node >Reporter: Ted Ross >Assignee: Ted Ross >Priority: Major > Fix For: 1.5.0 > > > Router core modules are reactive and respond to changes in connection, link, > and address state. This improvement provides an event API that can be used > by modules to register for events that are of interest. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1142) Edge Router Module - Connection manager to select the active uplink
[ https://issues.apache.org/jira/browse/DISPATCH-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-1142: --- Fix Version/s: (was: Backlog) 1.5.0 > Edge Router Module - Connection manager to select the active uplink > --- > > Key: DISPATCH-1142 > URL: https://issues.apache.org/jira/browse/DISPATCH-1142 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Router Node >Reporter: Ted Ross >Assignee: Ted Ross >Priority: Major > Fix For: 1.5.0 > > > An edge router may have multiple "edge-uplink" connections to interior > routers. The edge router must designate exactly one of these connections as > the active uplink and leave the others unused but ready as alternates to > serve as the new active if the current active is lost. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1119) Assert in qdr_del_link_ref in self test system_tests_multi_tenancy
[
https://issues.apache.org/jira/browse/DISPATCH-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1119.
-
Resolution: Fixed
> Assert in qdr_del_link_ref in self test system_tests_multi_tenancy
> --
>
> Key: DISPATCH-1119
> URL: https://issues.apache.org/jira/browse/DISPATCH-1119
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Routing Engine
>Affects Versions: 1.3.0
>Reporter: Chuck Rolke
>Assignee: michael goulish
>Priority: Major
> Fix For: 1.4.0
>
>
> {{qdrouterd: /home/chug/git/qpid-dispatch/src/router_core/router_core.c:441:
> qdr_del_link_ref: Assertion `(*ref_list).size > 0' failed.}}
> {{#0 0x7fe982b26feb in raise () from /lib64/libc.so.6}}
> {{#1 0x7fe982b115c1 in abort () from /lib64/libc.so.6}}
> {{#2 0x7fe982b11491 in __assert_fail_base.cold.0 () from
> /lib64/libc.so.6}}
> {{#3 0x7fe982b1f752 in __assert_fail () from /lib64/libc.so.6}}
> {{#4 0x7fe983de3559 in qdr_del_link_ref (ref_list=0x7fe96403c680,
> link=0x7fe9580c1a60, cls=1) at
> /home/chug/git/qpid-dispatch/src/router_core/router_core.c:441}}
> {{#5 0x7fe983dd4b6c in qdr_link_cleanup_CT (core=0x237a6e0,
> conn=0x7fe96403c5e0, link=0x7fe9580c1a60) at
> /home/chug/git/qpid-dispatch/src/router_core/connections.c:856}}
> {{#6 0x7fe983dd7b68 in qdr_link_inbound_detach_CT (core=0x237a6e0,
> action=0x237d7a0, discard=false) at
> /home/chug/git/qpid-dispatch/src/router_core/connections.c:1945}}
> {{#7 0x7fe983de434d in router_core_thread (arg=0x237a6e0) at
> /home/chug/git/qpid-dispatch/src/router_core/router_core_thread.c:83}}
> {{#8 0x7fe983714594 in start_thread () from /lib64/libpthread.so.0}}
> {{#9 0x7fe982bea0df in clone () from /lib64/libc.so.6}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1010) Intermittent test failure with system_tests_disallow_link_resumable_link_route
[
https://issues.apache.org/jira/browse/DISPATCH-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chuck Rolke resolved DISPATCH-1010.
---
Resolution: Fixed
> Intermittent test failure with system_tests_disallow_link_resumable_link_route
> --
>
> Key: DISPATCH-1010
> URL: https://issues.apache.org/jira/browse/DISPATCH-1010
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.0.0
>Reporter: Chuck Rolke
>Assignee: Chuck Rolke
>Priority: Major
> Fix For: 1.4.0
>
>
> The test starts the routers with
> {{wait=False and sleep(2)}}
> Sometimes the sleep is not enough and the tests all fail with connection
> errors because the routers are not up yet.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (DISPATCH-1125) AMQP framing errors on forwarded multicast messages
[ https://issues.apache.org/jira/browse/DISPATCH-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke closed DISPATCH-1125. - Resolution: Duplicate fixed at commit 430efa07 Work to fix this issue is recorded in DISPATCH-1136 > AMQP framing errors on forwarded multicast messages > --- > > Key: DISPATCH-1125 > URL: https://issues.apache.org/jira/browse/DISPATCH-1125 > Project: Qpid Dispatch > Issue Type: Bug > Components: Router Node >Affects Versions: 1.3.0 >Reporter: Chuck Rolke >Priority: Major > Fix For: 1.4.0 > > Attachments: DISPATCH-1125.txt > > > These errors show up using the same setup described in DISPATCH-1124. > A three-router linear network uses a wireless connection for the interrouter > links. > Messages are injected into a router at one end of the chain and are forwarded > to receivers on the other two routers. > * The receiver attached to the router in the middle may receive tens of > millions of messages before getting an underflow. > * The receiver attached to the router at the far end of the chain may file > as soon as 25 messages or as late as several thousand messages. > * Messages are text strings 1,443 bytes long > Some observations: > * Normal transfer frames have transport size of 0x5ec bytes. > * Messages that fail with underrun commonly have a size of 0x1aa bytes. It > is not always 0x1aa but that number shows up in consecutive runs. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1119) Assert in qdr_del_link_ref in self test system_tests_multi_tenancy
[
https://issues.apache.org/jira/browse/DISPATCH-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1119:
Fix Version/s: 1.4.0
> Assert in qdr_del_link_ref in self test system_tests_multi_tenancy
> --
>
> Key: DISPATCH-1119
> URL: https://issues.apache.org/jira/browse/DISPATCH-1119
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Routing Engine
>Affects Versions: 1.3.0
>Reporter: Chuck Rolke
>Assignee: michael goulish
>Priority: Major
> Fix For: 1.4.0
>
>
> {{qdrouterd: /home/chug/git/qpid-dispatch/src/router_core/router_core.c:441:
> qdr_del_link_ref: Assertion `(*ref_list).size > 0' failed.}}
> {{#0 0x7fe982b26feb in raise () from /lib64/libc.so.6}}
> {{#1 0x7fe982b115c1 in abort () from /lib64/libc.so.6}}
> {{#2 0x7fe982b11491 in __assert_fail_base.cold.0 () from
> /lib64/libc.so.6}}
> {{#3 0x7fe982b1f752 in __assert_fail () from /lib64/libc.so.6}}
> {{#4 0x7fe983de3559 in qdr_del_link_ref (ref_list=0x7fe96403c680,
> link=0x7fe9580c1a60, cls=1) at
> /home/chug/git/qpid-dispatch/src/router_core/router_core.c:441}}
> {{#5 0x7fe983dd4b6c in qdr_link_cleanup_CT (core=0x237a6e0,
> conn=0x7fe96403c5e0, link=0x7fe9580c1a60) at
> /home/chug/git/qpid-dispatch/src/router_core/connections.c:856}}
> {{#6 0x7fe983dd7b68 in qdr_link_inbound_detach_CT (core=0x237a6e0,
> action=0x237d7a0, discard=false) at
> /home/chug/git/qpid-dispatch/src/router_core/connections.c:1945}}
> {{#7 0x7fe983de434d in router_core_thread (arg=0x237a6e0) at
> /home/chug/git/qpid-dispatch/src/router_core/router_core_thread.c:83}}
> {{#8 0x7fe983714594 in start_thread () from /lib64/libpthread.so.0}}
> {{#9 0x7fe982bea0df in clone () from /lib64/libc.so.6}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1010) Intermittent test failure with system_tests_disallow_link_resumable_link_route
[
https://issues.apache.org/jira/browse/DISPATCH-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1010:
Fix Version/s: 1.4.0
> Intermittent test failure with system_tests_disallow_link_resumable_link_route
> --
>
> Key: DISPATCH-1010
> URL: https://issues.apache.org/jira/browse/DISPATCH-1010
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.0.0
>Reporter: Chuck Rolke
>Assignee: Chuck Rolke
>Priority: Major
> Fix For: 1.4.0
>
>
> The test starts the routers with
> {{wait=False and sleep(2)}}
> Sometimes the sleep is not enough and the tests all fail with connection
> errors because the routers are not up yet.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1125) AMQP framing errors on forwarded multicast messages
[ https://issues.apache.org/jira/browse/DISPATCH-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1125: Fix Version/s: 1.4.0 > AMQP framing errors on forwarded multicast messages > --- > > Key: DISPATCH-1125 > URL: https://issues.apache.org/jira/browse/DISPATCH-1125 > Project: Qpid Dispatch > Issue Type: Bug > Components: Router Node >Affects Versions: 1.3.0 >Reporter: Chuck Rolke >Priority: Major > Fix For: 1.4.0 > > Attachments: DISPATCH-1125.txt > > > These errors show up using the same setup described in DISPATCH-1124. > A three-router linear network uses a wireless connection for the interrouter > links. > Messages are injected into a router at one end of the chain and are forwarded > to receivers on the other two routers. > * The receiver attached to the router in the middle may receive tens of > millions of messages before getting an underflow. > * The receiver attached to the router at the far end of the chain may file > as soon as 25 messages or as late as several thousand messages. > * Messages are text strings 1,443 bytes long > Some observations: > * Normal transfer frames have transport size of 0x5ec bytes. > * Messages that fail with underrun commonly have a size of 0x1aa bytes. It > is not always 0x1aa but that number shows up in consecutive runs. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1079) Setting socketAddressFamily/protocolFamily does not take effect
[
https://issues.apache.org/jira/browse/DISPATCH-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1079:
Fix Version/s: (was: 1.4.0)
1.5.0
> Setting socketAddressFamily/protocolFamily does not take effect
> ---
>
> Key: DISPATCH-1079
> URL: https://issues.apache.org/jira/browse/DISPATCH-1079
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 1.2.0
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.5.0
>
>
> socketAddressFamily/protocolFamily can be specified on a listener like this
> {noformat}
> listener {
> idleTimeoutSeconds: 120
> saslMechanisms: ANONYMOUS
> host: ::1
> role: normal
> socketAddressFamily: IPv6
> authenticatePeer: no
> port: 29190
> }{noformat}
> In the above examole, socketAddressFamily to IPv6 makes sure that the
> connection be made on the IPv6 interface.
>
> The commit 6f56e289bec0db4a1de257883dc456a502c42fe7 removed all code to
> relating protocol family so the code does not enforce this anymore.
>
> Add back code to enforce this restriction.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1145) Edge Router - Implement address proxy component
[ https://issues.apache.org/jira/browse/DISPATCH-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16647951#comment-16647951 ] ASF subversion and git services commented on DISPATCH-1145: --- Commit 99d0377f0866c5355150864cffcb1daed350ab07 in qpid-dispatch's branch refs/heads/master from [~tr...@redhat.com] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=99d0377 ] DISPATCH-1145 - Implemented the addr_proxy component of the edge router. Responsibilities 1 and 2 are complete. > Edge Router - Implement address proxy component > --- > > Key: DISPATCH-1145 > URL: https://issues.apache.org/jira/browse/DISPATCH-1145 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Router Node >Reporter: Ted Ross >Assignee: Ted Ross >Priority: Major > Fix For: 1.5.0 > > > The Address Proxy is a component of the Edge Router module. It runs only on > an edge router. It has two main responsibilities: > Address Proxy has three main responsibilities: > # When an uplink becomes active, the "_uplink" address is properly linked to > an outgoing anonymous link on the active uplink connection. > # When an uplink becomes active, an incoming link is established over the > uplink connection that is used to transfer deliveries to topological > (dynamic) addresses on the edge router. > # Ensure that if there is an active uplink, that uplink should have one > incoming link for every address for which there is at least one local > consumer. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-2) [IGNORE ME] Subversion & Git to JIRA integration test
[ https://issues.apache.org/jira/browse/QPIDJMS-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16647946#comment-16647946 ] ASF subversion and git services commented on QPIDJMS-2: --- Commit 21f791a7deae7fe8d122130180cb3f36b4b02218 in qpid-jms's branch refs/heads/master from [~gemmellr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=21f791a ] QPIDJMS-2: commit for testing git to JIRA comment bot, ignore. > [IGNORE ME] Subversion & Git to JIRA integration test > -- > > Key: QPIDJMS-2 > URL: https://issues.apache.org/jira/browse/QPIDJMS-2 > Project: Qpid JMS > Issue Type: Task >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > > JIRA for testing gitsvn2jira integration, as with QPID-4891 and PROTON-321 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1145) Edge Router - Implement address proxy component
[ https://issues.apache.org/jira/browse/DISPATCH-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-1145: --- Description: The Address Proxy is a component of the Edge Router module. It runs only on an edge router. It has two main responsibilities: Address Proxy has three main responsibilities: # When an uplink becomes active, the "_uplink" address is properly linked to an outgoing anonymous link on the active uplink connection. # When an uplink becomes active, an incoming link is established over the uplink connection that is used to transfer deliveries to topological (dynamic) addresses on the edge router. # Ensure that if there is an active uplink, that uplink should have one incoming link for every address for which there is at least one local consumer. was: The Address Proxy is a component of the Edge Router module. It runs only on an edge router. It has two main responsibilities: # Ensure that if there is an active uplink, that uplink should have one incoming link for every address for which there is at least one local consumer. # When an uplink becomes active, the "_uplink" address is properly linked to the active uplink. > Edge Router - Implement address proxy component > --- > > Key: DISPATCH-1145 > URL: https://issues.apache.org/jira/browse/DISPATCH-1145 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Router Node >Reporter: Ted Ross >Assignee: Ted Ross >Priority: Major > Fix For: 1.5.0 > > > The Address Proxy is a component of the Edge Router module. It runs only on > an edge router. It has two main responsibilities: > Address Proxy has three main responsibilities: > # When an uplink becomes active, the "_uplink" address is properly linked to > an outgoing anonymous link on the active uplink connection. > # When an uplink becomes active, an incoming link is established over the > uplink connection that is used to transfer deliveries to topological > (dynamic) addresses on the edge router. > # Ensure that if there is an active uplink, that uplink should have one > incoming link for every address for which there is at least one local > consumer. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1145) Edge Router - Implement address proxy component
Ted Ross created DISPATCH-1145: -- Summary: Edge Router - Implement address proxy component Key: DISPATCH-1145 URL: https://issues.apache.org/jira/browse/DISPATCH-1145 Project: Qpid Dispatch Issue Type: New Feature Components: Router Node Reporter: Ted Ross Assignee: Ted Ross Fix For: 1.5.0 The Address Proxy is a component of the Edge Router module. It runs only on an edge router. It has two main responsibilities: # Ensure that if there is an active uplink, that uplink should have one incoming link for every address for which there is at least one local consumer. # When an uplink becomes active, the "_uplink" address is properly linked to the active uplink. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1140) tests for message priority
[ https://issues.apache.org/jira/browse/DISPATCH-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] michael goulish resolved DISPATCH-1140. --- Resolution: Duplicate Sorry – I should have just included this with DISPATCH-1139. When I PR that one, it will have a test that looks at both message and address priority. > tests for message priority > -- > > Key: DISPATCH-1140 > URL: https://issues.apache.org/jira/browse/DISPATCH-1140 > Project: Qpid Dispatch > Issue Type: New Feature >Reporter: michael goulish >Assignee: michael goulish >Priority: Major > > The message priority code recently checked in ( in DISPATCH-1096 ) should > have at least the following two tests: > > # Make a two-router network, A and B. Send messages from A to B, confirm > that they arrive, then kill and restart B and send and confirm more messages. > Do this test once with B connecting to A, and once with A connecting to B. > # Two-router network again. Send some messages from A to B (i.e. sender > attached to A, rcvr to B) – sending at least one message of each priority. > ( 0 - 9, inclusive ). Send management commands to A to see how many outgoing > inter-router links had message traffic go over them. The number should be 10. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
