Re: Proton 0.11.0 release notes and docs preview
Hello Justin, I took a quick look at the website and I noticed that the examples source code is not included in the C++ documentation. These pages, for example, are missing the attached source: http://people.apache.org/~jross/qpid-site/head/releases/qpid-proton-0.1 1.0/proton/cpp/api/broker_8cpp-example.html and http://people.apache.org/~jross/qpid-site/head/releases/qpid-proton-0.1 1.0/proton/cpp/api/client_8cpp-example.html Kind regards -- Otavio Rodolfo Piske Messaging Quality Assurance Engineer On Wed, 2015-10-28 at 13:49 -0400, Justin Ross wrote: > Hi again. Here's a staged build of the 0.11.0 website content: > > > http://people.apache.org/~jross/qpid-site/head/releases/qpid-proton-0 > .11.0/ > > http://people.apache.org/~jross/qpid-site/head/releases/qpid-proton-0 > .11.0/release-notes.html > > You can edit jira summaries to change the final output when I > regenerate > this content for release. If there are any special notes you'd like > me to > add, please request them on the release jira: > > https://issues.apache.org/jira/browse/QPID-6773 > > Thanks, > Justin > > --- > Proton 0.11.0 release page: > https://cwiki.apache.org/confluence/display/qpid/Qpid+Proton+0.11.0
Re: Proton 0.11.0 release update - Beta is available
I overlooked that your message had already ben moderated through when I replied off-list earlier. Just so the answer is out there for anyone else reading: You self-manage subscriptions to the mailing lists, details are at: http://qpid.apache.org/discussion.html Robbie On 28 October 2015 at 21:26, Ganesh Murthy wrote: > Can you please add me to this list? Thanks. > > - Forwarded Message - > From: "Ted Ross" > To: "ganesh Murthy" > Sent: Wednesday, October 28, 2015 5:24:07 PM > Subject: Fwd: Proton 0.11.0 release update - Beta is available > > > > > Forwarded Message > Subject: Proton 0.11.0 release update - Beta is available > Date: Wed, 28 Oct 2015 06:49:13 -0400 > From: Justin Ross > Reply-To: proton@qpid.apache.org > To: us...@qpid.apache.org , proton@qpid.apache.org > > Hi, everyone. The beta is now available from the following URL: > >https://dist.apache.org/repos/dist/dev/qpid/proton/0.11.0-beta/ > > Maven staging repo: > >https://repository.apache.org/content/repositories/orgapacheqpid-1047 > > Test output from my machine, Fedora 22 x86-64: > > > http://people.apache.org/~jross/qpid-releases/quirk-proton-0.11.0-beta.log > > Take notice! We are on a compressed schedule. Alpha was one week ago, and > RC is only one week away. We very much need testing and feedback on the > beta release. > > With the beta, we've branched for release, and release-branch commits > require approval. The release page[1] describes the procedure and criteria. > > Thanks! > Justin > > --- > [1] Proton 0.11.0 release page: > https://cwiki.apache.org/confluence/display/qpid/Qpid+Proton+0.11.0 > > >
[jira] [Commented] (PROTON-1031) [python] Bump the module version to 0.11.0
[ https://issues.apache.org/jira/browse/PROTON-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980285#comment-14980285 ] Robbie Gemmell commented on PROTON-1031: Is there an equivalent change needed on master? > [python] Bump the module version to 0.11.0 > -- > > Key: PROTON-1031 > URL: https://issues.apache.org/jira/browse/PROTON-1031 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.11 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Blocker > Fix For: 0.11 > > > Update the setup.py script and the module version number before we release > 0.11.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Proton 0.11.0 release notes and docs preview
Thanks, Otavio. I suspect that's a problem with my website scripting. I'll try to get it fixed. On Thu, Oct 29, 2015 at 6:58 AM, Otavio Rodolfo Piske wrote: > Hello Justin, > > I took a quick look at the website and I noticed that the examples > source code is not included in the C++ documentation. These pages, for > example, are missing the attached source: > > http://people.apache.org/~jross/qpid-site/head/releases/qpid-proton-0.1 > 1.0/proton/cpp/api/broker_8cpp-example.html > > and > > http://people.apache.org/~jross/qpid-site/head/releases/qpid-proton-0.1 > 1.0/proton/cpp/api/client_8cpp-example.html > > > Kind regards > -- > Otavio Rodolfo Piske > Messaging Quality Assurance Engineer > > > > On Wed, 2015-10-28 at 13:49 -0400, Justin Ross wrote: > > Hi again. Here's a staged build of the 0.11.0 website content: > > > > > > http://people.apache.org/~jross/qpid-site/head/releases/qpid-proton-0 > > .11.0/ > > > > http://people.apache.org/~jross/qpid-site/head/releases/qpid-proton-0 > > .11.0/release-notes.html > > > > You can edit jira summaries to change the final output when I > > regenerate > > this content for release. If there are any special notes you'd like > > me to > > add, please request them on the release jira: > > > > https://issues.apache.org/jira/browse/QPID-6773 > > > > Thanks, > > Justin > > > > --- > > Proton 0.11.0 release page: > > https://cwiki.apache.org/confluence/display/qpid/Qpid+Proton+0.11.0 >
[jira] [Commented] (PROTON-1031) [python] Bump the module version to 0.11.0
[ https://issues.apache.org/jira/browse/PROTON-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980330#comment-14980330 ] Ken Giusti commented on PROTON-1031: Yes! I've already got a patch for mainline - I'll get it in today. -K > [python] Bump the module version to 0.11.0 > -- > > Key: PROTON-1031 > URL: https://issues.apache.org/jira/browse/PROTON-1031 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.11 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Blocker > Fix For: 0.11 > > > Update the setup.py script and the module version number before we release > 0.11.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Proton 0.11.0 release update - Beta is available
I got down the proton 0.11 beta and ran dispatch tests and it looks good. I was specifically interested in two JIRAs that I created (which are fixed in this beta) and those fixes work as well. I am on Fedora 21. Thanks. Forwarded Message Subject: Proton 0.11.0 release update - Beta is available Date: Wed, 28 Oct 2015 06:49:13 -0400 From: Justin Ross Reply-To: proton@qpid.apache.org To: us...@qpid.apache.org , proton@qpid.apache.org Hi, everyone. The beta is now available from the following URL: https://dist.apache.org/repos/dist/dev/qpid/proton/0.11.0-beta/ Maven staging repo: https://repository.apache.org/content/repositories/orgapacheqpid-1047 Test output from my machine, Fedora 22 x86-64: http://people.apache.org/~jross/qpid-releases/quirk-proton-0.11.0-beta.log Take notice! We are on a compressed schedule. Alpha was one week ago, and RC is only one week away. We very much need testing and feedback on the beta release. With the beta, we've branched for release, and release-branch commits require approval. The release page[1] describes the procedure and criteria. Thanks! Justin --- [1] Proton 0.11.0 release page: https://cwiki.apache.org/confluence/display/qpid/Qpid+Proton+0.11.0
Re: Proton 0.11.0 release update - Beta is available
Thanks, Ganesh. On Thu, Oct 29, 2015 at 9:12 AM, Ganesh Murthy wrote: > I got down the proton 0.11 beta and ran dispatch tests and it looks good. > I was specifically interested in two JIRAs that I created (which are fixed > in this beta) and those fixes work as well. I am on Fedora 21. Thanks. > > > Forwarded Message > Subject: Proton 0.11.0 release update - Beta is available > Date: Wed, 28 Oct 2015 06:49:13 -0400 > From: Justin Ross > Reply-To: proton@qpid.apache.org > To: us...@qpid.apache.org , proton@qpid.apache.org > > Hi, everyone. The beta is now available from the following URL: > >https://dist.apache.org/repos/dist/dev/qpid/proton/0.11.0-beta/ > > Maven staging repo: > >https://repository.apache.org/content/repositories/orgapacheqpid-1047 > > Test output from my machine, Fedora 22 x86-64: > > > http://people.apache.org/~jross/qpid-releases/quirk-proton-0.11.0-beta.log > > Take notice! We are on a compressed schedule. Alpha was one week ago, and > RC is only one week away. We very much need testing and feedback on the > beta release. > > With the beta, we've branched for release, and release-branch commits > require approval. The release page[1] describes the procedure and > criteria. > > Thanks! > Justin > > --- > [1] Proton 0.11.0 release page: > https://cwiki.apache.org/confluence/display/qpid/Qpid+Proton+0.11.0 > > > >
pn_error_code() returning -2 error
Hi, Using Proton C library. I am following the demo example "send.c" shared in the archive. Currently using the mqx OS. 1. I have following function in *pn_error_code*(messenger->error); always returning *-2*. while calling the following function* pn_messenger_put*(messenger, message); 2. In the following demo "send.c" when will the socket be open. As I see following function "*pn_messenger_start*(messenger);" doesnt have any significance , since if (*messenger->flags | PN_FLAGS_CHECK_ROUTES*) *messenger->flags is never **PN_FLAGS_CHECK_ROUTES.* 3. Is there any basic code flow document that i can refer to start of the debug would be very helpful. Thanks in Advance
[jira] [Created] (PROTON-1032) Cannot call super() on classes derived from Exception in 2.4
Ken Giusti created PROTON-1032: -- Summary: Cannot call super() on classes derived from Exception in 2.4 Key: PROTON-1032 URL: https://issues.apache.org/jira/browse/PROTON-1032 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: 0.9.1 Reporter: Ken Giusti Assignee: Ken Giusti The proton 0.9.x series is the last release where python 2.4 is supported (only 2.6+ in 0.10.x+). Code on the 0.9.x branch uses the super() method on Exception derived classes. This is illegal on python 2.4. This fix is only targeted to this branch in case for whatever reason someone stuck with python 2.4 would like to use proton. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-1032) Cannot call super() on classes derived from Exception in 2.4
[ https://issues.apache.org/jira/browse/PROTON-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980638#comment-14980638 ] Ken Giusti commented on PROTON-1032: https://reviews.apache.org/r/39759/ > Cannot call super() on classes derived from Exception in 2.4 > > > Key: PROTON-1032 > URL: https://issues.apache.org/jira/browse/PROTON-1032 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.9.1 >Reporter: Ken Giusti >Assignee: Ken Giusti > > The proton 0.9.x series is the last release where python 2.4 is supported > (only 2.6+ in 0.10.x+). > Code on the 0.9.x branch uses the super() method on Exception derived > classes. This is illegal on python 2.4. > This fix is only targeted to this branch in case for whatever reason someone > stuck with python 2.4 would like to use proton. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (PROTON-1025) CLOSE_WAIT leak following reproducer for PROTON-1023 / PROTON-1024
[
https://issues.apache.org/jira/browse/PROTON-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec closed PROTON-1025.
-
Resolution: Not A Problem
> CLOSE_WAIT leak following reproducer for PROTON-1023 / PROTON-1024
> --
>
> Key: PROTON-1025
> URL: https://issues.apache.org/jira/browse/PROTON-1025
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
>Affects Versions: 0.10
>Reporter: Pavel Moravec
>Priority: Minor
>
> Following reproducer for PROTON-1023 or PROTON-1024 (attached at the botton),
> client leaves some sockets in CLOSE_WAIT state forever.
> I tested the reproducer before & after those two fixes and it is present in
> both. I.e. this bug is not a regression caused by PROTON-1023 or PROTON-1024.
> Reproducer:
> (assuming localhost runs qdrouterd that is restarted every 5 seconds in a
> loop):
> {code}
> #!/usr/bin/python
> from time import sleep
> from uuid import uuid4
> from proton import ConnectionException
> from proton.utils import BlockingConnection
> import traceback
> import random
> while True:
> sleep(random.uniform(0.3,3))
> try:
> conn = BlockingConnection("proton+amqp://localhost:5672",
> ssl_domain=None, heartbeat=2)
> rec = conn.create_receiver("another_address", name=str(uuid4()),
> dynamic=False, options=None)
> print "sleeping.."
> sleep(random.uniform(0.3,3))
> rec2 = conn.create_receiver("some_address", name=str(uuid4()),
> dynamic=False, options=None)
> except ConnectionException:
> try:
> if conn:
> conn.close()
> except Exception, e:
> print e
> print(traceback.format_exc())
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (PROTON-1025) CLOSE_WAIT leak following reproducer for PROTON-1023 / PROTON-1024
[
https://issues.apache.org/jira/browse/PROTON-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980661#comment-14980661
]
Pavel Moravec commented on PROTON-1025:
---
Good point. It makes sense the programmer should call "destructor" before
assigning a new instance of the class to the variable.
So I am closing this JIRA - let reopen when feature "BlockingConnection should
close itself on unreference" is required..
> CLOSE_WAIT leak following reproducer for PROTON-1023 / PROTON-1024
> --
>
> Key: PROTON-1025
> URL: https://issues.apache.org/jira/browse/PROTON-1025
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
>Affects Versions: 0.10
>Reporter: Pavel Moravec
>Priority: Minor
>
> Following reproducer for PROTON-1023 or PROTON-1024 (attached at the botton),
> client leaves some sockets in CLOSE_WAIT state forever.
> I tested the reproducer before & after those two fixes and it is present in
> both. I.e. this bug is not a regression caused by PROTON-1023 or PROTON-1024.
> Reproducer:
> (assuming localhost runs qdrouterd that is restarted every 5 seconds in a
> loop):
> {code}
> #!/usr/bin/python
> from time import sleep
> from uuid import uuid4
> from proton import ConnectionException
> from proton.utils import BlockingConnection
> import traceback
> import random
> while True:
> sleep(random.uniform(0.3,3))
> try:
> conn = BlockingConnection("proton+amqp://localhost:5672",
> ssl_domain=None, heartbeat=2)
> rec = conn.create_receiver("another_address", name=str(uuid4()),
> dynamic=False, options=None)
> print "sleeping.."
> sleep(random.uniform(0.3,3))
> rec2 = conn.create_receiver("some_address", name=str(uuid4()),
> dynamic=False, options=None)
> except ConnectionException:
> try:
> if conn:
> conn.close()
> except Exception, e:
> print e
> print(traceback.format_exc())
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (PROTON-1031) [python] Bump the module version to 0.11.0
[ https://issues.apache.org/jira/browse/PROTON-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980810#comment-14980810 ] ASF subversion and git services commented on PROTON-1031: - Commit badf8ef40e03962dcaf6288ac3d92ccf972e61b8 in qpid-proton's branch refs/heads/master from [~kgiusti] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=badf8ef ] PROTON-1031: bump the version number used by the setup.py script > [python] Bump the module version to 0.11.0 > -- > > Key: PROTON-1031 > URL: https://issues.apache.org/jira/browse/PROTON-1031 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.11 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Blocker > Fix For: 0.11 > > > Update the setup.py script and the module version number before we release > 0.11.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (PROTON-1031) [python] Bump the module version to 0.11.0
[ https://issues.apache.org/jira/browse/PROTON-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-1031. Resolution: Fixed Fix Version/s: 0.12.0 > [python] Bump the module version to 0.11.0 > -- > > Key: PROTON-1031 > URL: https://issues.apache.org/jira/browse/PROTON-1031 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.11 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Blocker > Fix For: 0.11, 0.12.0 > > > Update the setup.py script and the module version number before we release > 0.11.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-1032) Cannot call super() on classes derived from Exception in 2.4
[ https://issues.apache.org/jira/browse/PROTON-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980824#comment-14980824 ] ASF subversion and git services commented on PROTON-1032: - Commit c57ba7676b5a83f78caa4f49b7373a7ef94c71f1 in qpid-proton's branch refs/heads/0.9.x from [~kgiusti] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=c57ba76 ] PROTON-1032: for python 2.4 compatibility never call super() from a class derived from Exception > Cannot call super() on classes derived from Exception in 2.4 > > > Key: PROTON-1032 > URL: https://issues.apache.org/jira/browse/PROTON-1032 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.9.1 >Reporter: Ken Giusti >Assignee: Ken Giusti > > The proton 0.9.x series is the last release where python 2.4 is supported > (only 2.6+ in 0.10.x+). > Code on the 0.9.x branch uses the super() method on Exception derived > classes. This is illegal on python 2.4. > This fix is only targeted to this branch in case for whatever reason someone > stuck with python 2.4 would like to use proton. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (PROTON-1032) Cannot call super() on classes derived from Exception in 2.4
[ https://issues.apache.org/jira/browse/PROTON-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-1032. Resolution: Fixed Fix Version/s: 0.9.1 Not actually fixed in 0.9.1, but there was no "0.9.2" option to select! > Cannot call super() on classes derived from Exception in 2.4 > > > Key: PROTON-1032 > URL: https://issues.apache.org/jira/browse/PROTON-1032 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.9.1 >Reporter: Ken Giusti >Assignee: Ken Giusti > Fix For: 0.9.1 > > > The proton 0.9.x series is the last release where python 2.4 is supported > (only 2.6+ in 0.10.x+). > Code on the 0.9.x branch uses the super() method on Exception derived > classes. This is illegal on python 2.4. > This fix is only targeted to this branch in case for whatever reason someone > stuck with python 2.4 would like to use proton. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (PROTON-1033) Update the revision of the libqpid-proton library to 4
Ken Giusti created PROTON-1033: -- Summary: Update the revision of the libqpid-proton library to 4 Key: PROTON-1033 URL: https://issues.apache.org/jira/browse/PROTON-1033 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.11 Reporter: Ken Giusti Assignee: Justin Ross Priority: Blocker Fix For: 0.11 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-1003) ssl transport layer does not define an error handler
[ https://issues.apache.org/jira/browse/PROTON-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti updated PROTON-1003: --- Fix Version/s: 0.11 > ssl transport layer does not define an error handler > > > Key: PROTON-1003 > URL: https://issues.apache.org/jira/browse/PROTON-1003 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: 0.10 >Reporter: Gordon Sim >Assignee: Ken Giusti > Fix For: 0.11 > > > When the local process times out an ssl based connection due to lack of > heartbeats from its peer, the underlying socket is never closed. The cause of > this appears to be that the ssl transport layer doesn't define an error > handler, which is what is used to notify it of the locally initiated timeout. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Proton 0.11.0 release update - Beta is available
Building 0.11.0-beta has a list of issues on Windows, mostly around the Go
binding. Proton proper builds OK.
Maybe we could consider setting the Go binding off by default on Windows builds?
The new C++ binding produces DLL files OK (several new warnings) but I haven't
tested them.
-Chuck
-
1. CMake complains before even starting compiling anything
cmake command
=
cmake -G "Visual Studio 11 Win64"
-DCMAKE_INSTALL_PREFIX=P:\qpid-proton-0.11.0-beta\install_2012_x64
-DBUILD_JAVA=No ..
cmake output
-- Found Go: C:/tools/go/bin/go.exe (go version go1.4.2 windows/amd64)
CMake Warning (dev) at proton-c/bindings/go/CMakeLists.txt:63
(execute_process):
Syntax error in cmake code at
P:/qpid-proton-0.11.0-beta/proton-c/bindings/go/CMakeLists.txt:63
when parsing string
{{range
.GoFiles}}P:\qpid-proton-0.11.0-beta\proton-c\bindings\go\src\qpid.apache.org\amqp/{{.}};{{end}}
Invalid escape sequence \q
-
2. Go version is the same for 32- and 64-bit versions.
-- Found Go: C:/tools/go/bin/go.exe (go version go1.4.2 windows/amd64)
Not sure if this is an issue given how confused the script gets. None of the Go
projects in the solution are populated or usable.
3. 'ld' command looks for 'qpid-proton' when the file is named 'qpid-protond'
17>
C:/tools/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.8.3/../../../../x86_64-w64-mingw32/bin/ld.exe:
cannot find -lqpid-proton
17>collect2.exe : error : ld returned 1 exit status
4. Visual Studio has 7 failures all related to Go (I think) both debug and
release
== Build: 39 succeeded, 7 failed, 0 up-to-date, 0 skipped ==
- Original Message -
> From: "Justin Ross"
> To: us...@qpid.apache.org, proton@qpid.apache.org
> Sent: Wednesday, October 28, 2015 6:49:13 AM
> Subject: Proton 0.11.0 release update - Beta is available
>
> Hi, everyone. The beta is now available from the following URL:
>
> https://dist.apache.org/repos/dist/dev/qpid/proton/0.11.0-beta/
>
> Maven staging repo:
>
> https://repository.apache.org/content/repositories/orgapacheqpid-1047
>
> Test output from my machine, Fedora 22 x86-64:
>
> http://people.apache.org/~jross/qpid-releases/quirk-proton-0.11.0-beta.log
>
> Take notice! We are on a compressed schedule. Alpha was one week ago, and
> RC is only one week away. We very much need testing and feedback on the
> beta release.
>
> With the beta, we've branched for release, and release-branch commits
> require approval. The release page[1] describes the procedure and criteria.
>
> Thanks!
> Justin
>
> ---
> [1] Proton 0.11.0 release page:
> https://cwiki.apache.org/confluence/display/qpid/Qpid+Proton+0.11.0
>
Configured proton repo for reviewboard
Added .reviewboardrc configuration file so a simple `rbt post` on a branch will post a review to the Apache reviewboard. See `rbt --help` for more details. Tips: rbt post # Create a new review of current branch with diff against master rbt post --parent branchx # Review with diff against branchx instead of master rbt post -r12345 # Post a new patch to existing review 12345
[jira] [Commented] (PROTON-512) Possibility to set idle timeout for messenger
[ https://issues.apache.org/jira/browse/PROTON-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981702#comment-14981702 ] Rohan McGovern commented on PROTON-512: --- This issue is listed under "Bugs fixed" in both 0.7 and 0.8 release notes: https://qpid.apache.org/releases/qpid-proton-0.7/release-notes.html , https://qpid.apache.org/releases/qpid-proton-0.8/release-notes.html Is it fixed, or is that a mistake? > Possibility to set idle timeout for messenger > - > > Key: PROTON-512 > URL: https://issues.apache.org/jira/browse/PROTON-512 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: 0.6 >Reporter: Tomas Soltys > Labels: features, patch > Fix For: 0.9 > > Attachments: messenger.c.patch, messenger.h.patch > > > I would like to specify an idle timeout for a messenger which would be then > used for all created connections. I see that there is an interface for > pn_transport_t which is allowing it but it is not accessible from outside. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
