[jira] [Commented] (DISPATCH-911) Add link and address level counters at the global router level

2018-02-12 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on DISPATCH-911:
-

Github user ted-ross commented on a diff in the pull request:

https://github.com/apache/qpid-dispatch/pull/254#discussion_r167742873
  
--- Diff: src/router_node.c ---
@@ -33,7 +33,6 @@
 const char *QD_ROUTER_NODE_TYPE = "router.node";
 const char *QD_ROUTER_ADDRESS_TYPE = "router.address";
 const char *QD_ROUTER_LINK_TYPE = "router.link";
-const char *CORE_AGENT_ADDRESS = "$management";
--- End diff --

How is this related to the PR?


> Add link and address level counters at the global router level
> --
>
> Key: DISPATCH-911
> URL: https://issues.apache.org/jira/browse/DISPATCH-911
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Management Agent
>Affects Versions: 1.0.0
>Reporter: Ernest Allen
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.1.0
>
>
> Link already has the following counters - 
>  presettledCount
>  droppedPresettledCount
>  acceptedCount
>  rejectedCount
>  releasedCount
>  modifiedCount
> Address already has the following counters
>  deliveriesIngress
>  deliveriesEgress
>  deliveriesTransit
> 1. Add the above link and address counters to the global router level as well.
>  2. Add routeContainerDeliveriesEgress and routeContainerDeliveriesIngress as 
> address and global counters
>  3. Add router memory footprint as a global statistic



--
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 #254: DISPATCH-911 - Added global delivery counts

2018-02-12 Thread ted-ross 
Github user ted-ross commented on a diff in the pull request:

https://github.com/apache/qpid-dispatch/pull/254#discussion_r167742873
  
--- Diff: src/router_node.c ---
@@ -33,7 +33,6 @@
 const char *QD_ROUTER_NODE_TYPE = "router.node";
 const char *QD_ROUTER_ADDRESS_TYPE = "router.address";
 const char *QD_ROUTER_LINK_TYPE = "router.link";
-const char *CORE_AGENT_ADDRESS = "$management";
--- End diff --

How is this related to the PR?


---

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

[jira] [Commented] (DISPATCH-911) Add link and address level counters at the global router level

2018-02-12 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on DISPATCH-911:
-

GitHub user ganeshmurthy opened a pull request:

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

DISPATCH-911 - Added global delivery counts



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

$ git pull https://github.com/ganeshmurthy/qpid-dispatch DISPATCH-911-1

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

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


commit adea1d9908ee6699b493e6d27d3fae81b7468516
Author: Ganesh Murthy 
Date:   2018-01-26T18:12:12Z

DISPATCH-911 - Added global delivery counts




> Add link and address level counters at the global router level
> --
>
> Key: DISPATCH-911
> URL: https://issues.apache.org/jira/browse/DISPATCH-911
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Management Agent
>Affects Versions: 1.0.0
>Reporter: Ernest Allen
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.1.0
>
>
> Link already has the following counters - 
>  presettledCount
>  droppedPresettledCount
>  acceptedCount
>  rejectedCount
>  releasedCount
>  modifiedCount
> Address already has the following counters
>  deliveriesIngress
>  deliveriesEgress
>  deliveriesTransit
> 1. Add the above link and address counters to the global router level as well.
>  2. Add routeContainerDeliveriesEgress and routeContainerDeliveriesIngress as 
> address and global counters
>  3. Add router memory footprint as a global statistic



--
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 #254: DISPATCH-911 - Added global delivery counts

2018-02-12 Thread ganeshmurthy 
GitHub user ganeshmurthy opened a pull request:

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

DISPATCH-911 - Added global delivery counts



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

$ git pull https://github.com/ganeshmurthy/qpid-dispatch DISPATCH-911-1

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

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


commit adea1d9908ee6699b493e6d27d3fae81b7468516
Author: Ganesh Murthy 
Date:   2018-01-26T18:12:12Z

DISPATCH-911 - Added global delivery counts




---

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

[jira] [Updated] (QPID-8084) QMF management client sends binary application property keys under Python 2

2018-02-12 Thread Justin Ross (JIRA) 

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

Justin Ross updated QPID-8084:
--
Fix Version/s: qpid-python-1.38.0

> QMF management client sends binary application property keys under Python 2
> ---
>
> Key: QPID-8084
> URL: https://issues.apache.org/jira/browse/QPID-8084
> Project: Qpid
>  Issue Type: Bug
>  Components: Python Client
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Major
>  Labels: interop
> Fix For: qpid-python-1.38.0
>
> Attachments: py2.pcapng
>
>
> The AMQP 1.0 spec states that message application property keys MUST be 
> strings.
> Under Python 2.x, the QMF client communicates with the broker using binary 
> strings as keys in the application properties to pass QMF commands.
> Two issues arise:
>  # The Python client should not accept binary keys in application properties
>  # The broker appears to accept this without warning or error. This could be 
> considered undefined behavior, however.
> The reproducer can be found in QPID-8075. The attached Wireshark file shows 
> the transfer in frame 18.



