[GitHub] qpid-proton pull request #138: WIP - Remove obsolete docs and test code

2018-03-06 Thread ssorj 
GitHub user ssorj opened a pull request:

https://github.com/apache/qpid-proton/pull/138

WIP - Remove obsolete docs and test code

Part two of the planned source reorg.  This is intended to follow after 
https://github.com/apache/qpid-proton/pull/136 .


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ssorj/qpid-proton 
ssorj-remove-obsolete-docs-and-test-code

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-proton/pull/138.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 #138


commit 93e54946349509d46ea007a67c57c14e14bed517
Author: Justin Ross 
Date:   2018-02-14T01:16:15Z

Remove the perl, php, node, and javascript bindings

commit 1bcd14bbf0bd0b86f4e4e56f0ecb4bf49911aa6d
Author: Justin Ross 
Date:   2018-02-14T02:31:07Z

Remove the messenger docs

commit e72f0260cf60c258ba65060739eab552e519d81a
Author: Justin Ross 
Date:   2018-02-14T02:34:40Z

Remove the python messenger API

commit cc1af07068f0bbc5858e62a3302a4ca7e256c97f
Author: Justin Ross 
Date:   2018-02-14T03:16:19Z

Remove the ruby messenger API

commit 3c2933f0337d9bcf78be8d03ba131f501ec56e75
Author: Justin Ross 
Date:   2017-12-21T23:27:23Z

Remove the C++ reactor app

commit b25c790042ba8682107004d983ddfcc60270196b
Author: Justin Ross 
Date:   2017-12-21T14:32:50Z

Remove old docs; some of this content will be restored to new locations

commit 91641343baa970c1ce6bbe62a36995a9fbcc116d
Author: Justin Ross 
Date:   2017-12-21T22:33:49Z

xproton.py is no longer used

commit 17cd911bf3588bbec44aeacc5744fad765a41824
Author: Justin Ross 
Date:   2018-03-06T23:06:36Z

Remove the reactor-based quick_perf

commit 598a72486c724b75c10c57416d0f3af0a3a83b8d
Author: Justin Ross 
Date:   2018-03-06T23:13:35Z

Remove the python reactor-send impl




---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-8116) Please delete old releases from mirroring system

2018-03-06 Thread Sebb (JIRA) 

[ 
https://issues.apache.org/jira/browse/QPID-8116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16388699#comment-16388699
 ] 

Sebb commented on QPID-8116:


Given that the historic code does not use the mirror system, it seems to me 
that you might be able to use an .htaccess redirect to fix the issue.

BTW, if you refer to README_historic_cleanup.txt in public-facing mails/pages, 
please use the main website copy under www.apache.org/dist, not the one under 
dist.apache.org as that host is only intended to be used to publish files to 
the main website (and thence to the mirrors).

> Please delete old releases from mirroring system
> 
>
> Key: QPID-8116
> URL: https://issues.apache.org/jira/browse/QPID-8116
> Project: Qpid
>  Issue Type: Bug
> Environment: https://dist.apache.org/repos/dist/release/qpid/
>Reporter: Sebb
>Assignee: Robbie Gemmell
>Priority: Major
>
> To reduce the load on the ASF mirrors, projects are required to delete old 
> releases [1]
> Please can you remove all non-current releases?
> From the download page, it looks like all but the latest release of each 
> product can be deleted.
> It's unfair to expect the 3rd party mirrors to carry old releases.
> Note that older releases can still be linked from the download page, but such 
> links should use the archive server at:
> https://archive.apache.org/dist/incubator/mxnet/
> Please also make a note to remove the previous release when a new one is 
> announced.
> Thanks!
> [1] http://www.apache.org/dev/release.html#when-to-archive



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (PROTON-1785) Port builtin performance tests to the proactor

2018-03-06 Thread Justin Ross (JIRA) 
Justin Ross created PROTON-1785:
---

 Summary: Port builtin performance tests to the proactor
 Key: PROTON-1785
 URL: https://issues.apache.org/jira/browse/PROTON-1785
 Project: Qpid Proton
  Issue Type: Task
Reporter: Justin Ross
Assignee: Cliff Jansen






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (PROTON-1785) Port built-in performance tests to the proactor

2018-03-06 Thread Justin Ross (JIRA) 

 [ 
https://issues.apache.org/jira/browse/PROTON-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross updated PROTON-1785:

Summary: Port built-in performance tests to the proactor  (was: Port 
builtin performance tests to the proactor)

> Port built-in performance tests to the proactor
> ---
>
> Key: PROTON-1785
> URL: https://issues.apache.org/jira/browse/PROTON-1785
> Project: Qpid Proton
>  Issue Type: Task
>Reporter: Justin Ross
>Assignee: Cliff Jansen
>Priority: Major
>  Labels: testing
>




--
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] (PROTON-1784) [ruby] Connection#each_sender each_receiver should take a block

