Yes the tick function is used solely for heartbeat processing. Each peer
sets or declines to set its own heartbeat interval independently.
If you never call the tick function, you fail to send empty heartbeat
frames in time to the peer if required. You also fail to enforce the
presence of inbound
Hi Andrew,
It looks like your crash is in pni_process_tpwork which processes a linked
list of deliveries that have been modified and require wire (AMQP protocol)
frames sent to the peer to keep both sides of the connection in sync.
The actual call is made via a function pointer, which I don't
Hi Tom,
As a further note to whatever you have found so far...
The recommended route would be for you to retain your existing code
based on proton::container, and allow it to run with its own dedicated
thread (or threads) using its own epoll loop and let Proton manage the
sockets for the AMQP
There is some work starting to simplify platform dependencies in the
Proton C code base starting with switching to OpenSSL as the TLS
provider on Windows away from the native Schannel implementation.
The reason for this work starting now is twofold. First, the adoption
and support for open
+1
Built and tested on Windows VS 2022
Fedora 37 clang build and test
Fedora 37 gcc build and test + quiver soak test
Cliff
On Wed, May 31, 2023 at 4:59 AM Robbie Gemmell
wrote:
> Hi folks,
>
> I have put together a first spin for a Qpid Proton 0.39.0 release,
> please give it a test out
+1
Built the source and ran the tests without any failures on RHEL8.
On Mon, Dec 5, 2022 at 1:50 PM Timothy Bish wrote:
> Hi folks,
>
> I have put together a release candidate for a 1.0.0-M7 Qpid
> proton-dotnet release,
> please give it a test out and vote accordingly.
>
> The source and
+1
Downloaded the M2 source tar and checked the sha512sum
Built an alpine based image using docker/Dockerfile
Ran the image and executed “bash ./docker/run-tests.sh” on the extracted M2
source archive.
All tests passed.
Cliff
On Mon, Jul 11, 2022 at 12:13 PM Timothy Bish wrote:
> Hi
it is worth trying again with the current backlog
> setting?
>
>
> On Thu, Jun 2, 2022 at 5:11 PM Cliff Jansen wrote:
>
> > Please try raising your fd limit too. Perhaps doubling it or more.
> >
> > I would also try running your proton::container with more th
Please try raising your fd limit too. Perhaps doubling it or more.
I would also try running your proton::container with more threads, say 4
and then 16, and see if that makes a difference. It shouldn’t if your
processing within Proton is as minimal as you describe. However, if there
is lengthy
I can reproduce the problem seen by Roddie with Python 3.10.2 on Fedora 35.
It fails in the same way with 0.36.0, so it is not a regression.
If I increase the sleep time in the fdlimit.py driver program, the failure
goes away. In my opinion, this is a flaky test that Python 3.10 triggers
more
+1
Built and tested with new TLS library.
Did basic soak test with Quiver and Qpid Dispatch 1.19 RC2: high message
throughput alternating with 250 simultaneous connections.
On Tue, Mar 15, 2022 at 10:34 AM Robbie Gemmell
wrote:
> Hi folks,
>
> I have put together another spin for a Qpid
+1
Built and ran tests, including the new TLS library and associated example.
Ran some quiver soak tests against the Dispatch router, including 1, 3, and
125 arrow pairs.
On Thu, Feb 24, 2022 at 8:17 AM Robbie Gemmell
wrote:
> Hi folks,
>
> I have put together a first spin for a Qpid Proton
I can reproduce. I also get failures for Proton 0.36 on the same system.
In my opinion it is not a regression and not a reason to fail this RC.
I will raise a Jira to get this resolved for the next release.
On Mon, Feb 28, 2022 at 10:29 AM Ken Giusti wrote:
> +- "?"
>
> Just want to rule
This is a brief introduction to a proposed new Proton-C support library to
provide generalized TLS functionality.
The existing Proton SSL/TLS functionality is tightly coupled to AMQP
connections and does not provide application access to the encrypted or
decrypted stream data. As a result, there
Hi Glen,
I believe you are mixing old and new methodologies.
NSS and certutil are unrelated to the Qpid Proton C++ library which uses
OpenSSL on Posix systems. The environment variables QPID_SSL_CERT_XXX are
not used for TLS configuration.
See the example at
+1
Built and ran tests on Centos 8 and Fedora 34.
Ran 4 hour Quiver soak against Qpid Dispatch (4 arrow pairs) all built with
this release candidate. Fedora 34.
Cliff
On Mon, Nov 1, 2021 at 6:13 AM Robbie Gemmell
wrote:
> Hi folks,
>
> I have put together a first spin for a Qpid Proton
>
> P.S.: I’m off for holiday’s from tomorrow. Could you reply to all in CC
> when reacting to this mail?
>
>
>
> Thanks again!
>
>
>
> With kind regards,
>
>
>
> *Jaap Wiggelinkhuizen*
>
>
>
> *Van:* Cliff Jansen
> *Verzonden:* vrijdag 16
This is not a known bug. Despite your providing a helpful detailed account,
I am unable to see the possibility of a second “earlier” deadline in the
life of an AMQP connection. Even being off by one.
Please raise a JIRA including any additional information you can think of.
Obviously a
+1
Ran some quiver soak tests with the C based arrow driver in various
configurations on a 24 core /48 thread system (CentOS 7.9):
- peer-to-peer
- qpid-dispatch and 3 high throughput arrow pairs
- qpid-dispatch and 125 “credit 1” low throughput pairs
On Fri, Jun 25, 2021 at 7:56 AM
+1
Various Quiver and connexorciser soak/performance tests with C test broker
and Qpid Dispatch.
Build and ctest checkout on centos6 (last time?), centos7, fedora32.
On Tue, Nov 17, 2020 at 4:33 AM Robbie Gemmell
wrote:
> Hi folks,
>
> I have put together another spin for a Qpid Proton
-1 see PROTON-2304.
Yes, a hang in my own main contribution to this release. I was minutes
away from a +1 when this showed up. Fix looking likely by end of my working
day.
On Mon, Nov 16, 2020 at 7:21 AM Robbie Gemmell
wrote:
> Hi folks,
>
> I have put together another spin for a Qpid Proton
There is nothing wrong with your current strategy. You could
alternatively create a new connection on the same proactor instance.
You can also reuse a connection with a new transport, for example by
calling pn_proactor_release_connection() when you get the
PN_TRANSPORT_CLOSED event and before
+1
- I ran an overnight soak test compiled with “Debug” to expose asserts
- I ran dispatch with clang and thread sanitizer
Orange you glad I didn’t say banana?
On Thu, May 7, 2020 at 9:06 AM Robbie Gemmell
wrote:
> Hi folks,
>
> I have put together a third spin for a Qpid Proton 0.31.0
-1
Party pooper again.
I have a hang on a soak test. Inconclusive debugging so far. Best guess is
connections are not cleaning up on some condition and file descriptors are
leaking, preventing any new accepts. Still looking.
On Fri, May 1, 2020 at 9:41 AM Robbie Gemmell
wrote:
> Hi folks,
>
>
-1
See PROTON-2203.
On Tue, Apr 28, 2020 at 6:42 AM Robbie Gemmell
wrote:
> On Tue, 28 Apr 2020 at 13:01, Robbie Gemmell
> wrote:
> >
> > Hi folks,
> >
> > I have put together a spin for a Qpid Proton 0.31.0 release, please
> > give it a test out and vote accordingly.
> >
> > The files can be
[
https://issues.apache.org/jira/browse/PROTON-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-2081.
--
Resolution: Fixed
Fix Version/s: proton-c-0.29.0
> Hang in Windows proactor dur
Cliff Jansen created PROTON-2081:
Summary: Hang in Windows proactor during connect
Key: PROTON-2081
URL: https://issues.apache.org/jira/browse/PROTON-2081
Project: Qpid Proton
Issue Type
ace it instead by a
> connection.work_queue().add() everything comes back to normal.
>
> I tried to think about what might be the source of the problem but i can't
> find any ideas yet...
>
> Best regards,
> Rabih
>
>
>
> On Fri, Apr 26, 2019 at 9:38 AM Cliff Janse
[
https://issues.apache.org/jira/browse/PROTON-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16830729#comment-16830729
]
Cliff Jansen commented on PROTON-2036:
--
Also add a clearer description that
proton
Cliff Jansen created PROTON-2036:
Summary: Additional C++ threading documentation
Key: PROTON-2036
URL: https://issues.apache.org/jira/browse/PROTON-2036
Project: Qpid Proton
Issue Type
on the ref counting.
> This is why we proposed the atomic types in C11.
>
> Best regards.
> Jeremy and Rabih
>
>
> On Tue, Apr 23, 2019 at 9:28 AM Cliff Jansen wrote:
>>
>> I am of the same opinion as Gordon that fixing the counting (to be atomic)
>> will only ad
I am of the same opinion as Gordon that fixing the counting (to be atomic)
will only address the current symptom without preventing other races that
will present themselves later or on other hardware architectures.
Having two threads participating in Proton object reference counting is
[
https://issues.apache.org/jira/browse/PROTON-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-2027.
--
Resolution: Fixed
Test also works now on CentOS 6
> Proactor connection wake after mem
[
https://issues.apache.org/jira/browse/PROTON-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen reopened PROTON-2027:
--
Use make_work for more platform coverage.
> Proactor connection wake after memory freed w
[
https://issues.apache.org/jira/browse/PROTON-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-2027.
--
Resolution: Fixed
Fix Version/s: proton-c-0.28.0
> Proactor connection wake af
[
https://issues.apache.org/jira/browse/PROTON-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen updated PROTON-2027:
-
Affects Version/s: (was: proton-j-0.32.0)
proton-c-0.27.0
> Proac
Cliff Jansen created PROTON-2027:
Summary: Proactor connection wake after memory freed when using
pn_proactor_disconnect().
Key: PROTON-2027
URL: https://issues.apache.org/jira/browse/PROTON-2027
I can reproduce and it looks more like a proactor problem than the C++
container.stop().
I will investigate further and create an appropriate JIRA. Thank you
for the simple test case.
Cliff
On Wed, Apr 3, 2019 at 4:17 AM Rabih M wrote:
>
> Hello,
>
> Concerning this point, i still have the
[
https://issues.apache.org/jira/browse/DISPATCH-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16800883#comment-16800883
]
Cliff Jansen commented on DISPATCH-1274:
The connector timer is sometimes zero and sometimes
Cliff Jansen created DISPATCH-1295:
--
Summary: reduce cpu and locking in timer/immediate code.
Key: DISPATCH-1295
URL: https://issues.apache.org/jira/browse/DISPATCH-1295
Project: Qpid Dispatch
Cliff Jansen created QPID-8278:
--
Summary: Build failure on Windows
Key: QPID-8278
URL: https://issues.apache.org/jira/browse/QPID-8278
Project: Qpid
Issue Type: Bug
Components: C
Hi Jeremy,
Thank you for your testing and report.
I am not seeing these errors on a variety of systems. Would you please tell me
- Your OS
- Compiler of choice
- cmake build arguments
??
Also, can you confirm whether you see similar or no errors from the
0.26.0 release?
Many thanks.
[
https://issues.apache.org/jira/browse/PROTON-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen reopened PROTON-1990:
--
Naughty and unnecessary C++11 usage.
> drain gets st
[
https://issues.apache.org/jira/browse/PROTON-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759665#comment-16759665
]
Cliff Jansen commented on PROTON-1999:
--
Jeremy: I did not fully understand the scenario you have
[
https://issues.apache.org/jira/browse/PROTON-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759664#comment-16759664
]
Cliff Jansen commented on PROTON-1999:
--
Olivier Delbeke: the mapping mechanism between Proton-C
[
https://issues.apache.org/jira/browse/PROTON-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-1990.
--
Resolution: Fixed
Added a test.
Found a second instance of un-toggled drain that required
[
https://issues.apache.org/jira/browse/PROTON-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755400#comment-16755400
]
Cliff Jansen commented on PROTON-1999:
--
In example2.cpp
sender.work_queue()
is not thread safe
[
https://issues.apache.org/jira/browse/PROTON-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen reassigned PROTON-1999:
Assignee: Cliff Jansen
> [c] Crash in pn_connection_final
[
https://issues.apache.org/jira/browse/PROTON-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-1982.
--
Resolution: Fixed
Fix Version/s: proton-c-0.27.0
Debian:stretch build is now happy
[
https://issues.apache.org/jira/browse/PROTON-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16717563#comment-16717563
]
Cliff Jansen commented on PROTON-1982:
--
For me, the builds work up to f53c768 and fail after
Cliff Jansen created PROTON-1982:
Summary: Proton C build fails on debian:stretch
Key: PROTON-1982
URL: https://issues.apache.org/jira/browse/PROTON-1982
Project: Qpid Proton
Issue Type: Bug
[
https://issues.apache.org/jira/browse/PROTON-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715515#comment-16715515
]
Cliff Jansen commented on PROTON-1981:
--
Looking at the doc for pn_proactor_now() in proactor.h
Cliff Jansen created PROTON-1981:
Summary: Wrong posix time for pn_proactor_now()
Key: PROTON-1981
URL: https://issues.apache.org/jira/browse/PROTON-1981
Project: Qpid Proton
Issue Type: Bug
[
https://issues.apache.org/jira/browse/QPID-8209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved QPID-8209.
Resolution: Fixed
Fix Version/s: qpid-cpp-1.37.0
> qpidd segfault with huge backtrace w
[
https://issues.apache.org/jira/browse/QPID-8209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16614430#comment-16614430
]
Cliff Jansen commented on QPID-8209:
The value Queue::deleted can be set arbitrarily late because
Have you tried the libuv proactor implementation for Proton-C? See
qpid-proton/c/CMakeLists.txt.
The current release of libuv claims to be fully supported on "Linux >=
2.6.32 with glibc >= 2.12".
If libuv works for you, that might be the easiest solution.
On Thu, Sep 6, 2018 at 4:26 AM,
[
https://issues.apache.org/jira/browse/PROTON-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-1842.
--
Resolution: Fixed
Fix Version/s: proton-c-0.25.0
> [c] Dispatch/Proton crashes w
[
https://issues.apache.org/jira/browse/PROTON-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476036#comment-16476036
]
Cliff Jansen commented on PROTON-1833:
--
While I could not reproduce, it is plausible
[
https://issues.apache.org/jira/browse/PROTON-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-1844.
--
Resolution: Fixed
> Windows proactor memory corruption on clea
[
https://issues.apache.org/jira/browse/PROTON-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-1514.
--
Resolution: Fixed
> [proton-c] When last frame of multi-frame transfer has settled=t
[
https://issues.apache.org/jira/browse/PROTON-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16473323#comment-16473323
]
Cliff Jansen commented on PROTON-1770:
--
Just a reminder note. Epoll version consists of many
Cliff Jansen created PROTON-1844:
Summary: Windows proactor memory corruption on cleanup
Key: PROTON-1844
URL: https://issues.apache.org/jira/browse/PROTON-1844
Project: Qpid Proton
Issue
[
https://issues.apache.org/jira/browse/PROTON-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467772#comment-16467772
]
Cliff Jansen commented on PROTON-1842:
--
Thank-you for this additional info.
Yes, these look like
[
https://issues.apache.org/jira/browse/PROTON-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467486#comment-16467486
]
Cliff Jansen commented on PROTON-1842:
--
This test case is quite devilish. Thank-you.
The above fix
[
https://issues.apache.org/jira/browse/PROTON-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16455673#comment-16455673
]
Cliff Jansen commented on PROTON-1833:
--
I built the current master on VS2008 and VS2013 without
[
https://issues.apache.org/jira/browse/PROTON-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425053#comment-16425053
]
Cliff Jansen commented on PROTON-1800:
--
As a workaround, adding
client.receiver = None
[
https://issues.apache.org/jira/browse/PROTON-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16410314#comment-16410314
]
Cliff Jansen commented on PROTON-1514:
--
prior to reversion saw errors in qpid-dispatch
[
https://issues.apache.org/jira/browse/PROTON-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-1788.
--
Resolution: Won't Fix
See comment regarding further work for generic platforms.
This can
[
https://issues.apache.org/jira/browse/PROTON-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16391674#comment-16391674
]
Cliff Jansen commented on PROTON-1788:
--
p17988_0.patch is a sample implementation that works
[
https://issues.apache.org/jira/browse/PROTON-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen updated PROTON-1788:
-
Attachment: p1788_0.patch
> Thread-safe schedule for 0.1
Cliff Jansen created PROTON-1788:
Summary: Thread-safe schedule for 0.16 C++
Key: PROTON-1788
URL: https://issues.apache.org/jira/browse/PROTON-1788
Project: Qpid Proton
Issue Type: Wish
[
https://issues.apache.org/jira/browse/PROTON-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-1745.
--
Resolution: Fixed
Separate issue create for future test:
https://issues.apache.org/jira
Cliff Jansen created PROTON-1750:
Summary: Create test for address info on inbound sockets
Key: PROTON-1750
URL: https://issues.apache.org/jira/browse/PROTON-1750
Project: Qpid Proton
Issue
[
https://issues.apache.org/jira/browse/PROTON-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16329877#comment-16329877
]
Cliff Jansen commented on PROTON-1745:
--
Try the attached patch and see if that works. If so, we
[
https://issues.apache.org/jira/browse/PROTON-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen updated PROTON-1745:
-
Attachment: p1745_0.diff
> [proton-c, regression] PN_CONNECTION_BOUND event is emitted too s
electing the libuv proactor does not "unlock other functionalities in
proton". They all provide the same feature set.
Its purpose is indeed to increase the range of supported operating systems.
On platforms that have custom proactor implementations, i.e epoll on
Linux and iocp on Windows, the
Cliff Jansen created PROTON-1744:
Summary: bug in c-proactor-tests
Key: PROTON-1744
URL: https://issues.apache.org/jira/browse/PROTON-1744
Project: Qpid Proton
Issue Type: Bug
[
https://issues.apache.org/jira/browse/PROTON-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-1702.
--
Resolution: Fixed
> Fix epoll proactor listener for rearming and overflow per soc
[
https://issues.apache.org/jira/browse/PROTON-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-1531.
--
Resolution: Fixed
> C epoll proactor listener cleanup r
Cliff Jansen created PROTON-1702:
Summary: Fix epoll proactor listener for rearming and overflow per
socket
Key: PROTON-1702
URL: https://issues.apache.org/jira/browse/PROTON-1702
Project: Qpid
[
https://issues.apache.org/jira/browse/PROTON-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16264587#comment-16264587
]
Cliff Jansen commented on PROTON-1691:
--
In theory pn_free(link->context) should res
[
https://issues.apache.org/jira/browse/PROTON-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen reassigned PROTON-1691:
Assignee: Cliff Jansen
> Memory leak when creating endpoint objects with a hand
Cliff Jansen created PROTON-1650:
Summary: Missing extern "C" {} declaration in proton/netaddr.h
Key: PROTON-1650
URL: https://issues.apache.org/jira/browse/PROTON-1650
Project: Q
[
https://issues.apache.org/jira/browse/PROTON-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-824.
-
Resolution: Fixed
Yes. The last checkin should have been used as the time for resolution/close
[
https://issues.apache.org/jira/browse/PROTON-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-1641.
--
Resolution: Fixed
> Windows proactor hang on incoming connecti
Cliff Jansen created PROTON-1641:
Summary: Windows proactor hang on incoming connections
Key: PROTON-1641
URL: https://issues.apache.org/jira/browse/PROTON-1641
Project: Qpid Proton
Issue
[
https://issues.apache.org/jira/browse/PROTON-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-1534.
--
Resolution: Fixed
> Python client BlockingConnection fails cleanup on LinkDetached except
[
https://issues.apache.org/jira/browse/PROTON-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16201294#comment-16201294
]
Cliff Jansen commented on PROTON-1556:
--
The last fix is a safe band-aid.
Leaving the JIRA
[
https://issues.apache.org/jira/browse/PROTON-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16201283#comment-16201283
]
Cliff Jansen commented on PROTON-1556:
--
I originally thought that fostering greater thread safety
Cliff Jansen created PROTON-1620:
Summary: TLS / SSL thread safety with proactor
Key: PROTON-1620
URL: https://issues.apache.org/jira/browse/PROTON-1620
Project: Qpid Proton
Issue Type: Bug
[
https://issues.apache.org/jira/browse/PROTON-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-1601.
--
Resolution: Fixed
> windows proactor fails ipv6 target "
[
https://issues.apache.org/jira/browse/PROTON-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-1604.
--
Resolution: Fixed
> Windows C++ prefers std::endl to newli
[
https://issues.apache.org/jira/browse/PROTON-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-1601.
--
Resolution: Fixed
> windows proactor fails ipv6 target "
Cliff Jansen created PROTON-1604:
Summary: Windows C++ prefers std::endl to newlines
Key: PROTON-1604
URL: https://issues.apache.org/jira/browse/PROTON-1604
Project: Qpid Proton
Issue Type
Cliff Jansen created PROTON-1603:
Summary: Windows C++ container does not compile multithreaded
Key: PROTON-1603
URL: https://issues.apache.org/jira/browse/PROTON-1603
Project: Qpid Proton
Cliff Jansen created PROTON-1601:
Summary: windows proactor fails ipv6 target ":::5672"
Key: PROTON-1601
URL: https://issues.apache.org/jira/browse/PROTON-1601
Project: Qpid Proton
[
https://issues.apache.org/jira/browse/PROTON-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen updated PROTON-1349:
-
Attachment: p1349_2.patch
Patch for compiling the C broker.
> C "proactor" i
Cliff Jansen created PROTON-1564:
Summary: epoll proactor pn_proactor_release_connection reconnect
bugs
Key: PROTON-1564
URL: https://issues.apache.org/jira/browse/PROTON-1564
Project: Qpid Proton
Cliff Jansen created PROTON-1550:
Summary: Epoll proactor performance improvement
Key: PROTON-1550
URL: https://issues.apache.org/jira/browse/PROTON-1550
Project: Qpid Proton
Issue Type
Cliff Jansen created PROTON-1548:
Summary: C++ proactor_container_impl deadlock in schedule.
Key: PROTON-1548
URL: https://issues.apache.org/jira/browse/PROTON-1548
Project: Qpid Proton
1 - 100 of 713 matches
Mail list logo
