[jira] [Commented] (QPID-8134) qpid::client::Message::send multiple memory leaks
[ https://issues.apache.org/jira/browse/QPID-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16567695#comment-16567695 ] dan clark commented on QPID-8134: - what would be the 'amqp-1.0' equivalent version of the send/recv by topic? > qpid::client::Message::send multiple memory leaks > - > > Key: QPID-8134 > URL: https://issues.apache.org/jira/browse/QPID-8134 > Project: Qpid > Issue Type: Bug > Components: C++ Client >Affects Versions: qpid-cpp-1.37.0, qpid-cpp-1.38.0 > Environment: *CentOS* Linux release 7.4.1708 (Core) > Linux localhost.novalocal 3.10.0-327.el7.x86_64 #1 SMP Thu Nov 19 22:10:57 > UTC 2015 x86_64 x86_64 x86_64 GNU/Linux > *qpid*-qmf-1.37.0-1.el7.x86_64 > *qpid*-dispatch-debuginfo-1.0.0-1.el7.x86_64 > python-*qpid*-1.37.0-1.el7.noarch > *qpid*-proton-c-0.18.1-1.el7.x86_64 > python-*qpid*-qmf-1.37.0-1.el7.x86_64 > *qpid*-proton-debuginfo-0.18.1-1.el7.x86_64 > *qpid*-cpp-debuginfo-1.37.0-1.el7.x86_64 > *qpid*-cpp-client-devel-1.37.0-1.el7.x86_64 > *qpid*-cpp-server-1.37.0-1.el7.x86_64 > *qpid*-cpp-client-1.37.0-1.el7.x86_64 > >Reporter: dan clark >Priority: Blocker > Labels: maven > Attachments: drain.cpp, godrain.sh, gospout.sh, qpid-stat.out, > spout.cpp, spout.log > > Original Estimate: 40h > Remaining Estimate: 40h > > There may be multiple leaks of the outgoing message structure and associated > fields when using the qpid::client::amqp0_10::SenderImpl::send function to > publish messages under certain setups. I will concede that there may be > options that are beyond my ken to ameliorate the leak of messages structures, > especially since there is an indication that under prolonged runs (a > demonized version of an application like spout) that the statistics for quidd > indicate increased acquires with zero releases. > The basic notion is illustrated with the test application spout (and drain). > Consider a long running daemon reducing the overhead of open/send/close by > keeping the message connection open for long periods of time. Then the logic > would be: start application/open connection. In a loop send data (and never > reach a close). Thus the drain application illustrates the behavior and > demonstrates the leak using valgrind by sending the data followed by an > exit(0). > Note also the lack of 'releases' associated with the 'acquires' in the stats > output. > Capturing the leaks using the test applications spout/drain required adding > an 'exit()' prior to the close, as during normal operations of a daemon, the > connection remains open for a sustained period of time, thus the leak of > structures within the c++ client library are found as structures still > tracked by the library and cleaned up on 'connection.close()', but they > should be cleaned up as a result of the completion of the send/receive ack or > the termination of the life of the message based on the TTL of the message, > which ever comes first. I have witnessed growth of the leaked structures > into the millions of messages lasting more than 24hours with short (300sec) > TTL of the messages based on scenarios attached using spout/drain as test > vehicle. > The attached spout.log uses a short 10message test and the spout.log contains > 5 sets of different structures leaked (found with the 'bytes in 10 blocks are > still reachable' lines, that are in line with much more sustained leaks when > running the application for multiple days with millions of messages. > The leaks seem to be associated with structures allocation 'stdstrings' to > save the "subject" and the "payload" for string based messages using send for > amq.topic output. > Suggested work arounds are welcome based on application level changes to > spout/drain (if they are missing key components) or changes to the > address/setup of the queues for amq.topic messages (see the 'gospout.sh and > godrain.sh' test drivers providing the specific address structures being used. > For example, the following is one of the 5 different categories of leaked > data from 'spout.log' on a valgrind analysis of the output post the send and > session.sync but prior connection.close(): > > ==3388== 3,680 bytes in 10 blocks are still reachable in loss record 233 of > 234 > ==3388== at 0x4C2A203: operator new(unsigned long) > (vg_replace_malloc.c:334) > ==3388== by 0x4EB046C: qpid::client::Message::Message(std::string const&, > std::string const&) (Message.cpp:31) > ==3388== by 0x51742C1: > qpid::client::amqp0_10::OutgoingMessage::OutgoingMessage() > (OutgoingMessage.cpp:167) > ==3388== by 0x5186200: > qpid::client::amqp0_10::SenderImpl::sendImpl(qpid::messaging::Message const&) > (SenderImpl.cpp:140) > ==3388== by 0x5186485: operator() (SenderImpl.h:114) > ==3388==
[jira] [Commented] (QPID-8134) qpid::client::Message::send multiple memory leaks
[
https://issues.apache.org/jira/browse/QPID-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16567693#comment-16567693
]
dan clark commented on QPID-8134:
-
Isolated the problem to using the send link properties of 'at-least-once' where
there broker never seems to settle the messages and therefore results in the
qpid-c-client library never releasing any sent message buffers.
in other words: to demonstrate the leak run the shell scripts gospout.sh -a
doSubject (and the corresponding do drain.sh -a doSubject).
The work around is to specify link attributes to the sending (gospout)
application which sets the reliability attribute to 'unreliable' (or
equivalently according to documentation 'at-most-once' as they are synonyms).
per
[https://qpid.apache.org/releases/qpid-cpp-1.38.0/messaging-api/book/section-addresses.html]
Thus updating the examples to avoid the sender leak would look similar to:
./spout 'amq.topic; \{ create: sender, delete: sender, assert: sender, mode:
consume, node: {type: topic, durable: false, x-declare: {auto-delete: true,
ack-frequency: 1, exclusive: true} }*, link: \{ name: pubs-spout, durable:
false, reliability: at-most-once, timeout: 1}* }' \
--content payload \
--topic comp_spout \
--print \
$setexit \
--property 'qpid.subject'=comp_spout \
-c $cnt
Thus by changing the reliability: unreliable, the c++ sending library frees the
memory associated with the send buffer after the message is sent, alleviating
the memory leak.
Speculatively:
Perhaps the bug can be isolated to the behavior between the qpid broker and the
qpid client where for "reliability: exactly-once" the broker is not informing
the client of the message delivery so the client library never cleans up the
message memory.
> qpid::client::Message::send multiple memory leaks
> -
>
> Key: QPID-8134
> URL: https://issues.apache.org/jira/browse/QPID-8134
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
>Affects Versions: qpid-cpp-1.37.0, qpid-cpp-1.38.0
> Environment: *CentOS* Linux release 7.4.1708 (Core)
> Linux localhost.novalocal 3.10.0-327.el7.x86_64 #1 SMP Thu Nov 19 22:10:57
> UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
> *qpid*-qmf-1.37.0-1.el7.x86_64
> *qpid*-dispatch-debuginfo-1.0.0-1.el7.x86_64
> python-*qpid*-1.37.0-1.el7.noarch
> *qpid*-proton-c-0.18.1-1.el7.x86_64
> python-*qpid*-qmf-1.37.0-1.el7.x86_64
> *qpid*-proton-debuginfo-0.18.1-1.el7.x86_64
> *qpid*-cpp-debuginfo-1.37.0-1.el7.x86_64
> *qpid*-cpp-client-devel-1.37.0-1.el7.x86_64
> *qpid*-cpp-server-1.37.0-1.el7.x86_64
> *qpid*-cpp-client-1.37.0-1.el7.x86_64
>
>Reporter: dan clark
>Priority: Blocker
> Labels: maven
> Attachments: drain.cpp, godrain.sh, gospout.sh, qpid-stat.out,
> spout.cpp, spout.log
>
> Original Estimate: 40h
> Remaining Estimate: 40h
>
> There may be multiple leaks of the outgoing message structure and associated
> fields when using the qpid::client::amqp0_10::SenderImpl::send function to
> publish messages under certain setups. I will concede that there may be
> options that are beyond my ken to ameliorate the leak of messages structures,
> especially since there is an indication that under prolonged runs (a
> demonized version of an application like spout) that the statistics for quidd
> indicate increased acquires with zero releases.
> The basic notion is illustrated with the test application spout (and drain).
> Consider a long running daemon reducing the overhead of open/send/close by
> keeping the message connection open for long periods of time. Then the logic
> would be: start application/open connection. In a loop send data (and never
> reach a close). Thus the drain application illustrates the behavior and
> demonstrates the leak using valgrind by sending the data followed by an
> exit(0).
> Note also the lack of 'releases' associated with the 'acquires' in the stats
> output.
> Capturing the leaks using the test applications spout/drain required adding
> an 'exit()' prior to the close, as during normal operations of a daemon, the
> connection remains open for a sustained period of time, thus the leak of
> structures within the c++ client library are found as structures still
> tracked by the library and cleaned up on 'connection.close()', but they
> should be cleaned up as a result of the completion of the send/receive ack or
> the termination of the life of the message based on the TTL of the message,
> which ever comes first. I have witnessed growth of the leaked structures
> into the millions of messages lasting more than 24hours with short (300sec)
> TTL of the messages based on scenarios attached using spout/drain as test
> vehicle.
> The attached spout.log uses a short 10message test and the
[jira] [Commented] (QPIDJMS-391) Add support for the use of native OpenSSL based providers
[ https://issues.apache.org/jira/browse/QPIDJMS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16567465#comment-16567465 ] ASF subversion and git services commented on QPIDJMS-391: - Commit d5cde3ed4de43d5c2462930a068da15afa916d1d in qpid-jms's branch refs/heads/master from [~tabish121] [ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=d5cde3e ] QPIDJMS-391 Add support for netty OpenSSL implementations Allow the client to utilize netty openssl features if available and configured to do so. The user will need to provide a netty-tcnative dependency to the classpath such as the boringssl uber jar and set the transport.useOpenSSL option to true. The tests use the boringssl library v2.0.12.Final to validate. Updates to Netty 4.1.28.Final which has some OpenSSL bindings fixes. > Add support for the use of native OpenSSL based providers > - > > Key: QPIDJMS-391 > URL: https://issues.apache.org/jira/browse/QPIDJMS-391 > Project: Qpid JMS > Issue Type: New Feature > Components: qpid-jms-client >Reporter: Johan Stenberg >Priority: Minor > Labels: performance > Fix For: 0.36.0 > > > It would be great to have an option to use netty-tcnative-boringssl-static > instead of the java based SSL provider. In the ActiveMQ Artemis this was > implemented as part of https://issues.apache.org/jira/browse/ARTEMIS-1649 > In Netty 4.1.26 a new OpenSslX509KeyManagerFactory for easier configuration > was introduced. https://github.com/netty/netty/pull/8084 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1842) [c] Dispatch/Proton crashes when opening/closing connections
[
https://issues.apache.org/jira/browse/PROTON-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16567461#comment-16567461
]
ASF GitHub Bot commented on PROTON-1842:
Github user alanconway commented on the issue:
https://github.com/apache/qpid-proton/pull/145
I think this makes sense but it makes my head hurt a bit.
> [c] Dispatch/Proton crashes when opening/closing connections
>
>
> Key: PROTON-1842
> URL: https://issues.apache.org/jira/browse/PROTON-1842
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.22.0
>Reporter: Chuck Rolke
>Assignee: Alan Conway
>Priority: Major
> Attachments: helloworld.cpp, race.tsan, race.vg
>
>
> Using proton cpp example code that is modified to open and close connections
> by the thousands in the main loop and having the event loop short circuit any
> messaging with:
> {{ void on_connection_open(proton::connection& c) {}}
> {{ c.close();}}
> {{ }}}
> and then directing this client example to a dispatch router 1.1.0. Eventually
> (after 100,000 to 1,000,000 connection open/closes) the router crashes with:
> {{qdrouterd: /home/chug/git/qpid-proton/c/src/proactor/epoll.c:466:
> wake_pop_front: Assertion `p->wakes_in_progress' failed.}}
> and with:
> {{qdrouterd: /home/chug/git/qpid-proton/c/src/proactor/epoll.c:2014:
> proactor_do_epoll: Assertion `ee->type == PCONNECTION_TIMER' failed.}}
> This issue seems to happen only with qpid-dispatch accepting the open/close
> event stream. Proton cpp example _server_direct_ and c example _direct_ work
> properly with the same open/close event stream mounting into the 10s of
> millions of connections.
> A core dump backtrace with the PCONNECTION_TIMER failure reads as:
> {{(gdb) bt}}
> {{#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51}}
> {{#1 0x7f795c712c41 in __GI_abort () at abort.c:79}}
> {{#2 0x7f795c709f7a in __assert_fail_base (fmt=0x7f795c85a260
> "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n",
> assertion=assertion@entry=0x7f795d72e15a "ee->type == PCONNECTION_TIMER", }}
> {{ file=file@entry=0x7f795d72de98
> "/home/chug/git/qpid-proton/c/src/proactor/epoll.c", line=line@entry=2014, }}
> {{ function=function@entry=0x7f795d72e320 <__PRETTY_FUNCTION__.6307>
> "proactor_do_epoll") at assert.c:92}}
> {{#3 0x7f795c709ff2 in __GI___assert_fail (assertion=0x7f795d72e15a
> "ee->type == PCONNECTION_TIMER", file=0x7f795d72de98
> "/home/chug/git/qpid-proton/c/src/proactor/epoll.c", line=2014, }}
> {{ function=0x7f795d72e320 <__PRETTY_FUNCTION__.6307> "proactor_do_epoll")
> at assert.c:101}}
> {{#4 0x7f795d72d29f in proactor_do_epoll (p=0x26b7310, can_block=true)
> at /home/chug/git/qpid-proton/c/src/proactor/epoll.c:2014}}
> {{#5 0x7f795d72d30e in pn_proactor_wait (p=0x26b7310) at
> /home/chug/git/qpid-proton/c/src/proactor/epoll.c:2030}}
> {{#6 0x7f795dbe89ad in thread_run (arg=0x26be750) at
> /home/chug/git/qpid-dispatch/src/server.c:946}}
> {{#7 0x7f795d50e50b in start_thread (arg=0x7f794f486700) at
> pthread_create.c:465}}
> {{#8 0x7f795c7d216f in clone () at
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:95}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton issue #145: Potential chained epoll impl for PROTON-1842
Github user alanconway commented on the issue: https://github.com/apache/qpid-proton/pull/145 I think this makes sense but it makes my head hurt a bit. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPIDJMS-391) Add support for the use of native OpenSSL based providers
[ https://issues.apache.org/jira/browse/QPIDJMS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated QPIDJMS-391: - Fix Version/s: 0.36.0 > Add support for the use of native OpenSSL based providers > - > > Key: QPIDJMS-391 > URL: https://issues.apache.org/jira/browse/QPIDJMS-391 > Project: Qpid JMS > Issue Type: New Feature > Components: qpid-jms-client >Reporter: Johan Stenberg >Priority: Minor > Labels: performance > Fix For: 0.36.0 > > > It would be great to have an option to use netty-tcnative-boringssl-static > instead of the java based SSL provider. In the ActiveMQ Artemis this was > implemented as part of https://issues.apache.org/jira/browse/ARTEMIS-1649 > In Netty 4.1.26 a new OpenSslX509KeyManagerFactory for easier configuration > was introduced. https://github.com/netty/netty/pull/8084 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPIDJMS-391) Add support for the use of native OpenSSL based providers
[ https://issues.apache.org/jira/browse/QPIDJMS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated QPIDJMS-391: - Summary: Add support for the use of native OpenSSL based providers (was: Add support for SSL provider netty-tcnative-boringssl-static) > Add support for the use of native OpenSSL based providers > - > > Key: QPIDJMS-391 > URL: https://issues.apache.org/jira/browse/QPIDJMS-391 > Project: Qpid JMS > Issue Type: New Feature > Components: qpid-jms-client >Reporter: Johan Stenberg >Priority: Minor > Labels: performance > Fix For: 0.36.0 > > > It would be great to have an option to use netty-tcnative-boringssl-static > instead of the java based SSL provider. In the ActiveMQ Artemis this was > implemented as part of https://issues.apache.org/jira/browse/ARTEMIS-1649 > In Netty 4.1.26 a new OpenSslX509KeyManagerFactory for easier configuration > was introduced. https://github.com/netty/netty/pull/8084 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1898) Memory leak related to sending
[ https://issues.apache.org/jira/browse/PROTON-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16567440#comment-16567440 ] Alan Conway commented on PROTON-1898: - May be the same underlying issue. > Memory leak related to sending > -- > > Key: PROTON-1898 > URL: https://issues.apache.org/jira/browse/PROTON-1898 > Project: Qpid Proton > Issue Type: Bug > Components: go-binding >Affects Versions: proton-c-0.24.0 >Reporter: Christoph >Assignee: Alan Conway >Priority: Major > > I started implementing a GO application using qpid electron. There is one > connection used to receive messages (at-least-once). It works nicely with low > memory consumption, multiple links and multiple go routines, 50 bytes > payload, up to 3000 msg/s > But as soon as the application starts sending messages (to reply over the > same connection) memory consumption is continuously growing up to 2GB where I > stopped. > Even if electron does not leave many options for wrong usage there might be > an issue in the application. > So I tried the qpid electron example > "https://github.com/apache/qpid-proton/blob/master/go/examples/electron/send.go;, > the same issue. > To reproduce it: > * use the sample program, I just added connection options for SASL PLAIN > * let it send 10 messages or more to one destination > My setup: > * windows 10 pro > * go1.10.2 windows/amd64 > * qpid 0.24.0-rc1 > * go files and lib build from same git repository clone and branch > * visual studio 2015, release build, no errors > * Broker: Solace VMR 8.11.0.1029 with different durable queues as source and > target > I tried also qpid proton 0.23.0 earlier, but saw the same problem. > I tried SendAsync and SendSync, both in 10-50 go routines in > parallel.Finally, with SendForget my worker routines were soon blocked and > did not come back. > Best regards > Christoph > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1095) Skipped system tests are marked as failed on rhel6
[
https://issues.apache.org/jira/browse/DISPATCH-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1095.
-
Resolution: Fixed
> Skipped system tests are marked as failed on rhel6
> ---
>
> Key: DISPATCH-1095
> URL: https://issues.apache.org/jira/browse/DISPATCH-1095
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.2.0
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.3.0
>
>
> {noformat}
> Start 27: system_tests_sasl_plain
> 27: Test command: /usr/bin/python "/foo/qpid-dispatch/build/tests/run.py"
> "-x" "unit2" "-v" "system_tests_sasl_plain"
> 27: Test timeout computed to be: 1500
> 27: test_inter_router_plain_exists
> (system_tests_sasl_plain.RouterTestPlainSasl) ... ERROR
> 27: test_qdstat_connect_sasl (system_tests_sasl_plain.RouterTestPlainSasl)
> ... ERROR
> 27: test_qdstat_connect_sasl_password_file
> (system_tests_sasl_plain.RouterTestPlainSasl) ... ERROR
> 27: test__teardown_class (system_tests_sasl_plain.RouterTestPlainSasl)
> 27: Fake test to call tearDownClass ... ok
> 27: test__teardown_class
> (system_tests_sasl_plain.RouterTestPlainSaslCommon)
> 27: Fake test to call tearDownClass ... ok
> 27: test_aaa_qdstat_connect_sasl_over_ssl
> (system_tests_sasl_plain.RouterTestPlainSaslOverSsl) ... ERROR
> 27: test_inter_router_plain_over_ssl_exists
> (system_tests_sasl_plain.RouterTestPlainSaslOverSsl)
> 27: The setUpClass sets up two routers with SASL PLAIN enabled over TLS. ...
> ERROR
> 27: test__teardown_class
> (system_tests_sasl_plain.RouterTestPlainSaslOverSsl)
> 27: Fake test to call tearDownClass ... ok
> 27: test_inter_router_plain_over_ssl_exists
> (system_tests_sasl_plain.RouterTestVerifyHostNameNo) ... ERROR
> 27: test_zzz_delete_create_ssl_profile
> (system_tests_sasl_plain.RouterTestVerifyHostNameNo) ... ERROR
> 27: test__teardown_class
> (system_tests_sasl_plain.RouterTestVerifyHostNameNo)
> 27: Fake test to call tearDownClass ... ok
> 27: test_no_inter_router_connection
> (system_tests_sasl_plain.RouterTestVerifyHostNameYes) ... ERROR
> 27: test__teardown_class
> (system_tests_sasl_plain.RouterTestVerifyHostNameYes)
> 27: Fake test to call tearDownClass ... ok
> 27: test__teardown_class (system_test.TestCase)
> 27: Fake test to call tearDownClass ... ok
> 27:
> 27: ==
> 27: ERROR: test_inter_router_plain_exists
> (system_tests_sasl_plain.RouterTestPlainSasl)
> 27: --
> 27: Traceback (most recent call last):
> 27: File "/foo/qpid-dispatch/tests/system_tests_sasl_plain.py", line 128,
> in test_inter_router_plain_exists
> 27: ['qdstat', '-b', str(self.routers[0].addresses[1]), '-c'],
> 27: AttributeError: 'RouterTestPlainSasl' object has no attribute 'routers'
> 27:
> 27: ==
> 27: ERROR: test_qdstat_connect_sasl
> (system_tests_sasl_plain.RouterTestPlainSasl)
> 27: --
> 27: Traceback (most recent call last):
> 27: File "/foo/qpid-dispatch/tests/system_tests_sasl_plain.py", line 147,
> in test_qdstat_connect_sasl
> 27: ['qdstat', '-b', str(self.routers[0].addresses[2]), '-c',
> '--sasl-mechanisms=PLAIN',
> 27: AttributeError: 'RouterTestPlainSasl' object has no attribute 'routers'
> 27:
> 27: ==
> 27: ERROR: test_qdstat_connect_sasl_password_file
> (system_tests_sasl_plain.RouterTestPlainSasl)
> 27: --
> 27: Traceback (most recent call last):
> 27: File "/foo/qpid-dispatch/tests/system_tests_sasl_plain.py", line 179,
> in test_qdstat_connect_sasl_password_file
> 27: ['qdstat', '-b', str(self.routers[0].addresses[2]), '-c',
> '--sasl-mechanisms=PLAIN',
> 27: AttributeError: 'RouterTestPlainSasl' object has no attribute 'routers'
> 27:
> 27: ==
> 27: ERROR: test_aaa_qdstat_connect_sasl_over_ssl
> (system_tests_sasl_plain.RouterTestPlainSaslOverSsl)
> 27: --
> 27: Traceback (most recent call last):
> 27: File "/foo/qpid-dispatch/tests/system_tests_sasl_plain.py", line 279,
> in test_aaa_qdstat_connect_sasl_over_ssl
> 27: ['qdstat', '-b', str(self.routers[0].addresses[2]), '-c',
> 27: AttributeError: 'RouterTestPlainSaslOverSsl' object has no attribute
> 'routers'
> 27:
> 27: ==
> 27: ERROR:
[jira] [Commented] (DISPATCH-1095) Skipped system tests are marked as failed on rhel6
[
https://issues.apache.org/jira/browse/DISPATCH-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16567427#comment-16567427
]
ASF GitHub Bot commented on DISPATCH-1095:
--
Github user asfgit closed the pull request at:
https://github.com/apache/qpid-dispatch/pull/351
> Skipped system tests are marked as failed on rhel6
> ---
>
> Key: DISPATCH-1095
> URL: https://issues.apache.org/jira/browse/DISPATCH-1095
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.2.0
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.3.0
>
>
> {noformat}
> Start 27: system_tests_sasl_plain
> 27: Test command: /usr/bin/python "/foo/qpid-dispatch/build/tests/run.py"
> "-x" "unit2" "-v" "system_tests_sasl_plain"
> 27: Test timeout computed to be: 1500
> 27: test_inter_router_plain_exists
> (system_tests_sasl_plain.RouterTestPlainSasl) ... ERROR
> 27: test_qdstat_connect_sasl (system_tests_sasl_plain.RouterTestPlainSasl)
> ... ERROR
> 27: test_qdstat_connect_sasl_password_file
> (system_tests_sasl_plain.RouterTestPlainSasl) ... ERROR
> 27: test__teardown_class (system_tests_sasl_plain.RouterTestPlainSasl)
> 27: Fake test to call tearDownClass ... ok
> 27: test__teardown_class
> (system_tests_sasl_plain.RouterTestPlainSaslCommon)
> 27: Fake test to call tearDownClass ... ok
> 27: test_aaa_qdstat_connect_sasl_over_ssl
> (system_tests_sasl_plain.RouterTestPlainSaslOverSsl) ... ERROR
> 27: test_inter_router_plain_over_ssl_exists
> (system_tests_sasl_plain.RouterTestPlainSaslOverSsl)
> 27: The setUpClass sets up two routers with SASL PLAIN enabled over TLS. ...
> ERROR
> 27: test__teardown_class
> (system_tests_sasl_plain.RouterTestPlainSaslOverSsl)
> 27: Fake test to call tearDownClass ... ok
> 27: test_inter_router_plain_over_ssl_exists
> (system_tests_sasl_plain.RouterTestVerifyHostNameNo) ... ERROR
> 27: test_zzz_delete_create_ssl_profile
> (system_tests_sasl_plain.RouterTestVerifyHostNameNo) ... ERROR
> 27: test__teardown_class
> (system_tests_sasl_plain.RouterTestVerifyHostNameNo)
> 27: Fake test to call tearDownClass ... ok
> 27: test_no_inter_router_connection
> (system_tests_sasl_plain.RouterTestVerifyHostNameYes) ... ERROR
> 27: test__teardown_class
> (system_tests_sasl_plain.RouterTestVerifyHostNameYes)
> 27: Fake test to call tearDownClass ... ok
> 27: test__teardown_class (system_test.TestCase)
> 27: Fake test to call tearDownClass ... ok
> 27:
> 27: ==
> 27: ERROR: test_inter_router_plain_exists
> (system_tests_sasl_plain.RouterTestPlainSasl)
> 27: --
> 27: Traceback (most recent call last):
> 27: File "/foo/qpid-dispatch/tests/system_tests_sasl_plain.py", line 128,
> in test_inter_router_plain_exists
> 27: ['qdstat', '-b', str(self.routers[0].addresses[1]), '-c'],
> 27: AttributeError: 'RouterTestPlainSasl' object has no attribute 'routers'
> 27:
> 27: ==
> 27: ERROR: test_qdstat_connect_sasl
> (system_tests_sasl_plain.RouterTestPlainSasl)
> 27: --
> 27: Traceback (most recent call last):
> 27: File "/foo/qpid-dispatch/tests/system_tests_sasl_plain.py", line 147,
> in test_qdstat_connect_sasl
> 27: ['qdstat', '-b', str(self.routers[0].addresses[2]), '-c',
> '--sasl-mechanisms=PLAIN',
> 27: AttributeError: 'RouterTestPlainSasl' object has no attribute 'routers'
> 27:
> 27: ==
> 27: ERROR: test_qdstat_connect_sasl_password_file
> (system_tests_sasl_plain.RouterTestPlainSasl)
> 27: --
> 27: Traceback (most recent call last):
> 27: File "/foo/qpid-dispatch/tests/system_tests_sasl_plain.py", line 179,
> in test_qdstat_connect_sasl_password_file
> 27: ['qdstat', '-b', str(self.routers[0].addresses[2]), '-c',
> '--sasl-mechanisms=PLAIN',
> 27: AttributeError: 'RouterTestPlainSasl' object has no attribute 'routers'
> 27:
> 27: ==
> 27: ERROR: test_aaa_qdstat_connect_sasl_over_ssl
> (system_tests_sasl_plain.RouterTestPlainSaslOverSsl)
> 27: --
> 27: Traceback (most recent call last):
> 27: File "/foo/qpid-dispatch/tests/system_tests_sasl_plain.py", line 279,
> in test_aaa_qdstat_connect_sasl_over_ssl
> 27: ['qdstat', '-b', str(self.routers[0].addresses[2]), '-c',
> 27: AttributeError: 'RouterTestPlainSaslOverSsl' object has no attribute
> 'routers'
>
[GitHub] qpid-dispatch pull request #351: DISPATCH-1095 - Improved SkipIfNeeded decor...
Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/351 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1095) Skipped system tests are marked as failed on rhel6
[
https://issues.apache.org/jira/browse/DISPATCH-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16567426#comment-16567426
]
ASF subversion and git services commented on DISPATCH-1095:
---
Commit a1585a9c3f3f5ed2aa34c7b95c357256aa9e534a in qpid-dispatch's branch
refs/heads/master from [~fgiorget]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=a1585a9 ]
DISPATCH-1095 - Improved SkipIfNeeded decorator and added it to methods using
SASL when it is not installed. This closes #351
> Skipped system tests are marked as failed on rhel6
> ---
>
> Key: DISPATCH-1095
> URL: https://issues.apache.org/jira/browse/DISPATCH-1095
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.2.0
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.3.0
>
>
> {noformat}
> Start 27: system_tests_sasl_plain
> 27: Test command: /usr/bin/python "/foo/qpid-dispatch/build/tests/run.py"
> "-x" "unit2" "-v" "system_tests_sasl_plain"
> 27: Test timeout computed to be: 1500
> 27: test_inter_router_plain_exists
> (system_tests_sasl_plain.RouterTestPlainSasl) ... ERROR
> 27: test_qdstat_connect_sasl (system_tests_sasl_plain.RouterTestPlainSasl)
> ... ERROR
> 27: test_qdstat_connect_sasl_password_file
> (system_tests_sasl_plain.RouterTestPlainSasl) ... ERROR
> 27: test__teardown_class (system_tests_sasl_plain.RouterTestPlainSasl)
> 27: Fake test to call tearDownClass ... ok
> 27: test__teardown_class
> (system_tests_sasl_plain.RouterTestPlainSaslCommon)
> 27: Fake test to call tearDownClass ... ok
> 27: test_aaa_qdstat_connect_sasl_over_ssl
> (system_tests_sasl_plain.RouterTestPlainSaslOverSsl) ... ERROR
> 27: test_inter_router_plain_over_ssl_exists
> (system_tests_sasl_plain.RouterTestPlainSaslOverSsl)
> 27: The setUpClass sets up two routers with SASL PLAIN enabled over TLS. ...
> ERROR
> 27: test__teardown_class
> (system_tests_sasl_plain.RouterTestPlainSaslOverSsl)
> 27: Fake test to call tearDownClass ... ok
> 27: test_inter_router_plain_over_ssl_exists
> (system_tests_sasl_plain.RouterTestVerifyHostNameNo) ... ERROR
> 27: test_zzz_delete_create_ssl_profile
> (system_tests_sasl_plain.RouterTestVerifyHostNameNo) ... ERROR
> 27: test__teardown_class
> (system_tests_sasl_plain.RouterTestVerifyHostNameNo)
> 27: Fake test to call tearDownClass ... ok
> 27: test_no_inter_router_connection
> (system_tests_sasl_plain.RouterTestVerifyHostNameYes) ... ERROR
> 27: test__teardown_class
> (system_tests_sasl_plain.RouterTestVerifyHostNameYes)
> 27: Fake test to call tearDownClass ... ok
> 27: test__teardown_class (system_test.TestCase)
> 27: Fake test to call tearDownClass ... ok
> 27:
> 27: ==
> 27: ERROR: test_inter_router_plain_exists
> (system_tests_sasl_plain.RouterTestPlainSasl)
> 27: --
> 27: Traceback (most recent call last):
> 27: File "/foo/qpid-dispatch/tests/system_tests_sasl_plain.py", line 128,
> in test_inter_router_plain_exists
> 27: ['qdstat', '-b', str(self.routers[0].addresses[1]), '-c'],
> 27: AttributeError: 'RouterTestPlainSasl' object has no attribute 'routers'
> 27:
> 27: ==
> 27: ERROR: test_qdstat_connect_sasl
> (system_tests_sasl_plain.RouterTestPlainSasl)
> 27: --
> 27: Traceback (most recent call last):
> 27: File "/foo/qpid-dispatch/tests/system_tests_sasl_plain.py", line 147,
> in test_qdstat_connect_sasl
> 27: ['qdstat', '-b', str(self.routers[0].addresses[2]), '-c',
> '--sasl-mechanisms=PLAIN',
> 27: AttributeError: 'RouterTestPlainSasl' object has no attribute 'routers'
> 27:
> 27: ==
> 27: ERROR: test_qdstat_connect_sasl_password_file
> (system_tests_sasl_plain.RouterTestPlainSasl)
> 27: --
> 27: Traceback (most recent call last):
> 27: File "/foo/qpid-dispatch/tests/system_tests_sasl_plain.py", line 179,
> in test_qdstat_connect_sasl_password_file
> 27: ['qdstat', '-b', str(self.routers[0].addresses[2]), '-c',
> '--sasl-mechanisms=PLAIN',
> 27: AttributeError: 'RouterTestPlainSasl' object has no attribute 'routers'
> 27:
> 27: ==
> 27: ERROR: test_aaa_qdstat_connect_sasl_over_ssl
> (system_tests_sasl_plain.RouterTestPlainSaslOverSsl)
> 27: --
> 27: Traceback (most recent call last):
> 27: File
[jira] [Commented] (DISPATCH-1095) Skipped system tests are marked as failed on rhel6
[
https://issues.apache.org/jira/browse/DISPATCH-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16567398#comment-16567398
]
ASF GitHub Bot commented on DISPATCH-1095:
--
GitHub user fgiorgetti opened a pull request:
https://github.com/apache/qpid-dispatch/pull/351
DISPATCH-1095 - Improved SkipIfNeeded decorator and added it to metho…
…ds using SASL when it is not installed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/fgiorgetti/qpid-dispatch
fgiorgetti-DISPATCH-1095
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/qpid-dispatch/pull/351.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #351
commit 81504e94502807f8434c28715d9b2aab0845df47
Author: Fernando Giorgetti
Date: 2018-08-02T19:29:23Z
DISPATCH-1095 - Improved SkipIfNeeded decorator and added it to methods
using SASL when it is not installed
> Skipped system tests are marked as failed on rhel6
> ---
>
> Key: DISPATCH-1095
> URL: https://issues.apache.org/jira/browse/DISPATCH-1095
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.2.0
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.3.0
>
>
> {noformat}
> Start 27: system_tests_sasl_plain
> 27: Test command: /usr/bin/python "/foo/qpid-dispatch/build/tests/run.py"
> "-x" "unit2" "-v" "system_tests_sasl_plain"
> 27: Test timeout computed to be: 1500
> 27: test_inter_router_plain_exists
> (system_tests_sasl_plain.RouterTestPlainSasl) ... ERROR
> 27: test_qdstat_connect_sasl (system_tests_sasl_plain.RouterTestPlainSasl)
> ... ERROR
> 27: test_qdstat_connect_sasl_password_file
> (system_tests_sasl_plain.RouterTestPlainSasl) ... ERROR
> 27: test__teardown_class (system_tests_sasl_plain.RouterTestPlainSasl)
> 27: Fake test to call tearDownClass ... ok
> 27: test__teardown_class
> (system_tests_sasl_plain.RouterTestPlainSaslCommon)
> 27: Fake test to call tearDownClass ... ok
> 27: test_aaa_qdstat_connect_sasl_over_ssl
> (system_tests_sasl_plain.RouterTestPlainSaslOverSsl) ... ERROR
> 27: test_inter_router_plain_over_ssl_exists
> (system_tests_sasl_plain.RouterTestPlainSaslOverSsl)
> 27: The setUpClass sets up two routers with SASL PLAIN enabled over TLS. ...
> ERROR
> 27: test__teardown_class
> (system_tests_sasl_plain.RouterTestPlainSaslOverSsl)
> 27: Fake test to call tearDownClass ... ok
> 27: test_inter_router_plain_over_ssl_exists
> (system_tests_sasl_plain.RouterTestVerifyHostNameNo) ... ERROR
> 27: test_zzz_delete_create_ssl_profile
> (system_tests_sasl_plain.RouterTestVerifyHostNameNo) ... ERROR
> 27: test__teardown_class
> (system_tests_sasl_plain.RouterTestVerifyHostNameNo)
> 27: Fake test to call tearDownClass ... ok
> 27: test_no_inter_router_connection
> (system_tests_sasl_plain.RouterTestVerifyHostNameYes) ... ERROR
> 27: test__teardown_class
> (system_tests_sasl_plain.RouterTestVerifyHostNameYes)
> 27: Fake test to call tearDownClass ... ok
> 27: test__teardown_class (system_test.TestCase)
> 27: Fake test to call tearDownClass ... ok
> 27:
> 27: ==
> 27: ERROR: test_inter_router_plain_exists
> (system_tests_sasl_plain.RouterTestPlainSasl)
> 27: --
> 27: Traceback (most recent call last):
> 27: File "/foo/qpid-dispatch/tests/system_tests_sasl_plain.py", line 128,
> in test_inter_router_plain_exists
> 27: ['qdstat', '-b', str(self.routers[0].addresses[1]), '-c'],
> 27: AttributeError: 'RouterTestPlainSasl' object has no attribute 'routers'
> 27:
> 27: ==
> 27: ERROR: test_qdstat_connect_sasl
> (system_tests_sasl_plain.RouterTestPlainSasl)
> 27: --
> 27: Traceback (most recent call last):
> 27: File "/foo/qpid-dispatch/tests/system_tests_sasl_plain.py", line 147,
> in test_qdstat_connect_sasl
> 27: ['qdstat', '-b', str(self.routers[0].addresses[2]), '-c',
> '--sasl-mechanisms=PLAIN',
> 27: AttributeError: 'RouterTestPlainSasl' object has no attribute 'routers'
> 27:
> 27: ==
> 27: ERROR: test_qdstat_connect_sasl_password_file
> (system_tests_sasl_plain.RouterTestPlainSasl)
> 27: --
> 27: Traceback (most recent call last):
> 27: File "/foo/qpid-dispatch/tests/system_tests_sasl_plain.py", line 179,
> in
[GitHub] qpid-dispatch pull request #351: DISPATCH-1095 - Improved SkipIfNeeded decor...
GitHub user fgiorgetti opened a pull request: https://github.com/apache/qpid-dispatch/pull/351 DISPATCH-1095 - Improved SkipIfNeeded decorator and added it to metho⦠â¦ds using SASL when it is not installed You can merge this pull request into a Git repository by running: $ git pull https://github.com/fgiorgetti/qpid-dispatch fgiorgetti-DISPATCH-1095 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/351.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #351 commit 81504e94502807f8434c28715d9b2aab0845df47 Author: Fernando Giorgetti Date: 2018-08-02T19:29:23Z DISPATCH-1095 - Improved SkipIfNeeded decorator and added it to methods using SASL when it is not installed --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (PROTON-1909) c broker example does not seem to cope with sasl
[ https://issues.apache.org/jira/browse/PROTON-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim closed PROTON-1909. -- Resolution: Duplicate > c broker example does not seem to cope with sasl > > > Key: PROTON-1909 > URL: https://issues.apache.org/jira/browse/PROTON-1909 > Project: Qpid Proton > Issue Type: Improvement > Components: examples >Reporter: Gordon Sim >Priority: Minor > > therefore cannot be used by default with e.g. python helloworld.py as python > has a sasl layer on by default. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1909) c broker example does not seem to cope with sasl
Gordon Sim created PROTON-1909: -- Summary: c broker example does not seem to cope with sasl Key: PROTON-1909 URL: https://issues.apache.org/jira/browse/PROTON-1909 Project: Qpid Proton Issue Type: Improvement Components: examples Reporter: Gordon Sim therefore cannot be used by default with e.g. python helloworld.py as python has a sasl layer on by default. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1908) cpp broker example is very slow
Gordon Sim created PROTON-1908: -- Summary: cpp broker example is very slow Key: PROTON-1908 URL: https://issues.apache.org/jira/browse/PROTON-1908 Project: Qpid Proton Issue Type: Improvement Reporter: Gordon Sim The c++ broker example is an order of magnitude slower than the c version. Using qpid-send/qpid-receive I can get ~70,000 msgs/sec with c broker, only ~7500 msgs/sec on c++ version. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1095) Skipped system tests are marked as failed on rhel6
[
https://issues.apache.org/jira/browse/DISPATCH-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16567293#comment-16567293
]
Ganesh Murthy commented on DISPATCH-1095:
-
unittest2 does not support skipping feature on python 2.6
Look at https://issues.apache.org/jira/browse/DISPATCH-963
Adapt that fix to fix this issue
> Skipped system tests are marked as failed on rhel6
> ---
>
> Key: DISPATCH-1095
> URL: https://issues.apache.org/jira/browse/DISPATCH-1095
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.2.0
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.3.0
>
>
> {noformat}
> Start 27: system_tests_sasl_plain
> 27: Test command: /usr/bin/python "/foo/qpid-dispatch/build/tests/run.py"
> "-x" "unit2" "-v" "system_tests_sasl_plain"
> 27: Test timeout computed to be: 1500
> 27: test_inter_router_plain_exists
> (system_tests_sasl_plain.RouterTestPlainSasl) ... ERROR
> 27: test_qdstat_connect_sasl (system_tests_sasl_plain.RouterTestPlainSasl)
> ... ERROR
> 27: test_qdstat_connect_sasl_password_file
> (system_tests_sasl_plain.RouterTestPlainSasl) ... ERROR
> 27: test__teardown_class (system_tests_sasl_plain.RouterTestPlainSasl)
> 27: Fake test to call tearDownClass ... ok
> 27: test__teardown_class
> (system_tests_sasl_plain.RouterTestPlainSaslCommon)
> 27: Fake test to call tearDownClass ... ok
> 27: test_aaa_qdstat_connect_sasl_over_ssl
> (system_tests_sasl_plain.RouterTestPlainSaslOverSsl) ... ERROR
> 27: test_inter_router_plain_over_ssl_exists
> (system_tests_sasl_plain.RouterTestPlainSaslOverSsl)
> 27: The setUpClass sets up two routers with SASL PLAIN enabled over TLS. ...
> ERROR
> 27: test__teardown_class
> (system_tests_sasl_plain.RouterTestPlainSaslOverSsl)
> 27: Fake test to call tearDownClass ... ok
> 27: test_inter_router_plain_over_ssl_exists
> (system_tests_sasl_plain.RouterTestVerifyHostNameNo) ... ERROR
> 27: test_zzz_delete_create_ssl_profile
> (system_tests_sasl_plain.RouterTestVerifyHostNameNo) ... ERROR
> 27: test__teardown_class
> (system_tests_sasl_plain.RouterTestVerifyHostNameNo)
> 27: Fake test to call tearDownClass ... ok
> 27: test_no_inter_router_connection
> (system_tests_sasl_plain.RouterTestVerifyHostNameYes) ... ERROR
> 27: test__teardown_class
> (system_tests_sasl_plain.RouterTestVerifyHostNameYes)
> 27: Fake test to call tearDownClass ... ok
> 27: test__teardown_class (system_test.TestCase)
> 27: Fake test to call tearDownClass ... ok
> 27:
> 27: ==
> 27: ERROR: test_inter_router_plain_exists
> (system_tests_sasl_plain.RouterTestPlainSasl)
> 27: --
> 27: Traceback (most recent call last):
> 27: File "/foo/qpid-dispatch/tests/system_tests_sasl_plain.py", line 128,
> in test_inter_router_plain_exists
> 27: ['qdstat', '-b', str(self.routers[0].addresses[1]), '-c'],
> 27: AttributeError: 'RouterTestPlainSasl' object has no attribute 'routers'
> 27:
> 27: ==
> 27: ERROR: test_qdstat_connect_sasl
> (system_tests_sasl_plain.RouterTestPlainSasl)
> 27: --
> 27: Traceback (most recent call last):
> 27: File "/foo/qpid-dispatch/tests/system_tests_sasl_plain.py", line 147,
> in test_qdstat_connect_sasl
> 27: ['qdstat', '-b', str(self.routers[0].addresses[2]), '-c',
> '--sasl-mechanisms=PLAIN',
> 27: AttributeError: 'RouterTestPlainSasl' object has no attribute 'routers'
> 27:
> 27: ==
> 27: ERROR: test_qdstat_connect_sasl_password_file
> (system_tests_sasl_plain.RouterTestPlainSasl)
> 27: --
> 27: Traceback (most recent call last):
> 27: File "/foo/qpid-dispatch/tests/system_tests_sasl_plain.py", line 179,
> in test_qdstat_connect_sasl_password_file
> 27: ['qdstat', '-b', str(self.routers[0].addresses[2]), '-c',
> '--sasl-mechanisms=PLAIN',
> 27: AttributeError: 'RouterTestPlainSasl' object has no attribute 'routers'
> 27:
> 27: ==
> 27: ERROR: test_aaa_qdstat_connect_sasl_over_ssl
> (system_tests_sasl_plain.RouterTestPlainSaslOverSsl)
> 27: --
> 27: Traceback (most recent call last):
> 27: File "/foo/qpid-dispatch/tests/system_tests_sasl_plain.py", line 279,
> in test_aaa_qdstat_connect_sasl_over_ssl
> 27: ['qdstat', '-b', str(self.routers[0].addresses[2]), '-c',
> 27: AttributeError:
[jira] [Updated] (PROTON-1908) cpp broker example is very slow
[ https://issues.apache.org/jira/browse/PROTON-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated PROTON-1908: --- Component/s: examples > cpp broker example is very slow > --- > > Key: PROTON-1908 > URL: https://issues.apache.org/jira/browse/PROTON-1908 > Project: Qpid Proton > Issue Type: Improvement > Components: examples >Reporter: Gordon Sim >Priority: Minor > > The c++ broker example is an order of magnitude slower than the c version. > Using qpid-send/qpid-receive I can get ~70,000 msgs/sec with c broker, only > ~7500 msgs/sec on c++ version. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1095) Skipped system tests are marked as failed on rhel6
Ganesh Murthy created DISPATCH-1095:
---
Summary: Skipped system tests are marked as failed on rhel6
Key: DISPATCH-1095
URL: https://issues.apache.org/jira/browse/DISPATCH-1095
Project: Qpid Dispatch
Issue Type: Bug
Components: Tests
Affects Versions: 1.2.0
Reporter: Ganesh Murthy
Fix For: 1.3.0
{noformat}
Start 27: system_tests_sasl_plain
27: Test command: /usr/bin/python "/foo/qpid-dispatch/build/tests/run.py" "-x"
"unit2" "-v" "system_tests_sasl_plain"
27: Test timeout computed to be: 1500
27: test_inter_router_plain_exists
(system_tests_sasl_plain.RouterTestPlainSasl) ... ERROR
27: test_qdstat_connect_sasl (system_tests_sasl_plain.RouterTestPlainSasl) ...
ERROR
27: test_qdstat_connect_sasl_password_file
(system_tests_sasl_plain.RouterTestPlainSasl) ... ERROR
27: test__teardown_class (system_tests_sasl_plain.RouterTestPlainSasl)
27: Fake test to call tearDownClass ... ok
27: test__teardown_class (system_tests_sasl_plain.RouterTestPlainSaslCommon)
27: Fake test to call tearDownClass ... ok
27: test_aaa_qdstat_connect_sasl_over_ssl
(system_tests_sasl_plain.RouterTestPlainSaslOverSsl) ... ERROR
27: test_inter_router_plain_over_ssl_exists
(system_tests_sasl_plain.RouterTestPlainSaslOverSsl)
27: The setUpClass sets up two routers with SASL PLAIN enabled over TLS. ...
ERROR
27: test__teardown_class
(system_tests_sasl_plain.RouterTestPlainSaslOverSsl)
27: Fake test to call tearDownClass ... ok
27: test_inter_router_plain_over_ssl_exists
(system_tests_sasl_plain.RouterTestVerifyHostNameNo) ... ERROR
27: test_zzz_delete_create_ssl_profile
(system_tests_sasl_plain.RouterTestVerifyHostNameNo) ... ERROR
27: test__teardown_class
(system_tests_sasl_plain.RouterTestVerifyHostNameNo)
27: Fake test to call tearDownClass ... ok
27: test_no_inter_router_connection
(system_tests_sasl_plain.RouterTestVerifyHostNameYes) ... ERROR
27: test__teardown_class
(system_tests_sasl_plain.RouterTestVerifyHostNameYes)
27: Fake test to call tearDownClass ... ok
27: test__teardown_class (system_test.TestCase)
27: Fake test to call tearDownClass ... ok
27:
27: ==
27: ERROR: test_inter_router_plain_exists
(system_tests_sasl_plain.RouterTestPlainSasl)
27: --
27: Traceback (most recent call last):
27: File "/foo/qpid-dispatch/tests/system_tests_sasl_plain.py", line 128, in
test_inter_router_plain_exists
27: ['qdstat', '-b', str(self.routers[0].addresses[1]), '-c'],
27: AttributeError: 'RouterTestPlainSasl' object has no attribute 'routers'
27:
27: ==
27: ERROR: test_qdstat_connect_sasl
(system_tests_sasl_plain.RouterTestPlainSasl)
27: --
27: Traceback (most recent call last):
27: File "/foo/qpid-dispatch/tests/system_tests_sasl_plain.py", line 147, in
test_qdstat_connect_sasl
27: ['qdstat', '-b', str(self.routers[0].addresses[2]), '-c',
'--sasl-mechanisms=PLAIN',
27: AttributeError: 'RouterTestPlainSasl' object has no attribute 'routers'
27:
27: ==
27: ERROR: test_qdstat_connect_sasl_password_file
(system_tests_sasl_plain.RouterTestPlainSasl)
27: --
27: Traceback (most recent call last):
27: File "/foo/qpid-dispatch/tests/system_tests_sasl_plain.py", line 179, in
test_qdstat_connect_sasl_password_file
27: ['qdstat', '-b', str(self.routers[0].addresses[2]), '-c',
'--sasl-mechanisms=PLAIN',
27: AttributeError: 'RouterTestPlainSasl' object has no attribute 'routers'
27:
27: ==
27: ERROR: test_aaa_qdstat_connect_sasl_over_ssl
(system_tests_sasl_plain.RouterTestPlainSaslOverSsl)
27: --
27: Traceback (most recent call last):
27: File "/foo/qpid-dispatch/tests/system_tests_sasl_plain.py", line 279, in
test_aaa_qdstat_connect_sasl_over_ssl
27: ['qdstat', '-b', str(self.routers[0].addresses[2]), '-c',
27: AttributeError: 'RouterTestPlainSaslOverSsl' object has no attribute
'routers'
27:
27: ==
27: ERROR: test_inter_router_plain_over_ssl_exists
(system_tests_sasl_plain.RouterTestPlainSaslOverSsl)
27: The setUpClass sets up two routers with SASL PLAIN enabled over TLS.
27: --
27: Traceback (most recent call last):
27: File "/foo/qpid-dispatch/tests/system_tests_sasl_plain.py", line 319, in
test_inter_router_plain_over_ssl_exists
27: local_node =
[jira] [Resolved] (PROTON-1906) duplicating an empty composite buffer can lead to NPE
[ https://issues.apache.org/jira/browse/PROTON-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-1906. Resolution: Fixed Fix Version/s: (was: proton-j-0.29.0) proton-j-0.28.1 proton-j-0.27.3 > duplicating an empty composite buffer can lead to NPE > - > > Key: PROTON-1906 > URL: https://issues.apache.org/jira/browse/PROTON-1906 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Affects Versions: proton-j-0.27.0, proton-j-0.27.1, proton-j-0.27.2, > proton-j-0.28.0 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: proton-j-0.27.3, proton-j-0.28.1 > > > Duplicating an empty composite buffer can lead to NPE (but may not, depending > on how it came to exist and be in that state). -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1906) duplicating an empty composite buffer can lead to NPE
[ https://issues.apache.org/jira/browse/PROTON-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16567014#comment-16567014 ] ASF subversion and git services commented on PROTON-1906: - Commit 3db1d9c5a0a559e4b4badac91f00546253bc5c27 in qpid-proton-j's branch refs/heads/0.27.x from [~gemmellr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton-j.git;h=3db1d9c ] PROTON-1906: avoid potential NPE when duplicating composite buffer (cherry picked from commit 6b7750775bf57d05f9a8f29d79e7fc3e38a8d0a1) > duplicating an empty composite buffer can lead to NPE > - > > Key: PROTON-1906 > URL: https://issues.apache.org/jira/browse/PROTON-1906 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Affects Versions: proton-j-0.27.0, proton-j-0.27.1, proton-j-0.27.2, > proton-j-0.28.0 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: proton-j-0.29.0 > > > Duplicating an empty composite buffer can lead to NPE (but may not, depending > on how it came to exist and be in that state). -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1907) [electron/go] Memory leak seen when AtLeastOnce is used
Aaron Smith created PROTON-1907: --- Summary: [electron/go] Memory leak seen when AtLeastOnce is used Key: PROTON-1907 URL: https://issues.apache.org/jira/browse/PROTON-1907 Project: Qpid Proton Issue Type: Bug Components: go-binding Affects Versions: proton-c-0.24.0 Environment: RHEL 7.5, Go 1.10.2 Reporter: Aaron Smith Assignee: Alan Conway The test program located here: [https://github.com/redhat-nfvpe/telemetry-bench] runs out of memory when AtLeastOnce is enabled instead of AtMostOnce. The program tests throughput and connects to a 1.2 QDR. The program is generating about 20k messages per second and all messages are being ack'd. However, the program memory quickly hits several gigabytes and eventually crashes due to a lack of memory. When the the LinkOption is set to AtMostOnce, the program runs for hours with steady memory usage. The problem also occurs on fedora with proton-c-0.22. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1906) duplicating an empty composite buffer can lead to NPE
[ https://issues.apache.org/jira/browse/PROTON-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16567012#comment-16567012 ] ASF subversion and git services commented on PROTON-1906: - Commit 6b7750775bf57d05f9a8f29d79e7fc3e38a8d0a1 in qpid-proton-j's branch refs/heads/master from [~gemmellr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton-j.git;h=6b77507 ] PROTON-1906: avoid potential NPE when duplicating composite buffer > duplicating an empty composite buffer can lead to NPE > - > > Key: PROTON-1906 > URL: https://issues.apache.org/jira/browse/PROTON-1906 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Affects Versions: proton-j-0.27.0, proton-j-0.27.1, proton-j-0.27.2, > proton-j-0.28.0 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: proton-j-0.29.0 > > > Duplicating an empty composite buffer can lead to NPE (but may not, depending > on how it came to exist and be in that state). -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1906) duplicating an empty composite buffer can lead to NPE
Robbie Gemmell created PROTON-1906: -- Summary: duplicating an empty composite buffer can lead to NPE Key: PROTON-1906 URL: https://issues.apache.org/jira/browse/PROTON-1906 Project: Qpid Proton Issue Type: Bug Components: proton-j Affects Versions: proton-j-0.28.0, proton-j-0.27.2, proton-j-0.27.1, proton-j-0.27.0 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: proton-j-0.29.0 Duplicating an empty composite buffer can lead to NPE (but may not, depending on how it came to exist and be in that state). -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1092) in some cases qdrouterd crashes due to stale pn_session_t
[ https://issues.apache.org/jira/browse/DISPATCH-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved DISPATCH-1092. -- Resolution: Fixed Issue reproduced by having a "test" broker force the session to close when the link route closes. Unit test added. > in some cases qdrouterd crashes due to stale pn_session_t > - > > Key: DISPATCH-1092 > URL: https://issues.apache.org/jira/browse/DISPATCH-1092 > Project: Qpid Dispatch > Issue Type: Bug > Components: Routing Engine >Affects Versions: 1.2.0 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Fix For: 1.3.0 > > > The qd_connection_t stashes a reference to the connection's pn_session_t in > its pn_sess field, however once the pn_session_t is freed the stale reference > hangs around causing mayhem. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1092) in some cases qdrouterd crashes due to stale pn_session_t
[ https://issues.apache.org/jira/browse/DISPATCH-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16566762#comment-16566762 ] ASF subversion and git services commented on DISPATCH-1092: --- Commit ecfd325276cadc8c5da3e81159e30aa8ed582fef in qpid-dispatch's branch refs/heads/master from Kenneth Giusti [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=ecfd325 ] DISPATCH-1092: clear the cached session pointer when the session closes > in some cases qdrouterd crashes due to stale pn_session_t > - > > Key: DISPATCH-1092 > URL: https://issues.apache.org/jira/browse/DISPATCH-1092 > Project: Qpid Dispatch > Issue Type: Bug > Components: Routing Engine >Affects Versions: 1.2.0 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Fix For: 1.3.0 > > > The qd_connection_t stashes a reference to the connection's pn_session_t in > its pn_sess field, however once the pn_session_t is freed the stale reference > hangs around causing mayhem. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #349: DISPATCH-1092: clear the cached session poi...
Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/349 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1092) in some cases qdrouterd crashes due to stale pn_session_t
[ https://issues.apache.org/jira/browse/DISPATCH-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16566763#comment-16566763 ] ASF GitHub Bot commented on DISPATCH-1092: -- Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/349 > in some cases qdrouterd crashes due to stale pn_session_t > - > > Key: DISPATCH-1092 > URL: https://issues.apache.org/jira/browse/DISPATCH-1092 > Project: Qpid Dispatch > Issue Type: Bug > Components: Routing Engine >Affects Versions: 1.2.0 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Fix For: 1.3.0 > > > The qd_connection_t stashes a reference to the connection's pn_session_t in > its pn_sess field, however once the pn_session_t is freed the stale reference > hangs around causing mayhem. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8222) [JMS AMQP 0-x][AMQP 0-8..0-91] Transaction commit/rollback or recover can hang when failover is in progress
[
https://issues.apache.org/jira/browse/QPID-8222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1655#comment-1655
]
Alex Rudyy commented on QPID-8222:
--
The easiest way to reproduce the issue is to configure open transaction timeout
on broker side, start producing transaction, wait for the timeout to expire and
try to commit the transaction.
> [JMS AMQP 0-x][AMQP 0-8..0-91] Transaction commit/rollback or recover can
> hang when failover is in progress
> ---
>
> Key: QPID-8222
> URL: https://issues.apache.org/jira/browse/QPID-8222
> Project: Qpid
> Issue Type: Bug
> Components: JMS AMQP 0-x
>Affects Versions: qpid-java-6.1.6, qpid-java-6.0, qpid-java-6.0.1,
> qpid-java-6.0.2, qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5,
> qpid-java-6.1, qpid-java-6.0.6, qpid-java-6.1.1, qpid-java-6.1.2,
> qpid-java-6.0.7, qpid-java-6.1.3, qpid-java-6.0.8, qpid-java-6.1.4,
> qpid-java-client-0-x-6.3.0, qpid-java-6.1.5, qpid-java-client-0-x-6.3.1,
> qpid-java-client-0-x-6.3.2
>Reporter: Alex Rudyy
>Priority: Blocker
> Fix For: qpid-java-client-0-x-6.3.3
>
> Attachments: thread-dump.txt
>
>
> JMS transaction commit/rollback or recover can hang when connectivity is lost
> and failover is triggered to restore the connection. When
> commit/rollback/recover are invoked after restoring the connectivity and
> before failover finishes resubscribing of existing sessions, the syncing of
> dispatcher queue can hang due to race with adding the signal message into the
> queue from session operation and cleaning the queue by failover. Here is a
> dump of hang commit operation:
> {noformat}
> "main" #1 prio=5 os_prio=0 tid=0x0241c000 nid=0x2e18 waiting on
> condition [0x02a9f000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x00076d9f4c70> (a
> java.util.concurrent.CountDownLatch$Sync)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231)
> at
> org.apache.qpid.client.AMQSession.syncDispatchQueue(AMQSession.java:2343)
> at org.apache.qpid.client.AMQSession.rollback(AMQSession.java:1984)
> - locked <0x00076d67e5f8> (a java.lang.Object)
> at org.apache.qpid.client.AMQSession.commit(AMQSession.java:922)
> at org.apache.qpid.test.Test.main(Test.java:40)
> {noformat}
> The defect was introduced as part of changes committed against QPID-3521. I
> do not see any sensible work around for the issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8222) [JMS AMQP 0-x][AMQP 0-8..0-91] Transaction commit/rollback or recover can hang when failover is in progress
[
https://issues.apache.org/jira/browse/QPID-8222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8222:
-
Attachment: thread-dump.txt
> [JMS AMQP 0-x][AMQP 0-8..0-91] Transaction commit/rollback or recover can
> hang when failover is in progress
> ---
>
> Key: QPID-8222
> URL: https://issues.apache.org/jira/browse/QPID-8222
> Project: Qpid
> Issue Type: Bug
> Components: JMS AMQP 0-x
>Affects Versions: qpid-java-6.1.6, qpid-java-6.0, qpid-java-6.0.1,
> qpid-java-6.0.2, qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5,
> qpid-java-6.1, qpid-java-6.0.6, qpid-java-6.1.1, qpid-java-6.1.2,
> qpid-java-6.0.7, qpid-java-6.1.3, qpid-java-6.0.8, qpid-java-6.1.4,
> qpid-java-client-0-x-6.3.0, qpid-java-6.1.5, qpid-java-client-0-x-6.3.1,
> qpid-java-client-0-x-6.3.2
>Reporter: Alex Rudyy
>Priority: Blocker
> Fix For: qpid-java-client-0-x-6.3.3
>
> Attachments: thread-dump.txt
>
>
> JMS transaction commit/rollback or recover can hang when connectivity is lost
> and failover is triggered to restore the connection. When
> commit/rollback/recover are invoked after restoring the connectivity and
> before failover finishes resubscribing of existing sessions, the syncing of
> dispatcher queue can hang due to race with adding the signal message into the
> queue from session operation and cleaning the queue by failover. Here is a
> dump of hang commit operation:
> {noformat}
> "main" #1 prio=5 os_prio=0 tid=0x0241c000 nid=0x2e18 waiting on
> condition [0x02a9f000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x00076d9f4c70> (a
> java.util.concurrent.CountDownLatch$Sync)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231)
> at
> org.apache.qpid.client.AMQSession.syncDispatchQueue(AMQSession.java:2343)
> at org.apache.qpid.client.AMQSession.rollback(AMQSession.java:1984)
> - locked <0x00076d67e5f8> (a java.lang.Object)
> at org.apache.qpid.client.AMQSession.commit(AMQSession.java:922)
> at org.apache.qpid.test.Test.main(Test.java:40)
> {noformat}
> The defect was introduced as part of changes committed against QPID-3521. I
> do not see any sensible work around for the issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-8222) [JMS AMQP 0-x][AMQP 0-8..0-91] Transaction commit/rollback or recover can hang when failover is in progress
Alex Rudyy created QPID-8222:
Summary: [JMS AMQP 0-x][AMQP 0-8..0-91] Transaction
commit/rollback or recover can hang when failover is in progress
Key: QPID-8222
URL: https://issues.apache.org/jira/browse/QPID-8222
Project: Qpid
Issue Type: Bug
Components: JMS AMQP 0-x
Affects Versions: qpid-java-client-0-x-6.3.2, qpid-java-client-0-x-6.3.1,
qpid-java-6.1.5, qpid-java-client-0-x-6.3.0, qpid-java-6.1.4, qpid-java-6.0.8,
qpid-java-6.1.3, qpid-java-6.0.7, qpid-java-6.1.2, qpid-java-6.1.1,
qpid-java-6.0.6, qpid-java-6.1, qpid-java-6.0.5, qpid-java-6.0.4,
qpid-java-6.0.3, qpid-java-6.0.2, qpid-java-6.0.1, qpid-java-6.0,
qpid-java-6.1.6
Reporter: Alex Rudyy
Fix For: qpid-java-client-0-x-6.3.3
JMS transaction commit/rollback or recover can hang when connectivity is lost
and failover is triggered to restore the connection. When
commit/rollback/recover are invoked after restoring the connectivity and before
failover finishes resubscribing of existing sessions, the syncing of dispatcher
queue can hang due to race with adding the signal message into the queue from
session operation and cleaning the queue by failover. Here is a dump of hang
commit operation:
{noformat}
"main" #1 prio=5 os_prio=0 tid=0x0241c000 nid=0x2e18 waiting on
condition [0x02a9f000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00076d9f4c70> (a
java.util.concurrent.CountDownLatch$Sync)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231)
at
org.apache.qpid.client.AMQSession.syncDispatchQueue(AMQSession.java:2343)
at org.apache.qpid.client.AMQSession.rollback(AMQSession.java:1984)
- locked <0x00076d67e5f8> (a java.lang.Object)
at org.apache.qpid.client.AMQSession.commit(AMQSession.java:922)
at org.apache.qpid.test.Test.main(Test.java:40)
{noformat}
The defect was introduced as part of changes committed against QPID-3521. I do
not see any sensible work around for the issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1905) CompositeReadableBuffer.duplicate seen to throw a NPE
[
https://issues.apache.org/jira/browse/PROTON-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated PROTON-1905:
---
Description:
Whilst verifying the RC1 candidate for the 0.27.3 RC1, the
{{proton_tests.engine.CreditTest.testDrainOrder}} Jython test caused a NPE with
Proton-J's application code.I realised later my shell had the
{{PN_TRACE_FRM=true}} environment variable set. Unsetting the variable allows
the test to pass. The regression was introduced at 0.27.0.
{noformat}
proton_tests.engine.CreditTest.testDrainOrder
...[1346009488:0] -> Open{ containerId='',
hostname='null', maxFrameSize=16384, channelMax=65535, idleTimeOut=null,
outgoingLocales=null, incomingLocales=null, offeredCapabilities=null,
desiredCapabilities=null, properties=null}
[1346009488:0] -> Begin{remoteChannel=null, nextOutgoingId=1,
incomingWindow=2147483647, outgoingWindow=2147483647, handleMax=65535,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
[1346009488:0] <- Open{ containerId='', hostname='null', maxFrameSize=16384,
channelMax=65535, idleTimeOut=null, outgoingLocales=null, incomingLocales=null,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
[1346009488:0] <- Begin{remoteChannel=0, nextOutgoingId=1,
incomingWindow=2147483647, outgoingWindow=2147483647, handleMax=65535,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
[1346009488:0] -> Attach{name='test-link', handle=0, role=SENDER,
sndSettleMode=MIXED, rcvSettleMode=FIRST, source=Source{address='null',
durable=NONE, expiryPolicy=SESSION_END, timeout=0, dynamic=false,
dynamicNodeProperties=null, distributionMode=null, filter=null,
defaultOutcome=null, outcomes=null, capabilities=null},
target=Target{address='null', durable=NONE, expiryPolicy=SESSION_END,
timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
unsettled=null, incompleteUnsettled=false, initialDeliveryCount=0,
maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
properties=null}
[1346009488:0] <- Attach{name='test-link', handle=0, role=RECEIVER,
sndSettleMode=MIXED, rcvSettleMode=FIRST, source=Source{address='null',
durable=NONE, expiryPolicy=SESSION_END, timeout=0, dynamic=false,
dynamicNodeProperties=null, distributionMode=null, filter=null,
defaultOutcome=null, outcomes=null, capabilities=null},
target=Target{address='null', durable=NONE, expiryPolicy=SESSION_END,
timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
unsettled=null, incompleteUnsettled=false, initialDeliveryCount=null,
maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
properties=null}
[1346009488:0] <- Flow{nextIncomingId=1, incomingWindow=2147483647,
nextOutgoingId=1, outgoingWindow=2147483647, handle=0, deliveryCount=0,
linkCredit=10, available=null, drain=false, echo=false, properties=null}
[1346009488:0] -> Transfer{handle=0, deliveryId=0, deliveryTag=tagA,
messageFormat=0, settled=null, more=true, rcvSettleMode=null, state=null,
resume=false, aborted=false, batchable=false} (1) "A"
fail
Error during test: Traceback (most recent call last):
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton-test",
line 362, in run
phase()
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/engine.py",
line 1556, in testDrainOrder
self.pump()
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/engine.py",
line 112, in pump
pump(t1, t2, buffer_size)
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/common.py",
line 113, in pump
while (pump_uni(transport1, transport2, buffer_size) or
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/common.py",
line 86, in pump_uni
p = src.pending()
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/java/shim/binding/proton/__init__.py",
line 2764, in pending
p = pn_transport_pending(self._impl)
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/java/shim/cengine.py",
line 936, in pn_transport_pending
return trans.impl.pending()
NullPointerException: java.lang.NullPointerException
org.apache.qpid.proton.codec.CompositeReadableBuffer.(CompositeReadableBuffer.java:69)
org.apache.qpid.proton.codec.CompositeReadableBuffer.duplicate(CompositeReadableBuffer.java:474)
org.apache.qpid.proton.codec.CompositeReadableBuffer.duplicate(CompositeReadableBuffer.java:35)
org.apache.qpid.proton.amqp.Binary.create(Binary.java:181)
org.apache.qpid.proton.engine.impl.FrameWriter.logFrame(FrameWriter.java:200)
org.apache.qpid.proton.engine.impl.FrameWriter.writeFrame(FrameWriter.java:168)
[jira] [Updated] (PROTON-1905) CompositeReadableBuffer.duplicate seen to throw a NPE during frame logging
[
https://issues.apache.org/jira/browse/PROTON-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated PROTON-1905:
---
Summary: CompositeReadableBuffer.duplicate seen to throw a NPE during frame
logging (was: CompositeReadableBuffer.duplicate seen to throw a NPE)
> CompositeReadableBuffer.duplicate seen to throw a NPE during frame logging
> --
>
> Key: PROTON-1905
> URL: https://issues.apache.org/jira/browse/PROTON-1905
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
>Affects Versions: proton-j-0.27.0, proton-j-0.28.0
>Reporter: Keith Wall
>Priority: Major
>
> Whilst verifying the RC1 candidate for the 0.27.3 RC1, the
> {{proton_tests.engine.CreditTest.testDrainOrder}} Jython test caused a NPE
> with Proton-J's application code.I realised later my shell had the
> {{PN_TRACE_FRM=true}} environment variable set. Unsetting the variable allows
> the test to pass. The regression was introduced at 0.27.0.
> {noformat}
> proton_tests.engine.CreditTest.testDrainOrder
> ...[1346009488:0] -> Open{ containerId='',
> hostname='null', maxFrameSize=16384, channelMax=65535, idleTimeOut=null,
> outgoingLocales=null, incomingLocales=null, offeredCapabilities=null,
> desiredCapabilities=null, properties=null}
> [1346009488:0] -> Begin{remoteChannel=null, nextOutgoingId=1,
> incomingWindow=2147483647, outgoingWindow=2147483647, handleMax=65535,
> offeredCapabilities=null, desiredCapabilities=null, properties=null}
> [1346009488:0] <- Open{ containerId='', hostname='null', maxFrameSize=16384,
> channelMax=65535, idleTimeOut=null, outgoingLocales=null,
> incomingLocales=null, offeredCapabilities=null, desiredCapabilities=null,
> properties=null}
> [1346009488:0] <- Begin{remoteChannel=0, nextOutgoingId=1,
> incomingWindow=2147483647, outgoingWindow=2147483647, handleMax=65535,
> offeredCapabilities=null, desiredCapabilities=null, properties=null}
> [1346009488:0] -> Attach{name='test-link', handle=0, role=SENDER,
> sndSettleMode=MIXED, rcvSettleMode=FIRST, source=Source{address='null',
> durable=NONE, expiryPolicy=SESSION_END, timeout=0, dynamic=false,
> dynamicNodeProperties=null, distributionMode=null, filter=null,
> defaultOutcome=null, outcomes=null, capabilities=null},
> target=Target{address='null', durable=NONE, expiryPolicy=SESSION_END,
> timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
> unsettled=null, incompleteUnsettled=false, initialDeliveryCount=0,
> maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
> properties=null}
> [1346009488:0] <- Attach{name='test-link', handle=0, role=RECEIVER,
> sndSettleMode=MIXED, rcvSettleMode=FIRST, source=Source{address='null',
> durable=NONE, expiryPolicy=SESSION_END, timeout=0, dynamic=false,
> dynamicNodeProperties=null, distributionMode=null, filter=null,
> defaultOutcome=null, outcomes=null, capabilities=null},
> target=Target{address='null', durable=NONE, expiryPolicy=SESSION_END,
> timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
> unsettled=null, incompleteUnsettled=false, initialDeliveryCount=null,
> maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
> properties=null}
> [1346009488:0] <- Flow{nextIncomingId=1, incomingWindow=2147483647,
> nextOutgoingId=1, outgoingWindow=2147483647, handle=0, deliveryCount=0,
> linkCredit=10, available=null, drain=false, echo=false, properties=null}
> [1346009488:0] -> Transfer{handle=0, deliveryId=0, deliveryTag=tagA,
> messageFormat=0, settled=null, more=true, rcvSettleMode=null, state=null,
> resume=false, aborted=false, batchable=false} (1) "A"
> fail
> Error during test: Traceback (most recent call last):
> File
> "/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton-test",
> line 362, in run
> phase()
> File
> "/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/engine.py",
> line 1556, in testDrainOrder
> self.pump()
> File
> "/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/engine.py",
> line 112, in pump
> pump(t1, t2, buffer_size)
> File
> "/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/common.py",
> line 113, in pump
> while (pump_uni(transport1, transport2, buffer_size) or
> File
> "/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/common.py",
> line 86, in pump_uni
> p = src.pending()
> File
> "/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/java/shim/binding/proton/__init__.py",
> line 2764, in pending
> p = pn_transport_pending(self._impl)
> File
>
[jira] [Updated] (PROTON-1905) CompositeReadableBuffer.duplicate seen to throw a NPE
[
https://issues.apache.org/jira/browse/PROTON-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated PROTON-1905:
---
Affects Version/s: (was: proton-j-0.27.3)
> CompositeReadableBuffer.duplicate seen to throw a NPE
> -
>
> Key: PROTON-1905
> URL: https://issues.apache.org/jira/browse/PROTON-1905
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
>Affects Versions: proton-j-0.27.0, proton-j-0.28.0
>Reporter: Keith Wall
>Priority: Major
>
> Whilst verifying the RC1 candidate for the 0.27.3 RC1, the
> {{proton_tests.engine.CreditTest.testDrainOrder}} Jython test caused a NPE
> with Proton-J's application code.I realised later my shell had the
> {{PN_TRACE_FRM=true}} environment variable set. Unsetting the variable allows
> the test to pass.
> {noformat}
> proton_tests.engine.CreditTest.testDrainOrder
> ...[1346009488:0] -> Open{ containerId='',
> hostname='null', maxFrameSize=16384, channelMax=65535, idleTimeOut=null,
> outgoingLocales=null, incomingLocales=null, offeredCapabilities=null,
> desiredCapabilities=null, properties=null}
> [1346009488:0] -> Begin{remoteChannel=null, nextOutgoingId=1,
> incomingWindow=2147483647, outgoingWindow=2147483647, handleMax=65535,
> offeredCapabilities=null, desiredCapabilities=null, properties=null}
> [1346009488:0] <- Open{ containerId='', hostname='null', maxFrameSize=16384,
> channelMax=65535, idleTimeOut=null, outgoingLocales=null,
> incomingLocales=null, offeredCapabilities=null, desiredCapabilities=null,
> properties=null}
> [1346009488:0] <- Begin{remoteChannel=0, nextOutgoingId=1,
> incomingWindow=2147483647, outgoingWindow=2147483647, handleMax=65535,
> offeredCapabilities=null, desiredCapabilities=null, properties=null}
> [1346009488:0] -> Attach{name='test-link', handle=0, role=SENDER,
> sndSettleMode=MIXED, rcvSettleMode=FIRST, source=Source{address='null',
> durable=NONE, expiryPolicy=SESSION_END, timeout=0, dynamic=false,
> dynamicNodeProperties=null, distributionMode=null, filter=null,
> defaultOutcome=null, outcomes=null, capabilities=null},
> target=Target{address='null', durable=NONE, expiryPolicy=SESSION_END,
> timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
> unsettled=null, incompleteUnsettled=false, initialDeliveryCount=0,
> maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
> properties=null}
> [1346009488:0] <- Attach{name='test-link', handle=0, role=RECEIVER,
> sndSettleMode=MIXED, rcvSettleMode=FIRST, source=Source{address='null',
> durable=NONE, expiryPolicy=SESSION_END, timeout=0, dynamic=false,
> dynamicNodeProperties=null, distributionMode=null, filter=null,
> defaultOutcome=null, outcomes=null, capabilities=null},
> target=Target{address='null', durable=NONE, expiryPolicy=SESSION_END,
> timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
> unsettled=null, incompleteUnsettled=false, initialDeliveryCount=null,
> maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
> properties=null}
> [1346009488:0] <- Flow{nextIncomingId=1, incomingWindow=2147483647,
> nextOutgoingId=1, outgoingWindow=2147483647, handle=0, deliveryCount=0,
> linkCredit=10, available=null, drain=false, echo=false, properties=null}
> [1346009488:0] -> Transfer{handle=0, deliveryId=0, deliveryTag=tagA,
> messageFormat=0, settled=null, more=true, rcvSettleMode=null, state=null,
> resume=false, aborted=false, batchable=false} (1) "A"
> fail
> Error during test: Traceback (most recent call last):
> File
> "/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton-test",
> line 362, in run
> phase()
> File
> "/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/engine.py",
> line 1556, in testDrainOrder
> self.pump()
> File
> "/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/engine.py",
> line 112, in pump
> pump(t1, t2, buffer_size)
> File
> "/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/common.py",
> line 113, in pump
> while (pump_uni(transport1, transport2, buffer_size) or
> File
> "/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/common.py",
> line 86, in pump_uni
> p = src.pending()
> File
> "/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/java/shim/binding/proton/__init__.py",
> line 2764, in pending
> p = pn_transport_pending(self._impl)
> File
> "/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/java/shim/cengine.py",
> line 936, in pn_transport_pending
> return trans.impl.pending()
>
[jira] [Updated] (PROTON-1905) CompositeReadableBuffer.duplicate seen to throw a NPE
[
https://issues.apache.org/jira/browse/PROTON-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated PROTON-1905:
---
Affects Version/s: proton-j-0.27.0
proton-j-0.28.0
> CompositeReadableBuffer.duplicate seen to throw a NPE
> -
>
> Key: PROTON-1905
> URL: https://issues.apache.org/jira/browse/PROTON-1905
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
>Affects Versions: proton-j-0.27.0, proton-j-0.28.0, proton-j-0.27.3
>Reporter: Keith Wall
>Priority: Major
>
> Whilst verifying the RC1 candidate for the 0.27.3 RC1, the
> {{proton_tests.engine.CreditTest.testDrainOrder}} Jython test caused a NPE
> with Proton-J's application code.I realised later my shell had the
> {{PN_TRACE_FRM=true}} environment variable set. Unsetting the variable allows
> the test to pass.
> {noformat}
> proton_tests.engine.CreditTest.testDrainOrder
> ...[1346009488:0] -> Open{ containerId='',
> hostname='null', maxFrameSize=16384, channelMax=65535, idleTimeOut=null,
> outgoingLocales=null, incomingLocales=null, offeredCapabilities=null,
> desiredCapabilities=null, properties=null}
> [1346009488:0] -> Begin{remoteChannel=null, nextOutgoingId=1,
> incomingWindow=2147483647, outgoingWindow=2147483647, handleMax=65535,
> offeredCapabilities=null, desiredCapabilities=null, properties=null}
> [1346009488:0] <- Open{ containerId='', hostname='null', maxFrameSize=16384,
> channelMax=65535, idleTimeOut=null, outgoingLocales=null,
> incomingLocales=null, offeredCapabilities=null, desiredCapabilities=null,
> properties=null}
> [1346009488:0] <- Begin{remoteChannel=0, nextOutgoingId=1,
> incomingWindow=2147483647, outgoingWindow=2147483647, handleMax=65535,
> offeredCapabilities=null, desiredCapabilities=null, properties=null}
> [1346009488:0] -> Attach{name='test-link', handle=0, role=SENDER,
> sndSettleMode=MIXED, rcvSettleMode=FIRST, source=Source{address='null',
> durable=NONE, expiryPolicy=SESSION_END, timeout=0, dynamic=false,
> dynamicNodeProperties=null, distributionMode=null, filter=null,
> defaultOutcome=null, outcomes=null, capabilities=null},
> target=Target{address='null', durable=NONE, expiryPolicy=SESSION_END,
> timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
> unsettled=null, incompleteUnsettled=false, initialDeliveryCount=0,
> maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
> properties=null}
> [1346009488:0] <- Attach{name='test-link', handle=0, role=RECEIVER,
> sndSettleMode=MIXED, rcvSettleMode=FIRST, source=Source{address='null',
> durable=NONE, expiryPolicy=SESSION_END, timeout=0, dynamic=false,
> dynamicNodeProperties=null, distributionMode=null, filter=null,
> defaultOutcome=null, outcomes=null, capabilities=null},
> target=Target{address='null', durable=NONE, expiryPolicy=SESSION_END,
> timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
> unsettled=null, incompleteUnsettled=false, initialDeliveryCount=null,
> maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
> properties=null}
> [1346009488:0] <- Flow{nextIncomingId=1, incomingWindow=2147483647,
> nextOutgoingId=1, outgoingWindow=2147483647, handle=0, deliveryCount=0,
> linkCredit=10, available=null, drain=false, echo=false, properties=null}
> [1346009488:0] -> Transfer{handle=0, deliveryId=0, deliveryTag=tagA,
> messageFormat=0, settled=null, more=true, rcvSettleMode=null, state=null,
> resume=false, aborted=false, batchable=false} (1) "A"
> fail
> Error during test: Traceback (most recent call last):
> File
> "/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton-test",
> line 362, in run
> phase()
> File
> "/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/engine.py",
> line 1556, in testDrainOrder
> self.pump()
> File
> "/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/engine.py",
> line 112, in pump
> pump(t1, t2, buffer_size)
> File
> "/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/common.py",
> line 113, in pump
> while (pump_uni(transport1, transport2, buffer_size) or
> File
> "/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/common.py",
> line 86, in pump_uni
> p = src.pending()
> File
> "/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/java/shim/binding/proton/__init__.py",
> line 2764, in pending
> p = pn_transport_pending(self._impl)
> File
> "/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/java/shim/cengine.py",
> line 936, in pn_transport_pending
> return
[jira] [Updated] (PROTON-1905) CompositeReadableBuffer.duplicate seen to throw a NPE
[
https://issues.apache.org/jira/browse/PROTON-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated PROTON-1905:
---
Description:
Whilst verifying the RC1 candidate for the 0.27.3 RC1, the
{{proton_tests.engine.CreditTest.testDrainOrder}} Jython test caused a NPE with
Proton-J's application code.I realised later my shell had the
{{PN_TRACE_FRM=true}} environment variable set. Unsetting the variable allows
the test to pass.
{noformat}
proton_tests.engine.CreditTest.testDrainOrder
...[1346009488:0] -> Open{ containerId='',
hostname='null', maxFrameSize=16384, channelMax=65535, idleTimeOut=null,
outgoingLocales=null, incomingLocales=null, offeredCapabilities=null,
desiredCapabilities=null, properties=null}
[1346009488:0] -> Begin{remoteChannel=null, nextOutgoingId=1,
incomingWindow=2147483647, outgoingWindow=2147483647, handleMax=65535,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
[1346009488:0] <- Open{ containerId='', hostname='null', maxFrameSize=16384,
channelMax=65535, idleTimeOut=null, outgoingLocales=null, incomingLocales=null,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
[1346009488:0] <- Begin{remoteChannel=0, nextOutgoingId=1,
incomingWindow=2147483647, outgoingWindow=2147483647, handleMax=65535,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
[1346009488:0] -> Attach{name='test-link', handle=0, role=SENDER,
sndSettleMode=MIXED, rcvSettleMode=FIRST, source=Source{address='null',
durable=NONE, expiryPolicy=SESSION_END, timeout=0, dynamic=false,
dynamicNodeProperties=null, distributionMode=null, filter=null,
defaultOutcome=null, outcomes=null, capabilities=null},
target=Target{address='null', durable=NONE, expiryPolicy=SESSION_END,
timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
unsettled=null, incompleteUnsettled=false, initialDeliveryCount=0,
maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
properties=null}
[1346009488:0] <- Attach{name='test-link', handle=0, role=RECEIVER,
sndSettleMode=MIXED, rcvSettleMode=FIRST, source=Source{address='null',
durable=NONE, expiryPolicy=SESSION_END, timeout=0, dynamic=false,
dynamicNodeProperties=null, distributionMode=null, filter=null,
defaultOutcome=null, outcomes=null, capabilities=null},
target=Target{address='null', durable=NONE, expiryPolicy=SESSION_END,
timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
unsettled=null, incompleteUnsettled=false, initialDeliveryCount=null,
maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
properties=null}
[1346009488:0] <- Flow{nextIncomingId=1, incomingWindow=2147483647,
nextOutgoingId=1, outgoingWindow=2147483647, handle=0, deliveryCount=0,
linkCredit=10, available=null, drain=false, echo=false, properties=null}
[1346009488:0] -> Transfer{handle=0, deliveryId=0, deliveryTag=tagA,
messageFormat=0, settled=null, more=true, rcvSettleMode=null, state=null,
resume=false, aborted=false, batchable=false} (1) "A"
fail
Error during test: Traceback (most recent call last):
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton-test",
line 362, in run
phase()
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/engine.py",
line 1556, in testDrainOrder
self.pump()
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/engine.py",
line 112, in pump
pump(t1, t2, buffer_size)
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/common.py",
line 113, in pump
while (pump_uni(transport1, transport2, buffer_size) or
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/common.py",
line 86, in pump_uni
p = src.pending()
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/java/shim/binding/proton/__init__.py",
line 2764, in pending
p = pn_transport_pending(self._impl)
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/java/shim/cengine.py",
line 936, in pn_transport_pending
return trans.impl.pending()
NullPointerException: java.lang.NullPointerException
org.apache.qpid.proton.codec.CompositeReadableBuffer.(CompositeReadableBuffer.java:69)
org.apache.qpid.proton.codec.CompositeReadableBuffer.duplicate(CompositeReadableBuffer.java:474)
org.apache.qpid.proton.codec.CompositeReadableBuffer.duplicate(CompositeReadableBuffer.java:35)
org.apache.qpid.proton.amqp.Binary.create(Binary.java:181)
org.apache.qpid.proton.engine.impl.FrameWriter.logFrame(FrameWriter.java:200)
org.apache.qpid.proton.engine.impl.FrameWriter.writeFrame(FrameWriter.java:168)
[jira] [Updated] (PROTON-1905) CompositeReadableBuffer.duplicate seen to throw a NPE
[
https://issues.apache.org/jira/browse/PROTON-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated PROTON-1905:
---
Description:
Whilst verifying the RC1 candidate for the 0.27.3 RC1, the
{{proton_tests.engine.CreditTest.testDrainOrder}} Jython test caused a NPE with
Proton-J's application code.I realised later my shell had the
{{PN_TRACE_FRM=true}} environment variable set.
{noformat}
proton_tests.engine.CreditTest.testDrainOrder
...[1346009488:0] -> Open{ containerId='',
hostname='null', maxFrameSize=16384, channelMax=65535, idleTimeOut=null,
outgoingLocales=null, incomingLocales=null, offeredCapabilities=null,
desiredCapabilities=null, properties=null}
[1346009488:0] -> Begin{remoteChannel=null, nextOutgoingId=1,
incomingWindow=2147483647, outgoingWindow=2147483647, handleMax=65535,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
[1346009488:0] <- Open{ containerId='', hostname='null', maxFrameSize=16384,
channelMax=65535, idleTimeOut=null, outgoingLocales=null, incomingLocales=null,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
[1346009488:0] <- Begin{remoteChannel=0, nextOutgoingId=1,
incomingWindow=2147483647, outgoingWindow=2147483647, handleMax=65535,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
[1346009488:0] -> Attach{name='test-link', handle=0, role=SENDER,
sndSettleMode=MIXED, rcvSettleMode=FIRST, source=Source{address='null',
durable=NONE, expiryPolicy=SESSION_END, timeout=0, dynamic=false,
dynamicNodeProperties=null, distributionMode=null, filter=null,
defaultOutcome=null, outcomes=null, capabilities=null},
target=Target{address='null', durable=NONE, expiryPolicy=SESSION_END,
timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
unsettled=null, incompleteUnsettled=false, initialDeliveryCount=0,
maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
properties=null}
[1346009488:0] <- Attach{name='test-link', handle=0, role=RECEIVER,
sndSettleMode=MIXED, rcvSettleMode=FIRST, source=Source{address='null',
durable=NONE, expiryPolicy=SESSION_END, timeout=0, dynamic=false,
dynamicNodeProperties=null, distributionMode=null, filter=null,
defaultOutcome=null, outcomes=null, capabilities=null},
target=Target{address='null', durable=NONE, expiryPolicy=SESSION_END,
timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
unsettled=null, incompleteUnsettled=false, initialDeliveryCount=null,
maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
properties=null}
[1346009488:0] <- Flow{nextIncomingId=1, incomingWindow=2147483647,
nextOutgoingId=1, outgoingWindow=2147483647, handle=0, deliveryCount=0,
linkCredit=10, available=null, drain=false, echo=false, properties=null}
[1346009488:0] -> Transfer{handle=0, deliveryId=0, deliveryTag=tagA,
messageFormat=0, settled=null, more=true, rcvSettleMode=null, state=null,
resume=false, aborted=false, batchable=false} (1) "A"
fail
Error during test: Traceback (most recent call last):
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton-test",
line 362, in run
phase()
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/engine.py",
line 1556, in testDrainOrder
self.pump()
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/engine.py",
line 112, in pump
pump(t1, t2, buffer_size)
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/common.py",
line 113, in pump
while (pump_uni(transport1, transport2, buffer_size) or
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/common.py",
line 86, in pump_uni
p = src.pending()
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/java/shim/binding/proton/__init__.py",
line 2764, in pending
p = pn_transport_pending(self._impl)
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/java/shim/cengine.py",
line 936, in pn_transport_pending
return trans.impl.pending()
NullPointerException: java.lang.NullPointerException
org.apache.qpid.proton.codec.CompositeReadableBuffer.(CompositeReadableBuffer.java:69)
org.apache.qpid.proton.codec.CompositeReadableBuffer.duplicate(CompositeReadableBuffer.java:474)
org.apache.qpid.proton.codec.CompositeReadableBuffer.duplicate(CompositeReadableBuffer.java:35)
org.apache.qpid.proton.amqp.Binary.create(Binary.java:181)
org.apache.qpid.proton.engine.impl.FrameWriter.logFrame(FrameWriter.java:200)
org.apache.qpid.proton.engine.impl.FrameWriter.writeFrame(FrameWriter.java:168)
org.apache.qpid.proton.engine.impl.TransportImpl.writeFrame(TransportImpl.java:1081)
[jira] [Created] (PROTON-1905) CompositeReadableBuffer.duplicate seen to throw a NPE
Keith Wall created PROTON-1905:
--
Summary: CompositeReadableBuffer.duplicate seen to throw a NPE
Key: PROTON-1905
URL: https://issues.apache.org/jira/browse/PROTON-1905
Project: Qpid Proton
Issue Type: Bug
Components: proton-j
Affects Versions: proton-j-0.27.3
Reporter: Keith Wall
Whilst verify the RC1 candidate for the 0.27.3 RC1, the
{{proton_tests.engine.CreditTest.testDrainOrder}} Jython test caused a NPE with
Proton-J's application code.
{noformat}
proton_tests.engine.CreditTest.testDrainOrder
...[1346009488:0] -> Open{ containerId='',
hostname='null', maxFrameSize=16384, channelMax=65535, idleTimeOut=null,
outgoingLocales=null, incomingLocales=null, offeredCapabilities=null,
desiredCapabilities=null, properties=null}
[1346009488:0] -> Begin{remoteChannel=null, nextOutgoingId=1,
incomingWindow=2147483647, outgoingWindow=2147483647, handleMax=65535,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
[1346009488:0] <- Open{ containerId='', hostname='null', maxFrameSize=16384,
channelMax=65535, idleTimeOut=null, outgoingLocales=null, incomingLocales=null,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
[1346009488:0] <- Begin{remoteChannel=0, nextOutgoingId=1,
incomingWindow=2147483647, outgoingWindow=2147483647, handleMax=65535,
offeredCapabilities=null, desiredCapabilities=null, properties=null}
[1346009488:0] -> Attach{name='test-link', handle=0, role=SENDER,
sndSettleMode=MIXED, rcvSettleMode=FIRST, source=Source{address='null',
durable=NONE, expiryPolicy=SESSION_END, timeout=0, dynamic=false,
dynamicNodeProperties=null, distributionMode=null, filter=null,
defaultOutcome=null, outcomes=null, capabilities=null},
target=Target{address='null', durable=NONE, expiryPolicy=SESSION_END,
timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
unsettled=null, incompleteUnsettled=false, initialDeliveryCount=0,
maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
properties=null}
[1346009488:0] <- Attach{name='test-link', handle=0, role=RECEIVER,
sndSettleMode=MIXED, rcvSettleMode=FIRST, source=Source{address='null',
durable=NONE, expiryPolicy=SESSION_END, timeout=0, dynamic=false,
dynamicNodeProperties=null, distributionMode=null, filter=null,
defaultOutcome=null, outcomes=null, capabilities=null},
target=Target{address='null', durable=NONE, expiryPolicy=SESSION_END,
timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
unsettled=null, incompleteUnsettled=false, initialDeliveryCount=null,
maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
properties=null}
[1346009488:0] <- Flow{nextIncomingId=1, incomingWindow=2147483647,
nextOutgoingId=1, outgoingWindow=2147483647, handle=0, deliveryCount=0,
linkCredit=10, available=null, drain=false, echo=false, properties=null}
[1346009488:0] -> Transfer{handle=0, deliveryId=0, deliveryTag=tagA,
messageFormat=0, settled=null, more=true, rcvSettleMode=null, state=null,
resume=false, aborted=false, batchable=false} (1) "A"
fail
Error during test: Traceback (most recent call last):
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton-test",
line 362, in run
phase()
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/engine.py",
line 1556, in testDrainOrder
self.pump()
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/engine.py",
line 112, in pump
pump(t1, t2, buffer_size)
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/common.py",
line 113, in pump
while (pump_uni(transport1, transport2, buffer_size) or
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/python/proton_tests/common.py",
line 86, in pump_uni
p = src.pending()
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/java/shim/binding/proton/__init__.py",
line 2764, in pending
p = pn_transport_pending(self._impl)
File
"/Users/keith/releases/0273/apache-qpid-proton-j-0.27.3-src/tests/java/shim/cengine.py",
line 936, in pn_transport_pending
return trans.impl.pending()
NullPointerException: java.lang.NullPointerException
org.apache.qpid.proton.codec.CompositeReadableBuffer.(CompositeReadableBuffer.java:69)
org.apache.qpid.proton.codec.CompositeReadableBuffer.duplicate(CompositeReadableBuffer.java:474)
org.apache.qpid.proton.codec.CompositeReadableBuffer.duplicate(CompositeReadableBuffer.java:35)
org.apache.qpid.proton.amqp.Binary.create(Binary.java:181)
org.apache.qpid.proton.engine.impl.FrameWriter.logFrame(FrameWriter.java:200)
org.apache.qpid.proton.engine.impl.FrameWriter.writeFrame(FrameWriter.java:168)