--
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-911) Add link and address level counters at the global router level

2018-02-12 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on DISPATCH-911:
-

Github user ganeshmurthy closed the pull request at:

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


> Add link and address level counters at the global router level
> --
>
> Key: DISPATCH-911
> URL: https://issues.apache.org/jira/browse/DISPATCH-911
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Management Agent
>Affects Versions: 1.0.0
>Reporter: Ernest Allen
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.1.0
>
>
> Link already has the following counters - 
>  presettledCount
>  droppedPresettledCount
>  acceptedCount
>  rejectedCount
>  releasedCount
>  modifiedCount
> Address already has the following counters
>  deliveriesIngress
>  deliveriesEgress
>  deliveriesTransit
> 1. Add the above link and address counters to the global router level as well.
>  2. Add routeContainerDeliveriesEgress and routeContainerDeliveriesIngress as 
> address and global counters
>  3. Add router memory footprint as a global statistic



--
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 #247: DISPATCH-911 - Added global delivery counts

2018-02-12 Thread ganeshmurthy 
Github user ganeshmurthy closed the pull request at:

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


---

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

[GitHub] qpid-dispatch pull request #247: DISPATCH-911 - Added global delivery counts

2018-02-12 Thread ted-ross 
Github user ted-ross commented on a diff in the pull request:

https://github.com/apache/qpid-dispatch/pull/247#discussion_r167675656
  
--- Diff: src/router_core/agent_address.c ---
@@ -54,6 +56,8 @@ const char *qdr_address_columns[] =
  "deliveriesTransit",
  "deliveriesToContainer",
  "deliveriesFromContainer",
+ "deliveriesToRouteContainer",
+ "deliveriesFromRouteContainer",
--- End diff --

I find the names of these two new attributes misleading.  They appear to be 
grouped with the former two attributes "deliveriesToContainer" and 
"deliveriesFromContainer" because of the similar naming.  The new stats are 
supposed to be grouped with "deliveriesIngress" and "deliveriesEgress".  I 
think better names would be "deliveriesIngressRouteContainer" and 
"deliveriesEgressRouteContainer".


---

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

[jira] [Commented] (DISPATCH-911) Add link and address level counters at the global router level

2018-02-12 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on DISPATCH-911:
-

Github user ted-ross commented on a diff in the pull request:

https://github.com/apache/qpid-dispatch/pull/247#discussion_r167675656
  
--- Diff: src/router_core/agent_address.c ---
@@ -54,6 +56,8 @@ const char *qdr_address_columns[] =
  "deliveriesTransit",
  "deliveriesToContainer",
  "deliveriesFromContainer",
+ "deliveriesToRouteContainer",
+ "deliveriesFromRouteContainer",
--- End diff --

I find the names of these two new attributes misleading.  They appear to be 
grouped with the former two attributes "deliveriesToContainer" and 
"deliveriesFromContainer" because of the similar naming.  The new stats are 
supposed to be grouped with "deliveriesIngress" and "deliveriesEgress".  I 
think better names would be "deliveriesIngressRouteContainer" and 
"deliveriesEgressRouteContainer".


> Add link and address level counters at the global router level
> --
>
> Key: DISPATCH-911
> URL: https://issues.apache.org/jira/browse/DISPATCH-911
> Project: Qpid Dispatch
>  Issue Type: Improvement
>  Components: Management Agent
>Affects Versions: 1.0.0
>Reporter: Ernest Allen
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.1.0
>
>
> Link already has the following counters - 
>  presettledCount
>  droppedPresettledCount
>  acceptedCount
>  rejectedCount
>  releasedCount
>  modifiedCount
> Address already has the following counters
>  deliveriesIngress
>  deliveriesEgress
>  deliveriesTransit
> 1. Add the above link and address counters to the global router level as well.
>  2. Add routeContainerDeliveriesEgress and routeContainerDeliveriesIngress as 
> address and global counters
>  3. Add router memory footprint as a global statistic



--
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-1762) [ruby] gem does not contain examples or tests

2018-02-12 Thread Alan Conway (JIRA) 

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

Alan Conway updated PROTON-1762:

Description: 
The ruby gem created by cmake does not include example files or tests. 

The example sources should be included as part of the documentation and linked 
from the README.

 

The tests should be included as per: 
http://guides.rubygems.org/make-your-own-gem/#writing-tests

  was:
The ruby gem created by cmake does not include example files or tests. 

The example sources should be included as part of the documentation and linked 
from the README.

Need to find out whether/where it is appropriate to include tests in a Gem file


