michael goulish created DISPATCH-2255:
-
Summary: Investigate enable_mask for removal of malloc
Key: DISPATCH-2255
URL: https://issues.apache.org/jira/browse/DISPATCH-2255
Project: Qpid Dispatch
[
https://issues.apache.org/jira/browse/DISPATCH-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish updated DISPATCH-1956:
--
Summary: log.c rewrite to reduce locking scope (was: Potential deadlock:
logging lo
[
https://issues.apache.org/jira/browse/DISPATCH-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish reassigned DISPATCH-1956:
-
Assignee: michael goulish (was: Michael Goulish)
> Potential deadlock: loggi
[
https://issues.apache.org/jira/browse/DISPATCH-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish closed DISPATCH-2173.
-
Resolution: Won't Fix
It has been pointed out to me that a 30-mesh is not very realist
[
https://issues.apache.org/jira/browse/DISPATCH-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17419066#comment-17419066
]
michael goulish commented on DISPATCH-2252:
---
...And if I see along the way a
michael goulish created DISPATCH-2252:
-
Summary: Document router shutdown process
Key: DISPATCH-2252
URL: https://issues.apache.org/jira/browse/DISPATCH-2252
Project: Qpid Dispatch
Issue
michael goulish created DISPATCH-2173:
-
Summary: 30-Mesh Behaving Badly
Key: DISPATCH-2173
URL: https://issues.apache.org/jira/browse/DISPATCH-2173
Project: Qpid Dispatch
Issue Type: Bug
[
https://issues.apache.org/jira/browse/DISPATCH-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish reassigned DISPATCH-2122:
-
Assignee: michael goulish (was: Ken Giusti)
> Data race on alloc pool descri
[
https://issues.apache.org/jira/browse/DISPATCH-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17357425#comment-17357425
]
michael goulish commented on DISPATCH-1956:
---
I meant to close my *PR*. Crip
[
https://issues.apache.org/jira/browse/DISPATCH-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish closed DISPATCH-1956.
-
Resolution: Fixed
Closing this one in favor of a better one coming shortly.
> Potenti
[
https://issues.apache.org/jira/browse/DISPATCH-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish reopened DISPATCH-1956:
---
No, wait. I didn't mean it to say 'fixed'. Dang.
> Potential deadlock: logging lock
[
https://issues.apache.org/jira/browse/DISPATCH-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17357401#comment-17357401
]
michael goulish commented on DISPATCH-1956:
---
Hold on – I think I have a much
[
https://issues.apache.org/jira/browse/DISPATCH-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17356529#comment-17356529
]
michael goulish commented on DISPATCH-1956:
---
This might be an improvement in
[
https://issues.apache.org/jira/browse/DISPATCH-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17350564#comment-17350564
]
michael goulish commented on DISPATCH-1956:
---
Using Ken's reproducer, I canno
[
https://issues.apache.org/jira/browse/DISPATCH-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17347716#comment-17347716
]
michael goulish commented on DISPATCH-1956:
---
Thanks, Ken, that works!
I was
[
https://issues.apache.org/jira/browse/DISPATCH-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17347377#comment-17347377
]
michael goulish commented on DISPATCH-1956:
---
I will try the QE technique, an
[
https://issues.apache.org/jira/browse/DISPATCH-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17347365#comment-17347365
]
michael goulish commented on DISPATCH-1956:
---
I am trying to restore my 'mgou
[
https://issues.apache.org/jira/browse/DISPATCH-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17347330#comment-17347330
]
michael goulish commented on DISPATCH-1956:
---
As of recent code on master, th
[
https://issues.apache.org/jira/browse/DISPATCH-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish closed DISPATCH-2088.
-
Resolution: Fixed
Fixed by Chuck's PR:
https://github.com/apache/qpid-dispatch/pull/1
[
https://issues.apache.org/jira/browse/DISPATCH-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17334743#comment-17334743
]
michael goulish commented on DISPATCH-2088:
---
Here you go!
(gdb) thre
[
https://issues.apache.org/jira/browse/DISPATCH-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17334707#comment-17334707
]
michael goulish commented on DISPATCH-2088:
---
I cannot repro with Debug bu
[
https://issues.apache.org/jira/browse/DISPATCH-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17334451#comment-17334451
]
michael goulish commented on DISPATCH-2088:
---
I'm afraid only the last few li
[
https://issues.apache.org/jira/browse/DISPATCH-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1780#comment-1780
]
michael goulish commented on DISPATCH-2088:
---
Apparently it helps if you let
[
https://issues.apache.org/jira/browse/DISPATCH-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17333284#comment-17333284
]
michael goulish commented on DISPATCH-2088:
---
*The iperf commands I used in t
michael goulish created DISPATCH-2088:
-
Summary: SEGV in qd_buffer_dec_fanout
Key: DISPATCH-2088
URL: https://issues.apache.org/jira/browse/DISPATCH-2088
Project: Qpid Dispatch
Issue Type
[
https://issues.apache.org/jira/browse/PROTON-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313307#comment-17313307
]
michael goulish edited comment on PROTON-2362 at 4/1/21, 4:49 PM:
[
https://issues.apache.org/jira/browse/PROTON-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313307#comment-17313307
]
michael goulish edited comment on PROTON-2362 at 4/1/21, 4:48 PM:
[
https://issues.apache.org/jira/browse/PROTON-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313307#comment-17313307
]
michael goulish commented on PROTON-2362:
-
OK, here's the whole list.
64 thread
[
https://issues.apache.org/jira/browse/PROTON-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313151#comment-17313151
]
michael goulish commented on PROTON-2362:
-
I am running batches of 50 threaderci
michael goulish created PROTON-2362:
---
Summary: c-threaderciser timed out on 32-core machine.
Key: PROTON-2362
URL: https://issues.apache.org/jira/browse/PROTON-2362
Project: Qpid Proton
Iss
[
https://issues.apache.org/jira/browse/DISPATCH-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17312627#comment-17312627
]
michael goulish commented on DISPATCH-2014:
---
I just ran Proton's ctest suite
[
https://issues.apache.org/jira/browse/DISPATCH-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17306496#comment-17306496
]
michael goulish commented on DISPATCH-2014:
---
When I used 64 dispatch worker
michael goulish created DISPATCH-2014:
-
Summary: Router TCP Adapter crash with high thread count and load
Key: DISPATCH-2014
URL: https://issues.apache.org/jira/browse/DISPATCH-2014
Project: Qpid D
[
https://issues.apache.org/jira/browse/DISPATCH-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish reassigned DISPATCH-1368:
-
Assignee: michael goulish
> Link (address) priority is ignored by the second
michael goulish created PROTON-2046:
---
Summary: pn_connection_set_container should check for null or
empty string
Key: PROTON-2046
URL: https://issues.apache.org/jira/browse/PROTON-2046
Project: Qpid
[
https://issues.apache.org/jira/browse/DISPATCH-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16809913#comment-16809913
]
michael goulish commented on DISPATCH-1309:
---
Chuck –
Are you sure you mean
[
https://issues.apache.org/jira/browse/DISPATCH-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16809806#comment-16809806
]
michael goulish commented on DISPATCH-1309:
---
Yee hah!
Chuck's comment remin
[
https://issues.apache.org/jira/browse/DISPATCH-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808055#comment-16808055
]
michael goulish commented on DISPATCH-1309:
---
And since the above comment I h
[
https://issues.apache.org/jira/browse/DISPATCH-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808007#comment-16808007
]
michael goulish commented on DISPATCH-1309:
---
OK! I thought Mercury might hel
[
https://issues.apache.org/jira/browse/DISPATCH-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish closed DISPATCH-1280.
-
Resolution: Fixed
> http against https enabled listener causes segfault
>
[
https://issues.apache.org/jira/browse/DISPATCH-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798961#comment-16798961
]
michael goulish commented on DISPATCH-1280:
---
LWS developer pushed patch. I g
[
https://issues.apache.org/jira/browse/DISPATCH-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798302#comment-16798302
]
michael goulish edited comment on DISPATCH-1280 at 3/21/19 5:53 PM:
[
https://issues.apache.org/jira/browse/DISPATCH-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798302#comment-16798302
]
michael goulish commented on DISPATCH-1280:
---
Well, kinda.
I saw one crash u
[
https://issues.apache.org/jira/browse/DISPATCH-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797619#comment-16797619
]
michael goulish commented on DISPATCH-1280:
---
reproduced with simple example.
[
https://issues.apache.org/jira/browse/DISPATCH-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797575#comment-16797575
]
michael goulish commented on DISPATCH-1280:
---
Looked at closed issues back to
[
https://issues.apache.org/jira/browse/DISPATCH-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797391#comment-16797391
]
michael goulish commented on DISPATCH-1280:
---
It sounds like this happens all
[
https://issues.apache.org/jira/browse/DISPATCH-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish reassigned DISPATCH-1280:
-
Assignee: michael goulish
> http against https enabled listener causes segfau
michael goulish created DISPATCH-1215:
-
Summary: several memory leaks in edge-router soak test
Key: DISPATCH-1215
URL: https://issues.apache.org/jira/browse/DISPATCH-1215
Project: Qpid Dispatch
michael goulish created DISPATCH-1155:
-
Summary: dueling httpRootDirs
Key: DISPATCH-1155
URL: https://issues.apache.org/jira/browse/DISPATCH-1155
Project: Qpid Dispatch
Issue Type: Bug
[
https://issues.apache.org/jira/browse/DISPATCH-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16655668#comment-16655668
]
michael goulish commented on DISPATCH-959:
--
This is not a bug, it's a new feat
[
https://issues.apache.org/jira/browse/DISPATCH-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish closed DISPATCH-1139.
-
Resolution: Implemented
> support prioritized addresses
>
[
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.
michael goulish created DISPATCH-1140:
-
Summary: tests for message priority
Key: DISPATCH-1140
URL: https://issues.apache.org/jira/browse/DISPATCH-1140
Project: Qpid Dispatch
Issue Type:
[
https://issues.apache.org/jira/browse/DISPATCH-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish resolved DISPATCH-1096.
---
Resolution: Implemented
I will open a separate Jira for tests that this code needs
[
https://issues.apache.org/jira/browse/PROTON-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish closed PROTON-1949.
---
Resolution: Not A Problem
We have found a nice workaround for this–probably better, actually
[
https://issues.apache.org/jira/browse/PROTON-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16640115#comment-16640115
]
michael goulish commented on PROTON-1949:
-
Nolo contendere.
We have decided tha
michael goulish created DISPATCH-1139:
-
Summary: support prioritized addresses
Key: DISPATCH-1139
URL: https://issues.apache.org/jira/browse/DISPATCH-1139
Project: Qpid Dispatch
Issue Typ
[
https://issues.apache.org/jira/browse/DISPATCH-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16638896#comment-16638896
]
michael goulish commented on DISPATCH-1126:
---
pending fix for this in PR 384
michael goulish created PROTON-1949:
---
Summary: no message header if priority == default
Key: PROTON-1949
URL: https://issues.apache.org/jira/browse/PROTON-1949
Project: Qpid Proton
Issue Ty
michael goulish created DISPATCH-1135:
-
Summary: Router A leaks memory when router B killed and restarted.
Key: DISPATCH-1135
URL: https://issues.apache.org/jira/browse/DISPATCH-1135
Project: Qpid
[
https://issues.apache.org/jira/browse/DISPATCH-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish reassigned DISPATCH-1126:
-
Assignee: michael goulish
> ERROR Attempt to attach too many inter-router lin
[
https://issues.apache.org/jira/browse/DISPATCH-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621117#comment-16621117
]
michael goulish commented on DISPATCH-1096:
---
The priority code should make m
michael goulish created DISPATCH-1096:
-
Summary: support AMQP prioritized messages
Key: DISPATCH-1096
URL: https://issues.apache.org/jira/browse/DISPATCH-1096
Project: Qpid Dispatch
Issue
michael goulish created DISPATCH-873:
Summary: new routes calculated wrongly after connector deletion
Key: DISPATCH-873
URL: https://issues.apache.org/jira/browse/DISPATCH-873
Project: Qpid Dispatc
michael goulish created DISPATCH-870:
Summary: connection improperly reopened from closed connector
Key: DISPATCH-870
URL: https://issues.apache.org/jira/browse/DISPATCH-870
Project: Qpid Dispatch
[
https://issues.apache.org/jira/browse/PROTON-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish closed PROTON-1408.
---
Resolution: Fixed
Fix Version/s: 0.18.0
Fixed with checkin d22f124b0534983f6557850e48f
[
https://issues.apache.org/jira/browse/PROTON-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish updated PROTON-1408:
Attachment: jira_proton_1408_reproducer.tar.gz
Everything you need in a tidy little package
[
https://issues.apache.org/jira/browse/PROTON-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926821#comment-15926821
]
michael goulish commented on PROTON-1408:
-
I can now reproduce the problem 100%,
[
https://issues.apache.org/jira/browse/PROTON-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890860#comment-15890860
]
michael goulish commented on PROTON-1408:
-
Using proton and dispatch code from 17
michael goulish created PROTON-1408:
---
Summary: long-lived connections suffer large performance hit after
many messages
Key: PROTON-1408
URL: https://issues.apache.org/jira/browse/PROTON-1408
Project
[
https://issues.apache.org/jira/browse/DISPATCH-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish closed DISPATCH-113.
Resolution: Fixed
> expose NodeTracker::last_topology_change in management
>
michael goulish created DISPATCH-372:
Summary: qdstat should have a timeout command line argument
Key: DISPATCH-372
URL: https://issues.apache.org/jira/browse/DISPATCH-372
Project: Qpid Dispatch
[
https://issues.apache.org/jira/browse/DISPATCH-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321466#comment-15321466
]
michael goulish commented on DISPATCH-369:
--
...and without anything interesting
[
https://issues.apache.org/jira/browse/DISPATCH-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321448#comment-15321448
]
michael goulish commented on DISPATCH-369:
--
I rebuilt dispatch without the memo
[
https://issues.apache.org/jira/browse/DISPATCH-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish updated DISPATCH-369:
-
Attachment: n_senders_vs_MEM_three_trials.jpg
Results of repeating each test three times
michael goulish created DISPATCH-369:
Summary: investigate excursions in memory usage
Key: DISPATCH-369
URL: https://issues.apache.org/jira/browse/DISPATCH-369
Project: Qpid Dispatch
Issu
michael goulish created DISPATCH-344:
Summary: memory growth after repeated calls from qdstat -m
Key: DISPATCH-344
URL: https://issues.apache.org/jira/browse/DISPATCH-344
Project: Qpid Dispatch
[
https://issues.apache.org/jira/browse/PROTON-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15264603#comment-15264603
]
michael goulish commented on PROTON-992:
Dispatch is not yet immune to this issue.
[
https://issues.apache.org/jira/browse/DISPATCH-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15260774#comment-15260774
]
michael goulish commented on DISPATCH-296:
--
I have also seen this crash, with s
michael goulish created DISPATCH-210:
Summary: try an epoll-based driver ...
Key: DISPATCH-210
URL: https://issues.apache.org/jira/browse/DISPATCH-210
Project: Qpid Dispatch
Issue Type: I
michael goulish created DISPATCH-157:
Summary: add sasl tests to dispatch unit tests
Key: DISPATCH-157
URL: https://issues.apache.org/jira/browse/DISPATCH-157
Project: Qpid Dispatch
Issue
michael goulish created DISPATCH-140:
Summary: adapt to proton changes for large number of link-handles
Key: DISPATCH-140
URL: https://issues.apache.org/jira/browse/DISPATCH-140
Project: Qpid Dispa
[
https://issues.apache.org/jira/browse/DISPATCH-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish reassigned DISPATCH-139:
Assignee: michael goulish
> adapt to proton changes to avoid crashes under high s
michael goulish created DISPATCH-139:
Summary: adapt to proton changes to avoid crashes under high
session count
Key: DISPATCH-139
URL: https://issues.apache.org/jira/browse/DISPATCH-139
Project:
michael goulish created DISPATCH-118:
Summary: crash due to race on proton-c/src/error.c error
structures.
Key: DISPATCH-118
URL: https://issues.apache.org/jira/browse/DISPATCH-118
Project: Qpid
[
https://issues.apache.org/jira/browse/DISPATCH-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334815#comment-14334815
]
michael goulish commented on DISPATCH-117:
--
This checkin also fixed a rare cras
michael goulish created DISPATCH-113:
Summary: expose NodeTracker::last_topology_change in management
Key: DISPATCH-113
URL: https://issues.apache.org/jira/browse/DISPATCH-113
Project: Qpid Dispat
[
https://issues.apache.org/jira/browse/DISPATCH-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish resolved DISPATCH-106.
--
Resolution: Fixed
Committed revision 1657604.
> pn link corruption after router rest
[
https://issues.apache.org/jira/browse/DISPATCH-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303225#comment-14303225
]
michael goulish commented on DISPATCH-106:
--
In server.c, the function thread_ru
[
https://issues.apache.org/jira/browse/DISPATCH-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish updated DISPATCH-106:
-
Description:
With the standard 6-node demo network, (A-D, X, Y) after killing and
res
michael goulish created DISPATCH-106:
Summary: pn link corruption after router restart
Key: DISPATCH-106
URL: https://issues.apache.org/jira/browse/DISPATCH-106
Project: Qpid Dispatch
Iss
[
https://issues.apache.org/jira/browse/DISPATCH-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish resolved DISPATCH-64.
-
Resolution: Fixed
this was traced to a problem in proton, which rafi fixed.
> slow or sp
[
https://issues.apache.org/jira/browse/DISPATCH-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073643#comment-14073643
]
michael goulish commented on DISPATCH-64:
-
Yes, RSS is increasing much more smoot
michael goulish created DISPATCH-64:
---
Summary: slow or sporadic memory leak
Key: DISPATCH-64
URL: https://issues.apache.org/jira/browse/DISPATCH-64
Project: Qpid Dispatch
Issue Type: Bug
[
https://issues.apache.org/jira/browse/QPID-5815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish resolved QPID-5815.
---
Resolution: Fixed
fixed by commit 1612838,
committed by myself
on behalf of Irina Boverman.
[
https://issues.apache.org/jira/browse/QPID-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish closed QPID-5910.
-
Resolution: Fixed
fixed in rev 1612559
> Throughput regression relative to 0.14
> ---
michael goulish created QPID-5910:
-
Summary: Throughput regression relative to 0.14
Key: QPID-5910
URL: https://issues.apache.org/jira/browse/QPID-5910
Project: Qpid
Issue Type: Bug
Affec
[
https://issues.apache.org/jira/browse/QPID-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael goulish closed QPID-5734.
-
Resolution: Fixed
This is superseded by QPID-5737, which has been fixed.
> message loss in qpid c
[
https://issues.apache.org/jira/browse/QPID-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984606#comment-13984606
]
michael goulish commented on QPID-5734:
---
The receivers are proton messenger based.
I
michael goulish created QPID-5734:
-
Summary: message loss in qpid client
Key: QPID-5734
URL: https://issues.apache.org/jira/browse/QPID-5734
Project: Qpid
Issue Type: Bug
Reporter
1 - 100 of 121 matches
Mail list logo
