[jira] [Resolved] (PROTON-606) Python testReclaimCredit exposes test server messenger hang on windows
[ https://issues.apache.org/jira/browse/PROTON-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke resolved PROTON-606. Resolution: Fixed Fix Version/s: 0.8 Fixed at committed version 1602513. > Python testReclaimCredit exposes test server messenger hang on windows > -- > > Key: PROTON-606 > URL: https://issues.apache.org/jira/browse/PROTON-606 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: 0.7 > Environment: Windows Server 2012 R2 > Python 2.6.1 >Reporter: Chuck Rolke > Fix For: 0.8 > > > PROTON-603 testCreditReclaim exposes another issue on Windows platforms. > After the test failed at some assert then the teardown() function had another > assert because the server never stopped. The second assert overwrites the > first assert and hides the original error. > teardown() can't call client2.work or stimulate client2 to shut down. This > leaves the server stuck. > The proposed fix is to promote client2 to be a class member and drive it in > parallel with client and server. Other miscellaneous tweaks are required to > get the package working on windows. Please see the review board entry. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (PROTON-606) Python testReclaimCredit exposes test server messenger hang on windows
[ https://issues.apache.org/jira/browse/PROTON-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1403#comment-1403 ] ASF subversion and git services commented on PROTON-606: Commit 1602513 from c...@apache.org in branch 'proton/trunk' [ https://svn.apache.org/r1602513 ] PROTON-606: Python testReclaimCredit exposes test server messenger hang on windows Move client2 into NBMessengerTest scope and include it in main pump loop. > Python testReclaimCredit exposes test server messenger hang on windows > -- > > Key: PROTON-606 > URL: https://issues.apache.org/jira/browse/PROTON-606 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: 0.7 > Environment: Windows Server 2012 R2 > Python 2.6.1 >Reporter: Chuck Rolke > > PROTON-603 testCreditReclaim exposes another issue on Windows platforms. > After the test failed at some assert then the teardown() function had another > assert because the server never stopped. The second assert overwrites the > first assert and hides the original error. > teardown() can't call client2.work or stimulate client2 to shut down. This > leaves the server stuck. > The proposed fix is to promote client2 to be a class member and drive it in > parallel with client and server. Other miscellaneous tweaks are required to > get the package working on windows. Please see the review board entry. -- This message was sent by Atlassian JIRA (v6.2#6252)
Proton-c on android
Hello all, I recently took it upon myself to get proton-c working with android. I ended up being successful in my endeavor. It took me a couple weeks to get it working but I have put in some effort to make the process straightforward. The bulk of the work did not involve many changes to proton-c code, as it was mostly focused on getting the library to build for android. I did have to change a couple lines of code in driver.c, (getprotobyname doesn't work). My method utilizes the android build system 'ndk-build' and the swig bindings produced from proton 0.6. Because of the lack of swig bindings in proton-c 0.7 I have not used this version on android. I have been able to successfully create apps and upload them to my phone for sending and receiving messages with proton-c. This was not a straightforward process, but with the work I've done it's easy to build proton-c targeting ARM and other android architectures. I have a folder with a readme that lists the instructions for building the proton-c library targeting android architectures and all it involves is downloading the ndk, and calling 'ndk-build' three times in three different folders. I was wondering how I can contribute this to the proton project? It would be really cool if my work could somehow be included into the build system for proton so that with a simple option the ARM architecture libraries could be created alongside the normal build targets. For example I envision something along the lines of: cmake -DCMAKE_INSTALL_PREFIX=/usr -DINCLUDE_ANDROID .. Thanks, Jimmy
[jira] [Commented] (PROTON-606) Python testReclaimCredit exposes test server messenger hang on windows
[ https://issues.apache.org/jira/browse/PROTON-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14031104#comment-14031104 ] Chuck Rolke commented on PROTON-606: Review at https://reviews.apache.org/r/22528/ > Python testReclaimCredit exposes test server messenger hang on windows > -- > > Key: PROTON-606 > URL: https://issues.apache.org/jira/browse/PROTON-606 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: 0.7 > Environment: Windows Server 2012 R2 > Python 2.6.1 >Reporter: Chuck Rolke > > PROTON-603 testCreditReclaim exposes another issue on Windows platforms. > After the test failed at some assert then the teardown() function had another > assert because the server never stopped. The second assert overwrites the > first assert and hides the original error. > teardown() can't call client2.work or stimulate client2 to shut down. This > leaves the server stuck. > The proposed fix is to promote client2 to be a class member and drive it in > parallel with client and server. Other miscellaneous tweaks are required to > get the package working on windows. Please see the review board entry. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (PROTON-609) Assert in messenger.py test causes core dump
Chuck Rolke created PROTON-609:
--
Summary: Assert in messenger.py test causes core dump
Key: PROTON-609
URL: https://issues.apache.org/jira/browse/PROTON-609
Project: Qpid Proton
Issue Type: Bug
Components: proton-c
Affects Versions: 0.7
Environment: Windows or Linux
Reporter: Chuck Rolke
This assert:
{noformat}
Index: tests/python/proton_tests/messenger.py
===
--- tests/python/proton_tests/messenger.py (revision 1602460)
+++ tests/python/proton_tests/messenger.py (working copy)
@@ -843,6 +843,7 @@
msg2 = Message()
msg2.address = self.address + "/msg2"
self.client.put(msg2)
+assert False, "Whoops!"
self.pump()
assert self.server.incoming == 1, self.server.incoming
assert self.server.receiving == 8, self.server.receiving
{noformat}
causes a core dump in NBMessengerTest.teardown when the code tries to stop the
client. A user may work around this issue by
{noformat}
+ if msgr.outgoing > 0:
+msgr.settle()
+ while msgr.incoming > 0:
+msgr.get()
+ msgr.stop()
{noformat}
when all he wants is msgr.stop().
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (PROTON-608) seg fault if attach is sent before open and begin
[ https://issues.apache.org/jira/browse/PROTON-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14030641#comment-14030641 ] Gordon Sim commented on PROTON-608: --- > 2014-06-11 17:12:11 [Protocol] trace [qpid.127.0.0.1:5672-127.0.0.1:42526]: > <- AMQP > 2014-06-11 17:12:11 [Protocol] trace [qpid.127.0.0.1:5672-127.0.0.1:42526]: > 65535 <- @attach(18) [name="amq.topic_1", handle=0, role=false, > snd-settle-mode=2, rcv-settle-mode=0, target=@target(41) > [address="amq.topic"], incomplete-unsettled=false, initial-delivery-count=0] > Segmentation fault (core dumped) > Core was generated by `./src/qpidd --auth no --load-module ./src/amqp.so > --log-enable info+ --log-enab'. > Program terminated with signal 11, Segmentation fault. > #0 0x7f4a9be383b4 in pn_find_link () from > /home/gordon/qpid-releases/proton/0.7/installation/lib64/libqpid-proton.so.2 > Missing separate debuginfos, use: debuginfo-install > boost-program-options-1.48.0-14.fc17.x86_64 > cyrus-sasl-lib-2.1.23-31.fc17.x86_64 glibc-2.15-59.fc17.x86_64 > keyutils-libs-1.5.5-2.fc17.x86_64 krb5-libs-1.10.2-12.fc17.x86_64 > libcom_err-1.42.3-3.fc17.x86_64 libselinux-2.1.10-3.fc17.x86_64 > libuuid-2.21.2-4.fc17.x86_64 nspr-4.9.6-1.fc17.x86_64 > nss-3.14.3-2.fc17.x86_64 nss-softokn-freebl-3.14.3-1.fc17.x86_64 > nss-util-3.14.3-1.fc17.x86_64 openssl-1.0.0k-1.fc17.x86_64 > zlib-1.2.5-7.fc17.x86_64 > (gdb) bt > #0 0x7f4a9be383b4 in pn_find_link () from > /home/gordon/qpid-releases/proton/0.7/installation/lib64/libqpid-proton.so.2 > #1 0x7f4a9be385ce in pn_do_attach () from > /home/gordon/qpid-releases/proton/0.7/installation/lib64/libqpid-proton.so.2 > #2 0x7f4a9be32c34 in pn_dispatch_frame () from > /home/gordon/qpid-releases/proton/0.7/installation/lib64/libqpid-proton.so.2 > #3 0x7f4a9be32dc7 in pn_dispatcher_input () from > /home/gordon/qpid-releases/proton/0.7/installation/lib64/libqpid-proton.so.2 > #4 0x7f4a9be3a5ee in pn_input_read_amqp () from > /home/gordon/qpid-releases/proton/0.7/installation/lib64/libqpid-proton.so.2 > #5 0x7f4a9be39b65 in transport_consume () from > /home/gordon/qpid-releases/proton/0.7/installation/lib64/libqpid-proton.so.2 > #6 0x7f4a9be3aaf2 in pn_transport_process () from > /home/gordon/qpid-releases/proton/0.7/installation/lib64/libqpid-proton.so.2 > #7 0x7f4a9be3ac48 in pn_transport_input () from > /home/gordon/qpid-releases/proton/0.7/installation/lib64/libqpid-proton.so.2 > #8 0x7f4a9c103516 in qpid::broker::amqp::Connection::decode(char const*, > unsigned long) () from > seg fault if attach is sent before open and begin > - > > Key: PROTON-608 > URL: https://issues.apache.org/jira/browse/PROTON-608 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: 0.7 >Reporter: Gordon Sim > Fix For: 0.8 > > > While working with the proton-j engine, I inadvertently opened a link before > opening the corresponding session and connection. This resulted in the attach > being sent without the open or begin. Though clearly user error, it did show > up an issue with the proton-c engine, where this sequence causes a segfault. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (PROTON-608) seg fault if attach is sent before open and begin
Gordon Sim created PROTON-608: - Summary: seg fault if attach is sent before open and begin Key: PROTON-608 URL: https://issues.apache.org/jira/browse/PROTON-608 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.7 Reporter: Gordon Sim Fix For: 0.8 While working with the proton-j engine, I inadvertently opened a link before opening the corresponding session and connection. This resulted in the attach being sent without the open or begin. Though clearly user error, it did show up an issue with the proton-c engine, where this sequence causes a segfault. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (PROTON-607) Perl recv.pl shows error if a message has no subject
[ https://issues.apache.org/jira/browse/PROTON-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Pierce resolved PROTON-607. - Resolution: Fixed Fix Version/s: 0.8 > Perl recv.pl shows error if a message has no subject > > > Key: PROTON-607 > URL: https://issues.apache.org/jira/browse/PROTON-607 > Project: Qpid Proton > Issue Type: Bug > Components: perl-binding >Reporter: Darryl L. Pierce >Assignee: Darryl L. Pierce > Fix For: 0.8 > > > If the message has no subject then the recv.pl example outputs: > Use of uninitialized value in concatenation (.) or string at > ../examples/messenger/perl/recv.pl line 55. > The code should instead only output the subject if one is present. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (PROTON-607) Perl recv.pl shows error if a message has no subject
Darryl L. Pierce created PROTON-607: --- Summary: Perl recv.pl shows error if a message has no subject Key: PROTON-607 URL: https://issues.apache.org/jira/browse/PROTON-607 Project: Qpid Proton Issue Type: Bug Components: perl-binding Reporter: Darryl L. Pierce Assignee: Darryl L. Pierce If the message has no subject then the recv.pl example outputs: Use of uninitialized value in concatenation (.) or string at ../examples/messenger/perl/recv.pl line 55. The code should instead only output the subject if one is present. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (PROTON-607) Perl recv.pl shows error if a message has no subject
[ https://issues.apache.org/jira/browse/PROTON-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14030578#comment-14030578 ] ASF subversion and git services commented on PROTON-607: Commit 1602412 from [~mcpierce] in branch 'proton/trunk' [ https://svn.apache.org/r1602412 ] PROTON-607: Perl recv only shows subject if received Put a guard in place to only display the subject line if the message has a subject. > Perl recv.pl shows error if a message has no subject > > > Key: PROTON-607 > URL: https://issues.apache.org/jira/browse/PROTON-607 > Project: Qpid Proton > Issue Type: Bug > Components: perl-binding >Reporter: Darryl L. Pierce >Assignee: Darryl L. Pierce > > If the message has no subject then the recv.pl example outputs: > Use of uninitialized value in concatenation (.) or string at > ../examples/messenger/perl/recv.pl line 55. > The code should instead only output the subject if one is present. -- This message was sent by Atlassian JIRA (v6.2#6252)