> [ruby] gem does not contain examples or tests
> -
>
> Key: PROTON-1762
> URL: https://issues.apache.org/jira/browse/PROTON-1762
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: ruby-binding
>Affects Versions: proton-c-0.20.0
>Reporter: Alan Conway
>Assignee: Alan Conway
>Priority: Major
> Fix For: proton-c-0.21.0
>
>
> The ruby gem created by cmake does not include example files or tests. 
> The example sources should be included as part of the documentation and 
> linked from the README.
>  
> The tests should be included as per: 
> http://guides.rubygems.org/make-your-own-gem/#writing-tests



--
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-1762) [ruby] gem does not contain examples

2018-02-12 Thread Alan Conway (JIRA) 

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

Alan Conway updated PROTON-1762:

Description: 
The ruby gem created by cmake does not include example files or tests. 

The example sources should be included as part of the documentation and linked 
from the README.

Need to find out whether/where it is appropriate to include tests in a Gem file

  was:The ruby gem created by cmake does not include example files. The example 
sources should be included as part of the documentation and linked from the 
README.


> [ruby] gem does not contain examples
> 
>
> Key: PROTON-1762
> URL: https://issues.apache.org/jira/browse/PROTON-1762
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: ruby-binding
>Affects Versions: proton-c-0.20.0
>Reporter: Alan Conway
>Assignee: Alan Conway
>Priority: Major
> Fix For: proton-c-0.21.0
>
>
> The ruby gem created by cmake does not include example files or tests. 
> The example sources should be included as part of the documentation and 
> linked from the README.
> Need to find out whether/where it is appropriate to include tests in a Gem 
> file



--
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-1762) [ruby] gem does not contain examples or tests

2018-02-12 Thread Alan Conway (JIRA) 

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

Alan Conway updated PROTON-1762:

Summary: [ruby] gem does not contain examples or tests  (was: [ruby] gem 
does not contain examples)

> [ruby] gem does not contain examples or tests
> -
>
> Key: PROTON-1762
> URL: https://issues.apache.org/jira/browse/PROTON-1762
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: ruby-binding
>Affects Versions: proton-c-0.20.0
>Reporter: Alan Conway
>Assignee: Alan Conway
>Priority: Major
> Fix For: proton-c-0.21.0
>
>
> The ruby gem created by cmake does not include example files or tests. 
> The example sources should be included as part of the documentation and 
> linked from the README.
> Need to find out whether/where it is appropriate to include tests in a Gem 
> file



--
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-1751) Various doc improvements

2018-02-12 Thread Justin Ross (JIRA) 

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

Justin Ross resolved PROTON-1751.
-
Resolution: Done

On second thought, cloning to a new issue.

> Various doc improvements
> 
>
> Key: PROTON-1751
> URL: https://issues.apache.org/jira/browse/PROTON-1751
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Reporter: Justin Ross
>Assignee: Justin Ross
>Priority: Major
> Fix For: proton-c-0.20.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] [Created] (PROTON-1763) Various doc improvements

2018-02-12 Thread Justin Ross (JIRA) 
Justin Ross created PROTON-1763:
---

 Summary: Various doc improvements
 Key: PROTON-1763
 URL: https://issues.apache.org/jira/browse/PROTON-1763
 Project: Qpid Proton
  Issue Type: Improvement
  Components: proton-c
Reporter: Justin Ross
Assignee: Justin Ross
 Fix For: proton-c-0.20.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] [Updated] (PROTON-1763) Various doc improvements

2018-02-12 Thread Justin Ross (JIRA) 

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

Justin Ross updated PROTON-1763:

Fix Version/s: (was: proton-c-0.20.0)
   proton-c-0.21.0

> Various doc improvements
> 
>
> Key: PROTON-1763
> URL: https://issues.apache.org/jira/browse/PROTON-1763
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Reporter: Justin Ross
>Assignee: Justin Ross
>Priority: Major
> Fix For: proton-c-0.21.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] [Reopened] (PROTON-1751) Various doc improvements

2018-02-12 Thread Justin Ross (JIRA) 

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

Justin Ross reopened PROTON-1751:
-

Reopening this because I put the additional accept() doc on the wrong method.

> Various doc improvements
> 
>
> Key: PROTON-1751
> URL: https://issues.apache.org/jira/browse/PROTON-1751
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Reporter: Justin Ross
>Assignee: Justin Ross
>Priority: Major
> Fix For: proton-c-0.20.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] [Updated] (DISPATCH-914) qd_connector_t leaks mutexes

2018-02-12 Thread Ted Ross (JIRA) 

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

Ted Ross updated DISPATCH-914:
--
Fix Version/s: (was: 1.1.0)
   1.0.1

