[jira] [Commented] (QPIDIT-22) Add ability to run on Jenkins CI
[ https://issues.apache.org/jira/browse/QPIDIT-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15205012#comment-15205012 ] ASF subversion and git services commented on QPIDIT-22: --- Commit 4f9b9ac68f17137fd985342eb4acfdc4107ed1f1 in qpid-interop-test's branch refs/heads/master from [~kpvdr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=4f9b9ac ] QPIDIT-22: Updated AMQP and types test to latest Proton C++ API. Files missed in last commit > Add ability to run on Jenkins CI > > > Key: QPIDIT-22 > URL: https://issues.apache.org/jira/browse/QPIDIT-22 > Project: Apache QPID IT > Issue Type: Improvement >Reporter: Kim van der Riet >Assignee: Kim van der Riet > > Run the tests on Jenkins continuous integration system. For this to be > realized, the location of dependent components needs to be parameterized, as > they can no longer be in the usual installed locations. This includes: > * qpid-proton > * qpid-jms -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-22) Add ability to run on Jenkins CI
[ https://issues.apache.org/jira/browse/QPIDIT-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15205010#comment-15205010 ] ASF subversion and git services commented on QPIDIT-22: --- Commit ab84b0eee90b33912ccad8e9a0ee8b5660f413a0 in qpid-interop-test's branch refs/heads/master from [~kpvdr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=ab84b0e ] QPIDIT-22: Updated c++ shims for latest changes to Proton c++ API. WIP - JMS shims not working, issues with AMQP types > Add ability to run on Jenkins CI > > > Key: QPIDIT-22 > URL: https://issues.apache.org/jira/browse/QPIDIT-22 > Project: Apache QPID IT > Issue Type: Improvement >Reporter: Kim van der Riet >Assignee: Kim van der Riet > > Run the tests on Jenkins continuous integration system. For this to be > realized, the location of dependent components needs to be parameterized, as > they can no longer be in the usual installed locations. This includes: > * qpid-proton > * qpid-jms -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-22) Add ability to run on Jenkins CI
[ https://issues.apache.org/jira/browse/QPIDIT-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15205011#comment-15205011 ] ASF subversion and git services commented on QPIDIT-22: --- Commit 901635ad72f222ad11892dbc3163150afbca2349 in qpid-interop-test's branch refs/heads/master from [~kpvdr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=901635a ] QPIDIT-22: Updated AMQP and types test to latest Proton C++ API. > Add ability to run on Jenkins CI > > > Key: QPIDIT-22 > URL: https://issues.apache.org/jira/browse/QPIDIT-22 > Project: Apache QPID IT > Issue Type: Improvement >Reporter: Kim van der Riet >Assignee: Kim van der Riet > > Run the tests on Jenkins continuous integration system. For this to be > realized, the location of dependent components needs to be parameterized, as > they can no longer be in the usual installed locations. This includes: > * qpid-proton > * qpid-jms -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Review Request 45113: NO-JIRA: c++: Allow setting of conditions on endpoints.
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/45113/
---
(Updated March 21, 2016, 7:40 p.m.)
Review request for qpid, Andrew Stitcher, Cliff Jansen, and Justin Ross.
Changes
---
Fix typo.
Repository: qpid-proton-git
Description
---
Allow setting conditions in the "close()" function for endpoints and transport.
Modified the proton::condition class as follows:
- normal value semantics, user can construct and copy conditions without
surprises.
- memory safe: no core dumps, no dependency on endpoint lifecycle.
Example of use:
// Close a link with an error.
mylink.close(condition("myerr", "something went wrong"));
// Throw condition "name: description" as a proton::error
if (!session.condition().empty())
throw proton::error(session.condition().what());
// Save the condition to check/report/throw later
condition save_error = connection.condition();
Diffs (updated)
-
proton-c/bindings/cpp/include/proton/condition.hpp
9e157f3c7963530f469d1fb40f52fa12fe57d7bd
proton-c/bindings/cpp/include/proton/connection.hpp
da7f806c745e2c52c4d2677fea669105d8c703ce
proton-c/bindings/cpp/include/proton/endpoint.hpp
d59e09324887c0f6cf22da99816cf0075f8b79b7
proton-c/bindings/cpp/include/proton/link.hpp
8de2e7ba0f944e169560591ecbc4b32c182d8dee
proton-c/bindings/cpp/include/proton/session.hpp
014ab2a2d2b3c180a42162e7b22454492985f61c
proton-c/bindings/cpp/include/proton/transport.hpp
9e32ac508a6c711b912aaadcb7bea5923e6b47e1
proton-c/bindings/cpp/src/condition.cpp
b60425130b2116ebba8a08b3fac58fe4aa95d549
proton-c/bindings/cpp/src/connection.cpp
fc61190e900b9c2e48a98d06149221f03e30cd0a
proton-c/bindings/cpp/src/link.cpp 1ac730442018a4e93fad731941c888e600a68142
proton-c/bindings/cpp/src/session.cpp
545869f78ec1183a549f9c396908a530869ef1f6
proton-c/bindings/cpp/src/transport.cpp
88838064810e43dfbb2b44f51d87504d2a5d6d75
Diff: https://reviews.apache.org/r/45113/diff/
Testing
---
Thanks,
Alan Conway
[jira] [Assigned] (QPID-7112) Create UI for the CloudFoundry Group Provider
[ https://issues.apache.org/jira/browse/QPID-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-7112: Assignee: Keith Wall > Create UI for the CloudFoundry Group Provider > - > > Key: QPID-7112 > URL: https://issues.apache.org/jira/browse/QPID-7112 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Keith Wall >Priority: Minor > Fix For: qpid-java-6.1 > > Attachments: > 0001-QPID-7112-Java-Broker-Add-UI-for-CloudFoundryDashboa.patch > > > Create UI for the CloudFoundry Group Provider -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7112) Create UI for the CloudFoundry Group Provider
[ https://issues.apache.org/jira/browse/QPID-7112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7112: - Attachment: 0001-QPID-7112-Java-Broker-Add-UI-for-CloudFoundryDashboa.patch > Create UI for the CloudFoundry Group Provider > - > > Key: QPID-7112 > URL: https://issues.apache.org/jira/browse/QPID-7112 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Priority: Minor > Fix For: qpid-java-6.1 > > Attachments: > 0001-QPID-7112-Java-Broker-Add-UI-for-CloudFoundryDashboa.patch > > > Create UI for the CloudFoundry Group Provider -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Review Request 45113: NO-JIRA: c++: Allow setting of conditions on endpoints.
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/45113/
---
Review request for qpid, Andrew Stitcher, Cliff Jansen, and Justin Ross.
Repository: qpid-proton-git
Description
---
Allow setting conditions in the "close()" function for endpoints and transport.
Modified the proton::condition class as follows:
- normal value semantics, user can construct and copy conditions without
surprises.
- memory safe: no core dumps, no dependency on endpoint lifecycle.
Example of use:
// Close a link with an error.
mylink.close(condition("myerr", "something went wrong"));
// Throw condition "name: description" as a proton::error
if (!session.condition().empty())
throw proton::error(session.condition().what());
// Save the condition to check/report/throw later
condition save_error = connection.condition();
Diffs
-
proton-c/bindings/cpp/include/proton/condition.hpp
9e157f3c7963530f469d1fb40f52fa12fe57d7bd
proton-c/bindings/cpp/include/proton/connection.hpp
da7f806c745e2c52c4d2677fea669105d8c703ce
proton-c/bindings/cpp/include/proton/endpoint.hpp
d59e09324887c0f6cf22da99816cf0075f8b79b7
proton-c/bindings/cpp/include/proton/link.hpp
8de2e7ba0f944e169560591ecbc4b32c182d8dee
proton-c/bindings/cpp/include/proton/session.hpp
014ab2a2d2b3c180a42162e7b22454492985f61c
proton-c/bindings/cpp/include/proton/transport.hpp
9e32ac508a6c711b912aaadcb7bea5923e6b47e1
proton-c/bindings/cpp/src/condition.cpp
b60425130b2116ebba8a08b3fac58fe4aa95d549
proton-c/bindings/cpp/src/connection.cpp
fc61190e900b9c2e48a98d06149221f03e30cd0a
proton-c/bindings/cpp/src/link.cpp 1ac730442018a4e93fad731941c888e600a68142
proton-c/bindings/cpp/src/session.cpp
545869f78ec1183a549f9c396908a530869ef1f6
proton-c/bindings/cpp/src/transport.cpp
88838064810e43dfbb2b44f51d87504d2a5d6d75
Diff: https://reviews.apache.org/r/45113/diff/
Testing
---
Thanks,
Alan Conway
[jira] [Commented] (DISPATCH-242) Add options to qdstat to display autoLinks and linkRoutes
[ https://issues.apache.org/jira/browse/DISPATCH-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15204562#comment-15204562 ] ASF subversion and git services commented on DISPATCH-242: -- Commit d5a9fe82678a85a4e8f46a8e1bdd315378884ab9 in qpid-dispatch's branch refs/heads/master from [~tr...@redhat.com] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=d5a9fe8 ] DISPATCH-242 - Added -A option to qdstat to display autoLinks. > Add options to qdstat to display autoLinks and linkRoutes > - > > Key: DISPATCH-242 > URL: https://issues.apache.org/jira/browse/DISPATCH-242 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Console >Reporter: Ted Ross > Fix For: 0.6 > > > In 0.6, there will be a few new management entities that contain interesting > monitoring data: autoLink and linkRoute. qdstat should be enhanced to > display these entities. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7150) HA memory leak in primary broker when overwriting messages in a ring queue
[ https://issues.apache.org/jira/browse/QPID-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15204380#comment-15204380 ] Alan Conway commented on QPID-7150: --- That narrows it down a lot. The primary does some tracking of queue state even when no backup is connected, in order to be ready when a backup connects. That is probably where the problem lies. > HA memory leak in primary broker when overwriting messages in a ring queue > -- > > Key: QPID-7150 > URL: https://issues.apache.org/jira/browse/QPID-7150 > Project: Qpid > Issue Type: Bug > Components: C++ Clustering >Affects Versions: 0.32 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: qpid-cpp-next > > > From https://bugzilla.redhat.com/show_bug.cgi?id=1318180 > HA memory leak in primary broker when overwriting messages in a ring queue > ReplicatingSubscription accumulates IDs of dequeued messages to send on > dispatch. It should clear the accumulated IDs once sent. Due to a merge error, > since: > 014f0f3 QPID-4327: HA TX transactions: basic replication. > The ID set is not cleared, causing it to accumulate memory slowly. > This leak would be particularly noticeable on a busy ring-queue since a > ring-queue generates a dequeue event for every enqueue once it reaches its max > size. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-7149) [HA] active HA broker memory leak when ring queue discards overflow messages
[
https://issues.apache.org/jira/browse/QPID-7149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway reassigned QPID-7149:
-
Assignee: Alan Conway
> [HA] active HA broker memory leak when ring queue discards overflow messages
>
>
> Key: QPID-7149
> URL: https://issues.apache.org/jira/browse/QPID-7149
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Environment: RHEL6
> qpid trunk svn rev. 1735384
> - issue seen in very old releases (since active-passive HA cluster initial
> implementation, most probably)
> libstdc++-devel-4.4.7-4.el6.x86_64
> gcc-c++-4.4.7-4.el6.x86_64
> libgcc-4.4.7-4.el6.x86_64
> libstdc++-4.4.7-4.el6.x86_64
> gcc-4.4.7-4.el6.x86_64
>Reporter: Pavel Moravec
>Assignee: Alan Conway
>
> There is a memory leak on active HA broker, triggered most probably by
> purging overflow message from a ring queue. Basic scenario is to setup HA
> cluster, promote to primary and feed forever a ring queue with messages.
> Detailed scenario:
> 1) Start brokers and promote one to primary:
> {noformat}
> start_broker() {
> port=$1
> shift
> rm -rf _${port}
> mkdir _${port}
> nohup qpidd --load-module=ha.so --port=$port
> --log-to-file=qpidd.$port.log --data-dir=_${port} --auth=no
> --log-to-stderr=no --ha-cluster=yes
> --ha-brokers-url="$(hostname):5672,$(hostname):5673,$(hostname):5674"
> --ha-replicate=all --acl-file=/root/qpidd.acl "$@" > /dev/null 2>&1 &
> sleep 1
> }
> killall qpidd qpid-receive 2> /dev/null
> rm -f qpidd.*.log
> start_broker 5672
> sleep 1
> qpid-ha promote -b $(hostname):5672 --cluster-manager
> sleep 1
> start_broker 5673
> sleep 1
> start_broker 5674
> {noformat}
> 2) Create ring queues and send there messages (it is enough to have 1 queue,
> having more should show the leak faster):
> {noformat}
> for i in $(seq 0 9); do
> qpid-config add queue FromKeyServer_$i --max-queue-size=1
> --max-queue-count=10 --limit-policy=ring --argument=x-qpid-priorities=10
> done
> while true; do
> for j in $(seq 1 10); do
> for i in $(seq 1 10); do
> for k in $(seq 0 9); do
> qpid-send -a FromKeyServer_$k -m 100
> --send-rate=50 -- priority=$(($((RANDOM))%10)) &
> done
> done
> wait
> while [ $(qpid-stat -q | grep broker-replicator | sed "s/Y//g"
> | awk '{ print $2 }' | sort -n | tail -n1) != "0" ]; do
> sleep 1
> done
> done
> date
> ps aux | grep qpidd | grep "port=5672" | awk -F "--store-dir" '{ print
> $1 }'
> done
> {noformat}
> (the "while [ $(qpid-stat -q | .." cycle is there just to slow down the
> message enqueues to ensure replication federation queues dont have big
> backlog - that would interfere with memory consumpiton observation)
> 3) Run those scripts and monitor memory consumption.
> - without using priority queues and sending messages without priorities, leak
> is evident as well - sometimes smaller, sometimes the same
> - valgrind (on some older versions I tested before more thoroughly) detects
> nothing (neither leaked memory or reachable at shutdown)
> - same leak is evident even with --ha-replicate=none
> - number of backup brokers does not affect the memory leak
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7149) [HA] active HA broker memory leak when ring queue discards overflow messages
[
https://issues.apache.org/jira/browse/QPID-7149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15204363#comment-15204363
]
Alan Conway commented on QPID-7149:
---
That narrows it down considerably to the code that runs on the primary even
when no backups are present. The primary does do some tracking of queue state
even when there are no backups, in order to be ready if a backup does connect.
That is probably where the trouble lies.
> [HA] active HA broker memory leak when ring queue discards overflow messages
>
>
> Key: QPID-7149
> URL: https://issues.apache.org/jira/browse/QPID-7149
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Environment: RHEL6
> qpid trunk svn rev. 1735384
> - issue seen in very old releases (since active-passive HA cluster initial
> implementation, most probably)
> libstdc++-devel-4.4.7-4.el6.x86_64
> gcc-c++-4.4.7-4.el6.x86_64
> libgcc-4.4.7-4.el6.x86_64
> libstdc++-4.4.7-4.el6.x86_64
> gcc-4.4.7-4.el6.x86_64
>Reporter: Pavel Moravec
>
> There is a memory leak on active HA broker, triggered most probably by
> purging overflow message from a ring queue. Basic scenario is to setup HA
> cluster, promote to primary and feed forever a ring queue with messages.
> Detailed scenario:
> 1) Start brokers and promote one to primary:
> {noformat}
> start_broker() {
> port=$1
> shift
> rm -rf _${port}
> mkdir _${port}
> nohup qpidd --load-module=ha.so --port=$port
> --log-to-file=qpidd.$port.log --data-dir=_${port} --auth=no
> --log-to-stderr=no --ha-cluster=yes
> --ha-brokers-url="$(hostname):5672,$(hostname):5673,$(hostname):5674"
> --ha-replicate=all --acl-file=/root/qpidd.acl "$@" > /dev/null 2>&1 &
> sleep 1
> }
> killall qpidd qpid-receive 2> /dev/null
> rm -f qpidd.*.log
> start_broker 5672
> sleep 1
> qpid-ha promote -b $(hostname):5672 --cluster-manager
> sleep 1
> start_broker 5673
> sleep 1
> start_broker 5674
> {noformat}
> 2) Create ring queues and send there messages (it is enough to have 1 queue,
> having more should show the leak faster):
> {noformat}
> for i in $(seq 0 9); do
> qpid-config add queue FromKeyServer_$i --max-queue-size=1
> --max-queue-count=10 --limit-policy=ring --argument=x-qpid-priorities=10
> done
> while true; do
> for j in $(seq 1 10); do
> for i in $(seq 1 10); do
> for k in $(seq 0 9); do
> qpid-send -a FromKeyServer_$k -m 100
> --send-rate=50 -- priority=$(($((RANDOM))%10)) &
> done
> done
> wait
> while [ $(qpid-stat -q | grep broker-replicator | sed "s/Y//g"
> | awk '{ print $2 }' | sort -n | tail -n1) != "0" ]; do
> sleep 1
> done
> done
> date
> ps aux | grep qpidd | grep "port=5672" | awk -F "--store-dir" '{ print
> $1 }'
> done
> {noformat}
> (the "while [ $(qpid-stat -q | .." cycle is there just to slow down the
> message enqueues to ensure replication federation queues dont have big
> backlog - that would interfere with memory consumpiton observation)
> 3) Run those scripts and monitor memory consumption.
> - without using priority queues and sending messages without priorities, leak
> is evident as well - sometimes smaller, sometimes the same
> - valgrind (on some older versions I tested before more thoroughly) detects
> nothing (neither leaked memory or reachable at shutdown)
> - same leak is evident even with --ha-replicate=none
> - number of backup brokers does not affect the memory leak
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
Review Request 45107: NO-JIRA: Fixed compile and link errors
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/45107/ --- Review request for qpid, Ganesh Murthy, Kenneth Giusti, and Ted Ross. Repository: qpid-dispatch Description --- Several "variable not initiatialized" warnings. The offer one was definitely a bug but I'm not 100% sure of my fix.. Added missing extern declarations on const char* constants. Several tests are failing after this fix, not sure if the fix is the problem or they were already failing. Diffs - include/qpid/dispatch/amqp.h 2793c6de2006855ae3121b3c0f6ad55a7569cc7c src/router_core/transfer.c 47b499b16c5b04286c7cdc5534a3704b06f24ed7 src/router_node.c bf093df28d59548087f3c2fd95844fdeb920313f Diff: https://reviews.apache.org/r/45107/diff/ Testing --- ctest -VV shows several errors I am not sure if they were caused by my fix or were pre-existing == FAIL: test_create_connector_waypoint (system_tests_management.ManagementTest) Test creating waypoint, connector and fixedAddress -- Traceback (most recent call last): File "/home/aconway/dispatch/tests/system_tests_management.py", line 300, in test_create_connector_waypoint self.assertEqual(6, len(re.findall(r'MESSAGE.*to=.*/foo', f.read( AssertionError: 6 != 0 == FAIL: test_dummy (system_tests_management.ManagementTest) Test all operations on the dummy test entity -- Traceback (most recent call last): File "/home/aconway/dispatch/tests/system_tests_management.py", line 323, in test_dummy self.assertRaises(NotImplementedStatus, entity.delete) AssertionError: NotImplementedStatus not raised == FAIL: test_get_operations (system_tests_management.ManagementTest) -- Traceback (most recent call last): File "/home/aconway/dispatch/tests/system_tests_management.py", line 461, in test_get_operations self.assertEqual(["READ"], result[LINK]) AssertionError: Lists differ: ['READ'] != [u'UPDATE', u'READ'] First differing element 0: READ UPDATE Second list contains 1 additional elements. First extra element 1: READ - ['READ'] + [u'UPDATE', u'READ'] == FAIL: test_query_attributes (system_tests_management.ManagementTest) Query with attributes only -- Traceback (most recent call last): File "/home/aconway/dispatch/tests/system_tests_management.py", line 151, in test_query_attributes self.assertTrue(r in response.results) AssertionError: False is not true == FAIL: test_query_type (system_tests_management.ManagementTest) Query with type only -- Traceback (most recent call last): File "/home/aconway/dispatch/tests/system_tests_management.py", line 132, in test_query_type set(['l0', 'l1', 'l2']) <= set(r['name'] for r in response.get_entities())) AssertionError: False is not true == FAIL: test_query_type_attributes (system_tests_management.ManagementTest) Query with type and attribute names -- Traceback (most recent call last): File "/home/aconway/dispatch/tests/system_tests_management.py", line 141, in test_query_type_attributes self.assertTrue(r in response.results) AssertionError: False is not true -- Ran 20 tests in 34.795s Thanks, Alan Conway
[jira] [Created] (DISPATCH-242) Add options to qdstat to display autoLinks and linkRoutes
Ted Ross created DISPATCH-242: - Summary: Add options to qdstat to display autoLinks and linkRoutes Key: DISPATCH-242 URL: https://issues.apache.org/jira/browse/DISPATCH-242 Project: Qpid Dispatch Issue Type: Improvement Components: Console Reporter: Ted Ross Fix For: 0.6 In 0.6, there will be a few new management entities that contain interesting monitoring data: autoLink and linkRoute. qdstat should be enhanced to display these entities. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7095) [Java Broker] Add meta data for context variables describing their usage
[ https://issues.apache.org/jira/browse/QPID-7095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15204037#comment-15204037 ] ASF subversion and git services commented on QPID-7095: --- Commit 1735943 from [~godfrer] in branch 'java/trunk' [ https://svn.apache.org/r1735943 ] QPID-7095 : Add ability to describe context variables usage through meta data > [Java Broker] Add meta data for context variables describing their usage > > > Key: QPID-7095 > URL: https://issues.apache.org/jira/browse/QPID-7095 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey > > Currently there is no way to discover which context variables are used by the > broker, and the description of what they do. We should add meta data > covering this and also provide this information through the dynamic API docs. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-7152) [Java Broker, Documentation] Add documentation for OAuth2 authentication
[
https://issues.apache.org/jira/browse/QPID-7152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall resolved QPID-7152.
--
Resolution: Fixed
Looks reasonable to me,
> [Java Broker, Documentation] Add documentation for OAuth2 authentication
>
>
> Key: QPID-7152
> URL: https://issues.apache.org/jira/browse/QPID-7152
> Project: Qpid
> Issue Type: Improvement
> Components: Documentation, Java Broker
>Reporter: Lorenz Quack
> Fix For: qpid-java-6.1
>
>
> We currently do not have documentation covering the OAuth2 Authentication-
> and GroupProviders.
> We do not need huge amounts of documentation and we certainly do not want to
> explain how OAuth2 works but it should be mentioned and some more specific
> things (e.g., the {{serviceToManagementGroupMapping}}) should be explained.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7152) [Java Broker, Documentation] Add documentation for OAuth2 authentication
[
https://issues.apache.org/jira/browse/QPID-7152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7152:
-
Fix Version/s: qpid-java-6.1
> [Java Broker, Documentation] Add documentation for OAuth2 authentication
>
>
> Key: QPID-7152
> URL: https://issues.apache.org/jira/browse/QPID-7152
> Project: Qpid
> Issue Type: Improvement
> Components: Documentation, Java Broker
>Reporter: Lorenz Quack
> Fix For: qpid-java-6.1
>
>
> We currently do not have documentation covering the OAuth2 Authentication-
> and GroupProviders.
> We do not need huge amounts of documentation and we certainly do not want to
> explain how OAuth2 works but it should be mentioned and some more specific
> things (e.g., the {{serviceToManagementGroupMapping}}) should be explained.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7152) [Java Broker, Documentation] Add documentation for OAuth2 authentication
[
https://issues.apache.org/jira/browse/QPID-7152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15203979#comment-15203979
]
ASF subversion and git services commented on QPID-7152:
---
Commit 1735938 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1735938 ]
QPID-7152: [Java Broker Documentation] Correct typo in new OAuth2 docs
> [Java Broker, Documentation] Add documentation for OAuth2 authentication
>
>
> Key: QPID-7152
> URL: https://issues.apache.org/jira/browse/QPID-7152
> Project: Qpid
> Issue Type: Improvement
> Components: Documentation, Java Broker
>Reporter: Lorenz Quack
>
> We currently do not have documentation covering the OAuth2 Authentication-
> and GroupProviders.
> We do not need huge amounts of documentation and we certainly do not want to
> explain how OAuth2 works but it should be mentioned and some more specific
> things (e.g., the {{serviceToManagementGroupMapping}}) should be explained.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
