[jira] [Commented] (QPID-6933) Factor out a JMS client neutral messaging test suite from system tests
[ https://issues.apache.org/jira/browse/QPID-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273752#comment-16273752 ] ASF subversion and git services commented on QPID-6933: --- Commit 0a3b816baebf8ce1cb64ca63309565badbe725cf in qpid-broker-j's branch refs/heads/master from [~alex.rufous] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=0a3b816 ] QPID-6933: [System Tests] Add TopicSessionTest into JMS 1.1 system tests > Factor out a JMS client neutral messaging test suite from system tests > -- > > Key: QPID-6933 > URL: https://issues.apache.org/jira/browse/QPID-6933 > Project: Qpid > Issue Type: Improvement > Components: Java Tests >Reporter: Keith Wall >Assignee: Alex Rudyy > > The existing system testsuite is in a poor state. > * It is poorly structured > * Mixes different types of test. i.e. messaging behaviour with those that > test features of the Java Broker (e.g. REST). > * Many of the tests refer directly to the implementation classes of the Qpid > Client 0-8..0-10 client meaning the tests cannot be run using the new client. > As a first step, we want to factor out a separate messaging system test suite: > * The tests in this suite will be JMS client neutral. > * Written in terms of JNDI/JMS client > * Configurations/Broker observations will be performed via a clean > Broker-neutral facade. For instance > ** a mechanism to cause the queue to be created of a particular type. > ** a mechanism to observe a queue depth. > * The tests will be classified by feature (to be defined) > * The classification system will be used to drive an exclusion feature (to be > defined). -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6933) Factor out a JMS client neutral messaging test suite from system tests
[ https://issues.apache.org/jira/browse/QPID-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273733#comment-16273733 ] ASF subversion and git services commented on QPID-6933: --- Commit 569e7f6a4beb4fed96a946dd03da4a839330c1e5 in qpid-broker-j's branch refs/heads/master from [~alex.rufous] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=569e7f6 ] QPID-6933: [System Tests] Add TopicSubscriberTest into JMS 1.1 system tests > Factor out a JMS client neutral messaging test suite from system tests > -- > > Key: QPID-6933 > URL: https://issues.apache.org/jira/browse/QPID-6933 > Project: Qpid > Issue Type: Improvement > Components: Java Tests >Reporter: Keith Wall >Assignee: Alex Rudyy > > The existing system testsuite is in a poor state. > * It is poorly structured > * Mixes different types of test. i.e. messaging behaviour with those that > test features of the Java Broker (e.g. REST). > * Many of the tests refer directly to the implementation classes of the Qpid > Client 0-8..0-10 client meaning the tests cannot be run using the new client. > As a first step, we want to factor out a separate messaging system test suite: > * The tests in this suite will be JMS client neutral. > * Written in terms of JNDI/JMS client > * Configurations/Broker observations will be performed via a clean > Broker-neutral facade. For instance > ** a mechanism to cause the queue to be created of a particular type. > ** a mechanism to observe a queue depth. > * The tests will be classified by feature (to be defined) > * The classification system will be used to drive an exclusion feature (to be > defined). -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8038) [Broker-J][System Tests] Add protocol system test suites for AMQP 0-x
[ https://issues.apache.org/jira/browse/QPID-8038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273620#comment-16273620 ] ASF subversion and git services commented on QPID-8038: --- Commit b005f4d70eaa659af79da429ae9a734340f8868f in qpid-broker-j's branch refs/heads/master from [~k-wall] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=b005f4d ] QPID-8038: [Broker-J][AMQP 0-8..0-91] Add more queue protocol tests > [Broker-J][System Tests] Add protocol system test suites for AMQP 0-x > - > > Key: QPID-8038 > URL: https://issues.apache.org/jira/browse/QPID-8038 > Project: Qpid > Issue Type: Improvement > Components: Broker-J, Java Tests >Reporter: Alex Rudyy > > We need a test frameworks which would allow creation of tests which would be > sending the AMQP 0-x performatives over TCP and receiving and asserting > broker responses. > The framework should satisfy the following requirements: > * It should allow running tests against other AMQP brokers > * The framework should encapsulate starting/stopping of broker and queue > creation/deletion under special interface(s) which can be implemented by the > Broker developers in order to run tests against different Broker > implementations > * Tests should be able to start and stop broker if required or configured > * Tests should be able to generate AMQP performatives and assert received > peer's AMQP performatives > * The framework should allow using other transport than TCP if required > * The framework should be based on AMQP 0-x implementations of Broker-J -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1705) [go] binding puts build artifacts in the source tree
[ https://issues.apache.org/jira/browse/PROTON-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273587#comment-16273587 ] ASF subversion and git services commented on PROTON-1705: - Commit e60e2faebe115c8d992e287bf06a0fec52642f40 in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=e60e2fa ] PROTON-1705: [go] binding puts build artifacts in the source tree Build the go binding in the build tree, with a symlink to the sources in the source tree. > [go] binding puts build artifacts in the source tree > > > Key: PROTON-1705 > URL: https://issues.apache.org/jira/browse/PROTON-1705 > Project: Qpid Proton > Issue Type: Bug > Components: go-binding >Reporter: Alan Conway >Assignee: Alan Conway > > The Go build puts object files in the source tree which is bad practice and > causes confusion if artifacts are left behind. Make it do all its work in the > build tree. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1705) [go] binding puts build artifacts in the source tree
Alan Conway created PROTON-1705: --- Summary: [go] binding puts build artifacts in the source tree Key: PROTON-1705 URL: https://issues.apache.org/jira/browse/PROTON-1705 Project: Qpid Proton Issue Type: Bug Components: go-binding Reporter: Alan Conway Assignee: Alan Conway The Go build puts object files in the source tree which is bad practice and causes confusion if artifacts are left behind. Make it do all its work in the build tree. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (DISPATCH-878) qdrouterd should log real port if port 0 was specified for the listener port property in qdrouterd.conf
[
https://issues.apache.org/jira/browse/DISPATCH-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273531#comment-16273531
]
Ganesh Murthy edited comment on DISPATCH-878 at 11/30/17 9:51 PM:
--
Jeremy, are you simply looking for Dispatch to write the actual port to the log?
Like so instead of Dispatch logging the following INFO level log
{noformat}
CONN_MGR (info) Configured Listener: 0.0.0.0:0 proto=any, role=normal
{noformat}
are you looking for something like this
{noformat}
CONN_MGR (info) Configured Listener: 0.0.0.0:45678 proto=any, role=normal
{noformat}
You will have to parse the log entries to get at the actual port dispatch is
listening on
was (Author: ganeshmurthy):
Jeremy, are you simply looking for Dispatch to write the actual port to the log?
Like so instead of Dispatch logging the following INFO level log
{noformat}
CONN_MGR (info) Configured Listener: 0.0.0.0:0 proto=any, role=normal
{noformat}
you are looking for something like this
{noformat}
CONN_MGR (info) Configured Listener: 0.0.0.0:45678 proto=any, role=normal
{noformat}
You will have to parse the log entries to get at the actual port dispatch is
listening on
> qdrouterd should log real port if port 0 was specified for the listener port
> property in qdrouterd.conf
> ---
>
> Key: DISPATCH-878
> URL: https://issues.apache.org/jira/browse/DISPATCH-878
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
> Environment: OS: Red Hat Linux Server release 6.4
> Dispatch version: 0.7.0
>Reporter: Jeremy
>
> For such a qdrouterd.conf configuration:
> {noformat}
> router {
> mode: standalone
> id: Router.A
> }
> listener {
> host: 0.0.0.0
> *port: 5673*
> authenticatePeer: no
> saslMechanisms: ANONYMOUS
> }
> {noformat}
> qdrouterd logs the port as such:
> {noformat}
> CONN_MGR (info) Configured Listener: 0.0.0.0:5673 proto=any, role=normal
> {noformat}
> When specifying port 0, so that the dispatch router runs on a random
> available port, the log is as such:
> {noformat}
> CONN_MGR (info) Configured Listener: 0.0.0.0:0 proto=any, role=normal
> {noformat}
> qdrouterd process can log instead the real port that was randomly chosen.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-878) qdrouterd should log real port if port 0 was specified for the listener port property in qdrouterd.conf
[
https://issues.apache.org/jira/browse/DISPATCH-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273531#comment-16273531
]
Ganesh Murthy commented on DISPATCH-878:
Jeremy, are you simply looking for Dispatch to write the actual port to the log?
Like so instead of Dispatch logging the following INFO level log
{noformat}
CONN_MGR (info) Configured Listener: 0.0.0.0:0 proto=any, role=normal
{noformat}
you are looking for something like this
{noformat}
CONN_MGR (info) Configured Listener: 0.0.0.0:45678 proto=any, role=normal
{noformat}
You will have to parse the log entries to get at the actual port dispatch is
listening on
> qdrouterd should log real port if port 0 was specified for the listener port
> property in qdrouterd.conf
> ---
>
> Key: DISPATCH-878
> URL: https://issues.apache.org/jira/browse/DISPATCH-878
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
> Environment: OS: Red Hat Linux Server release 6.4
> Dispatch version: 0.7.0
>Reporter: Jeremy
>
> For such a qdrouterd.conf configuration:
> {noformat}
> router {
> mode: standalone
> id: Router.A
> }
> listener {
> host: 0.0.0.0
> *port: 5673*
> authenticatePeer: no
> saslMechanisms: ANONYMOUS
> }
> {noformat}
> qdrouterd logs the port as such:
> {noformat}
> CONN_MGR (info) Configured Listener: 0.0.0.0:5673 proto=any, role=normal
> {noformat}
> When specifying port 0, so that the dispatch router runs on a random
> available port, the log is as such:
> {noformat}
> CONN_MGR (info) Configured Listener: 0.0.0.0:0 proto=any, role=normal
> {noformat}
> qdrouterd process can log instead the real port that was randomly chosen.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-1704) [c proactor] test_ipv4_ipv6 intermittent failure on FreeBSD
[ https://issues.apache.org/jira/browse/PROTON-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1704. - Resolution: Fixed > [c proactor] test_ipv4_ipv6 intermittent failure on FreeBSD > --- > > Key: PROTON-1704 > URL: https://issues.apache.org/jira/browse/PROTON-1704 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.18.1 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: proton-c-0.19.0 > > > The negative tests that you can't connect from ipv4 to ipv6 and vice-versa > occasionally fail on FreeBSD because the connection succeeds. These tests are > not valid given the range of options for bridging ipv4 and ipv6, so they were > removed. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1064) ruby: native IO based on connection_driver.c
[ https://issues.apache.org/jira/browse/PROTON-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273520#comment-16273520 ] ASF subversion and git services commented on PROTON-1064: - Commit db1cb9f125b74dc18a45e99115cfeeea386b16d8 in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=db1cb9f ] PROTON-1064: [ruby] tidy up delivery/dispolsition - Move constants to DeliveryState module - Include DeliveryState constants in Delivery and Disposition - Move Acking module methods to Delivery > ruby: native IO based on connection_driver.c > - > > Key: PROTON-1064 > URL: https://issues.apache.org/jira/browse/PROTON-1064 > Project: Qpid Proton > Issue Type: Improvement > Components: ruby-binding >Affects Versions: 0.11.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: proton-c-0.19.0 > > > Refactor ruby binding to use a native Ruby IO driver with the C > pn_connection_driver for AMQP protocol support. > Ruby ConnectionDriver - drive a single connection, single threaded > - Use any ruby IO subclass > - Works with native Ruby polling primitives > - Avoids Ruby threading issue with GVL (all IO is done in Ruby) > - Thread safe function injection for MT use. > Client/server examples using native ruby connect, multi-threaded broker > example using ruby listen. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1064) ruby: native IO based on connection_driver.c
[ https://issues.apache.org/jira/browse/PROTON-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273516#comment-16273516 ] ASF subversion and git services commented on PROTON-1064: - Commit 0f03d826ba0e813c24ceb17b1a644c0f3cf9eccc in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=0f03d82 ] PROTON-1064: [ruby] Removed C-based Reactor Kept a deprecated compatibility shim `Reactor::Container`, delegates to the new native-ruby Qpid::Proton::Container > ruby: native IO based on connection_driver.c > - > > Key: PROTON-1064 > URL: https://issues.apache.org/jira/browse/PROTON-1064 > Project: Qpid Proton > Issue Type: Improvement > Components: ruby-binding >Affects Versions: 0.11.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: proton-c-0.19.0 > > > Refactor ruby binding to use a native Ruby IO driver with the C > pn_connection_driver for AMQP protocol support. > Ruby ConnectionDriver - drive a single connection, single threaded > - Use any ruby IO subclass > - Works with native Ruby polling primitives > - Avoids Ruby threading issue with GVL (all IO is done in Ruby) > - Thread safe function injection for MT use. > Client/server examples using native ruby connect, multi-threaded broker > example using ruby listen. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1064) ruby: native IO based on connection_driver.c
[ https://issues.apache.org/jira/browse/PROTON-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273515#comment-16273515 ] ASF subversion and git services commented on PROTON-1064: - Commit 67c4baecf77dd9bfcbe092b039cbaf7461bc8054 in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=67c4bae ] PROTON-1064: [ruby] Messenger deprecation message > ruby: native IO based on connection_driver.c > - > > Key: PROTON-1064 > URL: https://issues.apache.org/jira/browse/PROTON-1064 > Project: Qpid Proton > Issue Type: Improvement > Components: ruby-binding >Affects Versions: 0.11.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: proton-c-0.19.0 > > > Refactor ruby binding to use a native Ruby IO driver with the C > pn_connection_driver for AMQP protocol support. > Ruby ConnectionDriver - drive a single connection, single threaded > - Use any ruby IO subclass > - Works with native Ruby polling primitives > - Avoids Ruby threading issue with GVL (all IO is done in Ruby) > - Thread safe function injection for MT use. > Client/server examples using native ruby connect, multi-threaded broker > example using ruby listen. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1704) [c proactor] test_ipv4_ipv6 intermittent failure on FreeBSD
[ https://issues.apache.org/jira/browse/PROTON-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273524#comment-16273524 ] ASF subversion and git services commented on PROTON-1704: - Commit fe9069f9d9f5e27a8c3609eec366517ed8207b20 in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=fe9069f ] PROTON-1704: [c proactor] test_ipv4_ipv6 intermittent failure on FreeBSD The negative tests that you can't connect from ipv4 to ipv6 and vice-versa occasionally fail on FreeBSD because the connection succeeds. These tests are not valid given the range of options for bridging ipv4 and ipv6, so they were removed. > [c proactor] test_ipv4_ipv6 intermittent failure on FreeBSD > --- > > Key: PROTON-1704 > URL: https://issues.apache.org/jira/browse/PROTON-1704 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.18.1 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: proton-c-0.19.0 > > > The negative tests that you can't connect from ipv4 to ipv6 and vice-versa > occasionally fail on FreeBSD because the connection succeeds. These tests are > not valid given the range of options for bridging ipv4 and ipv6, so they were > removed. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1064) ruby: native IO based on connection_driver.c
[ https://issues.apache.org/jira/browse/PROTON-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273519#comment-16273519 ] ASF subversion and git services commented on PROTON-1064: - Commit de2d4908b8393c74f5cb7b11d14d37abeac561e0 in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=de2d490 ] PROTON-1064: [ruby] move engine.rb "helpers" to proper classes Move utils/engine.rb "helper" methods directly to the relevant classes: Message, Data, Condition > ruby: native IO based on connection_driver.c > - > > Key: PROTON-1064 > URL: https://issues.apache.org/jira/browse/PROTON-1064 > Project: Qpid Proton > Issue Type: Improvement > Components: ruby-binding >Affects Versions: 0.11.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: proton-c-0.19.0 > > > Refactor ruby binding to use a native Ruby IO driver with the C > pn_connection_driver for AMQP protocol support. > Ruby ConnectionDriver - drive a single connection, single threaded > - Use any ruby IO subclass > - Works with native Ruby polling primitives > - Avoids Ruby threading issue with GVL (all IO is done in Ruby) > - Thread safe function injection for MT use. > Client/server examples using native ruby connect, multi-threaded broker > example using ruby listen. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1064) ruby: native IO based on connection_driver.c
[ https://issues.apache.org/jira/browse/PROTON-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273517#comment-16273517 ] ASF subversion and git services commented on PROTON-1064: - Commit 15c804c7a7a2206ed94a5557bc95a4913a3261ae in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=15c804c ] PROTON-1064: [ruby] Move Condition to core > ruby: native IO based on connection_driver.c > - > > Key: PROTON-1064 > URL: https://issues.apache.org/jira/browse/PROTON-1064 > Project: Qpid Proton > Issue Type: Improvement > Components: ruby-binding >Affects Versions: 0.11.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: proton-c-0.19.0 > > > Refactor ruby binding to use a native Ruby IO driver with the C > pn_connection_driver for AMQP protocol support. > Ruby ConnectionDriver - drive a single connection, single threaded > - Use any ruby IO subclass > - Works with native Ruby polling primitives > - Avoids Ruby threading issue with GVL (all IO is done in Ruby) > - Thread safe function injection for MT use. > Client/server examples using native ruby connect, multi-threaded broker > example using ruby listen. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1064) ruby: native IO based on connection_driver.c
[ https://issues.apache.org/jira/browse/PROTON-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273522#comment-16273522 ] ASF subversion and git services commented on PROTON-1064: - Commit b883393baae53bd59710c1c9595dab36139a8417 in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=b883393 ] PROTON-1064: [ruby] Event handling refactor Event/handler/dispatch rework: - No wrapped C handlers, native ruby handlers - Simplified event class - MessagingHandler pure interface, can be duck-typed - Default handler logic moved to Handler::Adapter - on_error catches unhandled on_xxx_error events - on_unhandled catches all other unhandled events - dropped ruby Collector wrapper - now internal to connection_driver. Other changes - Added close(error) for all endpoints to set condition on close - Associate Connection with its Container - Transport options: sasl, idle_timeout etc. - Removed unused classes, corrected/clarified docs - Connection_driver fixes - delegate proton closes to IO > ruby: native IO based on connection_driver.c > - > > Key: PROTON-1064 > URL: https://issues.apache.org/jira/browse/PROTON-1064 > Project: Qpid Proton > Issue Type: Improvement > Components: ruby-binding >Affects Versions: 0.11.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: proton-c-0.19.0 > > > Refactor ruby binding to use a native Ruby IO driver with the C > pn_connection_driver for AMQP protocol support. > Ruby ConnectionDriver - drive a single connection, single threaded > - Use any ruby IO subclass > - Works with native Ruby polling primitives > - Avoids Ruby threading issue with GVL (all IO is done in Ruby) > - Thread safe function injection for MT use. > Client/server examples using native ruby connect, multi-threaded broker > example using ruby listen. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1064) ruby: native IO based on connection_driver.c
[ https://issues.apache.org/jira/browse/PROTON-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273521#comment-16273521 ] ASF subversion and git services commented on PROTON-1064: - Commit c4e5e58cd87aff704fc71c4c7b3c1d006de17f1b in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=c4e5e58 ] PROTON-1064: [ruby] consistent handling of conditions and exceptions > ruby: native IO based on connection_driver.c > - > > Key: PROTON-1064 > URL: https://issues.apache.org/jira/browse/PROTON-1064 > Project: Qpid Proton > Issue Type: Improvement > Components: ruby-binding >Affects Versions: 0.11.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: proton-c-0.19.0 > > > Refactor ruby binding to use a native Ruby IO driver with the C > pn_connection_driver for AMQP protocol support. > Ruby ConnectionDriver - drive a single connection, single threaded > - Use any ruby IO subclass > - Works with native Ruby polling primitives > - Avoids Ruby threading issue with GVL (all IO is done in Ruby) > - Thread safe function injection for MT use. > Client/server examples using native ruby connect, multi-threaded broker > example using ruby listen. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1064) ruby: native IO based on connection_driver.c
[ https://issues.apache.org/jira/browse/PROTON-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273523#comment-16273523 ] ASF subversion and git services commented on PROTON-1064: - Commit 06fbad394a48989e1028c684f374a4357854d97a in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=06fbad3 ] PROTON-1064: [ruby] allow multiple handlers to container > ruby: native IO based on connection_driver.c > - > > Key: PROTON-1064 > URL: https://issues.apache.org/jira/browse/PROTON-1064 > Project: Qpid Proton > Issue Type: Improvement > Components: ruby-binding >Affects Versions: 0.11.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: proton-c-0.19.0 > > > Refactor ruby binding to use a native Ruby IO driver with the C > pn_connection_driver for AMQP protocol support. > Ruby ConnectionDriver - drive a single connection, single threaded > - Use any ruby IO subclass > - Works with native Ruby polling primitives > - Avoids Ruby threading issue with GVL (all IO is done in Ruby) > - Thread safe function injection for MT use. > Client/server examples using native ruby connect, multi-threaded broker > example using ruby listen. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1064) ruby: native IO based on connection_driver.c
[ https://issues.apache.org/jira/browse/PROTON-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273518#comment-16273518 ] ASF subversion and git services commented on PROTON-1064: - Commit 1f06e4bf9ca2f2d7cd130adb1494c0b18296345b in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=1f06e4b ] PROTON-1064: [ruby] Move MessagingHandler to core > ruby: native IO based on connection_driver.c > - > > Key: PROTON-1064 > URL: https://issues.apache.org/jira/browse/PROTON-1064 > Project: Qpid Proton > Issue Type: Improvement > Components: ruby-binding >Affects Versions: 0.11.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: proton-c-0.19.0 > > > Refactor ruby binding to use a native Ruby IO driver with the C > pn_connection_driver for AMQP protocol support. > Ruby ConnectionDriver - drive a single connection, single threaded > - Use any ruby IO subclass > - Works with native Ruby polling primitives > - Avoids Ruby threading issue with GVL (all IO is done in Ruby) > - Thread safe function injection for MT use. > Client/server examples using native ruby connect, multi-threaded broker > example using ruby listen. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1704) [c proactor] test_ipv4_ipv6 intermittent failure on FreeBSD
Alan Conway created PROTON-1704: --- Summary: [c proactor] test_ipv4_ipv6 intermittent failure on FreeBSD Key: PROTON-1704 URL: https://issues.apache.org/jira/browse/PROTON-1704 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: proton-c-0.18.1 Reporter: Alan Conway Assignee: Alan Conway Fix For: proton-c-0.19.0 The negative tests that you can't connect from ipv4 to ipv6 and vice-versa occasionally fail on FreeBSD because the connection succeeds. These tests are not valid given the range of options for bridging ipv4 and ipv6, so they were removed. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-878) qdrouterd should log real port if port 0 was specified for the listener port property in qdrouterd.conf
[
https://issues.apache.org/jira/browse/DISPATCH-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273395#comment-16273395
]
Alan Conway commented on DISPATCH-878:
--
FYI, on Unix platforms you can find the port using standard UNIX tools like
lsof, ss or netstat - with no help from qdrouterd. These tricks work on any
server with a single listening port - it gets trickier if your router has
multiple listening ports:
{code}
[aconway@grommit ~]$ lsof -p $(pidof qdrouterd) | grep TCP
qdrouterd 19463 aconway7u IPv4 7805194 0t0 TCP
localhost:42433 (LISTEN)
[aconway@grommit ~]$ ss -tlp | grep qdrouter
LISTEN 0 50 127.0.0.1:42433*:*
users:(("qdrouterd",pid=19463,fd=7))
[aconway@grommit ~]$ netstat -tlp | grep qdrouter
tcp0 0 localhost:42433 0.0.0.0:* LISTEN
19463/qdrouterd
{code}
> qdrouterd should log real port if port 0 was specified for the listener port
> property in qdrouterd.conf
> ---
>
> Key: DISPATCH-878
> URL: https://issues.apache.org/jira/browse/DISPATCH-878
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
> Environment: OS: Red Hat Linux Server release 6.4
> Dispatch version: 0.7.0
>Reporter: Jeremy
>
> For such a qdrouterd.conf configuration:
> {noformat}
> router {
> mode: standalone
> id: Router.A
> }
> listener {
> host: 0.0.0.0
> *port: 5673*
> authenticatePeer: no
> saslMechanisms: ANONYMOUS
> }
> {noformat}
> qdrouterd logs the port as such:
> {noformat}
> CONN_MGR (info) Configured Listener: 0.0.0.0:5673 proto=any, role=normal
> {noformat}
> When specifying port 0, so that the dispatch router runs on a random
> available port, the log is as such:
> {noformat}
> CONN_MGR (info) Configured Listener: 0.0.0.0:0 proto=any, role=normal
> {noformat}
> qdrouterd process can log instead the real port that was randomly chosen.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #228: No JIRA: Add SASL plugin requirement to SAS...
Github user bhardesty closed the pull request at: https://github.com/apache/qpid-dispatch/pull/228 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #228: No JIRA: Add SASL plugin requirement to SAS...
Github user bhardesty commented on a diff in the pull request: https://github.com/apache/qpid-dispatch/pull/228#discussion_r154185786 --- Diff: doc/new-book/configuration-security.adoc --- @@ -122,14 +122,20 @@ For information about additional `sslProfile` attributes, see xref:router_config If you plan to use SASL to authenticate connections, you must first add the SASL attributes to the `router` entity in the router's configuration file. These attributes define a set of SASL parameters that can be used by the router's incoming and outgoing connections. -// Do we need to say something here about only supporting Cyrus SASL? - .Prerequisites Before you can set up SASL, you must have the following: * xref:generating_sasl_database[The SASL database is generated.] * xref:configuring_sasl_database[The SASL configuration file is configured.] +* The Cyrus SASL plugin is installed for each SASL mechanism you plan to use. --- End diff -- Yes, please do. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton issue #114: [Ruby code Example] fix Messenger package
Github user kbrock commented on the issue: https://github.com/apache/qpid-proton/pull/114 thanks --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #228: No JIRA: Add SASL plugin requirement to SAS...
Github user ganeshmurthy commented on a diff in the pull request: https://github.com/apache/qpid-dispatch/pull/228#discussion_r154176414 --- Diff: doc/new-book/configuration-security.adoc --- @@ -122,14 +122,20 @@ For information about additional `sslProfile` attributes, see xref:router_config If you plan to use SASL to authenticate connections, you must first add the SASL attributes to the `router` entity in the router's configuration file. These attributes define a set of SASL parameters that can be used by the router's incoming and outgoing connections. -// Do we need to say something here about only supporting Cyrus SASL? - .Prerequisites Before you can set up SASL, you must have the following: * xref:generating_sasl_database[The SASL database is generated.] * xref:configuring_sasl_database[The SASL configuration file is configured.] +* The Cyrus SASL plugin is installed for each SASL mechanism you plan to use. --- End diff -- I think that is sufficient. This PR can be merged. Do you want me to merge it? Thanks. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #228: No JIRA: Add SASL plugin requirement to SAS...
Github user bhardesty commented on a diff in the pull request: https://github.com/apache/qpid-dispatch/pull/228#discussion_r154166429 --- Diff: doc/new-book/configuration-security.adoc --- @@ -122,14 +122,20 @@ For information about additional `sslProfile` attributes, see xref:router_config If you plan to use SASL to authenticate connections, you must first add the SASL attributes to the `router` entity in the router's configuration file. These attributes define a set of SASL parameters that can be used by the router's incoming and outgoing connections. -// Do we need to say something here about only supporting Cyrus SASL? - .Prerequisites Before you can set up SASL, you must have the following: * xref:generating_sasl_database[The SASL database is generated.] * xref:configuring_sasl_database[The SASL configuration file is configured.] +* The Cyrus SASL plugin is installed for each SASL mechanism you plan to use. --- End diff -- In later sections, we talk about setting the SASL mechanism by using the saslMechanisms attribute (for example: https://github.com/apache/qpid-dispatch/blob/master/doc/new-book/configuration-security.adoc#adding_sasl_authentication_to_incoming_connection). Rather than list them all in the doc, we just point to the official list from the Cyrus SASL doc. Do you think that's sufficient, or is there something particular about EXTERNAL that we should mention it as a prereq to setting up SASL? --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8039) [CVE-2017-15702] [Broker-J] HTTP Ports may be tricked into using the wrong authentication provider
[ https://issues.apache.org/jira/browse/QPID-8039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8039: - Description: In Qpid Broker-J 0.18..0.32 the when connecting to the HTTP port, it is possible to trick the port into using an authentication provider other than the one configured on the port. This becomes an issue if many authentication providers are configured and one offers less trust than another. This was resolved in Qpid Broker-J v6.0.0 and above. was:To be filled in later. > [CVE-2017-15702] [Broker-J] HTTP Ports may be tricked into using the wrong > authentication provider > -- > > Key: QPID-8039 > URL: https://issues.apache.org/jira/browse/QPID-8039 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: 0.18, 0.32 >Reporter: Lorenz Quack > Fix For: qpid-java-6.0 > > > In Qpid Broker-J 0.18..0.32 the when connecting to the HTTP port, it is > possible to trick the port into using an authentication provider other than > the one configured on the port. This becomes an issue if many > authentication providers are configured and one offers less trust than > another. > This was resolved in Qpid Broker-J v6.0.0 and above. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8039) [CVE-2017-15702] [Broker-J] HTTP Ports may be tricked into using the wrong authentication provider
[ https://issues.apache.org/jira/browse/QPID-8039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8039: - Affects Version/s: 0.18 > [CVE-2017-15702] [Broker-J] HTTP Ports may be tricked into using the wrong > authentication provider > -- > > Key: QPID-8039 > URL: https://issues.apache.org/jira/browse/QPID-8039 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: 0.18, 0.32 >Reporter: Lorenz Quack > Fix For: qpid-java-6.0 > > > To be filled in later. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8039) [CVE-2017-15702] [Broker-J] HTTP Ports may be tricked into using the wrong authentication provider
[ https://issues.apache.org/jira/browse/QPID-8039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8039: - Summary: [CVE-2017-15702] [Broker-J] HTTP Ports may be tricked into using the wrong authentication provider (was: [CVE-2017-15702] [Broker-J] HTTP Ports may be tricked into using the wrong HTTP port) > [CVE-2017-15702] [Broker-J] HTTP Ports may be tricked into using the wrong > authentication provider > -- > > Key: QPID-8039 > URL: https://issues.apache.org/jira/browse/QPID-8039 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: 0.32 >Reporter: Lorenz Quack > Fix For: qpid-java-6.0 > > > To be filled in later. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8039) [CVE-2017-15702] [Broker-J] HTTP Ports may be tricked into using the wrong HTTP port
[ https://issues.apache.org/jira/browse/QPID-8039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8039: - Summary: [CVE-2017-15702] [Broker-J] HTTP Ports may be tricked into using the wrong HTTP port (was: [Broker-J] Placeholder) > [CVE-2017-15702] [Broker-J] HTTP Ports may be tricked into using the wrong > HTTP port > > > Key: QPID-8039 > URL: https://issues.apache.org/jira/browse/QPID-8039 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: 0.32 >Reporter: Lorenz Quack > Fix For: qpid-java-6.0 > > > To be filled in later. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8039) [Broker-J] Placeholder
[ https://issues.apache.org/jira/browse/QPID-8039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8039: - Fix Version/s: qpid-java-6.0 > [Broker-J] Placeholder > -- > > Key: QPID-8039 > URL: https://issues.apache.org/jira/browse/QPID-8039 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: 0.32 >Reporter: Lorenz Quack > Fix For: qpid-java-6.0 > > > To be filled in later. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7947) [CVE-2017-15701] [Java Broker] [AMQP 1.0] Improve handling of empty and overlarge frames
[ https://issues.apache.org/jira/browse/QPID-7947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7947: - Summary: [CVE-2017-15701] [Java Broker] [AMQP 1.0] Improve handling of empty and overlarge frames (was: [Java Broker] [AMQP 1.0] Improve handling of empty and overlarge frames) > [CVE-2017-15701] [Java Broker] [AMQP 1.0] Improve handling of empty and > overlarge frames > > > Key: QPID-7947 > URL: https://issues.apache.org/jira/browse/QPID-7947 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Reporter: Rob Godfrey >Assignee: Keith Wall > Fix For: qpid-java-broker-7.0.0, qpid-java-6.1.5 > > > Empty frames should only be allowed for AMQP (and not SASL) transports. > Overlarge frames should be detected as soon as possible. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6933) Factor out a JMS client neutral messaging test suite from system tests
[ https://issues.apache.org/jira/browse/QPID-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16272982#comment-16272982 ] ASF subversion and git services commented on QPID-6933: --- Commit ad2e6a5e6f76399ea6c9bda61d386ad6b3631e33 in qpid-broker-j's branch refs/heads/master from [~alex.rufous] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=ad2e6a5 ] QPID-6933: [System Tests] Move TemporaryTopicTest into JMS 1.1 system tests > Factor out a JMS client neutral messaging test suite from system tests > -- > > Key: QPID-6933 > URL: https://issues.apache.org/jira/browse/QPID-6933 > Project: Qpid > Issue Type: Improvement > Components: Java Tests >Reporter: Keith Wall >Assignee: Alex Rudyy > > The existing system testsuite is in a poor state. > * It is poorly structured > * Mixes different types of test. i.e. messaging behaviour with those that > test features of the Java Broker (e.g. REST). > * Many of the tests refer directly to the implementation classes of the Qpid > Client 0-8..0-10 client meaning the tests cannot be run using the new client. > As a first step, we want to factor out a separate messaging system test suite: > * The tests in this suite will be JMS client neutral. > * Written in terms of JNDI/JMS client > * Configurations/Broker observations will be performed via a clean > Broker-neutral facade. For instance > ** a mechanism to cause the queue to be created of a particular type. > ** a mechanism to observe a queue depth. > * The tests will be classified by feature (to be defined) > * The classification system will be used to drive an exclusion feature (to be > defined). -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[SECURITY] [CVE-2017-15701] Apache Qpid Broker-J Denial of Service Vulnerability
CVE-2017-15701: Apache Qpid Broker-J denial of service vulnerability Severity: Important Vendor: The Apache Software Foundation Versions Affected: 6.1.0, 6.1.1, 6.1.2, 6.1.3, and 6.1.4 Description: The broker does not properly enforce a maximum frame size in AMQP 1.0 frames. A remote unauthenticated attacker could exploit this to cause the broker to exhaust all available memory and eventually terminate. Older AMQP protocols are not affected. Resolution: Users who have AMQP 1.0 support enabled (default) should upgrade their Qpid Broker-J to version 6.1.5 or later. Mitigation: If upgrading the broker is not possible, users can choose to disable AMQP 1.0 by either setting the system property "qpid.plugin.disabled:protocolenginecreator.AMQP_1_0" to "true", excluding "AMQP_1_0" from the supported protocol list on all AMQP ports, or by removing the AMQP 1.0 related jar files from the Java classpath. References: https://issues.apache.org/jira/browse/QPID-7947 - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[SECURITY] [CVE-2017-15702] Apache Qpid Broker-J Authentication Vulnerability on HTTP Ports
CVE-2017-15702: Apache Qpid Broker-J authentication vulnerability on HTTP ports Severity: Important Vendor: The Apache Software Foundation Versions Affected: Versions 0.18 through 0.32 Description: If the broker is configured with different authentication providers on different ports one of which is an HTTP port, then the broker can be tricked by a remote unauthenticated attacker connecting to the HTTP port into using an authentication provider that was configured on a different port. The attacker still needs valid credentials with the authentication provider on the spoofed port. This becomes an issue when the spoofed port has weaker authentication protection (e.g., anonymous access, default accounts) and is normally protected by firewall rules or similar which can be circumvented by this vulnerability. AMQP ports are not affected. Versions 6.0.0 and newer are not affected. Resolution: Users of affected versions who have more than one port and different authentication providers configured on them should upgrade to a later unaffected version. Mitigation: If upgrading the broker is not possible then users should ensure all their authentication providers offer an equal amount of protection. In particular, authentication providers with default accounts and those with anonymous access should be removed if other providers in use require credentials. References: https://issues.apache.org/jira/browse/QPID-8039 - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6933) Factor out a JMS client neutral messaging test suite from system tests
[ https://issues.apache.org/jira/browse/QPID-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16272933#comment-16272933 ] ASF subversion and git services commented on QPID-6933: --- Commit 7e6e56eb9cff5fc6eecc43553abff66c65300764 in qpid-broker-j's branch refs/heads/master from [~alex.rufous] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=7e6e56e ] QPID-6933: [System Tests] Move more transaction tests into JMS 1.1 system tests > Factor out a JMS client neutral messaging test suite from system tests > -- > > Key: QPID-6933 > URL: https://issues.apache.org/jira/browse/QPID-6933 > Project: Qpid > Issue Type: Improvement > Components: Java Tests >Reporter: Keith Wall >Assignee: Alex Rudyy > > The existing system testsuite is in a poor state. > * It is poorly structured > * Mixes different types of test. i.e. messaging behaviour with those that > test features of the Java Broker (e.g. REST). > * Many of the tests refer directly to the implementation classes of the Qpid > Client 0-8..0-10 client meaning the tests cannot be run using the new client. > As a first step, we want to factor out a separate messaging system test suite: > * The tests in this suite will be JMS client neutral. > * Written in terms of JNDI/JMS client > * Configurations/Broker observations will be performed via a clean > Broker-neutral facade. For instance > ** a mechanism to cause the queue to be created of a particular type. > ** a mechanism to observe a queue depth. > * The tests will be classified by feature (to be defined) > * The classification system will be used to drive an exclusion feature (to be > defined). -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-1703) [cpp] Remove auto_settle from receiver options
[ https://issues.apache.org/jira/browse/PROTON-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1703. - Resolution: Fixed > [cpp] Remove auto_settle from receiver options > -- > > Key: PROTON-1703 > URL: https://issues.apache.org/jira/browse/PROTON-1703 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: proton-c-0.18.1 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: proton-c-0.19.0 > > > auto_settle is a sender-only option, the receiver equivalent is auto_accept. > auto_settle is only used at messaging_adapter.cpp#L172, which applies only to > senders, it was included in the option list by mistake. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1703) [cpp] Remove auto_settle from receiver options
[ https://issues.apache.org/jira/browse/PROTON-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16272697#comment-16272697 ] ASF subversion and git services commented on PROTON-1703: - Commit d5069e1250b50ec3dc7205a9fa0cb1b33bb1b1c8 in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=d5069e1 ] PROTON-1703: [cpp] Remove auto_settle from receiver_options auto_settle is a sender-only option, the receiver equivalent is auto_accept It is only used at messaging_adapter.cpp#L172, which applies only to senders. > [cpp] Remove auto_settle from receiver options > -- > > Key: PROTON-1703 > URL: https://issues.apache.org/jira/browse/PROTON-1703 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: proton-c-0.18.1 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: proton-c-0.19.0 > > > auto_settle is a sender-only option, the receiver equivalent is auto_accept. > auto_settle is only used at messaging_adapter.cpp#L172, which applies only to > senders, it was included in the option list by mistake. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1636) Fairly Consistent (but intermittent) hangs in ruby-example-test/ruby-test-container using Travis CI
[
https://issues.apache.org/jira/browse/PROTON-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16272695#comment-16272695
]
ASF subversion and git services commented on PROTON-1636:
-
Commit 0d399a229abd66e0bb3fa473e65f1681772cec2a in qpid-proton's branch
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=0d399a2 ]
PROTON-1636: [ruby] fix race condition in ruby container tests
Made "stopped" a terminal state for the Container to avoid races during
shut-down, e.g. because threads have not even entered #run when the container
auto-stops.
> Fairly Consistent (but intermittent) hangs in
> ruby-example-test/ruby-test-container using Travis CI
> ---
>
> Key: PROTON-1636
> URL: https://issues.apache.org/jira/browse/PROTON-1636
> Project: Qpid Proton
> Issue Type: Bug
> Components: ruby-binding
>Affects Versions: proton-c-0.18.0
> Environment: Travis CI:
> Ubuntu 1404 with lots of changes
>Reporter: Andrew Stitcher
>Assignee: Alan Conway
> Fix For: proton-c-0.19.0
>
>
> This is pretty annoying as it makes the build fail about 50% of the time for
> me and so it looks like the change just made failed the build.
> {noformat}
> Start 14: ruby-example-test
> 14: Test command: /home/travis/.rvm/rubies/ruby-2.4.1/bin/ruby
> "example_test.rb" "-v"
> 14: Test timeout computed to be: 1500
> 14: Run options: -v --seed 7224
> 14:
> 14: # Running:
> 14:
> 14: ExampleTest#test_client_server = 0.30 s = .
> No output has been received in the last 10m0s, this potentially indicates a
> stalled build or something wrong with the build itself.
> Check the details on how to adjust your build configuration on:
> https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received
> The build has been terminated
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1703) [cpp] Remove auto_settle from receiver options
Alan Conway created PROTON-1703: --- Summary: [cpp] Remove auto_settle from receiver options Key: PROTON-1703 URL: https://issues.apache.org/jira/browse/PROTON-1703 Project: Qpid Proton Issue Type: Bug Components: cpp-binding Affects Versions: proton-c-0.18.1 Reporter: Alan Conway Assignee: Alan Conway Fix For: proton-c-0.19.0 auto_settle is a sender-only option, the receiver equivalent is auto_accept. auto_settle is only used at messaging_adapter.cpp#L172, which applies only to senders, it was included in the option list by mistake. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6933) Factor out a JMS client neutral messaging test suite from system tests
[ https://issues.apache.org/jira/browse/QPID-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16272467#comment-16272467 ] ASF subversion and git services commented on QPID-6933: --- Commit dd1e90d663a4dc4c068d55c8ed2ed55cc48666fa in qpid-broker-j's branch refs/heads/master from [~alex.rufous] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=dd1e90d ] QPID-6933: [System Tests] Clean up tests > Factor out a JMS client neutral messaging test suite from system tests > -- > > Key: QPID-6933 > URL: https://issues.apache.org/jira/browse/QPID-6933 > Project: Qpid > Issue Type: Improvement > Components: Java Tests >Reporter: Keith Wall >Assignee: Alex Rudyy > > The existing system testsuite is in a poor state. > * It is poorly structured > * Mixes different types of test. i.e. messaging behaviour with those that > test features of the Java Broker (e.g. REST). > * Many of the tests refer directly to the implementation classes of the Qpid > Client 0-8..0-10 client meaning the tests cannot be run using the new client. > As a first step, we want to factor out a separate messaging system test suite: > * The tests in this suite will be JMS client neutral. > * Written in terms of JNDI/JMS client > * Configurations/Broker observations will be performed via a clean > Broker-neutral facade. For instance > ** a mechanism to cause the queue to be created of a particular type. > ** a mechanism to observe a queue depth. > * The tests will be classified by feature (to be defined) > * The classification system will be used to drive an exclusion feature (to be > defined). -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