> qd_connector_t leaks mutexes
> 
>
> Key: DISPATCH-914
> URL: https://issues.apache.org/jira/browse/DISPATCH-914
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Router Node
>Affects Versions: 1.1.0
> Environment: Unit tests fail with the following traceback when run 
> under valgrind:
>  
> 39: ==5443== 64 bytes in 1 blocks are definitely lost in loss record 1,047 of 
> 3,514
> 39: ==5443==    at 0x4C30D47: memalign (vg_replace_malloc.c:857)
> 39: ==5443==    by 0x4C30E45: posix_memalign (vg_replace_malloc.c:1020)
> 39: ==5443==    by 0x4E70B58: sys_mutex (threading.c:40)
> 39: ==5443==    by 0x4E8BCAA: qd_server_connector (server.c:1363)
> 39: ==5443==    by 0x4E61A49: qd_dispatch_configure_connector 
> (connection_manager.c:711)
> 39: ==5443==    by 0x10FC8BDD: ffi_call_unix64 (unix64.S:76)
> 39: ==5443==    by 0x10FC854E: ffi_call (ffi64.c:525)
> 39: ==5443==    by 0x10DB53A4: _ctypes_callproc (in 
> /usr/lib64/python2.7/lib-dynload/_ctypes.so)
> 39: ==5443==    by 0x10DAF0BD: ??? (in 
> /usr/lib64/python2.7/lib-dynload/_ctypes.so)
> 39: ==5443==    by 0x5BBE342: PyObject_Call (in 
> /usr/lib64/libpython2.7.so.1.0)
> 39: ==5443==    by 0x5C831B1: PyEval_EvalFrameEx (in 
> /usr/lib64/libpython2.7.so.1.0)
> 39: ==5443==    by 0x5C85B18: PyEval_EvalFrameEx (in 
> /usr/lib64/libpython2.7.so.1.0)
>Reporter: Ken Giusti
>Assignee: Ken Giusti
>Priority: Major
> Fix For: 1.0.1
>
>




--
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-908) Router loses dispositions over receive link on qpid-interop-test 2-node test

2018-02-12 Thread Ted Ross (JIRA) 

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

Ted Ross updated DISPATCH-908:
--
Fix Version/s: (was: 1.1.0)
   1.0.1

> Router loses dispositions over receive link on qpid-interop-test 2-node test
> 
>
> Key: DISPATCH-908
> URL: https://issues.apache.org/jira/browse/DISPATCH-908
> Project: Qpid Dispatch
>  Issue Type: Bug
>Reporter: Kim van der Riet
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.0.1
>
> Attachments: dispatch-2node.qpid-cpp.jms_hdrs_props.pcapng, 
> qdrouterd.node1.conf, qdrouterd.node2.conf, qpidd.conf, scan0001.pdf
>
>
> When running qpid_interop_test.jms_hdrs_props_test, failures occur owing to 
> the improper disposition of messages on the central broker node which were 
> sent to the receiver. Analysis of the AMQP traffic shows that the Receiver 
> sent a disposition to Node 2, but Node 2 simply sent an AMQP detach without 
> any disposition to the broker.
> It is probable that the other QIT tests show this behavior, but don't exhibit 
> errors because no checks are made that the queues on the broker are empty 
> once the test ends, and no two tests share the same queue. The 
> jms_hdrs_props_test shares queues, allowing the improperly disposed messages 
> to remain in the queue and cause problems for the next test.
> The test is configured as follows:
> {noformat}
>9001 5672   5672 9002
> Sender --> Dispatch --> Broker --> Dispatch --> Receiver
> Node 1  Node 2
> {noformat}
> The configuration files for the broker (in this case, qpid-cpp) and the two 
> nodes are attached. Also attached are the wireshark capture file and a 
> diagram showing the AMQP traffic on the four links in sequence (scan0001.pdf).
> Notes on diagram:
> # If using the default Linux pdf viewer, the diagram can be rotated left in 
> the view menu to get it to display in the correct orientation.
> # The following abbreviations are used to display the AMQP performatives:
> H - header
> O - open
> B - begin
> AR - Attach as receiver
> AS - Attach as sender
> F - flow
> TN - transfer id=N
> DRN - disposition as receiver, settled=N
> DSN - disposition as sender, settled=N
> C - close
> X - detach
> E - end
> Bar is return direction traffic relative to traffic initiator.



--
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-920) Enabled policy blocks inter-router links

2018-02-12 Thread Ted Ross (JIRA) 

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

Ted Ross updated DISPATCH-920:
--
Fix Version/s: (was: 1.1.0)
   1.0.1

> Enabled policy blocks inter-router links
> 
>
> Key: DISPATCH-920
> URL: https://issues.apache.org/jira/browse/DISPATCH-920
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Policy Engine
>Affects Versions: 1.0.0
>Reporter: Ted Ross
>Assignee: Ted Ross
>Priority: Blocker
> Fix For: 1.0.1
>
>
> The default policy blocks the creation of receiver links with no source 
> address.  Because the inter-router links have no addresses in their sources 
> or targets, the policy blocks inter-router router coordination.
>  



--
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-900) Memory leak when repeatedly opening and closing connections

2018-02-12 Thread Ted Ross (JIRA) 

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

Ted Ross updated DISPATCH-900:
--
Fix Version/s: (was: 1.1.0)
   1.0.1