2018-03-06 Thread Alan Conway (JIRA) 

 [ 
https://issues.apache.org/jira/browse/PROTON-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Conway resolved PROTON-1784.
-
Resolution: Fixed

d4241caa PROTON-1784 [ruby] Connection#each_sender/each_receiver take a block

> [ruby] Connection#each_sender each_receiver should take a block
> ---
>
> Key: PROTON-1784
> URL: https://issues.apache.org/jira/browse/PROTON-1784
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: ruby-binding
>Affects Versions: proton-c-0.21.0
>Reporter: Alan Conway
>Assignee: Alan Conway
>Priority: Major
> Fix For: proton-c-0.22.0
>
>
> Connection#each_link can return an Enumerator or take a block to operate on 
> the links, however each_sender and each_receiver only return the list of 
> senders/receivers and don't apply a block. They should be consistent.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (DISPATCH-938) Doc: Remove the "Configuration Reference"

2018-03-06 Thread Ben Hardesty (JIRA) 
Ben Hardesty created DISPATCH-938:
-

 Summary: Doc: Remove the "Configuration Reference"
 Key: DISPATCH-938
 URL: https://issues.apache.org/jira/browse/DISPATCH-938
 Project: Qpid Dispatch
  Issue Type: Improvement
  Components: Documentation
Reporter: Ben Hardesty
Assignee: Ben Hardesty


The "Configuration Reference" appendix in the Dispatch Router user guide is 
outdated and incorrect. It should be removed, and all references to it should 
be changed to point to the qdrouterd.conf man page.



--
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] (QPIDIT-114) [AMQP.NetLite] AMQP char type is not supported, but is not excluded from test

2018-03-06 Thread Chuck Rolke (JIRA) 

[ 
https://issues.apache.org/jira/browse/QPIDIT-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16388434#comment-16388434
 ] 

Chuck Rolke commented on QPIDIT-114:


This looks like an omission in the AmqpNetLite shim in the test suite. The char 
type appears to be supported by the AMQP.Net Lite library.

> [AMQP.NetLite] AMQP char type is not supported, but is not excluded from test
> -
>
> Key: QPIDIT-114
> URL: https://issues.apache.org/jira/browse/QPIDIT-114
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Bug
>  Components: .Net Lite Shim, AMQP Types Test
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Chuck Rolke
>Priority: Major
> Fix For: 0.2.0
>
>
> When the amqp_types_test is run against the ActiveMQ broker (which can handle 
> AMQP type char, unlike several other brokers), the tests of AMQP type 
> {{char}} fail with an error message from the AMQP.NetLite shims:
> {noformat}
> System.ApplicationException: Sender can not encode base type: char{noformat}
> As a mechanism exists in each test to exclude AMQP types based on the client 
> being run, this should be added.



--
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-925) Doc: Update anchor name format

2018-03-06 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/DISPATCH-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16388414#comment-16388414
 ] 

ASF GitHub Bot commented on DISPATCH-925:
-

GitHub user bhardesty opened a pull request:

https://github.com/apache/qpid-dispatch/pull/264

DISPATCH-925: Update anchor name format and links



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/bhardesty/qpid-dispatch 
DISPATCH-925-update-anchors

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-dispatch/pull/264.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 #264


commit 5bab0080108b98a44932905df30367443623f0b9
Author: Ben Hardesty 
Date:   2018-02-15T22:30:08Z

Update anchorname format and fix broken links




> Doc: Update anchor name format
> --
>
> Key: DISPATCH-925
> URL: https://issues.apache.org/jira/browse/DISPATCH-925
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Ben Hardesty
>Assignee: Ben Hardesty
>Priority: Major
>
> In the QDR doc, the anchor names should use the [id='anchor-name'] format, 
> which is more versatile than the [[anchor-name]] format. This also involves 
> updating each "xref" and "link" that refers to an anchor name.



--
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 #264: DISPATCH-925: Update anchor name format and...

2018-03-06 Thread bhardesty 
GitHub user bhardesty opened a pull request:

https://github.com/apache/qpid-dispatch/pull/264

DISPATCH-925: Update anchor name format and links



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/bhardesty/qpid-dispatch 
DISPATCH-925-update-anchors

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-dispatch/pull/264.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 #264


commit 5bab0080108b98a44932905df30367443623f0b9
Author: Ben Hardesty 
Date:   2018-02-15T22:30:08Z

Update anchorname format and fix broken links




---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1672) Large deliveries comprising many transfers are handled inefficiently

2018-03-06 Thread Robbie Gemmell (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16388315#comment-16388315
 ] 

Robbie Gemmell commented on PROTON-1672:


[~jr...@redhat.com], yep, this is the one I was thinking of.

> Large deliveries comprising many transfers are handled inefficiently
> 
>
> Key: PROTON-1672
> URL: https://issues.apache.org/jira/browse/PROTON-1672
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-j
>Affects Versions: proton-j-0.23.0
>Reporter: Keith Wall
>Priority: Major
> Attachments: JProfiler_PROTON-1672.tiff
>
>
> Running performance tests using Qpid Broker J and Qpid JMS Client (0.26.0) 
> shows that receipt of large messages is very slow in comparison with the send 
> of the same message.   For instance, sending 300MiB bytes message takes 5 
> seconds on my laptop.  The receipt takes 97 seconds.
> Instrumenting the client stack shows an obvious hot-spot in Proton-J.  
> {{org.apache.qpid.proton.engine.impl.TransportSession#handleTransfer}} 
> re-allocates/array copies the entire delivery buffer for ever transfer that 
> comprises it.  This leads to a non-linear loss of performance.   The stack 
> include Proton-J 0.23.0, but is looks like this code is unchanged.



--
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-1672) Large deliveries comprising many transfers are handled inefficiently

2018-03-06 Thread Justin Ross (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16388305#comment-16388305
 ] 

Justin Ross commented on PROTON-1672:
-

[~gemmellr], maybe this is the one to use for transfer frame rightsizing?

> Large deliveries comprising many transfers are handled inefficiently
> 
>
> Key: PROTON-1672
> URL: https://issues.apache.org/jira/browse/PROTON-1672
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-j
>Affects Versions: proton-j-0.23.0
>Reporter: Keith Wall
>Priority: Major
> Attachments: JProfiler_PROTON-1672.tiff
>
>
> Running performance tests using Qpid Broker J and Qpid JMS Client (0.26.0) 
> shows that receipt of large messages is very slow in comparison with the send 
> of the same message.   For instance, sending 300MiB bytes message takes 5 
> seconds on my laptop.  The receipt takes 97 seconds.
> Instrumenting the client stack shows an obvious hot-spot in Proton-J.  
> {{org.apache.qpid.proton.engine.impl.TransportSession#handleTransfer}} 
> re-allocates/array copies the entire delivery buffer for ever transfer that 
> comprises it.  This leads to a non-linear loss of performance.   The stack 
> include Proton-J 0.23.0, but is looks like this code is unchanged.



--
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-333) Add a chapter on policy to the Qpid Dispatch Router Book.

2018-03-06 Thread Ganesh Murthy (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DISPATCH-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ganesh Murthy resolved DISPATCH-333.

Resolution: Fixed

> Add a chapter on policy to the Qpid Dispatch Router Book.
> -
>
> Key: DISPATCH-333
> URL: https://issues.apache.org/jira/browse/DISPATCH-333
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Documentation
>Affects Versions: 0.7.0
>Reporter: Ganesh Murthy
>Assignee: Ben Hardesty
>Priority: Minor
>
> Add a new chapter containing details on how policy works and how to setup 
> policy to the Qpid Dispatch Router Book



--
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-333) Add a chapter on policy to the Qpid Dispatch Router Book.

2018-03-06 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/DISPATCH-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16388118#comment-16388118
 ] 

ASF GitHub Bot commented on DISPATCH-333:
-

Github user asfgit closed the pull request at:

https://github.com/apache/qpid-dispatch/pull/255


> Add a chapter on policy to the Qpid Dispatch Router Book.
> -
>
> Key: DISPATCH-333
> URL: https://issues.apache.org/jira/browse/DISPATCH-333
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Documentation
>Affects Versions: 0.7.0
>Reporter: Ganesh Murthy
>Assignee: Ben Hardesty
>Priority: Minor
>
> Add a new chapter containing details on how policy works and how to setup 
> policy to the Qpid Dispatch Router Book



--
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 #255: DISPATCH-333: Create new router policies do...

2018-03-06 Thread asfgit 
Github user asfgit closed the pull request at:

https://github.com/apache/qpid-dispatch/pull/255


---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (QPID-8116) Please delete old releases from mirroring system

2018-03-06 Thread Robbie Gemmell (JIRA) 

 [ 
https://issues.apache.org/jira/browse/QPID-8116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-8116.
--
Resolution: Fixed
  Assignee: Robbie Gemmell

We have cleared out all the non-current releases, except some older qpid-proton 
releases totalling about 15MB where removing them will break some other 
projects, due to a historic issue now outlined 
[here|https://dist.apache.org/repos/dist/release/qpid/proton/README_historic_cleanup.txt].
  I'll work with [~kgiusti], [~jr...@redhat.com] and infra to see if there is 
some other way we can address the issue without breaking existing users.

> Please delete old releases from mirroring system
> 
>
> Key: QPID-8116
> URL: https://issues.apache.org/jira/browse/QPID-8116
> Project: Qpid
>  Issue Type: Bug
> Environment: https://dist.apache.org/repos/dist/release/qpid/
>Reporter: Sebb
>Assignee: Robbie Gemmell
>Priority: Major
>
> To reduce the load on the ASF mirrors, projects are required to delete old 
> releases [1]
> Please can you remove all non-current releases?
> From the download page, it looks like all but the latest release of each 
> product can be deleted.
> It's unfair to expect the 3rd party mirrors to carry old releases.
> Note that older releases can still be linked from the download page, but such 
> links should use the archive server at:
> https://archive.apache.org/dist/incubator/mxnet/
> Please also make a note to remove the previous release when a new one is 
> announced.
> Thanks!
> [1] http://www.apache.org/dev/release.html#when-to-archive



--
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-1781) [c-proactor] fix mis-named netaddr functions

2018-03-06 Thread Alan Conway (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16388061#comment-16388061
 ] 

Alan Conway commented on PROTON-1781:
-

commit 06c3d6e2f46811038853b95401cd017cb21e2713 (github/netaddr-names, 
netaddr-names)
Author: Alan Conway 
Commit: Alan Conway 

PROTON-1781 [c-proactor] fix mis-named netaddr functions

The old functions are deprecated but still present - old binaries can still 
be
linked with new libraies, old source will fail to compile with a deprecation
message unless -DPN_USE_DEPRECATED_API is present in CMAKE_C_FLAGS


> [c-proactor] fix mis-named netaddr functions 
> -
>
> Key: PROTON-1781
> URL: https://issues.apache.org/jira/browse/PROTON-1781
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Affects Versions: proton-c-0.21.0
>Reporter: Alan Conway
>Assignee: Alan Conway
>Priority: Major
> Fix For: proton-c-0.22.0
>
>
> The functions pn_netaddr_remote, pn_netaddr_local and pn_netaddr_listening do 
> not follow proton's naming conventions - the first part of the name should be 
> the type of the first parameter to the function. Rename as 
> pn_transport_remote_addr, pn_transport_local_addr and 
> pn_transport_listener_addr



--
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] (PROTON-1781) [c-proactor] fix mis-named netaddr functions

2018-03-06 Thread Alan Conway (JIRA) 

 [ 
https://issues.apache.org/jira/browse/PROTON-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Conway resolved PROTON-1781.
-
Resolution: Fixed

> [c-proactor] fix mis-named netaddr functions 
> -
>
> Key: PROTON-1781
> URL: https://issues.apache.org/jira/browse/PROTON-1781
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Affects Versions: proton-c-0.21.0
>Reporter: Alan Conway
>Assignee: Alan Conway
>Priority: Major
> Fix For: proton-c-0.22.0
>
>
> The functions pn_netaddr_remote, pn_netaddr_local and pn_netaddr_listening do 
> not follow proton's naming conventions - the first part of the name should be 
> the type of the first parameter to the function. Rename as 
> pn_transport_remote_addr, pn_transport_local_addr and 
> pn_transport_listener_addr



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (PROTON-1784) [ruby] Connection#each_sender each_receiver should take a block

2018-03-06 Thread Alan Conway (JIRA) 
Alan Conway created PROTON-1784:
---

 Summary: [ruby] Connection#each_sender each_receiver should take a 
block
 Key: PROTON-1784
 URL: https://issues.apache.org/jira/browse/PROTON-1784
 Project: Qpid Proton
  Issue Type: Bug
  Components: ruby-binding
Affects Versions: proton-c-0.21.0
Reporter: Alan Conway
Assignee: Alan Conway
 Fix For: proton-c-0.22.0


Connection#each_link can return an Enumerator or take a block to operate on the 
links, however each_sender and each_receiver only return the list of 
senders/receivers and don't apply a block. They should be consistent.



--
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-8117) [Broker-J] Table prefix of JDBC Virtual Host Node is ignored by preferences store

2018-03-06 Thread Alex Rudyy (JIRA) 

 [ 
https://issues.apache.org/jira/browse/QPID-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-8117:
-
Description: 
QPID-7558 introduced a notion of table prefix which allows to share the same  
database/schema by multiple virtual hosts. The prefix is used in naming the 
store tables which allows to distinguish tables belonging to different VHNs.

However, the tables of preferences store do not respect the prefix. The 
preferences tables are created without a prefix. As result, the preference 
tables can be shared by  
multiple Virtual Host instances. On deletion of one of VHNs the preferences 
tables are deleted and attempts to save preferences for remaining virtual host 
nodes might end-up in broker crash.

The preferences store should respect the prefix and create the tables with the 
specified prefix.

  was:
QPID-7558 introduced a notion of table prefix which allows to share the same  
database/schema by multiple virtual hosts. The prefix is used in naming the 
store tables which allows to distinguish tables belonging to different VHNs.

However, the tables of preferences store do not respect the prefix. The 
preferences tables are created without a prefix. As result, the preference 
tables can be shared by  
multiple Virtual Host instances. On deletion of one of VHNs the preferences 
tables are deleted and attempts to save preferences for remaining virtual host 
node might end-up in broker crash.

The preferences store should respect the prefix and create the tables with the 
specified prefix.


> [Broker-J] Table prefix of JDBC Virtual Host Node is ignored by preferences 
> store
> -
>
> Key: QPID-8117
> URL: https://issues.apache.org/jira/browse/QPID-8117
> Project: Qpid
>  Issue Type: Task
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.2, qpid-java-6.1.2, 
> qpid-java-6.1.3, 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
>
> QPID-7558 introduced a notion of table prefix which allows to share the same  
> database/schema by multiple virtual hosts. The prefix is used in naming the 
> store tables which allows to distinguish tables belonging to different VHNs.
> However, the tables of preferences store do not respect the prefix. The 
> preferences tables are created without a prefix. As result, the preference 
> tables can be shared by  
> multiple Virtual Host instances. On deletion of one of VHNs the preferences 
> tables are deleted and attempts to save preferences for remaining virtual 
> host nodes might end-up in broker crash.
> The preferences store should respect the prefix and create the tables with 
> the specified prefix.



--
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-8117) [Broker-J] Table prefix of JDBC Virtual Host Node is ignored by preferences store

2018-03-06 Thread Alex Rudyy (JIRA) 

 [ 
https://issues.apache.org/jira/browse/QPID-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-8117:
-
Summary: [Broker-J] Table prefix of JDBC Virtual Host Node is ignored by 
preferences store  (was: [Broker-J] Table prefix of JDBC Virtual HOst Node is 
ignored by preferences store)

> [Broker-J] Table prefix of JDBC Virtual Host Node is ignored by preferences 
> store
> -
>
> Key: QPID-8117
> URL: https://issues.apache.org/jira/browse/QPID-8117
> Project: Qpid
>  Issue Type: Task
>  Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.2, qpid-java-6.1.2, 
> qpid-java-6.1.3, 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
>
> QPID-7558 introduced a notion of table prefix which allows to share the same  
> database/schema by multiple virtual hosts. The prefix is used in naming the 
> store tables which allows to distinguish tables belonging to different VHNs.
> However, the tables of preferences store do not respect the prefix. The 
> preferences tables are created without a prefix. As result, the preference 
> tables can be shared by  
> multiple Virtual Host instances. On deletion of one of VHNs the preferences 
> tables are deleted and attempts to save preferences for remaining virtual 
> host node might end-up in broker crash.
> The preferences store should respect the prefix and create the tables with 
> the specified prefix.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPID-8117) [Broker-J] Table prefix of JDBC Virtual HOst Node is ignored by preferences store

2018-03-06 Thread Alex Rudyy (JIRA) 
Alex Rudyy created QPID-8117:


 Summary: [Broker-J] Table prefix of JDBC Virtual HOst Node is 
ignored by preferences store
 Key: QPID-8117
 URL: https://issues.apache.org/jira/browse/QPID-8117
 Project: Qpid
  Issue Type: Task
  Components: Broker-J
Affects Versions: qpid-java-broker-7.0.1, qpid-java-6.1.5, 
qpid-java-broker-7.0.0, qpid-java-6.1.4, qpid-java-6.1.3, qpid-java-6.1.2, 
qpid-java-broker-7.0.2
Reporter: Alex Rudyy


QPID-7558 introduced a notion of table prefix which allows to share the same  
database/schema by multiple virtual hosts. The prefix is used in naming the 
store tables which allows to distinguish tables belonging to different VHNs.

However, the tables of preferences store do not respect the prefix. The 
preferences tables are created without a prefix. As result, the preference 
tables can be shared by  
multiple Virtual Host instances. On deletion of one of VHNs the preferences 
tables are deleted and attempts to save preferences for remaining virtual host 
node might end-up in broker crash.

The preferences store should respect the prefix and create the tables with the 
specified prefix.



--
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-7873) [Broker-J] Delete store notion confused

