[jira] [Commented] (DISPATCH-1005) New system to validate restriction of allowed TLS versions
[ https://issues.apache.org/jira/browse/DISPATCH-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16486591#comment-16486591 ] ASF GitHub Bot commented on DISPATCH-1005: -- GitHub user fgiorgetti opened a pull request: https://github.com/apache/qpid-dispatch/pull/308 DISPATCH-1005 - Fixed system_tests_ssl.py to work on rhel6 and other … …distros You can merge this pull request into a Git repository by running: $ git pull https://github.com/fgiorgetti/qpid-dispatch fgiorgetti-DISPATCH-1005 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/308.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 #308 commit 21728c133d4e63b2666de3bdbde438ef702c6755 Author: Fernando Giorgetti Date: 2018-05-22T20:44:14Z DISPATCH-1005 - Fixed system_tests_ssl.py to work on rhel6 and other distros > New system to validate restriction of allowed TLS versions > -- > > Key: DISPATCH-1005 > URL: https://issues.apache.org/jira/browse/DISPATCH-1005 > Project: Qpid Dispatch > Issue Type: Test > Components: Tests >Reporter: Fernando Giorgetti >Priority: Major > Fix For: 1.2.0 > > -- 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 #308: DISPATCH-1005 - Fixed system_tests_ssl.py t...
GitHub user fgiorgetti opened a pull request: https://github.com/apache/qpid-dispatch/pull/308 DISPATCH-1005 - Fixed system_tests_ssl.py to work on rhel6 and other ⦠â¦distros You can merge this pull request into a Git repository by running: $ git pull https://github.com/fgiorgetti/qpid-dispatch fgiorgetti-DISPATCH-1005 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/308.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 #308 commit 21728c133d4e63b2666de3bdbde438ef702c6755 Author: Fernando Giorgetti Date: 2018-05-22T20:44:14Z DISPATCH-1005 - Fixed system_tests_ssl.py to work on rhel6 and other distros --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8192) [Broker-J] Make bindingKey parameter mandatory in exchange bind/unbind operations
[ https://issues.apache.org/jira/browse/QPID-8192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8192: - Fix Version/s: (was: qpid-java-broker-7.0.4) qpid-java-broker-7.1.0 > [Broker-J] Make bindingKey parameter mandatory in exchange bind/unbind > operations > - > > Key: QPID-8192 > URL: https://issues.apache.org/jira/browse/QPID-8192 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.0.3, qpid-java-broker-7.0.2, > qpid-java-broker-7.0.0, qpid-java-broker-7.0.1 >Reporter: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.1.0 > > > Make bindingKey parameter mandatory in exchange bind/unbind operations but > allow the value of the binding key to be the empty string. Optional > bindingKey parameter causes confusions in understanding how bind/unbind > operations works, as omitting bindingKey in unbind operation could be > misinterpreted as bulk bindings deletion for the given destination. The > unbind operation description text should be fixed as well. -- 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-8181) [Broker-J] Add statistics for a total number of connections established on AMQP port
[ https://issues.apache.org/jira/browse/QPID-8181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8181: - Status: Reviewable (was: In Progress) > [Broker-J] Add statistics for a total number of connections established on > AMQP port > > > Key: QPID-8181 > URL: https://issues.apache.org/jira/browse/QPID-8181 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Minor > Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4 > > > A statistics for a current number of connections is available on AMQP port. > Introduction of additional statistic for a total number of connections > established on AMQP port would allow to detect such use cases as "connection > per message anti-pattern" without even looking into Qpid broker logs. -- 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-8181) [Broker-J] Add statistics for a total number of connections established on AMQP port
[ https://issues.apache.org/jira/browse/QPID-8181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484573#comment-16484573 ] ASF subversion and git services commented on QPID-8181: --- Commit 762d009f48f5cce8773dcc48352028541c6913d9 in qpid-broker-j's branch refs/heads/7.0.x from [~alex.rufous] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=762d009 ] QPID-8181: [Broker-J] Add statistics for a total number of messaging connections made to virtualhost (cherry picked from commit 830c3183735df7169c05b52cb71f0a6a1af5af39) > [Broker-J] Add statistics for a total number of connections established on > AMQP port > > > Key: QPID-8181 > URL: https://issues.apache.org/jira/browse/QPID-8181 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Minor > Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4 > > > A statistics for a current number of connections is available on AMQP port. > Introduction of additional statistic for a total number of connections > established on AMQP port would allow to detect such use cases as "connection > per message anti-pattern" without even looking into Qpid broker logs. -- 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-8181) [Broker-J] Add statistics for a total number of connections established on AMQP port
[ https://issues.apache.org/jira/browse/QPID-8181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484566#comment-16484566 ] ASF subversion and git services commented on QPID-8181: --- Commit 830c3183735df7169c05b52cb71f0a6a1af5af39 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=830c318 ] QPID-8181: [Broker-J] Add statistics for a total number of messaging connections made to virtualhost > [Broker-J] Add statistics for a total number of connections established on > AMQP port > > > Key: QPID-8181 > URL: https://issues.apache.org/jira/browse/QPID-8181 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Minor > Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4 > > > A statistics for a current number of connections is available on AMQP port. > Introduction of additional statistic for a total number of connections > established on AMQP port would allow to detect such use cases as "connection > per message anti-pattern" without even looking into Qpid broker logs. -- 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] [Reopened] (QPID-8181) [Broker-J] Add statistics for a total number of connections established on AMQP port
[ https://issues.apache.org/jira/browse/QPID-8181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reopened QPID-8181: -- Assignee: Alex Rudyy The statistics for a total number of connection can be also added into VirtualHost > [Broker-J] Add statistics for a total number of connections established on > AMQP port > > > Key: QPID-8181 > URL: https://issues.apache.org/jira/browse/QPID-8181 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Minor > Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4 > > > A statistics for a current number of connections is available on AMQP port. > Introduction of additional statistic for a total number of connections > established on AMQP port would allow to detect such use cases as "connection > per message anti-pattern" without even looking into Qpid broker logs. -- 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] [Closed] (QPID-8165) [Broker-J][WMC] Validation of configured object names is too restrictive in Web Management Console
[
https://issues.apache.org/jira/browse/QPID-8165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy closed QPID-8165.
Resolution: Fixed
> [Broker-J][WMC] Validation of configured object names is too restrictive in
> Web Management Console
> --
>
> Key: QPID-8165
> URL: https://issues.apache.org/jira/browse/QPID-8165
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-6.1.6, qpid-java-broker-7.0.3,
> qpid-java-broker-7.0.2, 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-broker-7.0.0,
> qpid-java-6.1.5, qpid-java-broker-7.0.1
>Reporter: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4
>
>
> WMC only allows to create (or edit) configured objects with names consisting
> only from any mixture of digits, letters, and underscores. This restriction
> was added into Web Management Console to meet the requirements of AMQP 0-8
> protocol. The queue and exchange names in domain definition are defined as
> name consisting only from digits, letters, and underscores.
> {quote}
> The queue name identifies the queue within the vhost. Queue
> names may consist of any mixture of digits, letters, and
> underscores.
> {quote}
> {quote}
> The exchange name is a client-selected string that identifies
> the exchange for publish methods. Exchange names may consist
> of any mixture of digits, letters, and underscores. Exchange
> names are scoped by the virtual host.
> {quote}
> However, in definitions of declare commands for queue and exchange the AMQP
> 0-8 specifies a regular expression for the names allowing more characters:
> {code}
> ^[a-zA-Z0-9-_.:]*$
> {code}
> The same regular expression is defined in specifications for AMQP 0-9 and
> 0-9-1.
> The names of virtual hosts in specifications for AMQP 0-8 and AMQP 0-9 should
> match regular expression (as per documentation for connection open)
> {code}
> ^[a-zA-Z0-9/-_]+$
> {code}
> AMQP 0-10 allows more characters in queue name
> {quote}
> Queue names must have a length
> of between 1 and 255 characters inclusive, must start with a digit,
> letter or underscores
> ('_') character, and must be otherwise encoded in UTF-8.
> {quote}
> As a minimum, the Web Management Console should allow creation of queues,
> exchanges with names matching {{\^[a-zA-Z0-9-_.:]\+$}}. The virtual host
> names matching regular expression {{\^[a-zA-Z0-9-_]+\$}} should be allowed
> (i.e. continue to disallow the slash). The names of other configured objects
> can be unrestricted.
> Alternatively, we can add some sort of AMQP compatibility modes to Web
> Management Console and management API when required level compatibility can
> be configured by the user and different validation rules can apply based on
> required compatibility.
--
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-8165) [Broker-J][WMC] Validation of configured object names is too restrictive in Web Management Console
[
https://issues.apache.org/jira/browse/QPID-8165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484516#comment-16484516
]
Alex Rudyy commented on QPID-8165:
--
Changes were reviewed and merged into 7.0.x branch. Thus, closing the JIRA
> [Broker-J][WMC] Validation of configured object names is too restrictive in
> Web Management Console
> --
>
> Key: QPID-8165
> URL: https://issues.apache.org/jira/browse/QPID-8165
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-6.1.6, qpid-java-broker-7.0.3,
> qpid-java-broker-7.0.2, 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-broker-7.0.0,
> qpid-java-6.1.5, qpid-java-broker-7.0.1
>Reporter: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4
>
>
> WMC only allows to create (or edit) configured objects with names consisting
> only from any mixture of digits, letters, and underscores. This restriction
> was added into Web Management Console to meet the requirements of AMQP 0-8
> protocol. The queue and exchange names in domain definition are defined as
> name consisting only from digits, letters, and underscores.
> {quote}
> The queue name identifies the queue within the vhost. Queue
> names may consist of any mixture of digits, letters, and
> underscores.
> {quote}
> {quote}
> The exchange name is a client-selected string that identifies
> the exchange for publish methods. Exchange names may consist
> of any mixture of digits, letters, and underscores. Exchange
> names are scoped by the virtual host.
> {quote}
> However, in definitions of declare commands for queue and exchange the AMQP
> 0-8 specifies a regular expression for the names allowing more characters:
> {code}
> ^[a-zA-Z0-9-_.:]*$
> {code}
> The same regular expression is defined in specifications for AMQP 0-9 and
> 0-9-1.
> The names of virtual hosts in specifications for AMQP 0-8 and AMQP 0-9 should
> match regular expression (as per documentation for connection open)
> {code}
> ^[a-zA-Z0-9/-_]+$
> {code}
> AMQP 0-10 allows more characters in queue name
> {quote}
> Queue names must have a length
> of between 1 and 255 characters inclusive, must start with a digit,
> letter or underscores
> ('_') character, and must be otherwise encoded in UTF-8.
> {quote}
> As a minimum, the Web Management Console should allow creation of queues,
> exchanges with names matching {{\^[a-zA-Z0-9-_.:]\+$}}. The virtual host
> names matching regular expression {{\^[a-zA-Z0-9-_]+\$}} should be allowed
> (i.e. continue to disallow the slash). The names of other configured objects
> can be unrestricted.
> Alternatively, we can add some sort of AMQP compatibility modes to Web
> Management Console and management API when required level compatibility can
> be configured by the user and different validation rules can apply based on
> required compatibility.
--
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-8165) [Broker-J][WMC] Validation of configured object names is too restrictive in Web Management Console
[
https://issues.apache.org/jira/browse/QPID-8165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484512#comment-16484512
]
ASF subversion and git services commented on QPID-8165:
---
Commit 9286ee01b1f7519762f8dd0d447679418ef002e4 in qpid-broker-j's branch
refs/heads/7.0.x from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=9286ee0 ]
QPID-8165: [Broker-J][WMC] Fix RegEx to allow more characters in configured
object names
(cherry picked from commit c8fae15492a09155039a61d11bf7d2dbdc280c65)
> [Broker-J][WMC] Validation of configured object names is too restrictive in
> Web Management Console
> --
>
> Key: QPID-8165
> URL: https://issues.apache.org/jira/browse/QPID-8165
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-6.1.6, qpid-java-broker-7.0.3,
> qpid-java-broker-7.0.2, 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-broker-7.0.0,
> qpid-java-6.1.5, qpid-java-broker-7.0.1
>Reporter: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.4
>
>
> WMC only allows to create (or edit) configured objects with names consisting
> only from any mixture of digits, letters, and underscores. This restriction
> was added into Web Management Console to meet the requirements of AMQP 0-8
> protocol. The queue and exchange names in domain definition are defined as
> name consisting only from digits, letters, and underscores.
> {quote}
> The queue name identifies the queue within the vhost. Queue
> names may consist of any mixture of digits, letters, and
> underscores.
> {quote}
> {quote}
> The exchange name is a client-selected string that identifies
> the exchange for publish methods. Exchange names may consist
> of any mixture of digits, letters, and underscores. Exchange
> names are scoped by the virtual host.
> {quote}
> However, in definitions of declare commands for queue and exchange the AMQP
> 0-8 specifies a regular expression for the names allowing more characters:
> {code}
> ^[a-zA-Z0-9-_.:]*$
> {code}
> The same regular expression is defined in specifications for AMQP 0-9 and
> 0-9-1.
> The names of virtual hosts in specifications for AMQP 0-8 and AMQP 0-9 should
> match regular expression (as per documentation for connection open)
> {code}
> ^[a-zA-Z0-9/-_]+$
> {code}
> AMQP 0-10 allows more characters in queue name
> {quote}
> Queue names must have a length
> of between 1 and 255 characters inclusive, must start with a digit,
> letter or underscores
> ('_') character, and must be otherwise encoded in UTF-8.
> {quote}
> As a minimum, the Web Management Console should allow creation of queues,
> exchanges with names matching {{\^[a-zA-Z0-9-_.:]\+$}}. The virtual host
> names matching regular expression {{\^[a-zA-Z0-9-_]+\$}} should be allowed
> (i.e. continue to disallow the slash). The names of other configured objects
> can be unrestricted.
> Alternatively, we can add some sort of AMQP compatibility modes to Web
> Management Console and management API when required level compatibility can
> be configured by the user and different validation rules can apply based on
> required compatibility.
--
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-1833) [cpp] Crash on Windows after calling container::stop()
[
https://issues.apache.org/jira/browse/PROTON-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484174#comment-16484174
]
VincentSa commented on PROTON-1833:
---
Hi. I will replace Baptiste as he joined another project.
I will test it with version proton-c-0.23.0 as soon as it is available and will
give you the result.
and then I will prepare a small test program If necessary,
> [cpp] Crash on Windows after calling container::stop()
> --
>
> Key: PROTON-1833
> URL: https://issues.apache.org/jira/browse/PROTON-1833
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.21.0
> Environment: Proton version : 0.21
> Windows 7 - 64 bits
> Visual studio 2010
>Reporter: Baptiste
>Assignee: Cliff Jansen
>Priority: Critical
> Labels: crash, windows
> Fix For: proton-c-0.23.0
>
>
> Just creating a proton::container, listening locally on
> [0.0.0.0:5672|http://0.0.0.0:5672/] and then call stop() on the container and
> getting outside of the scope (object is then destroy) => the crash happen.
> Where does it crash ? In *win_iocp.c*, the line in red
> void pn_proactor_free(pn_proactor_t *p)
> {
> {color:#ff}DeleteTimerQueueEx(p->timer_queue,
> INVALID_HANDLE_VALUE){color};
> DeleteCriticalSection(&p->timer_lock);
> DeleteCriticalSection(&p->bind_lock);
> proactor_shutdown(p);
> delete p->reaper;
> WSACleanup();
> pn_collector_free(p->collector);
> free(p);
> }
>
> NOTE:
> A lot of tests failed on windows :
> 1> The following tests FAILED:
> 1> 8 - cpp-container_test (Failed)
> 1> 10 - cpp-reconnect_test (Failed)
> 1> 21 - c-proactor-tests (Failed)
> 1> 23 - c-example-tests (Failed)
> 1> 24 - cpp-example-container (Failed)
> 1> 25 - cpp-example-container-ssl (Failed)
--
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] [Assigned] (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:all-tabpanel
]
Alan Conway reassigned PROTON-1842:
---
Assignee: Alan Conway
> [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-dispatch pull request #287: NO-JIRA - Removed sleep and introduced a ti...
Github user ganeshmurthy closed the pull request at: https://github.com/apache/qpid-dispatch/pull/287 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1005) New system to validate restriction of allowed TLS versions
[ https://issues.apache.org/jira/browse/DISPATCH-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-1005. - Resolution: Fixed Fix Version/s: 1.2.0 > New system to validate restriction of allowed TLS versions > -- > > Key: DISPATCH-1005 > URL: https://issues.apache.org/jira/browse/DISPATCH-1005 > Project: Qpid Dispatch > Issue Type: Test > Components: Tests >Reporter: Fernando Giorgetti >Priority: Major > Fix For: 1.2.0 > > -- 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-1005) New system to validate restriction of allowed TLS versions
[ https://issues.apache.org/jira/browse/DISPATCH-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484060#comment-16484060 ] ASF GitHub Bot commented on DISPATCH-1005: -- Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/307 > New system to validate restriction of allowed TLS versions > -- > > Key: DISPATCH-1005 > URL: https://issues.apache.org/jira/browse/DISPATCH-1005 > Project: Qpid Dispatch > Issue Type: Test > Components: Tests >Reporter: Fernando Giorgetti >Priority: Major > Fix For: 1.2.0 > > -- 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-1005) New system to validate restriction of allowed TLS versions
[ https://issues.apache.org/jira/browse/DISPATCH-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484059#comment-16484059 ] ASF subversion and git services commented on DISPATCH-1005: --- Commit 5d5db890716b87499f40bb16d4e9dbd3700f6f45 in qpid-dispatch's branch refs/heads/master from [~fgiorget] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=5d5db89 ] DISPATCH-1005 - New system test to validate restriction of TLS protocols > New system to validate restriction of allowed TLS versions > -- > > Key: DISPATCH-1005 > URL: https://issues.apache.org/jira/browse/DISPATCH-1005 > Project: Qpid Dispatch > Issue Type: Test > Components: Tests >Reporter: Fernando Giorgetti >Priority: Major > -- 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 #307: DISPATCH-1005 - New system test to validate...
Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/307 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (DISPATCH-1006) QIT 2-node test fails with all brokers
[
https://issues.apache.org/jira/browse/DISPATCH-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross closed DISPATCH-1006.
--
> QIT 2-node test fails with all brokers
> --
>
> Key: DISPATCH-1006
> URL: https://issues.apache.org/jira/browse/DISPATCH-1006
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Kim van der Riet
>Assignee: Ganesh Murthy
>Priority: Major
> Attachments: dispatch-2node.qpid-cpp.types.pcapng,
> qdrouterd.node1.conf, qdrouterd.node1.log, qdrouterd.node2.conf,
> qdrouterd.node2.log, qpidd.conf
>
>
> Running the Qpid Interop Test 2-node test using dispatch in the following
> configuration fails:
> {noformat}
> 900156729002
> sender --> node1 --> broker --> node2 --> receiver{noformat}
> Running the test as follows:
> {noformat}
> python -m qpid_interop_test.amqp_types_test --include-type boolean
> --include-shim ProtonCpp --sender localhost:9001 --receiver
> localhost:9002{noformat}
> results in a test hang (until it times out). Looking at the logs, I see when
> the sender connects:
> {noformat}
> 2018-05-21 11:47:39.811401 -0400 SERVER (info) Accepted connection to
> ::1:9001 from ::1:36088
> 2018-05-21 11:47:49.807716 -0400 SERVER (info) Connection from ::1:36088 (to
> ::1:9001) failed: amqp:connection:framing-error connection aborted
> {noformat}
> but there is never an AMQP close or error of any kind on the wire (see
> attached wireshark file). The test simply hangs until it times out. (If you
> use Wireshark, it will be necessary to change the AMQP protocol port from
> 5672 to 9001 to see this part of the conversation).
> The same occurs if using ActiveMQ and Artemis as the center broker. The same
> occurs for all clients, I have tried the ProtonCpp, ProtonPython2,
> ProtonPython3 and RheaJs clients, all with the same result. However, running
> a single-node test works ok.
> Also attached are the two config files for the two dispatch nodes, the config
> file for qpid-cpp and the log files for the two dispatch nodes.
--
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] (DISPATCH-1006) QIT 2-node test fails with all brokers
[
https://issues.apache.org/jira/browse/DISPATCH-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated DISPATCH-1006:
---
Fix Version/s: (was: 1.1.0)
> QIT 2-node test fails with all brokers
> --
>
> Key: DISPATCH-1006
> URL: https://issues.apache.org/jira/browse/DISPATCH-1006
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Kim van der Riet
>Assignee: Ganesh Murthy
>Priority: Major
> Attachments: dispatch-2node.qpid-cpp.types.pcapng,
> qdrouterd.node1.conf, qdrouterd.node1.log, qdrouterd.node2.conf,
> qdrouterd.node2.log, qpidd.conf
>
>
> Running the Qpid Interop Test 2-node test using dispatch in the following
> configuration fails:
> {noformat}
> 900156729002
> sender --> node1 --> broker --> node2 --> receiver{noformat}
> Running the test as follows:
> {noformat}
> python -m qpid_interop_test.amqp_types_test --include-type boolean
> --include-shim ProtonCpp --sender localhost:9001 --receiver
> localhost:9002{noformat}
> results in a test hang (until it times out). Looking at the logs, I see when
> the sender connects:
> {noformat}
> 2018-05-21 11:47:39.811401 -0400 SERVER (info) Accepted connection to
> ::1:9001 from ::1:36088
> 2018-05-21 11:47:49.807716 -0400 SERVER (info) Connection from ::1:36088 (to
> ::1:9001) failed: amqp:connection:framing-error connection aborted
> {noformat}
> but there is never an AMQP close or error of any kind on the wire (see
> attached wireshark file). The test simply hangs until it times out. (If you
> use Wireshark, it will be necessary to change the AMQP protocol port from
> 5672 to 9001 to see this part of the conversation).
> The same occurs if using ActiveMQ and Artemis as the center broker. The same
> occurs for all clients, I have tried the ProtonCpp, ProtonPython2,
> ProtonPython3 and RheaJs clients, all with the same result. However, running
> a single-node test works ok.
> Also attached are the two config files for the two dispatch nodes, the config
> file for qpid-cpp and the log files for the two dispatch nodes.
--
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-1006) QIT 2-node test fails with all brokers
[
https://issues.apache.org/jira/browse/DISPATCH-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1006.
-
Resolution: Not A Bug
Fix Version/s: 1.1.0
The sender was not sending to a link routed address and hence the lack of flow.
Once the sender sends to a link routed address, the problem goes away. Marking
this not a bug.
> QIT 2-node test fails with all brokers
> --
>
> Key: DISPATCH-1006
> URL: https://issues.apache.org/jira/browse/DISPATCH-1006
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Kim van der Riet
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.1.0
>
> Attachments: dispatch-2node.qpid-cpp.types.pcapng,
> qdrouterd.node1.conf, qdrouterd.node1.log, qdrouterd.node2.conf,
> qdrouterd.node2.log, qpidd.conf
>
>
> Running the Qpid Interop Test 2-node test using dispatch in the following
> configuration fails:
> {noformat}
> 900156729002
> sender --> node1 --> broker --> node2 --> receiver{noformat}
> Running the test as follows:
> {noformat}
> python -m qpid_interop_test.amqp_types_test --include-type boolean
> --include-shim ProtonCpp --sender localhost:9001 --receiver
> localhost:9002{noformat}
> results in a test hang (until it times out). Looking at the logs, I see when
> the sender connects:
> {noformat}
> 2018-05-21 11:47:39.811401 -0400 SERVER (info) Accepted connection to
> ::1:9001 from ::1:36088
> 2018-05-21 11:47:49.807716 -0400 SERVER (info) Connection from ::1:36088 (to
> ::1:9001) failed: amqp:connection:framing-error connection aborted
> {noformat}
> but there is never an AMQP close or error of any kind on the wire (see
> attached wireshark file). The test simply hangs until it times out. (If you
> use Wireshark, it will be necessary to change the AMQP protocol port from
> 5672 to 9001 to see this part of the conversation).
> The same occurs if using ActiveMQ and Artemis as the center broker. The same
> occurs for all clients, I have tried the ProtonCpp, ProtonPython2,
> ProtonPython3 and RheaJs clients, all with the same result. However, running
> a single-node test works ok.
> Also attached are the two config files for the two dispatch nodes, the config
> file for qpid-cpp and the log files for the two dispatch nodes.
--
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-1005) New system to validate restriction of allowed TLS versions
[ https://issues.apache.org/jira/browse/DISPATCH-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483963#comment-16483963 ] ASF GitHub Bot commented on DISPATCH-1005: -- GitHub user fgiorgetti opened a pull request: https://github.com/apache/qpid-dispatch/pull/307 DISPATCH-1005 - New system test to validate restriction of TLS protocols You can merge this pull request into a Git repository by running: $ git pull https://github.com/fgiorgetti/qpid-dispatch fgiorgetti-DISPATCH-1005 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/307.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 #307 commit 5d5db890716b87499f40bb16d4e9dbd3700f6f45 Author: Fernando Giorgetti Date: 2018-05-18T17:26:51Z DISPATCH-1005 - New system test to validate restriction of TLS protocols > New system to validate restriction of allowed TLS versions > -- > > Key: DISPATCH-1005 > URL: https://issues.apache.org/jira/browse/DISPATCH-1005 > Project: Qpid Dispatch > Issue Type: Test > Components: Tests >Reporter: Fernando Giorgetti >Priority: Major > -- 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 #307: DISPATCH-1005 - New system test to validate...
GitHub user fgiorgetti opened a pull request: https://github.com/apache/qpid-dispatch/pull/307 DISPATCH-1005 - New system test to validate restriction of TLS protocols You can merge this pull request into a Git repository by running: $ git pull https://github.com/fgiorgetti/qpid-dispatch fgiorgetti-DISPATCH-1005 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/307.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 #307 commit 5d5db890716b87499f40bb16d4e9dbd3700f6f45 Author: Fernando Giorgetti Date: 2018-05-18T17:26:51Z DISPATCH-1005 - New system test to validate restriction of TLS protocols --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #306: DISPATCH-1005 - New system test to validate...
Github user fgiorgetti closed the pull request at: https://github.com/apache/qpid-dispatch/pull/306 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1005) New system to validate restriction of allowed TLS versions
[ https://issues.apache.org/jira/browse/DISPATCH-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483956#comment-16483956 ] ASF GitHub Bot commented on DISPATCH-1005: -- Github user fgiorgetti closed the pull request at: https://github.com/apache/qpid-dispatch/pull/306 > New system to validate restriction of allowed TLS versions > -- > > Key: DISPATCH-1005 > URL: https://issues.apache.org/jira/browse/DISPATCH-1005 > Project: Qpid Dispatch > Issue Type: Test > Components: Tests >Reporter: Fernando Giorgetti >Priority: Major > -- 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-7153) Allow expired messages to be sent to DLQ
[ https://issues.apache.org/jira/browse/QPID-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483766#comment-16483766 ] Rob Godfrey commented on QPID-7153: --- Good point on the MAX_VALUE calculation. I did consider a third expiry behaviour "NEVER" which one could use for DLQs (rather than doing the hacky max value thing) but ultimately decided against it. I'll update the patch to address the issue. On the method naming I was thinking of "expire" as in the action of expiring a message rather than the state of the message, but expiresNow is probably less ambiguous. > Allow expired messages to be sent to DLQ > > > Key: QPID-7153 > URL: https://issues.apache.org/jira/browse/QPID-7153 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Keith Wall >Priority: Major > Attachments: QPID-7153v2.diff > > > Currently the Java Broker simply discards messages that expire (TTL). The > behaviour should be configurable and allow for expired messages to be > directed to the alternate exchange to allow for dead-lettering. -- 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-7153) Allow expired messages to be sent to DLQ
[
https://issues.apache.org/jira/browse/QPID-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483705#comment-16483705
]
Keith Wall commented on QPID-7153:
--
One comment. If as a user I want the expired messages that that land on the
DLQ to live indefinitely, then I would have expected to set the the DLQ's
{{minimumMessageTtl}} to {{Long.MAX_VALUE}}. This doesn't work because the
long arithmetic overflows within {{AbstactQueue#calculateExpiration}} and
{{wouldExpire}} (which would be better named wouldExpireNow) returns the wrong
value. Perhaps {{calculateExpiration}} should use {{Math.addExact}} and clamp
the value if ArithmeticException occurs.
Separately, largely note to self, when testing this feature with the Qpid JMS
Client, one needs to remember to turn off {{jms.localMessageExpiry}} otherwise
the client expires the message as it is consumed from the DLQ.
> Allow expired messages to be sent to DLQ
>
>
> Key: QPID-7153
> URL: https://issues.apache.org/jira/browse/QPID-7153
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Reporter: Keith Wall
>Priority: Major
> Attachments: QPID-7153v2.diff
>
>
> Currently the Java Broker simply discards messages that expire (TTL). The
> behaviour should be configurable and allow for expired messages to be
> directed to the alternate exchange to allow for dead-lettering.
--
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