> Memory leak when repeatedly opening and closing connections
> ---
>
> Key: DISPATCH-900
> URL: https://issues.apache.org/jira/browse/DISPATCH-900
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Container
>Affects Versions: 1.0.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.0.1
>
>
> Steps to reproduce - 
> 1. Start the router with the default config file
> 2. Run the following python program which simply opens and closes connections.
> {noformat}
> from proton.utils import BlockingConnection
> URL = '0.0.0.0:5672'
> continue_loop = True
> while continue_loop:
> connection = BlockingConnection(url=URL, ssl_domain=None)
> print 'Creating connection'
> connection.close()
> {noformat}
> 3. While the above python program is running, start up the *top* program and 
> watch the memory of the router grow.



--
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-895) qpid-dispatch crashes with a SEGFAULT in libqpid-proton

2018-02-12 Thread Ted Ross (JIRA) 

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

Ted Ross updated DISPATCH-895:
--
Fix Version/s: (was: 1.1.0)
   1.0.1

> qpid-dispatch crashes with a SEGFAULT in libqpid-proton
> ---
>
> Key: DISPATCH-895
> URL: https://issues.apache.org/jira/browse/DISPATCH-895
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Routing Engine
>Affects Versions: 0.8.0
> Environment: OS: Red Hat Enterprise Linux 7.4
> Arch: x86_64
> Installed Packages
> Name: qpid-cpp-client
> Arch: x86_64
> Version : 1.36.0
> Release : 9.el7
> Size: 4.4 M
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : Libraries for Qpid C++ client applications
> URL : http://qpid.apache.org
> License : ASL 2.0
> Description : Run-time libraries for AMQP client applications developed using 
> Qpid
> : C++. Clients exchange messages with an AMQP message broker using
> : the AMQP protocol.
> Name: qpid-cpp-server
> Arch: x86_64
> Version : 1.36.0
> Release : 9.el7
> Size: 5.2 M
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : An AMQP message broker daemon
> URL : http://qpid.apache.org
> License : ASL 2.0
> Description : A message broker daemon that receives stores and routes 
> messages using
> : the open AMQP messaging protocol.
> Name: qpid-cpp-server-linearstore
> Arch: x86_64
> Version : 1.36.0
> Release : 9.el7
> Size: 797 k
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : Red Hat persistence extension to the Qpid messaging sytem
> URL : http://qpid.apache.org
> License : ASL 2.0
> Description : Red Hat persistence extension to the Qpid AMQP broker: 
> persistent message
> : storage using a libaio-based asynchronous journal.
> Name: qpid-dispatch-debuginfo
> Arch: x86_64
> Version : 0.8.0
> Release : 10.el7
> Size: 2.1 M
> Repo: installed
> Summary : Debug information for package qpid-dispatch
> URL : http://qpid.apache.org/
> License : ASL 2.0
> Description : This package provides debug information for package 
> qpid-dispatch.
> : Debug information is useful when developing applications that 
> use this
> : package or when debugging this package.
> Name: qpid-dispatch-router
> Arch: x86_64
> Version : 0.8.0
> Release : 10.el7
> Size: 1.0 M
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : The Qpid Dispatch Router executable
> URL : http://qpid.apache.org/
> License : ASL 2.0
> Description : The Qpid Dispatch Router executable.
> Name: qpid-proton-c
> Arch: x86_64
> Version : 0.16.0
> Release : 7.el7
> Size: 334 k
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : C libraries for Qpid Proton
> URL : http://qpid.apache.org/proton/
> License : ASL 2.0
> Description : C libraries for Qpid Proton.
> Name: qpid-proton-debuginfo
> Arch: x86_64
> Version : 0.16.0
> Release : 7.el7
> Size: 6.8 M
> Repo: installed
> Summary : Debug information for package qpid-proton
> URL : http://qpid.apache.org/proton/
> License : ASL 2.0
> Description : This package provides debug information for package qpid-proton.
> : Debug information is useful when developing applications that 
> use this
> : package or when debugging this package.
> Name: qpid-qmf
> Arch: x86_64
> Version : 1.36.0
> Release : 9.el7
> Size: 476 k
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : The QPID Management Framework
> URL : http://qpid.apache.org
> License : ASL 2.0
> Description : The Qpid Management Framework is a general-purpose management 
> bus built on Qpid
> : messaging. It takes advantage of the scalability, security, and 
> rich
> : capabilities of Qpid to provide flexible and easy-to-use 
> manageability to a
> : large set of applications.
> Name: qpid-tools
> Arch: noarch
> Version : 1.36.0
> Release : 9.el7
> Size: 384 k
> Repo: installed
> From repo   : rhel-server-7-satellite-6-beta-rpms
> Summary : Management and diagostic tools for Apache Qpid
> URL : http://qpid.apache.org
> License : ASL 2.0
> Description : Management and diagnostic tools for Apache Qpid brokers and 
> clients.
>