2018-03-06 Thread Alex Rudyy (JIRA) 

[ 
https://issues.apache.org/jira/browse/QPID-7873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387812#comment-16387812
 ] 

Alex Rudyy commented on QPID-7873:
--

I am not sure that we need separate methods for structure removal and 
destruction of the store. The current responsibilities of onDelete/delete store 
methods is to perform the required clean up on store destruction which includes 
the deletion of tables in case of JDBC store or files removal in case of 
BDB/Derby/JSON. We do not invoke the cleanup methods in all scenarios. Thus, we 
need to re-mediate it and reliably cleanup the stores on deletion of virtual 
host nodes or/and virtual hosts

> [Broker-J] Delete store notion confused
> ---
>
> Key: QPID-7873
> URL: https://issues.apache.org/jira/browse/QPID-7873
> Project: Qpid
>  Issue Type: Improvement
>  Components: Broker-J
>Reporter: Keith Wall
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: Future
>
>
> org.apache.qpid.server.store.MessageStore#onDelete
> org.apache.qpid.server.store.DurableConfigurationStore#onDelete
> org.apache.qpid.server.protocol.v1_0.store.LinkStore#delete
> The Java Broker's delete store notion conflates the removal of the structures 
> from the store (e.g. the removal of a table from a RDBMS, for instance) with 
> the destruction of the store itself (e.g. removal of Derby or BDB files).  We 
> are also unclear about whether we expect a store to be in an open state when 
> the store is deleted.
> This problem does not currently cause a functional defect.



