o.a.q.s.m.p.ManagementException) - Unexpected Exception - Qpid 7.1.3
Hi, In management console when I click on Dashboard and then on browse then below WARN logged? Can I know why this happening on ONLY one server? 2019-07-15 09:23:18,626 WARN [qtp2103783970-291] (o.a.q.s.m.p.ManagementException) - Unexpected Exception 2019-07-15 09:24:09,734 WARN [qtp2103783970-167] (o.a.q.s.m.p.ManagementException) - Unexpected Exception 2019-07-15 09:24:21,724 WARN [qtp2103783970-287] (o.a.q.s.m.p.ManagementException) - IllegalArgumentException processing request /api/v7.1/virtualhost/RCO_1_FIX_VHN/FIX_VHNG/userpreferences/X-Dashboard from user '/10.20.9.117:61272/readonly-all/support': Preference 'FIX Dash' of type 'X-Dashboard' already exists Thanks, Balanna Nadikude Notice: All email and instant messages (including attachments) sent to or from Franklin Templeton Investments (FTI) personnel may be retained, monitored and/or reviewed by FTI and its agents, or authorized law enforcement personnel, without further notice or consent. Under new Data Protection regulations in Europe your personal information may be subject to our EU specific Privacy & Cookies Notice which you can read here, regardless of where the information originates. Depending on your location, other privacy laws and regulations may also apply to you. Please reference http://www.franklintempletonglobal.com/privacy .
Re: o.a.q.s.m.p.ManagementException) - Unexpected Exception - Qpid 7.1.3
Hi Balanna, This warning is reported when someone is trying to save a dashboard under the same name as existing one. For example, you can clone the dashboard and try to save cloned one using the same name as original dashboard. It should not happen whilst browsing. Kind Regards, Alex On Mon, 15 Jul 2019 at 17:23, Nadikude, Balanna < balanna.nadik...@franklintempleton.com> wrote: > Hi, > > In management console when I click on Dashboard and then on browse then > below WARN logged? Can I know why this happening on ONLY one server? > > > > 2019-07-15 09:23:18,626 WARN [qtp2103783970-291] > (o.a.q.s.m.p.ManagementException) - Unexpected Exception > > > > 2019-07-15 09:24:09,734 WARN [qtp2103783970-167] > (o.a.q.s.m.p.ManagementException) - Unexpected Exception > > > > 2019-07-15 09:24:21,724 WARN [qtp2103783970-287] > (o.a.q.s.m.p.ManagementException) - IllegalArgumentException processing > request > /api/v7.1/virtualhost/RCO_1_FIX_VHN/FIX_VHNG/userpreferences/X-Dashboard > from user '/10.20.9.117:61272/readonly-all/support': Preference 'FIX > Dash' of type 'X-Dashboard' already exists > > > > Thanks, > Balanna Nadikude > > Notice: All email and instant messages (including attachments) sent to or > from Franklin Templeton Investments (FTI) personnel may be retained, > monitored and/or reviewed by FTI and its agents, or authorized law > enforcement personnel, without further notice or consent. > > Under new Data Protection regulations in Europe your personal information > may be subject to our EU specific Privacy & Cookies Notice which you can > read here, regardless of where the information originates. Depending on > your location, other privacy laws and regulations may also apply to you. > Please reference http://www.franklintempletonglobal.com/privacy > > . >
[GitHub] [qpid-dispatch] ChugR commented on a change in pull request #527: DISPATCH-1374 - Added qdstat options --all-routers and --all-entities
ChugR commented on a change in pull request #527: DISPATCH-1374 - Added qdstat
options --all-routers and --all-entities
URL: https://github.com/apache/qpid-dispatch/pull/527#discussion_r303567508
##
File path: tools/qdstat.in
##
@@ -57,23 +58,31 @@ def parse_args(argv):
parser.add_option("-m", "--memory", help="Show Router Memory Stats",
action="store_const", const="m", dest="show")
parser.add_option("--autolinks", help="Show Auto Links",
action="store_const", const="autolinks", dest="show")
parser.add_option("--linkroutes", help="Show Link Routes",
action="store_const", const="linkroutes", dest="show")
+
+parser.add_option("--all-routers", help="Show entities for all routers in
network. Can also be used in combination with other options",
action="store_const", const="all_routers", dest="all_routers")
+parser.add_option("--all-entities", help="Show all router entities. Can be
combined with --all-routers option", action="store_const",
const="all_entities", dest="all_entities")
+
parser.add_option("-v", "--verbose", help="Show maximum detail",
action="store_true", dest="verbose")
parser.add_option("--log", help="Show recent log entries",
action="store_const", const="log", dest="show")
# This limit can be used to limit the number of output rows and
# can be used in conjunction with options
# like -c, -l, -a, --autolinks, --linkroutes and --log.
# By default, the limit is not set, which means the limit is unlimited.
-
parser.add_option("--limit", help="Limit number of output rows",
type="int", default=None)
opts, args = parser.parse_args(args=argv)
-if not opts.show:
-parser.error("You must specify one of these options: -g, -c, -l, -n,
-a, -m, -h, --autolinks, --linkroutes, or --log.")
+if opts.router and opts.all_routers:
+parser.error("--all-routers cannot be combined with single router
option -r " + opts.router)
-return opts, args
+if opts.all_entities and opts.show:
+ parser.error("--all-entities cannot be combined with specific
entity option -" + opts.show)
+
+if not opts.all_routers and not opts.all_entities and not opts.show:
+parser.error("You must specify one of these options: -g, -c, -l, -n,
-a, -m, -h, --autolinks, --linkroutes, --all-routers, --all-entities or --log.")
Review comment:
The new --all-entities switch would make a great default in the event of no
other option.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1374) Add qdstat options --all-routers and all-entities which display statistics of all routers and displays all entities
[
https://issues.apache.org/jira/browse/DISPATCH-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885466#comment-16885466
]
ASF GitHub Bot commented on DISPATCH-1374:
--
ChugR commented on pull request #527: DISPATCH-1374 - Added qdstat options
--all-routers and --all-entities
URL: https://github.com/apache/qpid-dispatch/pull/527#discussion_r303567508
##
File path: tools/qdstat.in
##
@@ -57,23 +58,31 @@ def parse_args(argv):
parser.add_option("-m", "--memory", help="Show Router Memory Stats",
action="store_const", const="m", dest="show")
parser.add_option("--autolinks", help="Show Auto Links",
action="store_const", const="autolinks", dest="show")
parser.add_option("--linkroutes", help="Show Link Routes",
action="store_const", const="linkroutes", dest="show")
+
+parser.add_option("--all-routers", help="Show entities for all routers in
network. Can also be used in combination with other options",
action="store_const", const="all_routers", dest="all_routers")
+parser.add_option("--all-entities", help="Show all router entities. Can be
combined with --all-routers option", action="store_const",
const="all_entities", dest="all_entities")
+
parser.add_option("-v", "--verbose", help="Show maximum detail",
action="store_true", dest="verbose")
parser.add_option("--log", help="Show recent log entries",
action="store_const", const="log", dest="show")
# This limit can be used to limit the number of output rows and
# can be used in conjunction with options
# like -c, -l, -a, --autolinks, --linkroutes and --log.
# By default, the limit is not set, which means the limit is unlimited.
-
parser.add_option("--limit", help="Limit number of output rows",
type="int", default=None)
opts, args = parser.parse_args(args=argv)
-if not opts.show:
-parser.error("You must specify one of these options: -g, -c, -l, -n,
-a, -m, -h, --autolinks, --linkroutes, or --log.")
+if opts.router and opts.all_routers:
+parser.error("--all-routers cannot be combined with single router
option -r " + opts.router)
-return opts, args
+if opts.all_entities and opts.show:
+ parser.error("--all-entities cannot be combined with specific
entity option -" + opts.show)
+
+if not opts.all_routers and not opts.all_entities and not opts.show:
+parser.error("You must specify one of these options: -g, -c, -l, -n,
-a, -m, -h, --autolinks, --linkroutes, --all-routers, --all-entities or --log.")
Review comment:
The new --all-entities switch would make a great default in the event of no
other option.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add qdstat options --all-routers and all-entities which display statistics of
> all routers and displays all entities
> ---
>
> Key: DISPATCH-1374
> URL: https://issues.apache.org/jira/browse/DISPATCH-1374
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
>Affects Versions: 1.7.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.9.0
>
>
> # Introduce two new command line options to qdstat called --all-routers and
> --all-entities
> # qdstat --all-routers - Is the same as - qdstat --all-routers
> --all-entities.
> ## Will display information on all entities from all interior routers if the
> qdstat client connects to an interior router.
> ## Will display information on all entities from only that edge router if
> the qdstat client connects to an edge router
> # qdstat --all-entities
> ## Will display information on all entities from only that interior or edge
> router that the qdstat client is connecting to.
> # qdstat --all-entities -c
> ## Error. Cannot ask for all entities and also specifically ask for
> connection entity ?
> # qdstat -c
> ## As usual, just display connections in the router that the qdstat client
> is connecting to
> # qdstat -c --all-routers
> ## Will display connection information for all interior routers in the
> network if the qdstat client is connected to an interior router
> ## Will display connection information for only that edge router if the
> qdstat client is connected to and edge router.
> # qdstat --all-entities --all-routers
> ## Same as qdstat --all-routers (see #2)
> # General stuff
> # Include date timestamp when
[GitHub] [qpid-dispatch] ganeshmurthy commented on a change in pull request #527: DISPATCH-1374 - Added qdstat options --all-routers and --all-entities
ganeshmurthy commented on a change in pull request #527: DISPATCH-1374 - Added
qdstat options --all-routers and --all-entities
URL: https://github.com/apache/qpid-dispatch/pull/527#discussion_r303569285
##
File path: tools/qdstat.in
##
@@ -57,23 +58,31 @@ def parse_args(argv):
parser.add_option("-m", "--memory", help="Show Router Memory Stats",
action="store_const", const="m", dest="show")
parser.add_option("--autolinks", help="Show Auto Links",
action="store_const", const="autolinks", dest="show")
parser.add_option("--linkroutes", help="Show Link Routes",
action="store_const", const="linkroutes", dest="show")
+
+parser.add_option("--all-routers", help="Show entities for all routers in
network. Can also be used in combination with other options",
action="store_const", const="all_routers", dest="all_routers")
+parser.add_option("--all-entities", help="Show all router entities. Can be
combined with --all-routers option", action="store_const",
const="all_entities", dest="all_entities")
+
parser.add_option("-v", "--verbose", help="Show maximum detail",
action="store_true", dest="verbose")
parser.add_option("--log", help="Show recent log entries",
action="store_const", const="log", dest="show")
# This limit can be used to limit the number of output rows and
# can be used in conjunction with options
# like -c, -l, -a, --autolinks, --linkroutes and --log.
# By default, the limit is not set, which means the limit is unlimited.
-
parser.add_option("--limit", help="Limit number of output rows",
type="int", default=None)
opts, args = parser.parse_args(args=argv)
-if not opts.show:
-parser.error("You must specify one of these options: -g, -c, -l, -n,
-a, -m, -h, --autolinks, --linkroutes, or --log.")
+if opts.router and opts.all_routers:
+parser.error("--all-routers cannot be combined with single router
option -r " + opts.router)
-return opts, args
+if opts.all_entities and opts.show:
+ parser.error("--all-entities cannot be combined with specific
entity option -" + opts.show)
+
+if not opts.all_routers and not opts.all_entities and not opts.show:
+parser.error("You must specify one of these options: -g, -c, -l, -n,
-a, -m, -h, --autolinks, --linkroutes, --all-routers, --all-entities or --log.")
Review comment:
@ChugR Hi Chuck, You mean to say that if people just type qdstat (without
ANY options) then it should default to qdstat --all-entities?
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1374) Add qdstat options --all-routers and all-entities which display statistics of all routers and displays all entities
[
https://issues.apache.org/jira/browse/DISPATCH-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885470#comment-16885470
]
ASF GitHub Bot commented on DISPATCH-1374:
--
ganeshmurthy commented on pull request #527: DISPATCH-1374 - Added qdstat
options --all-routers and --all-entities
URL: https://github.com/apache/qpid-dispatch/pull/527#discussion_r303569285
##
File path: tools/qdstat.in
##
@@ -57,23 +58,31 @@ def parse_args(argv):
parser.add_option("-m", "--memory", help="Show Router Memory Stats",
action="store_const", const="m", dest="show")
parser.add_option("--autolinks", help="Show Auto Links",
action="store_const", const="autolinks", dest="show")
parser.add_option("--linkroutes", help="Show Link Routes",
action="store_const", const="linkroutes", dest="show")
+
+parser.add_option("--all-routers", help="Show entities for all routers in
network. Can also be used in combination with other options",
action="store_const", const="all_routers", dest="all_routers")
+parser.add_option("--all-entities", help="Show all router entities. Can be
combined with --all-routers option", action="store_const",
const="all_entities", dest="all_entities")
+
parser.add_option("-v", "--verbose", help="Show maximum detail",
action="store_true", dest="verbose")
parser.add_option("--log", help="Show recent log entries",
action="store_const", const="log", dest="show")
# This limit can be used to limit the number of output rows and
# can be used in conjunction with options
# like -c, -l, -a, --autolinks, --linkroutes and --log.
# By default, the limit is not set, which means the limit is unlimited.
-
parser.add_option("--limit", help="Limit number of output rows",
type="int", default=None)
opts, args = parser.parse_args(args=argv)
-if not opts.show:
-parser.error("You must specify one of these options: -g, -c, -l, -n,
-a, -m, -h, --autolinks, --linkroutes, or --log.")
+if opts.router and opts.all_routers:
+parser.error("--all-routers cannot be combined with single router
option -r " + opts.router)
-return opts, args
+if opts.all_entities and opts.show:
+ parser.error("--all-entities cannot be combined with specific
entity option -" + opts.show)
+
+if not opts.all_routers and not opts.all_entities and not opts.show:
+parser.error("You must specify one of these options: -g, -c, -l, -n,
-a, -m, -h, --autolinks, --linkroutes, --all-routers, --all-entities or --log.")
Review comment:
@ChugR Hi Chuck, You mean to say that if people just type qdstat (without
ANY options) then it should default to qdstat --all-entities?
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add qdstat options --all-routers and all-entities which display statistics of
> all routers and displays all entities
> ---
>
> Key: DISPATCH-1374
> URL: https://issues.apache.org/jira/browse/DISPATCH-1374
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
>Affects Versions: 1.7.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.9.0
>
>
> # Introduce two new command line options to qdstat called --all-routers and
> --all-entities
> # qdstat --all-routers - Is the same as - qdstat --all-routers
> --all-entities.
> ## Will display information on all entities from all interior routers if the
> qdstat client connects to an interior router.
> ## Will display information on all entities from only that edge router if
> the qdstat client connects to an edge router
> # qdstat --all-entities
> ## Will display information on all entities from only that interior or edge
> router that the qdstat client is connecting to.
> # qdstat --all-entities -c
> ## Error. Cannot ask for all entities and also specifically ask for
> connection entity ?
> # qdstat -c
> ## As usual, just display connections in the router that the qdstat client
> is connecting to
> # qdstat -c --all-routers
> ## Will display connection information for all interior routers in the
> network if the qdstat client is connected to an interior router
> ## Will display connection information for only that edge router if the
> qdstat client is connected to and edge router.
> # qdstat --all-entities --all-routers
> ## Same as qdstat --all-routers (see #2
[jira] [Commented] (DISPATCH-1374) Add qdstat options --all-routers and all-entities which display statistics of all routers and displays all entities
[ https://issues.apache.org/jira/browse/DISPATCH-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885484#comment-16885484 ] ASF GitHub Bot commented on DISPATCH-1374: -- ChugR commented on issue #527: DISPATCH-1374 - Added qdstat options --all-routers and --all-entities URL: https://github.com/apache/qpid-dispatch/pull/527#issuecomment-511516590 This is a great addition. I made a half-hearted suggestion to change the default qdstat command to be --all-entities. It's better than the error message and it's usually what most people would like to see anyway. I suggested changing the text of the line that shows the router name to be different from the text of lines that show data fields. This is not a show stopper and I approve of this commit either way. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add qdstat options --all-routers and all-entities which display statistics of > all routers and displays all entities > --- > > Key: DISPATCH-1374 > URL: https://issues.apache.org/jira/browse/DISPATCH-1374 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Container >Affects Versions: 1.7.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.9.0 > > > # Introduce two new command line options to qdstat called --all-routers and > --all-entities > # qdstat --all-routers - Is the same as - qdstat --all-routers > --all-entities. > ## Will display information on all entities from all interior routers if the > qdstat client connects to an interior router. > ## Will display information on all entities from only that edge router if > the qdstat client connects to an edge router > # qdstat --all-entities > ## Will display information on all entities from only that interior or edge > router that the qdstat client is connecting to. > # qdstat --all-entities -c > ## Error. Cannot ask for all entities and also specifically ask for > connection entity ? > # qdstat -c > ## As usual, just display connections in the router that the qdstat client > is connecting to > # qdstat -c --all-routers > ## Will display connection information for all interior routers in the > network if the qdstat client is connected to an interior router > ## Will display connection information for only that edge router if the > qdstat client is connected to and edge router. > # qdstat --all-entities --all-routers > ## Same as qdstat --all-routers (see #2) > # General stuff > # Include date timestamp when the dump was taken > # Display in stdout just like other qdstat options > # Aggregated output must consist of distinct sections which pertain to each > router and should be preceded by the router id for easy identification -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] ChugR commented on issue #527: DISPATCH-1374 - Added qdstat options --all-routers and --all-entities
ChugR commented on issue #527: DISPATCH-1374 - Added qdstat options --all-routers and --all-entities URL: https://github.com/apache/qpid-dispatch/pull/527#issuecomment-511516590 This is a great addition. I made a half-hearted suggestion to change the default qdstat command to be --all-entities. It's better than the error message and it's usually what most people would like to see anyway. I suggested changing the text of the line that shows the router name to be different from the text of lines that show data fields. This is not a show stopper and I approve of this commit either way. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] bhardesty opened a new pull request #536: NO-JIRA: Change name of kill button to close
bhardesty opened a new pull request #536: NO-JIRA: Change name of kill button to close URL: https://github.com/apache/qpid-dispatch/pull/536 The name of the console button to close a connection changed from "Kill" to "Close". Updated the doc to reflect this change. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] ted-ross commented on a change in pull request #532: DISPATCH-1381: Create procedure for handling undeliverable messages
ted-ross commented on a change in pull request #532: DISPATCH-1381: Create
procedure for handling undeliverable messages
URL: https://github.com/apache/qpid-dispatch/pull/532#discussion_r303589676
##
File path: docs/books/user-guide/routing.adoc
##
@@ -551,6 +551,87 @@ autoLink {
For information about additional attributes, see
link:{qdrouterdConfManPageUrl}#_autolink[autoLink] in the `qdrouterd.conf` man
page.
--
+=== Handling Undeliverable Messages for an Address
+
+You handle undeliverable messages for an address by configuring _fallback
destinations_.
+A fallback destination is a queue on a broker that stores messages that are
not directly routable to any consumers.
+
+During normal message delivery,
+{RouterName} delivers messages to the consumers that are attached to the
router network.
+However, if no consumers are reachable,
+the messages are diverted to any fallback destinations that were configured
for the address.
Review comment:
... any fallback destinations that are attached for the address...
It's possible that the auto-links are inactive, in which case messages
aren't delivered anywhere. Also, it is possible for a fallback destination to
attach by itself (using the qd.fallback capability) without using an auto-link.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1381) Create documentation for configuring fallback destinations
[
https://issues.apache.org/jira/browse/DISPATCH-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885527#comment-16885527
]
ASF GitHub Bot commented on DISPATCH-1381:
--
ted-ross commented on pull request #532: DISPATCH-1381: Create procedure for
handling undeliverable messages
URL: https://github.com/apache/qpid-dispatch/pull/532#discussion_r303589676
##
File path: docs/books/user-guide/routing.adoc
##
@@ -551,6 +551,87 @@ autoLink {
For information about additional attributes, see
link:{qdrouterdConfManPageUrl}#_autolink[autoLink] in the `qdrouterd.conf` man
page.
--
+=== Handling Undeliverable Messages for an Address
+
+You handle undeliverable messages for an address by configuring _fallback
destinations_.
+A fallback destination is a queue on a broker that stores messages that are
not directly routable to any consumers.
+
+During normal message delivery,
+{RouterName} delivers messages to the consumers that are attached to the
router network.
+However, if no consumers are reachable,
+the messages are diverted to any fallback destinations that were configured
for the address.
Review comment:
... any fallback destinations that are attached for the address...
It's possible that the auto-links are inactive, in which case messages
aren't delivered anywhere. Also, it is possible for a fallback destination to
attach by itself (using the qd.fallback capability) without using an auto-link.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Create documentation for configuring fallback destinations
> --
>
> Key: DISPATCH-1381
> URL: https://issues.apache.org/jira/browse/DISPATCH-1381
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Documentation
>Reporter: Ben Hardesty
>Priority: Major
>
> The Dispatch Router documentation should be updated to describe how to
> configure fallback destinations for an address (DISPATCH-1337).
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] ted-ross commented on a change in pull request #532: DISPATCH-1381: Create procedure for handling undeliverable messages
ted-ross commented on a change in pull request #532: DISPATCH-1381: Create
procedure for handling undeliverable messages
URL: https://github.com/apache/qpid-dispatch/pull/532#discussion_r303590310
##
File path: docs/books/user-guide/routing.adoc
##
@@ -551,6 +551,87 @@ autoLink {
For information about additional attributes, see
link:{qdrouterdConfManPageUrl}#_autolink[autoLink] in the `qdrouterd.conf` man
page.
--
+=== Handling Undeliverable Messages for an Address
+
+You handle undeliverable messages for an address by configuring _fallback
destinations_.
+A fallback destination is a queue on a broker that stores messages that are
not directly routable to any consumers.
+
+During normal message delivery,
+{RouterName} delivers messages to the consumers that are attached to the
router network.
+However, if no consumers are reachable,
+the messages are diverted to any fallback destinations that were configured
for the address.
+When a consumer reconnects and becomes reachable again,
+it receives the messages stored at the fallback destination.
+
+[NOTE]
+
+{RouterName} does not preserve delivery order for messages stored at a
fallback destination. When a consumer reconnects, it will receive the stored
messages interleaved with any new messages sent by producers.
Review comment:
To be more accurate: message delivery is preserved in the queue and the
queue will deliver those messages in the same order in which they were
received. However, new messages produced while the queue is draining will be
interleaved with the draining messages.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1381) Create documentation for configuring fallback destinations
[
https://issues.apache.org/jira/browse/DISPATCH-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885529#comment-16885529
]
ASF GitHub Bot commented on DISPATCH-1381:
--
ted-ross commented on pull request #532: DISPATCH-1381: Create procedure for
handling undeliverable messages
URL: https://github.com/apache/qpid-dispatch/pull/532#discussion_r303590310
##
File path: docs/books/user-guide/routing.adoc
##
@@ -551,6 +551,87 @@ autoLink {
For information about additional attributes, see
link:{qdrouterdConfManPageUrl}#_autolink[autoLink] in the `qdrouterd.conf` man
page.
--
+=== Handling Undeliverable Messages for an Address
+
+You handle undeliverable messages for an address by configuring _fallback
destinations_.
+A fallback destination is a queue on a broker that stores messages that are
not directly routable to any consumers.
+
+During normal message delivery,
+{RouterName} delivers messages to the consumers that are attached to the
router network.
+However, if no consumers are reachable,
+the messages are diverted to any fallback destinations that were configured
for the address.
+When a consumer reconnects and becomes reachable again,
+it receives the messages stored at the fallback destination.
+
+[NOTE]
+
+{RouterName} does not preserve delivery order for messages stored at a
fallback destination. When a consumer reconnects, it will receive the stored
messages interleaved with any new messages sent by producers.
Review comment:
To be more accurate: message delivery is preserved in the queue and the
queue will deliver those messages in the same order in which they were
received. However, new messages produced while the queue is draining will be
interleaved with the draining messages.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Create documentation for configuring fallback destinations
> --
>
> Key: DISPATCH-1381
> URL: https://issues.apache.org/jira/browse/DISPATCH-1381
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Documentation
>Reporter: Ben Hardesty
>Priority: Major
>
> The Dispatch Router documentation should be updated to describe how to
> configure fallback destinations for an address (DISPATCH-1337).
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] ted-ross commented on a change in pull request #532: DISPATCH-1381: Create procedure for handling undeliverable messages
ted-ross commented on a change in pull request #532: DISPATCH-1381: Create
procedure for handling undeliverable messages
URL: https://github.com/apache/qpid-dispatch/pull/532#discussion_r303591010
##
File path: docs/books/user-guide/routing.adoc
##
@@ -551,6 +551,87 @@ autoLink {
For information about additional attributes, see
link:{qdrouterdConfManPageUrl}#_autolink[autoLink] in the `qdrouterd.conf` man
page.
--
+=== Handling Undeliverable Messages for an Address
+
+You handle undeliverable messages for an address by configuring _fallback
destinations_.
+A fallback destination is a queue on a broker that stores messages that are
not directly routable to any consumers.
Review comment:
This is probably the most common use for fallback-destination. However,
there is no reason that the fallback destination must be a queue on a broker.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1381) Create documentation for configuring fallback destinations
[
https://issues.apache.org/jira/browse/DISPATCH-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885530#comment-16885530
]
ASF GitHub Bot commented on DISPATCH-1381:
--
ted-ross commented on pull request #532: DISPATCH-1381: Create procedure for
handling undeliverable messages
URL: https://github.com/apache/qpid-dispatch/pull/532#discussion_r303591010
##
File path: docs/books/user-guide/routing.adoc
##
@@ -551,6 +551,87 @@ autoLink {
For information about additional attributes, see
link:{qdrouterdConfManPageUrl}#_autolink[autoLink] in the `qdrouterd.conf` man
page.
--
+=== Handling Undeliverable Messages for an Address
+
+You handle undeliverable messages for an address by configuring _fallback
destinations_.
+A fallback destination is a queue on a broker that stores messages that are
not directly routable to any consumers.
Review comment:
This is probably the most common use for fallback-destination. However,
there is no reason that the fallback destination must be a queue on a broker.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Create documentation for configuring fallback destinations
> --
>
> Key: DISPATCH-1381
> URL: https://issues.apache.org/jira/browse/DISPATCH-1381
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Documentation
>Reporter: Ben Hardesty
>Priority: Major
>
> The Dispatch Router documentation should be updated to describe how to
> configure fallback destinations for an address (DISPATCH-1337).
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] ted-ross commented on a change in pull request #532: DISPATCH-1381: Create procedure for handling undeliverable messages
ted-ross commented on a change in pull request #532: DISPATCH-1381: Create
procedure for handling undeliverable messages
URL: https://github.com/apache/qpid-dispatch/pull/532#discussion_r303592075
##
File path: docs/books/user-guide/routing.adoc
##
@@ -551,6 +551,87 @@ autoLink {
For information about additional attributes, see
link:{qdrouterdConfManPageUrl}#_autolink[autoLink] in the `qdrouterd.conf` man
page.
--
+=== Handling Undeliverable Messages for an Address
+
+You handle undeliverable messages for an address by configuring _fallback
destinations_.
+A fallback destination is a queue on a broker that stores messages that are
not directly routable to any consumers.
+
+During normal message delivery,
+{RouterName} delivers messages to the consumers that are attached to the
router network.
+However, if no consumers are reachable,
+the messages are diverted to any fallback destinations that were configured
for the address.
+When a consumer reconnects and becomes reachable again,
+it receives the messages stored at the fallback destination.
+
+[NOTE]
+
+{RouterName} does not preserve delivery order for messages stored at a
fallback destination. When a consumer reconnects, it will receive the stored
messages interleaved with any new messages sent by producers.
+
+
+.Prerequisites
+
+* The router is connected to a broker.
++
+For more information, see xref:connecting-to-external-amqp-containers-router[].
+
+.Procedure
+
+This procedure enables fallback for an address
+and configures autolinks to connect to the broker queue
+that provides the fallback destination for the address.
+
+. Enable fallback destinations for the address.
++
+[options="nowrap",subs="+quotes"]
+
+address {
+prefix: my-address
+enableFallback: yes
+}
+
+
+. Add an _outgoing_ autolink to a queue on the broker.
++
+--
+For the address for which you enabled fallback,
+if messages are not routable to any consumers,
+the router will use this autolink to send the messages to a queue on the
broker.
+
+[options="nowrap",subs="+quotes"]
+
+autoLink {
+address: my-address.2
+direction: out
+connection: my-broker
+fallback: yes
+}
+
+--
+
+. If you want the router to send queued messages to attached consumers as soon
as they connect to the router network,
+add an _incoming_ autolink.
++
+--
+As soon as a consumer attaches to the router,
+it will receive the messages stored in the broker queue,
+along with any new messages sent by the producer.
+However, the original delivery order of the queued messages is not preserved;
the queued messages will be interleaved with the new messages.
Review comment:
The original delivery order of the queued messages _is_ preserved. New
messages produced during queue-draining are not run through the queue, they are
sent directly to the consumers, interleaved with the draining messages.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1381) Create documentation for configuring fallback destinations
[
https://issues.apache.org/jira/browse/DISPATCH-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885533#comment-16885533
]
ASF GitHub Bot commented on DISPATCH-1381:
--
ted-ross commented on pull request #532: DISPATCH-1381: Create procedure for
handling undeliverable messages
URL: https://github.com/apache/qpid-dispatch/pull/532#discussion_r303592075
##
File path: docs/books/user-guide/routing.adoc
##
@@ -551,6 +551,87 @@ autoLink {
For information about additional attributes, see
link:{qdrouterdConfManPageUrl}#_autolink[autoLink] in the `qdrouterd.conf` man
page.
--
+=== Handling Undeliverable Messages for an Address
+
+You handle undeliverable messages for an address by configuring _fallback
destinations_.
+A fallback destination is a queue on a broker that stores messages that are
not directly routable to any consumers.
+
+During normal message delivery,
+{RouterName} delivers messages to the consumers that are attached to the
router network.
+However, if no consumers are reachable,
+the messages are diverted to any fallback destinations that were configured
for the address.
+When a consumer reconnects and becomes reachable again,
+it receives the messages stored at the fallback destination.
+
+[NOTE]
+
+{RouterName} does not preserve delivery order for messages stored at a
fallback destination. When a consumer reconnects, it will receive the stored
messages interleaved with any new messages sent by producers.
+
+
+.Prerequisites
+
+* The router is connected to a broker.
++
+For more information, see xref:connecting-to-external-amqp-containers-router[].
+
+.Procedure
+
+This procedure enables fallback for an address
+and configures autolinks to connect to the broker queue
+that provides the fallback destination for the address.
+
+. Enable fallback destinations for the address.
++
+[options="nowrap",subs="+quotes"]
+
+address {
+prefix: my-address
+enableFallback: yes
+}
+
+
+. Add an _outgoing_ autolink to a queue on the broker.
++
+--
+For the address for which you enabled fallback,
+if messages are not routable to any consumers,
+the router will use this autolink to send the messages to a queue on the
broker.
+
+[options="nowrap",subs="+quotes"]
+
+autoLink {
+address: my-address.2
+direction: out
+connection: my-broker
+fallback: yes
+}
+
+--
+
+. If you want the router to send queued messages to attached consumers as soon
as they connect to the router network,
+add an _incoming_ autolink.
++
+--
+As soon as a consumer attaches to the router,
+it will receive the messages stored in the broker queue,
+along with any new messages sent by the producer.
+However, the original delivery order of the queued messages is not preserved;
the queued messages will be interleaved with the new messages.
Review comment:
The original delivery order of the queued messages _is_ preserved. New
messages produced during queue-draining are not run through the queue, they are
sent directly to the consumers, interleaved with the draining messages.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Create documentation for configuring fallback destinations
> --
>
> Key: DISPATCH-1381
> URL: https://issues.apache.org/jira/browse/DISPATCH-1381
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Documentation
>Reporter: Ben Hardesty
>Priority: Major
>
> The Dispatch Router documentation should be updated to describe how to
> configure fallback destinations for an address (DISPATCH-1337).
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] ted-ross commented on a change in pull request #532: DISPATCH-1381: Create procedure for handling undeliverable messages
ted-ross commented on a change in pull request #532: DISPATCH-1381: Create
procedure for handling undeliverable messages
URL: https://github.com/apache/qpid-dispatch/pull/532#discussion_r303592407
##
File path: docs/books/user-guide/routing.adoc
##
@@ -551,6 +551,87 @@ autoLink {
For information about additional attributes, see
link:{qdrouterdConfManPageUrl}#_autolink[autoLink] in the `qdrouterd.conf` man
page.
--
+=== Handling Undeliverable Messages for an Address
+
+You handle undeliverable messages for an address by configuring _fallback
destinations_.
+A fallback destination is a queue on a broker that stores messages that are
not directly routable to any consumers.
+
+During normal message delivery,
+{RouterName} delivers messages to the consumers that are attached to the
router network.
+However, if no consumers are reachable,
+the messages are diverted to any fallback destinations that were configured
for the address.
+When a consumer reconnects and becomes reachable again,
+it receives the messages stored at the fallback destination.
+
+[NOTE]
+
+{RouterName} does not preserve delivery order for messages stored at a
fallback destination. When a consumer reconnects, it will receive the stored
messages interleaved with any new messages sent by producers.
+
+
+.Prerequisites
+
+* The router is connected to a broker.
++
+For more information, see xref:connecting-to-external-amqp-containers-router[].
+
+.Procedure
+
+This procedure enables fallback for an address
+and configures autolinks to connect to the broker queue
+that provides the fallback destination for the address.
+
+. Enable fallback destinations for the address.
++
+[options="nowrap",subs="+quotes"]
+
+address {
+prefix: my-address
+enableFallback: yes
+}
+
+
+. Add an _outgoing_ autolink to a queue on the broker.
++
+--
+For the address for which you enabled fallback,
+if messages are not routable to any consumers,
+the router will use this autolink to send the messages to a queue on the
broker.
+
+[options="nowrap",subs="+quotes"]
+
+autoLink {
+address: my-address.2
+direction: out
+connection: my-broker
+fallback: yes
+}
+
+--
+
+. If you want the router to send queued messages to attached consumers as soon
as they connect to the router network,
+add an _incoming_ autolink.
++
+--
+As soon as a consumer attaches to the router,
+it will receive the messages stored in the broker queue,
+along with any new messages sent by the producer.
+However, the original delivery order of the queued messages is not preserved;
the queued messages will be interleaved with the new messages.
+
+If you do not add the incoming autolink,
+the messages will be stored on the broker,
+but will not be automatically sent to consumers when they attach to the router.
Review comment:
I would delete "automatically" as it's not adding any valuable meaning.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1381) Create documentation for configuring fallback destinations
[
https://issues.apache.org/jira/browse/DISPATCH-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885536#comment-16885536
]
ASF GitHub Bot commented on DISPATCH-1381:
--
ted-ross commented on pull request #532: DISPATCH-1381: Create procedure for
handling undeliverable messages
URL: https://github.com/apache/qpid-dispatch/pull/532#discussion_r303592407
##
File path: docs/books/user-guide/routing.adoc
##
@@ -551,6 +551,87 @@ autoLink {
For information about additional attributes, see
link:{qdrouterdConfManPageUrl}#_autolink[autoLink] in the `qdrouterd.conf` man
page.
--
+=== Handling Undeliverable Messages for an Address
+
+You handle undeliverable messages for an address by configuring _fallback
destinations_.
+A fallback destination is a queue on a broker that stores messages that are
not directly routable to any consumers.
+
+During normal message delivery,
+{RouterName} delivers messages to the consumers that are attached to the
router network.
+However, if no consumers are reachable,
+the messages are diverted to any fallback destinations that were configured
for the address.
+When a consumer reconnects and becomes reachable again,
+it receives the messages stored at the fallback destination.
+
+[NOTE]
+
+{RouterName} does not preserve delivery order for messages stored at a
fallback destination. When a consumer reconnects, it will receive the stored
messages interleaved with any new messages sent by producers.
+
+
+.Prerequisites
+
+* The router is connected to a broker.
++
+For more information, see xref:connecting-to-external-amqp-containers-router[].
+
+.Procedure
+
+This procedure enables fallback for an address
+and configures autolinks to connect to the broker queue
+that provides the fallback destination for the address.
+
+. Enable fallback destinations for the address.
++
+[options="nowrap",subs="+quotes"]
+
+address {
+prefix: my-address
+enableFallback: yes
+}
+
+
+. Add an _outgoing_ autolink to a queue on the broker.
++
+--
+For the address for which you enabled fallback,
+if messages are not routable to any consumers,
+the router will use this autolink to send the messages to a queue on the
broker.
+
+[options="nowrap",subs="+quotes"]
+
+autoLink {
+address: my-address.2
+direction: out
+connection: my-broker
+fallback: yes
+}
+
+--
+
+. If you want the router to send queued messages to attached consumers as soon
as they connect to the router network,
+add an _incoming_ autolink.
++
+--
+As soon as a consumer attaches to the router,
+it will receive the messages stored in the broker queue,
+along with any new messages sent by the producer.
+However, the original delivery order of the queued messages is not preserved;
the queued messages will be interleaved with the new messages.
+
+If you do not add the incoming autolink,
+the messages will be stored on the broker,
+but will not be automatically sent to consumers when they attach to the router.
Review comment:
I would delete "automatically" as it's not adding any valuable meaning.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Create documentation for configuring fallback destinations
> --
>
> Key: DISPATCH-1381
> URL: https://issues.apache.org/jira/browse/DISPATCH-1381
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Documentation
>Reporter: Ben Hardesty
>Priority: Major
>
> The Dispatch Router documentation should be updated to describe how to
> configure fallback destinations for an address (DISPATCH-1337).
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] codecov-io edited a comment on issue #532: DISPATCH-1381: Create procedure for handling undeliverable messages
codecov-io edited a comment on issue #532: DISPATCH-1381: Create procedure for handling undeliverable messages URL: https://github.com/apache/qpid-dispatch/pull/532#issuecomment-508257756 # [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/532?src=pr&el=h1) Report > Merging [#532](https://codecov.io/gh/apache/qpid-dispatch/pull/532?src=pr&el=desc) into [master](https://codecov.io/gh/apache/qpid-dispatch/commit/f22766996be12f5a0d6b388d04be6d7ccad1eb80?src=pr&el=desc) will **decrease** coverage by `0.06%`. > The diff coverage is `n/a`. [](https://codecov.io/gh/apache/qpid-dispatch/pull/532?src=pr&el=tree) ```diff @@Coverage Diff @@ ## master #532 +/- ## == - Coverage 86.91% 86.85% -0.07% == Files 87 87 Lines 1952119523 +2 == - Hits1696716957 -10 - Misses 2554 2566 +12 ``` | [Impacted Files](https://codecov.io/gh/apache/qpid-dispatch/pull/532?src=pr&el=tree) | Coverage Δ | | |---|---|---| | [src/parse.c](https://codecov.io/gh/apache/qpid-dispatch/pull/532/diff?src=pr&el=tree#diff-c3JjL3BhcnNlLmM=) | `84.76% <0%> (-1.64%)` | :arrow_down: | | [src/router\_core/transfer.c](https://codecov.io/gh/apache/qpid-dispatch/pull/532/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL3RyYW5zZmVyLmM=) | `94.62% <0%> (-0.77%)` | :arrow_down: | | [src/router\_core/agent\_link.c](https://codecov.io/gh/apache/qpid-dispatch/pull/532/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL2FnZW50X2xpbmsuYw==) | `67.52% <0%> (-0.52%)` | :arrow_down: | | [src/iterator.c](https://codecov.io/gh/apache/qpid-dispatch/pull/532/diff?src=pr&el=tree#diff-c3JjL2l0ZXJhdG9yLmM=) | `89.03% <0%> (-0.2%)` | :arrow_down: | | [src/router\_core/connections.c](https://codecov.io/gh/apache/qpid-dispatch/pull/532/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL2Nvbm5lY3Rpb25zLmM=) | `94.7% <0%> (-0.12%)` | :arrow_down: | | [src/router\_core/core\_client\_api.c](https://codecov.io/gh/apache/qpid-dispatch/pull/532/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL2NvcmVfY2xpZW50X2FwaS5j) | `91.94% <0%> (+0.36%)` | :arrow_up: | -- [Continue to review full report at Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/532?src=pr&el=continue). > **Legend** - [Click here to learn more](https://docs.codecov.io/docs/codecov-delta) > `Δ = absolute (impact)`, `ø = not affected`, `? = missing data` > Powered by [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/532?src=pr&el=footer). Last update [f227669...d0cec63](https://codecov.io/gh/apache/qpid-dispatch/pull/532?src=pr&el=lastupdated). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments). This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1381) Create documentation for configuring fallback destinations
[ https://issues.apache.org/jira/browse/DISPATCH-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885604#comment-16885604 ] ASF GitHub Bot commented on DISPATCH-1381: -- codecov-io commented on issue #532: DISPATCH-1381: Create procedure for handling undeliverable messages URL: https://github.com/apache/qpid-dispatch/pull/532#issuecomment-508257756 # [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/532?src=pr&el=h1) Report > Merging [#532](https://codecov.io/gh/apache/qpid-dispatch/pull/532?src=pr&el=desc) into [master](https://codecov.io/gh/apache/qpid-dispatch/commit/f22766996be12f5a0d6b388d04be6d7ccad1eb80?src=pr&el=desc) will **decrease** coverage by `0.06%`. > The diff coverage is `n/a`. [](https://codecov.io/gh/apache/qpid-dispatch/pull/532?src=pr&el=tree) ```diff @@Coverage Diff @@ ## master #532 +/- ## == - Coverage 86.91% 86.85% -0.07% == Files 87 87 Lines 1952119523 +2 == - Hits1696716957 -10 - Misses 2554 2566 +12 ``` | [Impacted Files](https://codecov.io/gh/apache/qpid-dispatch/pull/532?src=pr&el=tree) | Coverage Δ | | |---|---|---| | [src/parse.c](https://codecov.io/gh/apache/qpid-dispatch/pull/532/diff?src=pr&el=tree#diff-c3JjL3BhcnNlLmM=) | `84.76% <0%> (-1.64%)` | :arrow_down: | | [src/router\_core/transfer.c](https://codecov.io/gh/apache/qpid-dispatch/pull/532/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL3RyYW5zZmVyLmM=) | `94.62% <0%> (-0.77%)` | :arrow_down: | | [src/router\_core/agent\_link.c](https://codecov.io/gh/apache/qpid-dispatch/pull/532/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL2FnZW50X2xpbmsuYw==) | `67.52% <0%> (-0.52%)` | :arrow_down: | | [src/iterator.c](https://codecov.io/gh/apache/qpid-dispatch/pull/532/diff?src=pr&el=tree#diff-c3JjL2l0ZXJhdG9yLmM=) | `89.03% <0%> (-0.2%)` | :arrow_down: | | [src/router\_core/connections.c](https://codecov.io/gh/apache/qpid-dispatch/pull/532/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL2Nvbm5lY3Rpb25zLmM=) | `94.7% <0%> (-0.12%)` | :arrow_down: | | [src/router\_core/core\_client\_api.c](https://codecov.io/gh/apache/qpid-dispatch/pull/532/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL2NvcmVfY2xpZW50X2FwaS5j) | `91.94% <0%> (+0.36%)` | :arrow_up: | -- [Continue to review full report at Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/532?src=pr&el=continue). > **Legend** - [Click here to learn more](https://docs.codecov.io/docs/codecov-delta) > `Δ = absolute (impact)`, `ø = not affected`, `? = missing data` > Powered by [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/532?src=pr&el=footer). Last update [f227669...d0cec63](https://codecov.io/gh/apache/qpid-dispatch/pull/532?src=pr&el=lastupdated). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments). This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Create documentation for configuring fallback destinations > -- > > Key: DISPATCH-1381 > URL: https://issues.apache.org/jira/browse/DISPATCH-1381 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Documentation >Reporter: Ben Hardesty >Priority: Major > > The Dispatch Router documentation should be updated to describe how to > configure fallback destinations for an address (DISPATCH-1337). -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] asfgit closed pull request #527: DISPATCH-1374 - Added qdstat options --all-routers and --all-entities
asfgit closed pull request #527: DISPATCH-1374 - Added qdstat options --all-routers and --all-entities URL: https://github.com/apache/qpid-dispatch/pull/527 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1374) Add qdstat options --all-routers and all-entities which display statistics of all routers and displays all entities
[ https://issues.apache.org/jira/browse/DISPATCH-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885613#comment-16885613 ] ASF GitHub Bot commented on DISPATCH-1374: -- asfgit commented on pull request #527: DISPATCH-1374 - Added qdstat options --all-routers and --all-entities URL: https://github.com/apache/qpid-dispatch/pull/527 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add qdstat options --all-routers and all-entities which display statistics of > all routers and displays all entities > --- > > Key: DISPATCH-1374 > URL: https://issues.apache.org/jira/browse/DISPATCH-1374 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Container >Affects Versions: 1.7.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.9.0 > > > # Introduce two new command line options to qdstat called --all-routers and > --all-entities > # qdstat --all-routers - Is the same as - qdstat --all-routers > --all-entities. > ## Will display information on all entities from all interior routers if the > qdstat client connects to an interior router. > ## Will display information on all entities from only that edge router if > the qdstat client connects to an edge router > # qdstat --all-entities > ## Will display information on all entities from only that interior or edge > router that the qdstat client is connecting to. > # qdstat --all-entities -c > ## Error. Cannot ask for all entities and also specifically ask for > connection entity ? > # qdstat -c > ## As usual, just display connections in the router that the qdstat client > is connecting to > # qdstat -c --all-routers > ## Will display connection information for all interior routers in the > network if the qdstat client is connected to an interior router > ## Will display connection information for only that edge router if the > qdstat client is connected to and edge router. > # qdstat --all-entities --all-routers > ## Same as qdstat --all-routers (see #2) > # General stuff > # Include date timestamp when the dump was taken > # Display in stdout just like other qdstat options > # Aggregated output must consist of distinct sections which pertain to each > router and should be preceded by the router id for easy identification -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1374) Add qdstat options --all-routers and all-entities which display statistics of all routers and displays all entities
[ https://issues.apache.org/jira/browse/DISPATCH-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885612#comment-16885612 ] ASF subversion and git services commented on DISPATCH-1374: --- Commit 81da3d6da2d680e41527191c2a4b6eafc2bda3e8 in qpid-dispatch's branch refs/heads/master from Ganesh Murthy [ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=81da3d6 ] DISPATCH-1374 - Added qdstat options --all-routers and --all-entities. This closes #527. > Add qdstat options --all-routers and all-entities which display statistics of > all routers and displays all entities > --- > > Key: DISPATCH-1374 > URL: https://issues.apache.org/jira/browse/DISPATCH-1374 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Container >Affects Versions: 1.7.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.9.0 > > > # Introduce two new command line options to qdstat called --all-routers and > --all-entities > # qdstat --all-routers - Is the same as - qdstat --all-routers > --all-entities. > ## Will display information on all entities from all interior routers if the > qdstat client connects to an interior router. > ## Will display information on all entities from only that edge router if > the qdstat client connects to an edge router > # qdstat --all-entities > ## Will display information on all entities from only that interior or edge > router that the qdstat client is connecting to. > # qdstat --all-entities -c > ## Error. Cannot ask for all entities and also specifically ask for > connection entity ? > # qdstat -c > ## As usual, just display connections in the router that the qdstat client > is connecting to > # qdstat -c --all-routers > ## Will display connection information for all interior routers in the > network if the qdstat client is connected to an interior router > ## Will display connection information for only that edge router if the > qdstat client is connected to and edge router. > # qdstat --all-entities --all-routers > ## Same as qdstat --all-routers (see #2) > # General stuff > # Include date timestamp when the dump was taken > # Display in stdout just like other qdstat options > # Aggregated output must consist of distinct sections which pertain to each > router and should be preceded by the router id for easy identification -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1374) Add qdstat options --all-routers and all-entities which display statistics of all routers and displays all entities
[ https://issues.apache.org/jira/browse/DISPATCH-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-1374. - Resolution: Fixed > Add qdstat options --all-routers and all-entities which display statistics of > all routers and displays all entities > --- > > Key: DISPATCH-1374 > URL: https://issues.apache.org/jira/browse/DISPATCH-1374 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Container >Affects Versions: 1.7.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.9.0 > > > # Introduce two new command line options to qdstat called --all-routers and > --all-entities > # qdstat --all-routers - Is the same as - qdstat --all-routers > --all-entities. > ## Will display information on all entities from all interior routers if the > qdstat client connects to an interior router. > ## Will display information on all entities from only that edge router if > the qdstat client connects to an edge router > # qdstat --all-entities > ## Will display information on all entities from only that interior or edge > router that the qdstat client is connecting to. > # qdstat --all-entities -c > ## Error. Cannot ask for all entities and also specifically ask for > connection entity ? > # qdstat -c > ## As usual, just display connections in the router that the qdstat client > is connecting to > # qdstat -c --all-routers > ## Will display connection information for all interior routers in the > network if the qdstat client is connected to an interior router > ## Will display connection information for only that edge router if the > qdstat client is connected to and edge router. > # qdstat --all-entities --all-routers > ## Same as qdstat --all-routers (see #2) > # General stuff > # Include date timestamp when the dump was taken > # Display in stdout just like other qdstat options > # Aggregated output must consist of distinct sections which pertain to each > router and should be preceded by the router id for easy identification -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8341) [Broker-J] Reject overflow policy can erroneously rejects messages when maximumQueueDepthBytes is specified
[ https://issues.apache.org/jira/browse/QPID-8341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885694#comment-16885694 ] ASF subversion and git services commented on QPID-8341: --- Commit 66a56dee7f6ebcda8b6282ae1c73efd9454c7949 in qpid-broker-j's branch refs/heads/master from Alex Rudyy [ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=66a56de ] QPID-8341: [Broker-J] Fix failing test > [Broker-J] Reject overflow policy can erroneously rejects messages when > maximumQueueDepthBytes is specified > --- > > Key: QPID-8341 > URL: https://issues.apache.org/jira/browse/QPID-8341 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.0, qpid-java-broker-7.1.1, > qpid-java-broker-7.1.2, qpid-java-broker-7.0.8, qpid-java-broker-7.1.3, > qpid-java-broker-7.1.4 >Reporter: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.1.5 > > > The reject overflow policy can erroneously rejects messages when > maximumQueueDepthBytes is configured. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8341) [Broker-J] Reject overflow policy can erroneously rejects messages when maximumQueueDepthBytes is specified
[ https://issues.apache.org/jira/browse/QPID-8341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885705#comment-16885705 ] ASF subversion and git services commented on QPID-8341: --- Commit c0d92b971d7f4e27347fa167071b021b04b8ac78 in qpid-broker-j's branch refs/heads/7.1.x from Alex Rudyy [ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=c0d92b9 ] QPID-8341: [Broker-J] Fix failing test (cherry picked from commit 66a56dee7f6ebcda8b6282ae1c73efd9454c7949) > [Broker-J] Reject overflow policy can erroneously rejects messages when > maximumQueueDepthBytes is specified > --- > > Key: QPID-8341 > URL: https://issues.apache.org/jira/browse/QPID-8341 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.0, qpid-java-broker-7.1.1, > qpid-java-broker-7.1.2, qpid-java-broker-7.0.8, qpid-java-broker-7.1.3, > qpid-java-broker-7.1.4 >Reporter: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.1.5 > > > The reject overflow policy can erroneously rejects messages when > maximumQueueDepthBytes is configured. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