[jira] [Updated] (DISPATCH-889) linkRoute patterns beginning with #/string match substrings after the /

2018-02-12 Thread Ted Ross (JIRA) 

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

Ted Ross updated DISPATCH-889:
--
Fix Version/s: (was: 1.1.0)
   1.0.1

> linkRoute patterns beginning with #/string match substrings after the / 
> 
>
> Key: DISPATCH-889
> URL: https://issues.apache.org/jira/browse/DISPATCH-889
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Container
>Affects Versions: 1.0.0
>Reporter: Ernest Allen
>Assignee: Ken Giusti
>Priority: Major
> Fix For: 1.0.1
>
>
> linkRoutes with a pattern of #/policy match substrings of the word policy
> - 1. setup a router
> router {
> mode: standalone
> id: A
> }
> listener {
> host: 0.0.0.0
> port: 2
> role: normal
> saslMechanisms: ANONYMOUS
> }
> connector {
> name: policy-connector
> role: route-container
> host: 0.0.0.0
> port:  
> saslMechanisms: ANONYMOUS
> }
> linkRoute {
>pattern: #/policy
>dir: in
>   connection: policy-connector
> }
> - 2. start an acceptor on that host:port
> qpid-proton/examples/python/server_direct.py
> - 3. verify linkRoute is established
> qdstat -b 0.0.0.0:2 --linkroutes
> Link Routes
>   address   dir  distrib   status
>   =
>   #/policy  in   linkBalanced  active
> - 4. send some messages through the router
> addresses that should match
> qpid-proton/examples/python/simple_send -a 0.0.0.0:2/bob.com/policy -m 1
>   -> message received at server_direct.py
> qpid-proton/examples/python/simple_send -a 0.0.0.0:2/ken-is-great/policy 
> -m 1
>   -> message received at server_direct.py
> qpid-proton/examples/python/simple_send -a 0.0.0.0:2/policy -m 1
>   -> message received at server_direct.py
> addresses that should not match
> qpid-proton/examples/python/simple_send -a 0.0.0.0:2/bob.com/a -m 1
>   -> message NOT sent - this is the correct behavior 
> qpid-proton/examples/python/simple_send -a 0.0.0.0:2/bob.com/p -m 1
>   -> message received at server_direct.py - this is a bug
> qpid-proton/examples/python/simple_send -a 0.0.0.0:2/poli -m 1
>   -> message received at server_direct.py - this is a bug



--
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-883) Router crashes when it processes management request for connections

2018-02-12 Thread Ted Ross (JIRA) 

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

Ted Ross updated DISPATCH-883:
--
Fix Version/s: (was: 1.1.0)
   1.0.1

> Router crashes when it processes management request for connections
> ---
>
> Key: DISPATCH-883
> URL: https://issues.apache.org/jira/browse/DISPATCH-883
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Container
>Affects Versions: 1.0.0
>Reporter: Ernest Allen
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.0.1
>
>
> Router crashes when attempting to service a management request. 
> When a python client sets its connections properties to a map, then as soon 
> as the router receives a management request for the connection info, the 
> router will crash.
> If the client sets its connections properties to a string, then there is no 
> crash.
> To reproduce:
> - start the router using tests/config-1/A.conf
> - modify the proton example server.py to set a properties map on line 37:
>   self.conn = event.container.connect(self.url, 
> properties={'client_identifier': 'policy_server'})
> - start the modified proton example: ./server.py -a 0.0.0.0:2/example
> - all is well until you do a  qdstat -b 0.0.0.0:2 -c
> backtrace:
> Thread 2 "qdrouterd" received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fffec03b700 (LWP 26782)]
> 0x76739766 in strlen () from /lib64/libc.so.6
> Missing separate debuginfos, use: dnf debuginfo-install 
> libffi-3.1-12.fc26.x86_64 libwebsockets-2.2.1-1.fc26.x86_64 
> openssl-libs-1.1.0f-7.fc26.x86_64 python2-libs-2.7.14-2.fc26.x86_64 
> zlib-1.2.11-2.fc26.x86_64
> (gdb) bt
> #0  0x76739766 in strlen () from /lib64/libc.so.6
> #1  0x77b6f805 in qd_compose_insert_string (field=0x7fffe005cb60, 
> value=0x0) at /home/eallen/workspace/qpid-dispatch/src/compose.c:444
> #2  0x77b90225 in qdr_connection_insert_column_CT (
> conn=0x7fffd400b620, col=12, body=0x7fffe005cb60, as_map=false)
> at 
> /home/eallen/workspace/qpid-dispatch/src/router_core/agent_connection.c:215
> #3  0x77b90300 in qdr_agent_write_connection_CT 
> (query=0x7fffe0077da0, 
> conn=0x7fffd400b620)
> at 
> /home/eallen/workspace/qpid-dispatch/src/router_core/agent_connection.c:242
> #4  0x77b90449 in qdra_connection_get_first_CT (core=0x92c090, 
> query=0x7fffe0077da0, offset=0)
> at 
> /home/eallen/workspace/qpid-dispatch/src/router_core/agent_connection.c:284
> #5  0x77b8c850 in qdrh_query_get_first_CT (core=0x92c090, 
> action=0x7fffe000dfa0, discard=false)
> at /home/eallen/workspace/qpid-dispatch/src/router_core/agent.c:455
> #6  0x77b9f86a in router_core_thread (arg=0x92c090)
> at 
> /home/eallen/workspace/qpid-dispatch/src/router_core/router_core_thread.c:83
> #7  0x774f836d in start_thread () from /lib64/libpthread.so.0
> #8  0x767b5e1f in clone () from /lib64/libc.so.6



