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
[
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 deadl
[
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
[
https://issues.apache.org/jira/browse/DISPATCH-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17419066#comment-17419066
]
michael goulish commented on DISPATCH-2252:
---
...And if I see along the way anything
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 p
[
https://issues.apache.org/jira/browse/DISPATCH-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17357425#comment-17357425
]
michael goulish commented on DISPATCH-1956:
---
I meant to close my *PR*. Cripes
[
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
[
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: logg
[
https://issues.apache.org/jira/browse/DISPATCH-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17357401#comment-17357401
]
michael goulish commented on DISPATCH-1956:
---
Hold on – I think I have a much better solution
[
https://issues.apache.org/jira/browse/DISPATCH-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17356529#comment-17356529
]
michael goulish commented on DISPATCH-1956:
---
This might be an improvement in code logic
[
https://issues.apache.org/jira/browse/DISPATCH-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17350564#comment-17350564
]
michael goulish commented on DISPATCH-1956:
---
Using Ken's reproducer, I cannot see exactly
[
https://issues.apache.org/jira/browse/DISPATCH-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17347716#comment-17347716
]
michael goulish commented on DISPATCH-1956:
---
Thanks, Ken, that works!
I was commenting out
[
https://issues.apache.org/jira/browse/DISPATCH-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17347377#comment-17347377
]
michael goulish commented on DISPATCH-1956:
---
I will try the QE technique, and something I
[
https://issues.apache.org/jira/browse/DISPATCH-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17347365#comment-17347365
]
michael goulish commented on DISPATCH-1956:
---
I am trying to restore my 'mgoulish' RH account
[
https://issues.apache.org/jira/browse/DISPATCH-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17347330#comment-17347330
]
michael goulish commented on DISPATCH-1956:
---
As of recent code on master, this is gone
[
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
[
https://issues.apache.org/jira/browse/DISPATCH-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17334743#comment-17334743
]
michael goulish commented on DISPATCH-2088:
---
Here you go!
(gdb) thread apply all bt
[
https://issues.apache.org/jira/browse/DISPATCH-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17334707#comment-17334707
]
michael goulish commented on DISPATCH-2088:
---
I cannot repro with Debug build.
400
[
https://issues.apache.org/jira/browse/DISPATCH-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17334451#comment-17334451
]
michael goulish commented on DISPATCH-2088:
---
I'm afraid only the last few lines have
[
https://issues.apache.org/jira/browse/DISPATCH-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1780#comment-1780
]
michael goulish commented on DISPATCH-2088:
---
Apparently it helps if you let the code cool
[
https://issues.apache.org/jira/browse/DISPATCH-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333284#comment-17333284
]
michael goulish commented on DISPATCH-2088:
---
*The iperf commands I used in the test
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
[
https://issues.apache.org/jira/browse/PROTON-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313307#comment-17313307
]
michael goulish edited comment on PROTON-2362 at 4/1/21, 4:49 PM:
--
OK
[
https://issues.apache.org/jira/browse/PROTON-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313307#comment-17313307
]
michael goulish edited comment on PROTON-2362 at 4/1/21, 4:48 PM:
--
OK
[
https://issues.apache.org/jira/browse/PROTON-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313307#comment-17313307
]
michael goulish commented on PROTON-2362:
-
OK, here's the whole list.
64 threads, 30 seconds
[
https://issues.apache.org/jira/browse/PROTON-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313151#comment-17313151
]
michael goulish commented on PROTON-2362:
-
I am running batches of 50 threaderciser tests, 64
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
[
https://issues.apache.org/jira/browse/DISPATCH-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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=17306496#comment-17306496
]
michael goulish commented on DISPATCH-2014:
---
When I used 64 dispatch worker threads and hit
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
+1
It has now completed 120 million messages without problem in the following
test:
* single router
* 250 receivers, 250 senders, 250 addresses
* senders in 5 groups, each throttled to send messages at different
intervals: {13, 17, 19, 23, 29} msec.
* router has *64 worker threads*
g streaming messages it wasn't
> clear to me. I'll update the JIRA with your recommendations, thanks!
>
>
> On Sat, Apr 4, 2020 at 12:32 PM Michael Goulish
> wrote:
>
>> Ken --
>>
>> I have a proactor client in Mercury and it handles timeouts differently
>>
Ken --
I have a proactor client in Mercury and it handles timeouts differently
than your code.
I don't remember now exactly why this was necessary, but I do vaguely
recall weird
behavior before I fixed it, at aconway's suggestion.
I think that, in the PN_PROACTOR_TIMEOUT case in the event
*+ 1*
I did a 2-million link test, i.e. 1 million in, 1 million out, spread
evenly over 100 connections -- on a single router, coming from a single
client -- using Gordon's python client made for this purpose -- and nothing
blew up or melted down. And it did not use an exorbitant amount of memory
+1
Two large-scale tests done, with no trouble.
Test 1
5 routers linear network (A...E)
500 senders on router A, 500 receivers on router E
1 unique address per client-pair
distribution : closest
senders throttled to 10 messages per second
non-pre-settled, 100 byte payload
May I vote DELAY?
Could you please not conclude this vote until you receive my vote?
I am seeing something that I don't understand with a large multicast test,
and I would like to cast my vote only after I have a chance to talk to Ken
Giusti about it.
Unfortunately I am out today seeing a doctor
[
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 sec
11, 2019 at 11:58 AM Michael Goulish
> wrote:
>
> > Of course I will not change my vote based on a suggestion ( from me and
> > Gordon ) that the failure I am seeing might be caused by a missing
> > package.
> >
> > What I will do is start looking into thi
Of course I will not change my vote based on a suggestion ( from me and
Gordon ) that the failure I am seeing might be caused by a missing
package.
What I will do is start looking into this to see if that is indeed the case.
And then we will make a change that detects and warns about that case.
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
[
https://issues.apache.org/jira/browse/DISPATCH-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16809913#comment-16809913
]
michael goulish commented on DISPATCH-1309:
---
Chuck –
Are you sure you mean "5672&quo
[
https://issues.apache.org/jira/browse/DISPATCH-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16809806#comment-16809806
]
michael goulish commented on DISPATCH-1309:
---
Yee hah!
Chuck's comment reminded me – I
[
https://issues.apache.org/jira/browse/DISPATCH-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16808055#comment-16808055
]
michael goulish commented on DISPATCH-1309:
---
And since the above comment I have not been
[
https://issues.apache.org/jira/browse/DISPATCH-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16808007#comment-16808007
]
michael goulish commented on DISPATCH-1309:
---
OK! I thought Mercury might help reproduce
[
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 segfa
[
https://issues.apache.org/jira/browse/DISPATCH-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798961#comment-16798961
]
michael goulish commented on DISPATCH-1280:
---
LWS developer pushed patch. I got through 100
[
https://issues.apache.org/jira/browse/DISPATCH-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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=16798302#comment-16798302
]
michael goulish commented on DISPATCH-1280:
---
Well, kinda.
I saw one crash using LWS latest
[
https://issues.apache.org/jira/browse/DISPATCH-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16797619#comment-16797619
]
michael goulish commented on DISPATCH-1280:
---
reproduced with simple example.
What I did
[
https://issues.apache.org/jira/browse/DISPATCH-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16797575#comment-16797575
]
michael goulish commented on DISPATCH-1280:
---
Looked at closed issues back to release date
[
https://issues.apache.org/jira/browse/DISPATCH-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16797391#comment-16797391
]
michael goulish commented on DISPATCH-1280:
---
It sounds like this happens all the time
[
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 cau
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=16655668#comment-16655668
]
michael goulish commented on DISPATCH-959:
--
This is not a bug, it's a new feature.
> R
[
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 addres
[
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
[
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
[
https://issues.apache.org/jira/browse/PROTON-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16640115#comment-16640115
]
michael goulish commented on PROTON-1949:
-
Nolo contendere.
We have decided that it is better
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
[
https://issues.apache.org/jira/browse/DISPATCH-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638896#comment-16638896
]
michael goulish commented on DISPATCH-1126:
---
pending fix for this in PR 384
> ERROR Atte
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
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-rou
[
https://issues.apache.org/jira/browse/DISPATCH-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16621117#comment-16621117
]
michael goulish commented on DISPATCH-1096:
---
The priority code should make messages default
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
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
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
[
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
[
https://issues.apache.org/jira/browse/PROTON-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15926821#comment-15926821
]
michael goulish commented on PROTON-1408:
-
I can now reproduce the problem 100%, and after just
[
https://issues.apache.org/jira/browse/PROTON-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890860#comment-15890860
]
michael goulish commented on PROTON-1408:
-
Using proton and dispatch code from 17 Feb 2017, I am
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
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=15321466#comment-15321466
]
michael goulish commented on DISPATCH-369:
--
...and without anything interesting showing up
[
https://issues.apache.org/jira/browse/DISPATCH-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15321448#comment-15321448
]
michael goulish commented on DISPATCH-369:
--
I rebuilt dispatch without the memory pooling
[
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
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
>
> In other words, are we trying for a fixed frequency or an "at least"
> delay?
>
What I need this feature for is to be able to send messages at a fixed
frequency.
-
To unsubscribe, e-mail:
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=15264603#comment-15264603
]
michael goulish commented on PROTON-992:
Dispatch is not yet immune to this issue.
Also, I think
[
https://issues.apache.org/jira/browse/DISPATCH-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15260774#comment-15260774
]
michael goulish commented on DISPATCH-296:
--
I have also seen this crash, with same frequency
I think this is confusing, because the link origins
seem a little router-centric, while the link message
directions are client-centric.
Why not make everything rclearly router-centric, in
this context. Like this:
links made by clients are "client links" (or "client-originated links")
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
server init and client init fns are
called exactly once.
Thanks,
michael goulish
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
with Java tests running.
Thanks,
michael goulish
., michael goulish wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36992/
---
(Updated Aug. 5, 2015, 9:52 a.m.)
Review
We should move the code to git,
Any way you look at it.
It's the best code control system
So new and shiny that it glistens.
We should move it any day.
We should move it right away.
But one fact here we should construe.
When I say We, I'm meaning You.
:-)
[X] Yes - move the qpid-dispatch repo
+1
It does clear like the development universe has decided that git
is the preferred technology. Then it's worth it just so that developers
on this project will not have to keep two different source code control
systems in their heads.
Also, I do _not_ think that git is just a fashion. It's a
/protocol.h.py bbc0dfe
proton-c/src/transport/transport.c 6abf862
tests/python/proton_tests/engine.py 7a1d539
Diff: https://reviews.apache.org/r/36992/diff/
Testing
---
ctest -VV with Java tests running.
Thanks,
michael goulish
/35798/diff/
Testing (updated)
---
ctest -VV --- C and Java
Please note: This Jira changes the public interface in that it adds #define
PN_OK 0 to the list of possible error return values in error.h
Thanks,
michael goulish
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36546/#review91888
---
On July 16, 2015, 1:52 p.m., michael goulish wrote
*/
#define AMQP_OPEN_MAX_FRAME_SIZE_DEFAULT 4294967295
#define AMQP_OPEN_CHANNEL_MAX_DEFAULT 65535
#define AMQP_BEGIN_HANDLE_MAX_DEFAULT 4294967295
#define AMQP_SOURCE_TIMEOUT_DEFAULT 0
#define AMQP_TARGET_TIMEOUT_DEFAULT 0
Thanks,
michael goulish
: This Jira changes the public interface in that it adds #define
PN_OK 0 to the list of possible error return values in error.h
Thanks,
michael goulish
1 - 100 of 189 matches
Mail list logo