--
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-933) Introduce a new RouterStats entity and move all stats from the RouterEntity to the RouterStats entity

2018-03-06 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/DISPATCH-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387802#comment-16387802
 ] 

ASF GitHub Bot commented on DISPATCH-933:
-

Github user bhardesty commented on a diff in the pull request:

https://github.com/apache/qpid-dispatch/pull/263#discussion_r172520473
  
--- Diff: python/qpid_dispatch/management/qdrouter.json ---
@@ -431,37 +431,100 @@
 "description": "Time in seconds after which link state 
is declared stale if no RA is received.",
 "create": true
 },
-"addrCount": {
-"type": "integer",
-"description":"Number of addresses known to the 
router.",
-"graph": true
-},
-"linkCount": {
+"workerThreads": {
 "type": "integer",
-"description":"Number of links attached to the router 
node.",
-"graph": true
+"default": 4,
+"description": "The number of threads that will be 
created to process message traffic and other application work (timers, non-amqp 
file descriptors, etc.) .",
+"create": true
 },
-"nodeCount": {
-"type": "integer",
-"description":"Number of known peer router nodes.",
-"graph": true
+"debugDump": {
+"type": "path",
+"description": "A file to dump debugging information 
that can't be logged normally.",
--- End diff --

In that case, how about this:

The absolute path to the location for the debug dump file. The router 
writes debug-level information to this file if the logger is not available.


> Introduce a new RouterStats entity and move all stats from the RouterEntity 
> to the RouterStats entity
> -
>
> Key: DISPATCH-933
> URL: https://issues.apache.org/jira/browse/DISPATCH-933
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 1.0.1
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.2.0
>
>
> Right now all router statistics attributes like deliveriesIngress, 
> rejectedDeliveries, droppedPresettledDeliveries etc. reside in the router 
> entity..
>  
> Router Config Attributes  like saslConfigPath, saslConfigName, 
> helloIntervalSeconds, helloMaxAgeSeconds etc. also reside in the router entity
>  
> When a qdmanage query is issued, the results do not include the router config 
> attributes. This is because the core does not have access to these attributes
>  
> {noformat}
> [gmurthy@localhost qpid-dispatch]$ qdmanage QUERY --type=router
> [
>   {
>     "linkRouteCount": 0,
>     "droppedPresettledDeliveries": 0,
>     "rejectedDeliveries": 0,
>     "autoLinkCount": 0,
>     "id": "Router.A",
>     "presettledDeliveries": 0,
>     "area": "0",
>     "deliveriesIngress": 1,
>     "deliveriesIngressRouteContainer": 0,
>     "acceptedDeliveries": 1,
>     "version": "1.0.0",
>     "linkCount": 2,
>     "connectionCount": 1,
>     "addrCount": 4,
>     "deliveriesEgressRouteContainer": 0,
>     "nodeCount": 0,
>     "modifiedDeliveries": 0,
>     "identity": "1",
>     "deliveriesEgress": 0,
>     "releasedDeliveries": 0,
>     "name": "Router.A",
>     "type": "org.apache.qpid.dispatch.router",
>     "deliveriesTransit": 0,
>     "mode": "standalone"
>   }
> ]
> {noformat}
>  
> The solution to this problem is to create a new entity called RouterStats and 
> move all the statistics related attributes to RouterStats. This RouterStats 
> entity will be handled by the C management agent.
>  
> The old Router entity which is currently handled by the C agent will be 
> handled by the Python agent instead.



--
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 #263: DISPATCH-933 - Created new RouterStats enti...

2018-03-06 Thread bhardesty 
Github user bhardesty commented on a diff in the pull request:

https://github.com/apache/qpid-dispatch/pull/263#discussion_r172520473
  
--- Diff: python/qpid_dispatch/management/qdrouter.json ---
@@ -431,37 +431,100 @@
 "description": "Time in seconds after which link state 
is declared stale if no RA is received.",
 "create": true
 },
-"addrCount": {
-"type": "integer",
-"description":"Number of addresses known to the 
router.",
-"graph": true
-},
-"linkCount": {
+"workerThreads": {
 "type": "integer",
-"description":"Number of links attached to the router 
node.",
-"graph": true
+"default": 4,
+"description": "The number of threads that will be 
created to process message traffic and other application work (timers, non-amqp 
file descriptors, etc.) .",
+"create": true
 },
-"nodeCount": {
-"type": "integer",
-"description":"Number of known peer router nodes.",
-"graph": true
+"debugDump": {
+"type": "path",
+"description": "A file to dump debugging information 
that can't be logged normally.",
--- End diff --

In that case, how about this:

The absolute path to the location for the debug dump file. The router 
writes debug-level information to this file if the logger is not available.


---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPID-7873) [Broker-J] Delete store notion confused

2018-03-06 Thread Alex Rudyy (JIRA) 

 [ 
https://issues.apache.org/jira/browse/QPID-7873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-7873:
-
Summary: [Broker-J] Delete store notion confused  (was: Delete store notion 
confused)

> [Broker-J] Delete store notion confused
> ---
>
> Key: QPID-7873
> URL: https://issues.apache.org/jira/browse/QPID-7873
> Project: Qpid
>  Issue Type: Improvement
>  Components: Broker-J
>Reporter: Keith Wall
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: Future
>
>
> org.apache.qpid.server.store.MessageStore#onDelete
> org.apache.qpid.server.store.DurableConfigurationStore#onDelete
> org.apache.qpid.server.protocol.v1_0.store.LinkStore#delete
> The Java Broker's delete store notion conflates the removal of the structures 
> from the store (e.g. the removal of a table from a RDBMS, for instance) with 
> the destruction of the store itself (e.g. removal of Derby or BDB files).  We 
> are also unclear about whether we expect a store to be in an open state when 
> the store is deleted.
> This problem does not currently cause a functional defect.



--
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] (QPID-7873) Delete store notion confused

2018-03-06 Thread Alex Rudyy (JIRA) 

 [ 
https://issues.apache.org/jira/browse/QPID-7873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy reassigned QPID-7873:


Assignee: Alex Rudyy

> Delete store notion confused
> 
>
> Key: QPID-7873
> URL: https://issues.apache.org/jira/browse/QPID-7873
> Project: Qpid
>  Issue Type: Improvement
>  Components: Broker-J
>Reporter: Keith Wall
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: Future
>
>
> org.apache.qpid.server.store.MessageStore#onDelete
> org.apache.qpid.server.store.DurableConfigurationStore#onDelete
> org.apache.qpid.server.protocol.v1_0.store.LinkStore#delete
> The Java Broker's delete store notion conflates the removal of the structures 
> from the store (e.g. the removal of a table from a RDBMS, for instance) with 
> the destruction of the store itself (e.g. removal of Derby or BDB files).  We 
> are also unclear about whether we expect a store to be in an open state when 
> the store is deleted.
> This problem does not currently cause a functional defect.



--
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

[ANNOUNCE] Apache Qpid Proton 0.21.0 released

2018-03-06 Thread Robbie Gemmell 
The Apache Qpid (http://qpid.apache.org) community is pleased to announce
the immediate availability of Apache Qpid Proton 0.21.0.

Apache Qpid Proton is a messaging library for the Advanced Message Queuing
Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org). It can be used
in a wide range of messaging applications including brokers, clients,
routers, bridges, proxies, and more.

The release is available now from our website:
http://qpid.apache.org/download.html

Release notes can be found at:
http://qpid.apache.org/releases/qpid-proton-0.21.0/release-notes.html

Thanks to all involved,
Robbie

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (PROTON-1766) [cpp] seg fault in reconnect test

2018-03-06 Thread Robbie Gemmell (JIRA) 

 [ 
https://issues.apache.org/jira/browse/PROTON-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell updated PROTON-1766:
---
Issue Type: Bug  (was: Improvement)

> [cpp] seg fault in reconnect test
> -
>
> Key: PROTON-1766
> URL: https://issues.apache.org/jira/browse/PROTON-1766
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding, proton-c
>Affects Versions: proton-c-0.20.0
>Reporter: Alan Conway
>Assignee: Alan Conway
>Priority: Major
> Fix For: proton-c-0.21.0
>
>
> See [https://issues.jboss.org/browse/ENTMQCL-600] for details and reproducer 
> code, summary:
>  
> Using the to be attached reproducer and broker configuration:
> Running amqsender
> ./amqsender   microseconds>
> e.g.
> ./amqsender testbox111:5672 testbox111:5673 anon anon Q1 1
> You can reproduce the coredump with just one broker
> 1. keep slave down
> 2. start master broker
> 3. run amqsender with a very low frequency
> 4. kill master broker
> This should reproduce the coredump.
> The reproducer has events implemented for on_transport_close yet we see:
> {code}
> .
> .
> .
> [0x7fffec0169b0]:(PN_TRANSPORT, pn_transport<0x7fffec0169b0>)
> [0x7fffec0169b0]:(PN_TRANSPORT, pn_transport<0x7fffec0169b0>)
> [0x7fffec0169b0]:(PN_CONNECTION_WAKE, pn_connection<0x7fffec000b90>)
> AMQSender::on_connection_wake pn_connection<0x7fffec000b90>
> [0x7fffec0169b0]:(PN_TRANSPORT_TAIL_CLOSED, pn_transport<0x7fffec0169b0>)
> [0x7fffec0169b0]:(PN_TRANSPORT_ERROR, pn_transport<0x7fffec0169b0>)
> [0x7fffec0169b0]:(PN_TRANSPORT_HEAD_CLOSED, pn_transport<0x7fffec0169b0>)
> [0x7fffec0169b0]:(PN_TRANSPORT_CLOSED, pn_transport<0x7fffec0169b0>)
> [0x7fffec0169b0]:(PN_CONNECTION_INIT, pn_connection<0x7fffec000b90>)
> Thread 1 "amqsender" received signal SIGSEGV, Segmentation fault.
> 0x772bcdd0 in pthread_mutex_lock () from /lib64/libpthread.so.0
> Missing separate debuginfos, use: dnf debuginfo-install 
> cyrus-sasl-gssapi-2.1.26-26.2.fc24.x86_64 
> cyrus-sasl-lib-2.1.26-26.2.fc24.x86_64 cyrus-sasl-md5-2.1.26-26.2.fc24.x86_64 
> cyrus-sasl-plain-2.1.26-26.2.fc24.x86_64 
> cyrus-sasl-scram-2.1.26-26.2.fc24.x86_64 keyutils-libs-1.5.9-8.fc24.x86_64 
> krb5-libs-1.14.4-7.fc25.x86_64 libcom_err-1.43.3-1.fc25.x86_64 
> libcrypt-nss-2.24-4.fc25.x86_64 libdb-5.3.28-16.fc25.x86_64 
> libgcc-6.3.1-1.fc25.x86_64 libselinux-2.5-13.fc25.x86_64 
> libstdc++-6.3.1-1.fc25.x86_64 nss-softokn-freebl-3.28.3-1.1.fc25.x86_64 
> openssl-libs-1.0.2k-1.fc25.x86_64 pcre-8.40-5.fc25.x86_64 
> zlib-1.2.8-10.fc24.x86_64
> (gdb) bt
> #0  0x772bcdd0 in pthread_mutex_lock () from /lib64/libpthread.so.0
> #1  0x776dc4fa in lock (m=0x1a0) at 
> /home/rkieley/LocalProjects/src/rh/rh-qpid-proton/proton-c/src/proactor/epoll.c:112
> #2  0x776dcc09 in wake (ctx=0x7fffec2b8ac0) at 
> /home/rkieley/LocalProjects/src/rh/rh-qpid-proton/proton-c/src/proactor/epoll.c:436
> #3  0x776def0e in pn_connection_wake (c=0x7fffec000b90) at 
> /home/rkieley/LocalProjects/src/rh/rh-qpid-proton/proton-c/src/proactor/epoll.c:1302
> #4  0x77b81b82 in proton::container::impl::connection_work_queue::add 
> (this=0x7fffec001d30, f=...) at 
> /home/rkieley/LocalProjects/src/rh/rh-qpid-proton/proton-c/bindings/cpp/src/proactor_container_impl.cpp:118
> #5  0x77bacde5 in proton::work_queue::add (this=0x7fffec001cd8, 
> f=...) at 
> /home/rkieley/LocalProjects/src/rh/rh-qpid-proton/proton-c/bindings/cpp/src/work_queue.cpp:43
> #6  0x0040536f in AMQSender::send (this=this@entry=0x7fffd960, 
> strMsg="7578") at ../attachments/AMQSender.cpp:42
> #7  0x0040328f in main (argc=, argv=0x7fffdbd8) at 
> ../attachments/amqsend.cpp:20
> (gdb) frame 2
> #2  0x776dcc09 in wake (ctx=0x7fffec2b8ac0) at 
> /home/rkieley/LocalProjects/src/rh/rh-qpid-proton/proton-c/src/proactor/epoll.c:436
> 436   lock(>eventfd_mutex);
> (gdb) print p
> $3 = (pn_proactor_t *) 0x0
> (gdb)
> {code}



--
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