--
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-887) Dispatch reestablishes connection inspite of deleting the connector

2018-02-12 Thread Ted Ross (JIRA) 

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

Ted Ross updated DISPATCH-887:
--
Fix Version/s: (was: 1.1.0)
   1.0.1

> Dispatch reestablishes connection inspite of deleting the connector
> ---
>
> Key: DISPATCH-887
> URL: https://issues.apache.org/jira/browse/DISPATCH-887
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Container
>Affects Versions: 1.0.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.0.1
>
>
> There is a race condition happening when a connector is deleted.
> On connector delete, the following function is called 
> {code}
> void qd_connection_manager_delete_connector(qd_dispatch_t *qd, void *impl)
> {
> qd_connector_t *ct = (qd_connector_t*) impl;
> if (ct) {
> sys_mutex_lock(ct->lock);
> if (ct->ctx && ct->ctx->pn_conn) {
> qd_connection_invoke_deferred(ct->ctx, deferred_close, 
> ct->ctx->pn_conn);
> }
> sys_mutex_unlock(ct->lock);
> DEQ_REMOVE(qd->connection_manager->connectors, ct);
> qd_connector_decref(ct);
> }
> }
> {code}
> The deferred_close() is invoked before qd_connector_decref() is invoked hence 
> the connection's connector is still in place and the connector is 
> re-established.



--
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-882) router buffers messages for slow presettled receiver

2018-02-12 Thread Ted Ross (JIRA) 

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

Ted Ross updated DISPATCH-882:
--
Fix Version/s: (was: 1.1.0)
   1.0.1

> router buffers messages for slow presettled receiver
> 
>
> Key: DISPATCH-882
> URL: https://issues.apache.org/jira/browse/DISPATCH-882
> Project: Qpid Dispatch
>  Issue Type: Bug
>Reporter: Gordon Sim
>Assignee: Ken Giusti
>Priority: Major
> Fix For: 1.0.1
>
>
> For an anycast address with incoming transfers unsettled and outgoing 
> transfers pre-settled, if the receiver can't keep up with the sender, the 
> router appears to buffer a growing number of deliveries.
> The link stats for the receiver, which is receiving pre-settled, are shown as 
> accepted and unsettled (with a small number of undelivered) with presettled 
> count remaining at zero and the unsettled count growing. qpid-stat -m shows 
> growth in buffer and message content related types.
> It looks like there is no limit to the amount of messages the router will try 
> to buffer in this case(?) though I did not push it all the way to failure.



--
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-881) Inbound pre-settled messages causes memory leak of deliveries

2018-02-12 Thread Ted Ross (JIRA) 

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

Ted Ross updated DISPATCH-881:
--
Fix Version/s: (was: 1.1.0)
   1.0.1

> Inbound pre-settled messages causes memory leak of deliveries
> -
>
> Key: DISPATCH-881
> URL: https://issues.apache.org/jira/browse/DISPATCH-881
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Routing Engine
>Affects Versions: 1.0.0
>Reporter: Ken Giusti
>Assignee: Ken Giusti
>Priority: Major
> Fix For: 1.0.1
>
>
> Messages sent as pre-settled do not get freed.
> To reproduce:
> qpid-send -a "example; {link:{reliability:at-most-once}}" --send-rate 100 -m 
> 1 --connection-options "{protocol:'amqp1.0'}" --capacity 100
> The # of qdr_delivery_t (and associated message buffers) keeps increasing:
> qdstat -m | grep qdr_delivery_t



--
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-874) unable to load .json or .woff2 files from local file system from http port

2018-02-12 Thread Ted Ross (JIRA) 

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

Ted Ross updated DISPATCH-874:
--
Fix Version/s: (was: 1.1.0)
   1.0.1

> unable to load .json or .woff2 files from local file system from http port
> --
>
> Key: DISPATCH-874
> URL: https://issues.apache.org/jira/browse/DISPATCH-874
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Container
>Affects Versions: 0.8.0, 1.0.0
>Reporter: Ernest Allen
>Assignee: Alan Conway
>Priority: Major
> Fix For: 1.0.1
>
>
> When serving the console from a router with a listener that has http: true, 
> files with extensions of .json and .woff2 fail to load.
> To reproduce:
> - setup a router with an http listener (ie. on port 5673)
> - load the console from a browser using that port (localhost:5673/)
> - attempt to load the file localhost:5673/plugin/data/world-110m.json
> What you get:
> a 404 page
> What you should get:
> the contents of the file
> Just to verify:
> - copy a .js file to the plugin/data/ directory where the console is installed
> - attempt to load localhost:5673/plugin/data/name_of_js_file.js
> - you should see the .js file in the browser. It's just .json and .woff2 
> files that won't load
> - also to verify: if you load the console from an apache web server, the 
> plugin/data/world-110m.json loads just fine.
> The .woff2 files are fonts. You can see that they fail to load in the 
> browser's debugging console -> Network tab.



--
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-8038) [Broker-J][System Tests] Add protocol system test suites for AMQP 0-x

2018-02-12 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on QPID-8038:
---

Commit 91eb1cb224e3cbff8646aa81e08114f01fa1e936 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=91eb1cb ]

QPID-8038: [Broker-J] Add AMQP 1.0 idle and protocol header timeout protocol 
tests, eliminating the old systems tests built using pieces of the old client


> [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
>Priority: Major
>
> 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
(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-8091) [Broker-J] [AMQP 1.0] Store transaction timeout feature

2018-02-12 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on QPID-8091:
---

Commit fa2b1ff31ef116d30f495f3df1ab46ac57adf3c4 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=fa2b1ff ]

QPID-8091: [Broker-J] Correct typo in package name


> [Broker-J] [AMQP 1.0] Store transaction timeout feature
> ---
>
> Key: QPID-8091
> URL: https://issues.apache.org/jira/browse/QPID-8091
> Project: Qpid
>  Issue Type: Improvement
>  Components: Broker-J
>Reporter: Keith Wall
>Assignee: Keith Wall
>Priority: Major
> Fix For: qpid-java-broker-7.1.0
>
>
> Berkeley JE's design means that once a transaction has begun, its internal 
> cleaner is unable to clean beyond the point the transaction started in the 
> transaction log.  Other transaction work continues as normal, but the disk 
> space utilisation can't shrink until the long running transaction is 
> completed.  In an extreme case, disk space can be exhausted.
> This has consequence for long running store transactions in Qpid.  For 0-x, 
> the transaction timeout features allows the the length of time a transaction 
> may be open or idle to be constrained, thus limiting the harmful effects of a 
> long running store transaction.
> For robustness, that features needs to be implemented on AMQP 1.0 too.   A 
> decision needs to be made about the correct course of action to be taken when 
> a long running transaction exceeds the threshold.   The transaction 
> coordinator link could be closed with an error or the entire connection 
> closed.



--
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-8038) [Broker-J][System Tests] Add protocol system test suites for AMQP 0-x

2018-02-12 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on QPID-8038:
---

Commit cc8b3c0bffdcc45086a35ef5e4a129969a791ae7 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=cc8b3c0 ]

QPID-8038: [Broker-J] Add authentication timeout 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
>Priority: Major
>
> 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
(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 #253: Enhanced link-statistics

2018-02-12 Thread ted-ross 
GitHub user ted-ross opened a pull request:

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

Enhanced link-statistics

This pull request contains a code change that adds the following contents 
to the management entities in the router:
- An index number has been added to the router.node entity to facilitate 
mapping histogram slots to router identities.
- A new attribute in the 'link' entity called 'ingressHistogram'.  This 
attribute is valid only for outgoing links on normal connections.  It contains 
an array of numbers that indicate the number of deliveries that arrived on each 
ingress router in the network.

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

$ git pull https://github.com/ted-ross/qpid-dispatch tross-link-stats

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

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


commit 98720da4674f15524b4b64b8b0fc892f64e53ad0
Author: Ted Ross 
Date:   2018-02-09T15:52:31Z

Added index number to the router.node entity.  This will be needed to map 
histogram slots to router identities.

commit f3fe1e290a75cce3ad1168b64afcc0011fd9a3dd
Author: Ted Ross 
Date:   2018-02-09T21:54:02Z

Added functioning ingress histogram for endpoint out-links.
Still needed:
  - Tests
  - Removal of the older mechanism for determing ingress router in 
multicast forwarder




---

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

[jira] [Created] (PROTON-1762) [ruby] gem does not contain examples

2018-02-12 Thread Alan Conway (JIRA) 
Alan Conway created PROTON-1762:
---

 Summary: [ruby] gem does not contain examples
 Key: PROTON-1762
 URL: https://issues.apache.org/jira/browse/PROTON-1762
 Project: Qpid Proton
  Issue Type: Improvement
  Components: ruby-binding
Affects Versions: proton-c-0.20.0
Reporter: Alan Conway
Assignee: Alan Conway
 Fix For: proton-c-0.21.0


The ruby gem created by cmake does not include example files. The example 
sources should be included as part of the documentation and linked from the 
README.



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