[jira] [Assigned] (QPID-5319) Add ability to get list of connections through server management agent
[ https://issues.apache.org/jira/browse/QPID-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned QPID-5319: -- Assignee: Ted Ross Add ability to get list of connections through server management agent -- Key: QPID-5319 URL: https://issues.apache.org/jira/browse/QPID-5319 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Affects Versions: Future Reporter: Ernest Allen Assignee: Ted Ross Attachments: dispatch.connectors.diff3 Add a management agent handler that will return a list of connections. The following info should be returned: state - the state of the connection (Connecting, Opening, Operational, Failed, User) host - the host of the connection's container port - the post of the connection's container container - the name of the remote connection container sasl - the sasl mechanism list of the connection's container role - the role of the connection's container tools/src/py/qdstat should also be updated with a -c command line switch. ./qdstat -c -b localhost:20001 Connections statehost port container sasl-mechanisms role === Operational 0.0.0.0 20002 QDR.B ANONYMOUSinter-router Operational 0.0.0.0 20003 QDR.C ANONYMOUSinter-router Operational 0.0.0.0 20004 QDR.D ANONYMOUSinter-router -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5319) Add ability to get list of connections through server management agent
[ https://issues.apache.org/jira/browse/QPID-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13817773#comment-13817773 ] Ted Ross commented on QPID-5319: I tested this patch with two routers connected together. If I look at the connections on one router, I see a connection to the other. If I look at the other, I see no connections. If repeatedly invoke qdstat -c, the connections eventually disappear. Also, I never see the connection that comes from qdstat itself. Add ability to get list of connections through server management agent -- Key: QPID-5319 URL: https://issues.apache.org/jira/browse/QPID-5319 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Affects Versions: Future Reporter: Ernest Allen Assignee: Ted Ross Attachments: dispatch.connectors.diff3 Add a management agent handler that will return a list of connections. The following info should be returned: state - the state of the connection (Connecting, Opening, Operational, Failed, User) host - the host of the connection's container port - the post of the connection's container container - the name of the remote connection container sasl - the sasl mechanism list of the connection's container role - the role of the connection's container tools/src/py/qdstat should also be updated with a -c command line switch. ./qdstat -c -b localhost:20001 Connections statehost port container sasl-mechanisms role === Operational 0.0.0.0 20002 QDR.B ANONYMOUSinter-router Operational 0.0.0.0 20003 QDR.C ANONYMOUSinter-router Operational 0.0.0.0 20004 QDR.D ANONYMOUSinter-router -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5339) Dispatch - Intermittent crashes during scripted six-node tests
Ted Ross created QPID-5339: -- Summary: Dispatch - Intermittent crashes during scripted six-node tests Key: QPID-5339 URL: https://issues.apache.org/jira/browse/QPID-5339 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Hat Tip: Mick Goulish Mick did some soak testing and discovered that a six-router topology, set up by a script, would occasionally leave core dumps. Analysis revealed that the crash would occur sometimes when two threads simultaneously attempted to allocate the first instance of the same type. There is a thread-safety issue in the initializer for the type-allocator. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5339) Dispatch - Intermittent crashes during scripted six-node tests
[ https://issues.apache.org/jira/browse/QPID-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-5339. Resolution: Fixed Dispatch - Intermittent crashes during scripted six-node tests -- Key: QPID-5339 URL: https://issues.apache.org/jira/browse/QPID-5339 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Hat Tip: Mick Goulish Mick did some soak testing and discovered that a six-router topology, set up by a script, would occasionally leave core dumps. Analysis revealed that the crash would occur sometimes when two threads simultaneously attempted to allocate the first instance of the same type. There is a thread-safety issue in the initializer for the type-allocator. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5319) Add ability to get list of connections through server management agent
[ https://issues.apache.org/jira/browse/QPID-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-5319. Resolution: Fixed Add ability to get list of connections through server management agent -- Key: QPID-5319 URL: https://issues.apache.org/jira/browse/QPID-5319 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Affects Versions: Future Reporter: Ernest Allen Assignee: Ted Ross Attachments: dispatch.connectors.diff4 Add a management agent handler that will return a list of connections. The following info should be returned: state - the state of the connection (Connecting, Opening, Operational, Failed, User) host - the host of the connection's container port - the post of the connection's container container - the name of the remote connection container sasl - the sasl mechanism list of the connection's container role - the role of the connection's container tools/src/py/qdstat should also be updated with a -c command line switch. ./qdstat -c -b localhost:20001 Connections statehost port container sasl-mechanisms role === Operational 0.0.0.0 20002 QDR.B ANONYMOUSinter-router Operational 0.0.0.0 20003 QDR.C ANONYMOUSinter-router Operational 0.0.0.0 20004 QDR.D ANONYMOUSinter-router -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5343) Dispatch does not properly handle the drain protocol on senders.
Ted Ross created QPID-5343: -- Summary: Dispatch does not properly handle the drain protocol on senders. Key: QPID-5343 URL: https://issues.apache.org/jira/browse/QPID-5343 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Dispatch does not respond with a flow(drain=True) when it receives a flow(drain=True) on a sender. This causes endpoints implemented with qpid::messaging and using the Receiver::fetch call to hang waiting for a confirmation of the drained credits. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5343) Dispatch does not properly handle the drain protocol on senders.
[ https://issues.apache.org/jira/browse/QPID-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-5343. Resolution: Fixed Dispatch does not properly handle the drain protocol on senders. Key: QPID-5343 URL: https://issues.apache.org/jira/browse/QPID-5343 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Dispatch does not respond with a flow(drain=True) when it receives a flow(drain=True) on a sender. This causes endpoints implemented with qpid::messaging and using the Receiver::fetch call to hang waiting for a confirmation of the drained credits. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5343) Dispatch does not properly handle the drain protocol on senders.
[ https://issues.apache.org/jira/browse/QPID-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13822956#comment-13822956 ] Ted Ross commented on QPID-5343: Note: The fix for this issue requires Proton 0.6. If built against 0.5, the old behavior will remain. Dispatch does not properly handle the drain protocol on senders. Key: QPID-5343 URL: https://issues.apache.org/jira/browse/QPID-5343 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Dispatch does not respond with a flow(drain=True) when it receives a flow(drain=True) on a sender. This causes endpoints implemented with qpid::messaging and using the Receiver::fetch call to hang waiting for a confirmation of the drained credits. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5350) Dispatch - Management queries that receive empty tables results in corrupt response
Ted Ross created QPID-5350: -- Summary: Dispatch - Management queries that receive empty tables results in corrupt response Key: QPID-5350 URL: https://issues.apache.org/jira/browse/QPID-5350 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross A management query that results in an empty response causes a corrupt message body in the response. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5350) Dispatch - Management queries that receive empty tables results in corrupt response
[ https://issues.apache.org/jira/browse/QPID-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-5350. Resolution: Fixed Dispatch - Management queries that receive empty tables results in corrupt response --- Key: QPID-5350 URL: https://issues.apache.org/jira/browse/QPID-5350 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross A management query that results in an empty response causes a corrupt message body in the response. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-5351) Settle on one prefix for Dispatch names
[
https://issues.apache.org/jira/browse/QPID-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross reassigned QPID-5351:
--
Assignee: Ted Ross
Settle on one prefix for Dispatch names
---
Key: QPID-5351
URL: https://issues.apache.org/jira/browse/QPID-5351
Project: Qpid
Issue Type: Improvement
Components: Qpid Dispatch
Reporter: Justin Ross
Assignee: Ted Ross
Attachments: consistent-naming.patch
When we have a chance to clarify a true connection for our users by
using a consistent convention, we should. Here's what we have now:
{noformat}
qpid-dxrouter.conf
qpid-dxrouterd
qdstat
QD_TOOLS_HOME
dx_ for C symbols
qdx for AMQP addresses
{noformat}
A mess! I propose one of the following:
{noformat}
dxrouterd.conf qdxrouterd.confqdrouterd.conf
dxrouterd qdxrouterd qdrouterd
dxstat qdxstatqdstat
DX_TOOLS_HOME QDX_TOOLS_HOME QD_TOOLS_HOME
dx_ for symbolsqdx_ for symbols qd_ for symbols
dx for addresses qdx for addresses qd for addresses
{noformat}
Expressed as a rule: where it's sensible to use a short form, always
use qd (or whatever ends up being canonical). Otherwise, spell it
out: qpid/dispatch.
A standard prefix also improves command-line discoverability:
qd[TAB][TAB] shows you all the entrypoints.
I slightly prefer qd because it's the simplest abbreviation of Qpid
Dispatch. The patch attached here uses it, but I am quite willing to
supply a new set of patches that use another prefix.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5351) Settle on one prefix for Dispatch names
[
https://issues.apache.org/jira/browse/QPID-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross resolved QPID-5351.
Resolution: Fixed
Settle on one prefix for Dispatch names
---
Key: QPID-5351
URL: https://issues.apache.org/jira/browse/QPID-5351
Project: Qpid
Issue Type: Improvement
Components: Qpid Dispatch
Reporter: Justin Ross
Assignee: Ted Ross
Attachments: consistent-naming.patch
When we have a chance to clarify a true connection for our users by
using a consistent convention, we should. Here's what we have now:
{noformat}
qpid-dxrouter.conf
qpid-dxrouterd
qdstat
QD_TOOLS_HOME
dx_ for C symbols
qdx for AMQP addresses
{noformat}
A mess! I propose one of the following:
{noformat}
dxrouterd.conf qdxrouterd.confqdrouterd.conf
dxrouterd qdxrouterd qdrouterd
dxstat qdxstatqdstat
DX_TOOLS_HOME QDX_TOOLS_HOME QD_TOOLS_HOME
dx_ for symbolsqdx_ for symbols qd_ for symbols
dx for addresses qdx for addresses qd for addresses
{noformat}
Expressed as a rule: where it's sensible to use a short form, always
use qd (or whatever ends up being canonical). Otherwise, spell it
out: qpid/dispatch.
A standard prefix also improves command-line discoverability:
qd[TAB][TAB] shows you all the entrypoints.
I slightly prefer qd because it's the simplest abbreviation of Qpid
Dispatch. The patch attached here uses it, but I am quite willing to
supply a new set of patches that use another prefix.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5352) Installation of python code ignores prefix
[ https://issues.apache.org/jira/browse/QPID-5352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-5352. Resolution: Fixed Installation of python code ignores prefix -- Key: QPID-5352 URL: https://issues.apache.org/jira/browse/QPID-5352 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Justin Ross Attachments: use-install-prefix.patch See https://issues.apache.org/jira/browse/PROTON-445 . It's the same problem, repeated in the dispatch code. Unprivileged make installs fail because it's trying to install the python code to a system path outside the prefix I give it. As I noted elsewhere, this will result in users accidentally clobbering distro-installed files. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5365) Clean up file locations in Dispatch
[ https://issues.apache.org/jira/browse/QPID-5365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13827922#comment-13827922 ] Ted Ross commented on QPID-5365: Justin, Go ahead and commit the change. Darryl, Lets address the the private path issue on top of this update. Clean up file locations in Dispatch --- Key: QPID-5365 URL: https://issues.apache.org/jira/browse/QPID-5365 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Justin Ross Assignee: Justin Ross Attachments: relocations.patch The attached patch makes the file locations consistent wrt the conventions outlined in QPID-5351 and otherwise removes redundancies, simplifies, and prepares for future additions. With this change, the tests and installs without error in my environment. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5368) Dispatch - Exercise qdstat in the tests
[ https://issues.apache.org/jira/browse/QPID-5368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13828014#comment-13828014 ] Ted Ross commented on QPID-5368: You should be able to do this in the context of system_tests_one_router.py. All the tests in that module operate against a running router. Dispatch - Exercise qdstat in the tests --- Key: QPID-5368 URL: https://issues.apache.org/jira/browse/QPID-5368 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Justin Ross Assignee: Justin Ross Make sure qdstat is executed in various ways when the developer runs make test. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-4853) Connectors are not closed when connections are closed cleanly
[ https://issues.apache.org/jira/browse/QPID-4853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-4853. Resolution: Duplicate Connectors are not closed when connections are closed cleanly - Key: QPID-4853 URL: https://issues.apache.org/jira/browse/QPID-4853 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Priority: Blocker When a connection is closed cleanly by a client, the pn_connector_closed condition never occurs and the connector is not closed. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4611) Dispatch - Pause/Resume broken when invoked from non-server thread
[ https://issues.apache.org/jira/browse/QPID-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated QPID-4611: --- Priority: Trivial (was: Major) Dispatch - Pause/Resume broken when invoked from non-server thread -- Key: QPID-4611 URL: https://issues.apache.org/jira/browse/QPID-4611 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Priority: Trivial If an application starts Dispatch Server using dx_server_start (i.e. the non-blocking start method), the main thread cannot be used to invoke dx_server_pause/dx_server_resume. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-5335) Dispatch Python libraries need to install to a private directory.
[ https://issues.apache.org/jira/browse/QPID-5335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned QPID-5335: -- Assignee: Ted Ross Dispatch Python libraries need to install to a private directory. - Key: QPID-5335 URL: https://issues.apache.org/jira/browse/QPID-5335 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Darryl L. Pierce Assignee: Ted Ross Currently the embedded Python libraries are installed to the site-packages directory and are public, which is undesirable. Instead they should install to: /usr/lib/qpid-dispatch The binary should set this directory by default (or have it set as a compile time option) and also provide a way to override it as a command line option. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5335) Dispatch Python libraries need to install to a private directory.
[ https://issues.apache.org/jira/browse/QPID-5335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-5335. Resolution: Fixed Dispatch Python libraries need to install to a private directory. - Key: QPID-5335 URL: https://issues.apache.org/jira/browse/QPID-5335 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Darryl L. Pierce Assignee: Ted Ross Currently the embedded Python libraries are installed to the site-packages directory and are public, which is undesirable. Instead they should install to: /usr/lib/qpid-dispatch The binary should set this directory by default (or have it set as a compile time option) and also provide a way to override it as a command line option. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5381) Dispatch - Use dynamic source address for the reply-to in qdstat tool
Ted Ross created QPID-5381: -- Summary: Dispatch - Use dynamic source address for the reply-to in qdstat tool Key: QPID-5381 URL: https://issues.apache.org/jira/browse/QPID-5381 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross With dynamic-source available in Proton Messenger (Python - Introduced in 0.6), update the qdstat tool to use a proper dynamic reply-to address. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5382) Dispatch - Enhance qdstat tool to link usage to users
Ted Ross created QPID-5382: -- Summary: Dispatch - Enhance qdstat tool to link usage to users Key: QPID-5382 URL: https://issues.apache.org/jira/browse/QPID-5382 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Ted Ross The qdstat tool (and the management schema for Dispatch) should be enhanced such that admins can trace address usage (links) to connections/hosts/users. Specifically: - Provide source and target information for links - Identify the connection associated with links - Investigate providing remote pid/process information in connections (like qpidd) -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5381) Dispatch - Use dynamic source address for the reply-to in qdstat tool
[ https://issues.apache.org/jira/browse/QPID-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-5381. Resolution: Fixed Dispatch - Use dynamic source address for the reply-to in qdstat tool - Key: QPID-5381 URL: https://issues.apache.org/jira/browse/QPID-5381 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross With dynamic-source available in Proton Messenger (Python - Introduced in 0.6), update the qdstat tool to use a proper dynamic reply-to address. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5393) Dispatch - Allow qdstat to query any router in the network from a connection
Ted Ross created QPID-5393: -- Summary: Dispatch - Allow qdstat to query any router in the network from a connection Key: QPID-5393 URL: https://issues.apache.org/jira/browse/QPID-5393 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross This improvement allows the qdstat CLI tool to query any router in the network regardless of which one it is attached to. There are two relevant options for this feature: || Option || Description || || --bus host:port || This defines the access point for the tool. Normally, this is the host/port of the _nearest_ router || || --router router-id || This is the identifier of the router to be queried || Note that the list of routers can be found using qdstat -n. This is an important feature for situations where a remote router may not be accessible directly via TCP/IP because it is behind a firewall or in a disjoint private network. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5393) Dispatch - Allow qdstat to query any router in the network from a connection
[ https://issues.apache.org/jira/browse/QPID-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-5393. Resolution: Fixed Dispatch - Allow qdstat to query any router in the network from a connection Key: QPID-5393 URL: https://issues.apache.org/jira/browse/QPID-5393 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross This improvement allows the qdstat CLI tool to query any router in the network regardless of which one it is attached to. There are two relevant options for this feature: || Option || Description || || --bus host:port || This defines the access point for the tool. Normally, this is the host/port of the _nearest_ router || || --router router-id || This is the identifier of the router to be queried || Note that the list of routers can be found using qdstat -n. This is an important feature for situations where a remote router may not be accessible directly via TCP/IP because it is behind a firewall or in a disjoint private network. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5397) Dispatch - Crash occurs when linked deliveries are concurrently settled
[ https://issues.apache.org/jira/browse/QPID-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-5397. Resolution: Fixed Dispatch - Crash occurs when linked deliveries are concurrently settled --- Key: QPID-5397 URL: https://issues.apache.org/jira/browse/QPID-5397 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Dispatch router crashed while running a test in which a client/server pair exchanges requests and responses with acknowledgement (not pre-settled). The test does not throttle the message rates. After several tens-of-thousands of transfers, the router crashed while settling a delivery and attempting to unlink it from its peer. Apparently two linked deliveries were concurrently settled on separate threads. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5397) Dispatch - Crash occurs when linked deliveries are concurrently settled
Ted Ross created QPID-5397: -- Summary: Dispatch - Crash occurs when linked deliveries are concurrently settled Key: QPID-5397 URL: https://issues.apache.org/jira/browse/QPID-5397 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Dispatch router crashed while running a test in which a client/server pair exchanges requests and responses with acknowledgement (not pre-settled). The test does not throttle the message rates. After several tens-of-thousands of transfers, the router crashed while settling a delivery and attempting to unlink it from its peer. Apparently two linked deliveries were concurrently settled on separate threads. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Reopened] (QPID-5397) Dispatch - Crash occurs when linked deliveries are concurrently settled
[ https://issues.apache.org/jira/browse/QPID-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reopened QPID-5397: The fix was an improvement, but there is still a window of opportunity for a problem. If a delivery is sent unsettled, and is then settled by the sender before being settled by the receiver (due to exceeding the outgoing window in Messenger for example), Dispatch may attempt to re-settle the sender-side delivery when the receiver settles thus causing problems in Proton Engine and possibly double-freeing the structure. A new fix will hold off the unlinking and freeing of linked deliveries until they are both settled. Dispatch - Crash occurs when linked deliveries are concurrently settled --- Key: QPID-5397 URL: https://issues.apache.org/jira/browse/QPID-5397 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Dispatch router crashed while running a test in which a client/server pair exchanges requests and responses with acknowledgement (not pre-settled). The test does not throttle the message rates. After several tens-of-thousands of transfers, the router crashed while settling a delivery and attempting to unlink it from its peer. Apparently two linked deliveries were concurrently settled on separate threads. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5403) Dispatch - The router-specific annotations have reserved keys
Ted Ross created QPID-5403: -- Summary: Dispatch - The router-specific annotations have reserved keys Key: QPID-5403 URL: https://issues.apache.org/jira/browse/QPID-5403 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross The keys in the annotations used in Dispatch Router are reserved. They need to be changed so they are prefixed with x-opt-. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5403) Dispatch - The router-specific annotations have reserved keys
[ https://issues.apache.org/jira/browse/QPID-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-5403. Resolution: Fixed Dispatch - The router-specific annotations have reserved keys - Key: QPID-5403 URL: https://issues.apache.org/jira/browse/QPID-5403 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross The keys in the annotations used in Dispatch Router are reserved. They need to be changed so they are prefixed with x-opt-. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5397) Dispatch - Crash occurs when linked deliveries are concurrently settled
[ https://issues.apache.org/jira/browse/QPID-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated QPID-5397: --- Priority: Blocker (was: Major) Dispatch - Crash occurs when linked deliveries are concurrently settled --- Key: QPID-5397 URL: https://issues.apache.org/jira/browse/QPID-5397 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Priority: Blocker Dispatch router crashed while running a test in which a client/server pair exchanges requests and responses with acknowledgement (not pre-settled). The test does not throttle the message rates. After several tens-of-thousands of transfers, the router crashed while settling a delivery and attempting to unlink it from its peer. Apparently two linked deliveries were concurrently settled on separate threads. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5397) Dispatch - Crash occurs when linked deliveries are concurrently settled
[ https://issues.apache.org/jira/browse/QPID-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-5397. Resolution: Fixed Dispatch - Crash occurs when linked deliveries are concurrently settled --- Key: QPID-5397 URL: https://issues.apache.org/jira/browse/QPID-5397 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Priority: Blocker Dispatch router crashed while running a test in which a client/server pair exchanges requests and responses with acknowledgement (not pre-settled). The test does not throttle the message rates. After several tens-of-thousands of transfers, the router crashed while settling a delivery and attempting to unlink it from its peer. Apparently two linked deliveries were concurrently settled on separate threads. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5367) Dispatch - Add man pages and stubs for other documentation
[ https://issues.apache.org/jira/browse/QPID-5367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-5367. Resolution: Fixed Dispatch - Add man pages and stubs for other documentation -- Key: QPID-5367 URL: https://issues.apache.org/jira/browse/QPID-5367 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Justin Ross Assignee: Justin Ross - Man pages for qdstat, qdrouterd, and qdrouterd.conf - Start a book for more involved documentation, and port some of the content from the website - Add a place for developer notes; add a note about code conventions - Add a place for api doc resources such as an overview for doxygen -- This message was sent by Atlassian JIRA (v6.1.4#6159) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5217) Dispatch - Cleanup of API inconsistencies and oddities
[ https://issues.apache.org/jira/browse/QPID-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-5217. Resolution: Fixed Dispatch - Cleanup of API inconsistencies and oddities -- Key: QPID-5217 URL: https://issues.apache.org/jira/browse/QPID-5217 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Attachments: callback-typedef.patch This issue is for various API-related issues like cleanup, documentation, consistency, etc. in the Dispatch header files. -- This message was sent by Atlassian JIRA (v6.1.4#6159) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5443) Dispatch - Improve error reporting in the configuration file
Ted Ross created QPID-5443: -- Summary: Dispatch - Improve error reporting in the configuration file Key: QPID-5443 URL: https://issues.apache.org/jira/browse/QPID-5443 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross The configuration module should provide better error reports when there are problems in the configuration file. -- This message was sent by Atlassian JIRA (v6.1.4#6159) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5443) Dispatch - Improve error reporting in the configuration file
[ https://issues.apache.org/jira/browse/QPID-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-5443. Resolution: Fixed Dispatch - Improve error reporting in the configuration file Key: QPID-5443 URL: https://issues.apache.org/jira/browse/QPID-5443 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross The configuration module should provide better error reports when there are problems in the configuration file. -- This message was sent by Atlassian JIRA (v6.1.4#6159) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5436) Setting SYSCONF_INSTALL_PREFIX to an empty string causes install the fail
[ https://issues.apache.org/jira/browse/QPID-5436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-5436. Resolution: Fixed Setting SYSCONF_INSTALL_PREFIX to an empty string causes install the fail - Key: QPID-5436 URL: https://issues.apache.org/jira/browse/QPID-5436 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Darryl L. Pierce Assignee: Darryl L. Pierce Attachments: 0001-QPID-5436-Fix-when-the-SYSCONF_INSTALL_PREFIX-is-not.patch If SYSCONF_INSTALL_PREFIX is set to a blank string then CMake attempts to install the configuration file to //etc/qpid-dispatch, which fails. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-5448) qdstat does not have the correct Python path for the internal libraries
[ https://issues.apache.org/jira/browse/QPID-5448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned QPID-5448: -- Assignee: Ted Ross (was: Darryl L. Pierce) qdstat does not have the correct Python path for the internal libraries --- Key: QPID-5448 URL: https://issues.apache.org/jira/browse/QPID-5448 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Darryl L. Pierce Assignee: Ted Ross Attachments: 0001-QPID-5448-Fix-the-default-private-Python-library-ins.patch The default path that is set in the source doesn't include the install prefix, so ends up being lib/qpid-dispatch. The attached patch fixes the issue. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5448) qdstat does not have the correct Python path for the internal libraries
[ https://issues.apache.org/jira/browse/QPID-5448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-5448. Resolution: Fixed qdstat does not have the correct Python path for the internal libraries --- Key: QPID-5448 URL: https://issues.apache.org/jira/browse/QPID-5448 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Darryl L. Pierce Assignee: Ted Ross Attachments: 0001-QPID-5448-Fix-the-default-private-Python-library-ins.patch The default path that is set in the source doesn't include the install prefix, so ends up being lib/qpid-dispatch. The attached patch fixes the issue. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5466) Dispatch - Add different forwarding semantics for addresses
Ted Ross created QPID-5466: -- Summary: Dispatch - Add different forwarding semantics for addresses Key: QPID-5466 URL: https://issues.apache.org/jira/browse/QPID-5466 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross (For version 0.2) At present, if there are multiple receivers for a particular address, Dispatch delivers a copy of each message to all of the receivers. This feature adds the ability to by-configuration deliver messages to only one of those receivers. The configuration for this feature is per-address and defines two settings: - _fanout_ is either Multiple or Single (and a placeholder for Group). Multiple fanout means all subscribers receive each message. Single fanout means that only one subscriber receives the message. - _bias_ controls how single-fanout is treated. The following values for bias are provided: - Closest - each message is delivered to the closest/least-cost subscriber. - Spread - messages are spread indeterminately across all subscribers. - Latency - (not implemented yet) Messages are delivered in a balanced way to all subscribers based on the latency of acknowledgements. This mode attempts to keep all subscribers equally fed with incoming messages. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5466) Dispatch - Add different forwarding semantics for addresses
[ https://issues.apache.org/jira/browse/QPID-5466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated QPID-5466: --- Description: (For version 0.2) At present, if there are multiple receivers for a particular address, Dispatch delivers a copy of each message to all of the receivers. This feature adds the ability to by-configuration deliver messages to only one of those receivers. The configuration for this feature is per-address and defines two settings: - _fanout_ is either Multiple or Single (and a placeholder for Group). Multiple fanout means all subscribers receive each message. Single fanout means that only one subscriber receives the message. - _bias_ controls how single-fanout is treated. The following values for bias are provided: -- _Closest_ - each message is delivered to the closest/least-cost subscriber. -- _Spread_ - messages are spread indeterminately across all subscribers. -- _Latency_ - (not implemented yet) Messages are delivered in a balanced way to all subscribers based on the latency of acknowledgements. This mode attempts to keep all subscribers equally fed with incoming messages. was: (For version 0.2) At present, if there are multiple receivers for a particular address, Dispatch delivers a copy of each message to all of the receivers. This feature adds the ability to by-configuration deliver messages to only one of those receivers. The configuration for this feature is per-address and defines two settings: - _fanout_ is either Multiple or Single (and a placeholder for Group). Multiple fanout means all subscribers receive each message. Single fanout means that only one subscriber receives the message. - _bias_ controls how single-fanout is treated. The following values for bias are provided: - Closest - each message is delivered to the closest/least-cost subscriber. - Spread - messages are spread indeterminately across all subscribers. - Latency - (not implemented yet) Messages are delivered in a balanced way to all subscribers based on the latency of acknowledgements. This mode attempts to keep all subscribers equally fed with incoming messages. Dispatch - Add different forwarding semantics for addresses --- Key: QPID-5466 URL: https://issues.apache.org/jira/browse/QPID-5466 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross (For version 0.2) At present, if there are multiple receivers for a particular address, Dispatch delivers a copy of each message to all of the receivers. This feature adds the ability to by-configuration deliver messages to only one of those receivers. The configuration for this feature is per-address and defines two settings: - _fanout_ is either Multiple or Single (and a placeholder for Group). Multiple fanout means all subscribers receive each message. Single fanout means that only one subscriber receives the message. - _bias_ controls how single-fanout is treated. The following values for bias are provided: -- _Closest_ - each message is delivered to the closest/least-cost subscriber. -- _Spread_ - messages are spread indeterminately across all subscribers. -- _Latency_ - (not implemented yet) Messages are delivered in a balanced way to all subscribers based on the latency of acknowledgements. This mode attempts to keep all subscribers equally fed with incoming messages. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5505) Dispatch - Refactor configuration to clean up the library interface
Ted Ross created QPID-5505: -- Summary: Dispatch - Refactor configuration to clean up the library interface Key: QPID-5505 URL: https://issues.apache.org/jira/browse/QPID-5505 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Even though Dispatch Router is an application, it is designed as an application written against a container library. As a result, the configuration contains two sections: The common library configuration (container, connections, etc.) and the router configuration (addresses, etc.). In version 0.1, the configuration is monolithic and it is therefore very awkward to use the Dispatch library for any purpose other than the router. This improvement separates the common configuration from the application-specific configuration, making it easier to build other things on top of the Dispatch AMQP container. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5505) Dispatch - Refactor configuration to clean up the library interface
[ https://issues.apache.org/jira/browse/QPID-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-5505. Resolution: Fixed Fixed in 0.2 Dispatch - Refactor configuration to clean up the library interface --- Key: QPID-5505 URL: https://issues.apache.org/jira/browse/QPID-5505 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Even though Dispatch Router is an application, it is designed as an application written against a container library. As a result, the configuration contains two sections: The common library configuration (container, connections, etc.) and the router configuration (addresses, etc.). In version 0.1, the configuration is monolithic and it is therefore very awkward to use the Dispatch library for any purpose other than the router. This improvement separates the common configuration from the application-specific configuration, making it easier to build other things on top of the Dispatch AMQP container. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-5515) Dispatch - Use pn_ssl_domain_set_trusted_ca_db to pass ca_db to proton
[ https://issues.apache.org/jira/browse/QPID-5515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned QPID-5515: -- Assignee: Ted Ross Dispatch - Use pn_ssl_domain_set_trusted_ca_db to pass ca_db to proton -- Key: QPID-5515 URL: https://issues.apache.org/jira/browse/QPID-5515 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Irina Boverman Assignee: Ted Ross Configure dispatch to use SSL, start dispatch mode, observe error: Listener : 0.0.0.0:amqp SASL: ANONYMOUS SSL: 0 Listener : 0.0.0.0:2 SASL: ANONYMOUS SSL: 1 unsec: 0 cert-file: /root/iboverma/server-certificate.pem key-file: /root/iboverma/server-private-key.pem cert-db: /root/iboverma/ca-certificate.pem peer-auth: 1 Sat Jan 25 15:04:43 2014 SERVER (INFO) Operational, 6 Threads Running Sat Jan 25 15:04:43 2014 SERVER (INFO) Running in DEBUG Mode Sat Jan 25 15:10:23 2014 SERVER (DEBUG) added listener connection Error: cannot verify peer without a trusted CA configured. Use pn_ssl_domain_set_trusted_ca_db() [0x7ff124013dd0]:ERROR[-2] SSL Failure: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol Sat Jan 25 15:10:23 2014 SERVER (DEBUG) removed listener connection Sat Jan 25 15:10:28 2014 SERVER (DEBUG) added listener connection Error: cannot verify peer without a trusted CA configured. Use pn_ssl_domain_set_trusted_ca_db() -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5515) Dispatch - Use pn_ssl_domain_set_trusted_ca_db to pass ca_db to proton
[ https://issues.apache.org/jira/browse/QPID-5515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-5515. Resolution: Fixed Fixed for 0.2 Dispatch - Use pn_ssl_domain_set_trusted_ca_db to pass ca_db to proton -- Key: QPID-5515 URL: https://issues.apache.org/jira/browse/QPID-5515 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Irina Boverman Assignee: Ted Ross Configure dispatch to use SSL, start dispatch mode, observe error: Listener : 0.0.0.0:amqp SASL: ANONYMOUS SSL: 0 Listener : 0.0.0.0:2 SASL: ANONYMOUS SSL: 1 unsec: 0 cert-file: /root/iboverma/server-certificate.pem key-file: /root/iboverma/server-private-key.pem cert-db: /root/iboverma/ca-certificate.pem peer-auth: 1 Sat Jan 25 15:04:43 2014 SERVER (INFO) Operational, 6 Threads Running Sat Jan 25 15:04:43 2014 SERVER (INFO) Running in DEBUG Mode Sat Jan 25 15:10:23 2014 SERVER (DEBUG) added listener connection Error: cannot verify peer without a trusted CA configured. Use pn_ssl_domain_set_trusted_ca_db() [0x7ff124013dd0]:ERROR[-2] SSL Failure: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol Sat Jan 25 15:10:23 2014 SERVER (DEBUG) removed listener connection Sat Jan 25 15:10:28 2014 SERVER (DEBUG) added listener connection Error: cannot verify peer without a trusted CA configured. Use pn_ssl_domain_set_trusted_ca_db() -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1) Use Target Address from the link if there is no To field in a message from a producer
Ted Ross created DISPATCH-1: --- Summary: Use Target Address from the link if there is no To field in a message from a producer Key: DISPATCH-1 URL: https://issues.apache.org/jira/browse/DISPATCH-1 Project: Qpid Dispatch Issue Type: Improvement Reporter: Ted Ross When testing Dispatch against the Qpid messaging clients, messages are not properly forwarded because the clients use target.address instead of properties.to. Both cases should be supported by the router. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1) Use Target Address from the link if there is no To field in a message from a producer
[ https://issues.apache.org/jira/browse/DISPATCH-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-1: Affects Version/s: 0.1 Use Target Address from the link if there is no To field in a message from a producer - Key: DISPATCH-1 URL: https://issues.apache.org/jira/browse/DISPATCH-1 Project: Qpid Dispatch Issue Type: Improvement Affects Versions: 0.1 Reporter: Ted Ross When testing Dispatch against the Qpid messaging clients, messages are not properly forwarded because the clients use target.address instead of properties.to. Both cases should be supported by the router. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-2) Adhere to the AMQP Management Specification for remote management
Ted Ross created DISPATCH-2: --- Summary: Adhere to the AMQP Management Specification for remote management Key: DISPATCH-2 URL: https://issues.apache.org/jira/browse/DISPATCH-2 Project: Qpid Dispatch Issue Type: Improvement Affects Versions: 0.1 Reporter: Ted Ross Assignee: Ted Ross Qpid Dispatch should adhere as closely as possible to the emerging Management specification from the AMQP technical committee. This issue will track work and comments related to compliance with the specification. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-5175) Dispatch - Use Target Address from the link if there is no To field in a message from a producer
[ https://issues.apache.org/jira/browse/QPID-5175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross closed QPID-5175. -- Resolution: Duplicate Dispatch - Use Target Address from the link if there is no To field in a message from a producer Key: QPID-5175 URL: https://issues.apache.org/jira/browse/QPID-5175 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross When testing Dispatch against the Qpid messaging clients, messages are not properly forwarded because the clients use target.address instead of properties.to. Both cases should be supported by the router. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-5238) Dispatch - Adhere to the AMQP Management Specification for remote management
[ https://issues.apache.org/jira/browse/QPID-5238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross closed QPID-5238. -- Resolution: Duplicate Dispatch - Adhere to the AMQP Management Specification for remote management Key: QPID-5238 URL: https://issues.apache.org/jira/browse/QPID-5238 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Qpid Dispatch should adhere as closely as possible to the emerging Management specification from the AMQP technical committee. This issue will track work and comments related to compliance with the specification. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-3) Pause/Resume broken when invoked from non-server thread
Ted Ross created DISPATCH-3: --- Summary: Pause/Resume broken when invoked from non-server thread Key: DISPATCH-3 URL: https://issues.apache.org/jira/browse/DISPATCH-3 Project: Qpid Dispatch Issue Type: Bug Affects Versions: 0.1 Reporter: Ted Ross Assignee: Ted Ross Priority: Minor -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-4964) Dispatch does not detect the closure of SSL connections that are closed uncleanly
[ https://issues.apache.org/jira/browse/QPID-4964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross closed QPID-4964. -- Resolution: Duplicate Dispatch does not detect the closure of SSL connections that are closed uncleanly - Key: QPID-4964 URL: https://issues.apache.org/jira/browse/QPID-4964 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross If a client connects to the Dispatch router using SSL, an unclean (process killed) disconnect is not detected by Dispatch and resources are not returned. Connections in-the-clear do not exhibit this symptom. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-4611) Dispatch - Pause/Resume broken when invoked from non-server thread
[ https://issues.apache.org/jira/browse/QPID-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross closed QPID-4611. -- Resolution: Duplicate Dispatch - Pause/Resume broken when invoked from non-server thread -- Key: QPID-4611 URL: https://issues.apache.org/jira/browse/QPID-4611 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross Priority: Trivial If an application starts Dispatch Server using dx_server_start (i.e. the non-blocking start method), the main thread cannot be used to invoke dx_server_pause/dx_server_resume. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-4) Dispatch does not detect the closure of SSL connections that are closed uncleanly
Ted Ross created DISPATCH-4: --- Summary: Dispatch does not detect the closure of SSL connections that are closed uncleanly Key: DISPATCH-4 URL: https://issues.apache.org/jira/browse/DISPATCH-4 Project: Qpid Dispatch Issue Type: Bug Affects Versions: 0.1 Reporter: Ted Ross If a client connects to the Dispatch router using SSL, an unclean (process killed) disconnect is not detected by Dispatch and resources are not returned. Connections in-the-clear do not exhibit this symptom. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-5063) Execute a program when a message arrives addressed to a specific adress
[
https://issues.apache.org/jira/browse/QPID-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross closed QPID-5063.
--
Resolution: Duplicate
Execute a program when a message arrives addressed to a specific adress
---
Key: QPID-5063
URL: https://issues.apache.org/jira/browse/QPID-5063
Project: Qpid
Issue Type: Improvement
Components: Qpid Dispatch
Environment: linux
Reporter: Sean Gallagher
Assignee: Ted Ross
Priority: Minor
Start a server (if not already running) when a message arrives at a
pre-configured address.
Broadly similar in intent to xinetd or http CGI scripts.
My application has some large jobs that execute infrequently. It would be
good if these could be run on demand rather than keeping a large process in
memory that does nothing most of the time. Having the server restart when
needed is also a good guard against resource leaks / selfish garbage
collectors.
There doesn't seem to be a convenient way to do this at present but I'm
thinking it might be added relatively easily to Dispatch Router and I suspect
many would find it useful.
Working out locks / race conditions would be tricky but one simple idea I had
would be to execute a user-supplied command line when a message arrives and
then lockout further invocations for a configurable time period. This would
give the new server time to startup and connect to Dispatch. Dispatch would
not invoke the command if a link was available to deliver the message.
A section could be added to qpid-dispatch.conf to configure this. e.g.
on-demand {
##
## deliveries to this address will trigger the command if link does not
already exist
##
to: myserver/myservice
##
## command line to run
##
run: myprogram
##
## delay after triggering the command before it may be retried (in
response to a new delivery)
##
lockout-interval: 60
}
This idea could be further developed in many directions, what I've put here
is the basics.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-5) Execute a program when a message arrives addressed to a specific address
Ted Ross created DISPATCH-5:
---
Summary: Execute a program when a message arrives addressed to a
specific address
Key: DISPATCH-5
URL: https://issues.apache.org/jira/browse/DISPATCH-5
Project: Qpid Dispatch
Issue Type: Improvement
Reporter: Ted Ross
Priority: Minor
Start a server (if not already running) when a message arrives at a
pre-configured address.
Broadly similar in intent to xinetd or http CGI scripts.
My application has some large jobs that execute infrequently. It would be good
if these could be run on demand rather than keeping a large process in memory
that does nothing most of the time. Having the server restart when needed is
also a good guard against resource leaks / selfish garbage collectors.
There doesn't seem to be a convenient way to do this at present but I'm
thinking it might be added relatively easily to Dispatch Router and I suspect
many would find it useful.
Working out locks / race conditions would be tricky but one simple idea I had
would be to execute a user-supplied command line when a message arrives and
then lockout further invocations for a configurable time period. This would
give the new server time to startup and connect to Dispatch. Dispatch would not
invoke the command if a link was available to deliver the message.
A section could be added to qpid-dispatch.conf to configure this. e.g.
on-demand
{ ## ## deliveries to this address will trigger the command if link does not
already exist ## to: myserver/myservice ## ## command line to run ## run:
myprogram ## ## delay after triggering the command before it may be retried (in
response to a new delivery) ## lockout-interval: 60 }
This idea could be further developed in many directions, what I've put here is
the basics.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-5268) Dispatch - Implement link-routing
[ https://issues.apache.org/jira/browse/QPID-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross closed QPID-5268. -- Resolution: Duplicate Dispatch - Implement link-routing - Key: QPID-5268 URL: https://issues.apache.org/jira/browse/QPID-5268 Project: Qpid Issue Type: New Feature Components: Qpid Dispatch Reporter: Ted Ross All routing is done at the message-delivery level in Dispatch. Implement link routing (at the link-attach level) as an alternative mechanism. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-6) Implement link-routing
Ted Ross created DISPATCH-6: --- Summary: Implement link-routing Key: DISPATCH-6 URL: https://issues.apache.org/jira/browse/DISPATCH-6 Project: Qpid Dispatch Issue Type: New Feature Reporter: Ted Ross All routing is done at the message-delivery level in Dispatch. Implement link routing (at the link-attach level) as an alternative mechanism. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-7) Improve message-forwarding during topology changes
Ted Ross created DISPATCH-7: --- Summary: Improve message-forwarding during topology changes Key: DISPATCH-7 URL: https://issues.apache.org/jira/browse/DISPATCH-7 Project: Qpid Dispatch Issue Type: Improvement Affects Versions: 0.1 Reporter: Ted Ross Assignee: Ted Ross When the network topology changes, messages can be silently dropped. Update the routing engine such that messages can be automatically re-tried (without participation from the endpoint) when a route is lost. If a message cannot be routed to its destination, Dispatch should do its best to return a RELEASED disposition to the original sender. Note that this issue pertains to message routing only. The failure-recovery mechanisms for link routing will be different. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-8) Message:user-id must be authenticated on ingress
Ted Ross created DISPATCH-8: --- Summary: Message:user-id must be authenticated on ingress Key: DISPATCH-8 URL: https://issues.apache.org/jira/browse/DISPATCH-8 Project: Qpid Dispatch Issue Type: Bug Affects Versions: 0.1 Reporter: Ted Ross When a message is received on an ingress link (i.e. from an originating endpoint) and the message has a user-id field in its properties, that user-id must be authenticated. At first, this means that the user-id must be the same as that which was used to authenticate the connection. There may be other means of authenticating user-ids in the future, but Dispatch must not simply pass them on unchecked. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-5269) Dispatch - Improve message-forwarding during topology changes
[ https://issues.apache.org/jira/browse/QPID-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross closed QPID-5269. -- Resolution: Duplicate Dispatch - Improve message-forwarding during topology changes - Key: QPID-5269 URL: https://issues.apache.org/jira/browse/QPID-5269 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross When the network topology changes, messages can be silently dropped. Update the routing engine such that messages can be automatically re-tried (without participation from the endpoint) when a route is lost. If a message cannot be routed to its destination, Dispatch should do its best to return a RELEASED disposition to the original sender. Note that this issue pertains to message routing only. The failure-recovery mechanisms for link routing will be different. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-5270) Dispatch - Message:user-id must be authenticated on ingress
[ https://issues.apache.org/jira/browse/QPID-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross closed QPID-5270. -- Resolution: Duplicate Dispatch - Message:user-id must be authenticated on ingress --- Key: QPID-5270 URL: https://issues.apache.org/jira/browse/QPID-5270 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Ted Ross When a message is received on an ingress link (i.e. from an originating endpoint) and the message has a user-id field in its properties, that user-id must be authenticated. At first, this means that the user-id must be the same as that which was used to authenticate the connection. There may be other means of authenticating user-ids in the future, but Dispatch must not simply pass them on unchecked. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-9) Refactor the routing fast-path to allow the insertion of an asynchronous address lookup
Ted Ross created DISPATCH-9: --- Summary: Refactor the routing fast-path to allow the insertion of an asynchronous address lookup Key: DISPATCH-9 URL: https://issues.apache.org/jira/browse/DISPATCH-9 Project: Qpid Dispatch Issue Type: Improvement Affects Versions: 0.1 Reporter: Ted Ross Assignee: Ted Ross As we introduce more sophisticated ways to look up addresses, the router fast-path needs to be able to accommodate the insertion of an asynchronous look up. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-10) Add link-cost for route computation
Ted Ross created DISPATCH-10: Summary: Add link-cost for route computation Key: DISPATCH-10 URL: https://issues.apache.org/jira/browse/DISPATCH-10 Project: Qpid Dispatch Issue Type: Improvement Affects Versions: 0.1 Reporter: Ted Ross The route computation algorithm has the ability to take link cost into consideration when choosing best paths. Inter-router links need to be configured with an optional cost metric that is fed into the routing algorithm. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-5271) Dispatch - Refactor the routing fast-path to allow the insertion of an asynchronous address lookup
[ https://issues.apache.org/jira/browse/QPID-5271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross closed QPID-5271. -- Resolution: Duplicate Dispatch - Refactor the routing fast-path to allow the insertion of an asynchronous address lookup -- Key: QPID-5271 URL: https://issues.apache.org/jira/browse/QPID-5271 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross As we introduce more sophisticated ways to look up addresses, the router fast-path needs to be able to accommodate the insertion of an asynchronous look up. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-11) Remove all the Dispatch tunables; we have no idea if they're important
Ted Ross created DISPATCH-11: Summary: Remove all the Dispatch tunables; we have no idea if they're important Key: DISPATCH-11 URL: https://issues.apache.org/jira/browse/DISPATCH-11 Project: Qpid Dispatch Issue Type: Improvement Affects Versions: 0.1 Reporter: Ted Ross A car has a simple interface: steering, gear selection, lights, wipers. Those things are important to drivers. A car also has another interface, for car mechanics: valve timing, fuel-air mix, and more stuff I'm pretending I know about. Dispatch's config is currently confronting drivers with things only car mechanics should have to care about: worker-threads, hello-interval, hello-max-age, ra-interval, remote-ls-max-age, mobile-addr-max-age. That's the wrong bias. It's much to be preferred that we, the people developing the software, discover ways to provide good defaults that don't require tunables. Then, only when we face a particular need and no way to handle it seamlessly, should we consider exposing config for it. Build it for drivers, not car mechanics. http://stackoverflow.com/questions/150355/programmatically-find-the-number-of-cores-on-a-machine -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-11) Remove all the Dispatch tunables; we have no idea if they're important
[ https://issues.apache.org/jira/browse/DISPATCH-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-11: - Reporter: Justin Ross (was: Ted Ross) Remove all the Dispatch tunables; we have no idea if they're important -- Key: DISPATCH-11 URL: https://issues.apache.org/jira/browse/DISPATCH-11 Project: Qpid Dispatch Issue Type: Improvement Affects Versions: 0.1 Reporter: Justin Ross A car has a simple interface: steering, gear selection, lights, wipers. Those things are important to drivers. A car also has another interface, for car mechanics: valve timing, fuel-air mix, and more stuff I'm pretending I know about. Dispatch's config is currently confronting drivers with things only car mechanics should have to care about: worker-threads, hello-interval, hello-max-age, ra-interval, remote-ls-max-age, mobile-addr-max-age. That's the wrong bias. It's much to be preferred that we, the people developing the software, discover ways to provide good defaults that don't require tunables. Then, only when we face a particular need and no way to handle it seamlessly, should we consider exposing config for it. Build it for drivers, not car mechanics. http://stackoverflow.com/questions/150355/programmatically-find-the-number-of-cores-on-a-machine -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-5272) Dispatch - Add link-cost for route computation
[ https://issues.apache.org/jira/browse/QPID-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross closed QPID-5272. -- Resolution: Duplicate Dispatch - Add link-cost for route computation -- Key: QPID-5272 URL: https://issues.apache.org/jira/browse/QPID-5272 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Ted Ross The route computation algorithm has the ability to take link cost into consideration when choosing best paths. Inter-router links need to be configured with an optional cost metric that is fed into the routing algorithm. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-5353) Remove all the Dispatch tunables; we have no idea if they're important
[ https://issues.apache.org/jira/browse/QPID-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross closed QPID-5353. -- Resolution: Duplicate Remove all the Dispatch tunables; we have no idea if they're important -- Key: QPID-5353 URL: https://issues.apache.org/jira/browse/QPID-5353 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Justin Ross Attachments: remove-tunables.patch A car has a simple interface: steering, gear selection, lights, wipers. Those things are important to drivers. A car also has another interface, for car mechanics: valve timing, fuel-air mix, and more stuff I'm pretending I know about. Dispatch's config is currently confronting drivers with things only car mechanics should have to care about: worker-threads, hello-interval, hello-max-age, ra-interval, remote-ls-max-age, mobile-addr-max-age. That's the wrong bias. It's much to be preferred that we, the people developing the software, discover ways to provide good defaults that don't require tunables. Then, only when we face a particular need and no way to handle it seamlessly, should we consider exposing config for it. Build it for drivers, not car mechanics. http://stackoverflow.com/questions/150355/programmatically-find-the-number-of-cores-on-a-machine -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-12) Exercise qdstat in the tests
Ted Ross created DISPATCH-12: Summary: Exercise qdstat in the tests Key: DISPATCH-12 URL: https://issues.apache.org/jira/browse/DISPATCH-12 Project: Qpid Dispatch Issue Type: Improvement Affects Versions: 0.1 Reporter: Ted Ross Make sure qdstat is executed in various ways when the developer runs make test. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-5368) Dispatch - Exercise qdstat in the tests
[ https://issues.apache.org/jira/browse/QPID-5368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross closed QPID-5368. -- Resolution: Duplicate Dispatch - Exercise qdstat in the tests --- Key: QPID-5368 URL: https://issues.apache.org/jira/browse/QPID-5368 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Justin Ross Assignee: Justin Ross Make sure qdstat is executed in various ways when the developer runs make test. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-12) Exercise qdstat in the tests
[ https://issues.apache.org/jira/browse/DISPATCH-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-12: - Reporter: Justin Ross (was: Ted Ross) Exercise qdstat in the tests Key: DISPATCH-12 URL: https://issues.apache.org/jira/browse/DISPATCH-12 Project: Qpid Dispatch Issue Type: Improvement Affects Versions: 0.1 Reporter: Justin Ross Make sure qdstat is executed in various ways when the developer runs make test. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-13) Enhance qdstat tool to link usage to users
Ted Ross created DISPATCH-13: Summary: Enhance qdstat tool to link usage to users Key: DISPATCH-13 URL: https://issues.apache.org/jira/browse/DISPATCH-13 Project: Qpid Dispatch Issue Type: Improvement Affects Versions: 0.1 Reporter: Ted Ross The qdstat tool (and the management schema for Dispatch) should be enhanced such that admins can trace address usage (links) to connections/hosts/users. Specifically: - Provide source and target information for links - Identify the connection associated with links - Investigate providing remote pid/process information in connections (like qpidd) -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-5382) Dispatch - Enhance qdstat tool to link usage to users
[ https://issues.apache.org/jira/browse/QPID-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross closed QPID-5382. -- Resolution: Duplicate Dispatch - Enhance qdstat tool to link usage to users - Key: QPID-5382 URL: https://issues.apache.org/jira/browse/QPID-5382 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Ted Ross The qdstat tool (and the management schema for Dispatch) should be enhanced such that admins can trace address usage (links) to connections/hosts/users. Specifically: - Provide source and target information for links - Identify the connection associated with links - Investigate providing remote pid/process information in connections (like qpidd) -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-13) Enhance qdstat tool to link usage to users
[ https://issues.apache.org/jira/browse/DISPATCH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-13: - Reporter: Justin Ross (was: Ted Ross) Enhance qdstat tool to link usage to users -- Key: DISPATCH-13 URL: https://issues.apache.org/jira/browse/DISPATCH-13 Project: Qpid Dispatch Issue Type: Improvement Affects Versions: 0.1 Reporter: Justin Ross The qdstat tool (and the management schema for Dispatch) should be enhanced such that admins can trace address usage (links) to connections/hosts/users. Specifically: - Provide source and target information for links - Identify the connection associated with links - Investigate providing remote pid/process information in connections (like qpidd) -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-13) Enhance qdstat tool to link usage to users
[ https://issues.apache.org/jira/browse/DISPATCH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-13: - Reporter: Ted Ross (was: Justin Ross) Enhance qdstat tool to link usage to users -- Key: DISPATCH-13 URL: https://issues.apache.org/jira/browse/DISPATCH-13 Project: Qpid Dispatch Issue Type: Improvement Affects Versions: 0.1 Reporter: Ted Ross The qdstat tool (and the management schema for Dispatch) should be enhanced such that admins can trace address usage (links) to connections/hosts/users. Specifically: - Provide source and target information for links - Identify the connection associated with links - Investigate providing remote pid/process information in connections (like qpidd) -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-14) Review and improve the qdstat command line UI
[ https://issues.apache.org/jira/browse/DISPATCH-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-14: - Reporter: Justin Ross (was: Ted Ross) Review and improve the qdstat command line UI - Key: DISPATCH-14 URL: https://issues.apache.org/jira/browse/DISPATCH-14 Project: Qpid Dispatch Issue Type: Improvement Affects Versions: 0.1 Reporter: Justin Ross Qdstat has some possible UI issues I'd like to discuss. - sasl-mechanism - Is that supposed to be a mechanism list? In any case, it doesn't appear to be used at the moment. - ssl-certificate - For consistency with the terms used in qdrouterd's config file, I think this should be ssl-cert - bus - For me the particular meaning of bus is still hazy, so I'd like to hear more about it. In addition to these questions, there are some other small consistency issues that I will address directly with commits. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-14) Review and improve the qdstat command line UI
Ted Ross created DISPATCH-14: Summary: Review and improve the qdstat command line UI Key: DISPATCH-14 URL: https://issues.apache.org/jira/browse/DISPATCH-14 Project: Qpid Dispatch Issue Type: Improvement Affects Versions: 0.1 Reporter: Ted Ross Qdstat has some possible UI issues I'd like to discuss. - sasl-mechanism - Is that supposed to be a mechanism list? In any case, it doesn't appear to be used at the moment. - ssl-certificate - For consistency with the terms used in qdrouterd's config file, I think this should be ssl-cert - bus - For me the particular meaning of bus is still hazy, so I'd like to hear more about it. In addition to these questions, there are some other small consistency issues that I will address directly with commits. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-5466) Dispatch - Add different forwarding semantics for addresses
[ https://issues.apache.org/jira/browse/QPID-5466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross closed QPID-5466. -- Resolution: Duplicate Dispatch - Add different forwarding semantics for addresses --- Key: QPID-5466 URL: https://issues.apache.org/jira/browse/QPID-5466 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Ted Ross Assignee: Ted Ross (For version 0.2) At present, if there are multiple receivers for a particular address, Dispatch delivers a copy of each message to all of the receivers. This feature adds the ability to by-configuration deliver messages to only one of those receivers. The configuration for this feature is per-address and defines two settings: - _fanout_ is either Multiple or Single (and a placeholder for Group). Multiple fanout means all subscribers receive each message. Single fanout means that only one subscriber receives the message. - _bias_ controls how single-fanout is treated. The following values for bias are provided: -- _Closest_ - each message is delivered to the closest/least-cost subscriber. -- _Spread_ - messages are spread indeterminately across all subscribers. -- _Latency_ - (not implemented yet) Messages are delivered in a balanced way to all subscribers based on the latency of acknowledgements. This mode attempts to keep all subscribers equally fed with incoming messages. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-5391) Dispatch - Review and improve the qdstat command line UI
[ https://issues.apache.org/jira/browse/QPID-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross closed QPID-5391. -- Resolution: Duplicate Dispatch - Review and improve the qdstat command line UI Key: QPID-5391 URL: https://issues.apache.org/jira/browse/QPID-5391 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Reporter: Justin Ross Assignee: Justin Ross Qdstat has some possible UI issues I'd like to discuss. - sasl-mechanism - Is that supposed to be a mechanism list? In any case, it doesn't appear to be used at the moment. - ssl-certificate - For consistency with the terms used in qdrouterd's config file, I think this should be ssl-cert - bus - For me the particular meaning of bus is still hazy, so I'd like to hear more about it. In addition to these questions, there are some other small consistency issues that I will address directly with commits. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-15) Add different forwarding semantics for addresses
Ted Ross created DISPATCH-15: Summary: Add different forwarding semantics for addresses Key: DISPATCH-15 URL: https://issues.apache.org/jira/browse/DISPATCH-15 Project: Qpid Dispatch Issue Type: Improvement Affects Versions: 0.1 Reporter: Ted Ross Assignee: Ted Ross Fix For: 0.2 At present, if there are multiple receivers for a particular address, Dispatch delivers a copy of each message to all of the receivers. This feature adds the ability to by-configuration deliver messages to only one of those receivers. The configuration for this feature is per-address and defines two settings: - _fanout_ is either Multiple or Single (and a placeholder for Group). Multiple fanout means all subscribers receive each message. Single fanout means that only one subscriber receives the message. - _bias_ controls how single-fanout is treated. The following values for bias are provided: -- _Closest_ - each message is delivered to the closest/least-cost subscriber. -- _Spread_ - messages are spread indeterminately across all subscribers. -- _Latency_ - (not implemented yet) Messages are delivered in a balanced way to all subscribers based on the latency of acknowledgements. This mode attempts to keep all subscribers equally fed with incoming messages. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-5491) Improve logging for dispatch
[ https://issues.apache.org/jira/browse/QPID-5491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross closed QPID-5491. -- Resolution: Duplicate Improve logging for dispatch Key: QPID-5491 URL: https://issues.apache.org/jira/browse/QPID-5491 Project: Qpid Issue Type: Improvement Components: Qpid Dispatch Environment: The following improvements are planned. 1. Add support for configuring logging on a per module basis. 2. File support including log rotation. 3. Syslog support. Reporter: Rajith Attapattu Assignee: Rajith Attapattu Fix For: Future Attachments: log_patch.3 -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-16) Improve logging for dispatch
[ https://issues.apache.org/jira/browse/DISPATCH-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-16: - Reporter: Rajith Attapattu (was: Ted Ross) Improve logging for dispatch Key: DISPATCH-16 URL: https://issues.apache.org/jira/browse/DISPATCH-16 Project: Qpid Dispatch Issue Type: Improvement Affects Versions: 0.1 Reporter: Rajith Attapattu Assignee: Rajith Attapattu Fix For: 0.2 The following improvements are planned. 1. Add support for configuring logging on a per module basis. 2. File support including log rotation. 3. Syslog support. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-17) Build system ignores user-defined CFLAGS
Ted Ross created DISPATCH-17: Summary: Build system ignores user-defined CFLAGS Key: DISPATCH-17 URL: https://issues.apache.org/jira/browse/DISPATCH-17 Project: Qpid Dispatch Issue Type: Bug Affects Versions: 0.1 Reporter: Ted Ross Fix For: 0.2 When setting the CFLAGS in CMakeLists.txt, the system should append the project's flags to those defined by the user when setting the value. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-17) Build system ignores user-defined CFLAGS
[ https://issues.apache.org/jira/browse/DISPATCH-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-17: - Reporter: Darryl L. Pierce (was: Ted Ross) Build system ignores user-defined CFLAGS Key: DISPATCH-17 URL: https://issues.apache.org/jira/browse/DISPATCH-17 Project: Qpid Dispatch Issue Type: Bug Affects Versions: 0.1 Reporter: Darryl L. Pierce Fix For: 0.2 When setting the CFLAGS in CMakeLists.txt, the system should append the project's flags to those defined by the user when setting the value. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-5517) Build system ignores user-defined CFLAGS
[ https://issues.apache.org/jira/browse/QPID-5517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross closed QPID-5517. -- Resolution: Duplicate Build system ignores user-defined CFLAGS Key: QPID-5517 URL: https://issues.apache.org/jira/browse/QPID-5517 Project: Qpid Issue Type: Bug Components: Qpid Dispatch Reporter: Darryl L. Pierce Assignee: Darryl L. Pierce Attachments: qpid-dispatch-cflags.patch When setting the CFLAGS in CMakeLists.txt, the system should append the project's flags to those defined by the user when setting the value. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-16) Improve logging for dispatch
Ted Ross created DISPATCH-16: Summary: Improve logging for dispatch Key: DISPATCH-16 URL: https://issues.apache.org/jira/browse/DISPATCH-16 Project: Qpid Dispatch Issue Type: Improvement Affects Versions: 0.1 Reporter: Ted Ross Assignee: Rajith Attapattu Fix For: 0.2 The following improvements are planned. 1. Add support for configuring logging on a per module basis. 2. File support including log rotation. 3. Syslog support. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-5) Execute a program when a message arrives addressed to a specific address
[
https://issues.apache.org/jira/browse/DISPATCH-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated DISPATCH-5:
Reporter: Sean Gallagher (was: Ted Ross)
Execute a program when a message arrives addressed to a specific address
Key: DISPATCH-5
URL: https://issues.apache.org/jira/browse/DISPATCH-5
Project: Qpid Dispatch
Issue Type: Improvement
Reporter: Sean Gallagher
Priority: Minor
Start a server (if not already running) when a message arrives at a
pre-configured address.
Broadly similar in intent to xinetd or http CGI scripts.
My application has some large jobs that execute infrequently. It would be
good if these could be run on demand rather than keeping a large process in
memory that does nothing most of the time. Having the server restart when
needed is also a good guard against resource leaks / selfish garbage
collectors.
There doesn't seem to be a convenient way to do this at present but I'm
thinking it might be added relatively easily to Dispatch Router and I suspect
many would find it useful.
Working out locks / race conditions would be tricky but one simple idea I had
would be to execute a user-supplied command line when a message arrives and
then lockout further invocations for a configurable time period. This would
give the new server time to startup and connect to Dispatch. Dispatch would
not invoke the command if a link was available to deliver the message.
A section could be added to qpid-dispatch.conf to configure this. e.g.
on-demand
{ ## ## deliveries to this address will trigger the command if link does not
already exist ## to: myserver/myservice ## ## command line to run ## run:
myprogram ## ## delay after triggering the command before it may be retried
(in response to a new delivery) ## lockout-interval: 60 }
This idea could be further developed in many directions, what I've put here
is the basics.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-17) Build system ignores user-defined CFLAGS
[ https://issues.apache.org/jira/browse/DISPATCH-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-17: - Assignee: Darryl L. Pierce Build system ignores user-defined CFLAGS Key: DISPATCH-17 URL: https://issues.apache.org/jira/browse/DISPATCH-17 Project: Qpid Dispatch Issue Type: Bug Affects Versions: 0.1 Reporter: Darryl L. Pierce Assignee: Darryl L. Pierce Fix For: 0.2 When setting the CFLAGS in CMakeLists.txt, the system should append the project's flags to those defined by the user when setting the value. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-17) Build system ignores user-defined CFLAGS
[ https://issues.apache.org/jira/browse/DISPATCH-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-17: - Assignee: (was: Darryl L. Pierce) Build system ignores user-defined CFLAGS Key: DISPATCH-17 URL: https://issues.apache.org/jira/browse/DISPATCH-17 Project: Qpid Dispatch Issue Type: Bug Affects Versions: 0.1 Reporter: Darryl L. Pierce Fix For: 0.2 When setting the CFLAGS in CMakeLists.txt, the system should append the project's flags to those defined by the user when setting the value. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-17) Build system ignores user-defined CFLAGS
[ https://issues.apache.org/jira/browse/DISPATCH-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-17: - Assignee: Darryl L. Pierce Build system ignores user-defined CFLAGS Key: DISPATCH-17 URL: https://issues.apache.org/jira/browse/DISPATCH-17 Project: Qpid Dispatch Issue Type: Bug Affects Versions: 0.1 Reporter: Darryl L. Pierce Assignee: Darryl L. Pierce Fix For: 0.2 When setting the CFLAGS in CMakeLists.txt, the system should append the project's flags to those defined by the user when setting the value. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-18) SSL inter-router connections seem to run in-the-clear
Ted Ross created DISPATCH-18: Summary: SSL inter-router connections seem to run in-the-clear Key: DISPATCH-18 URL: https://issues.apache.org/jira/browse/DISPATCH-18 Project: Qpid Dispatch Issue Type: Bug Affects Versions: 0.1 Reporter: Ted Ross Assignee: Ted Ross Fix For: 0.2 When using SSL with client authentication in an inter-router connection, a packet trace suggests that the data is being sent in-the-clear by the client. The connection is never established. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-17) Build system ignores user-defined CFLAGS
[ https://issues.apache.org/jira/browse/DISPATCH-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-17. -- Resolution: Fixed Build system ignores user-defined CFLAGS Key: DISPATCH-17 URL: https://issues.apache.org/jira/browse/DISPATCH-17 Project: Qpid Dispatch Issue Type: Bug Affects Versions: 0.1 Reporter: Darryl L. Pierce Assignee: Darryl L. Pierce Fix For: 0.2 When setting the CFLAGS in CMakeLists.txt, the system should append the project's flags to those defined by the user when setting the value. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1) Use Target Address from the link if there is no To field in a message from a producer
[ https://issues.apache.org/jira/browse/DISPATCH-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-1. - Resolution: Fixed Fix Version/s: 0.2 Assignee: Ted Ross Use Target Address from the link if there is no To field in a message from a producer - Key: DISPATCH-1 URL: https://issues.apache.org/jira/browse/DISPATCH-1 Project: Qpid Dispatch Issue Type: Improvement Affects Versions: 0.1 Reporter: Ted Ross Assignee: Ted Ross Fix For: 0.2 When testing Dispatch against the Qpid messaging clients, messages are not properly forwarded because the clients use target.address instead of properties.to. Both cases should be supported by the router. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-19) Replace the non-standard GET with the standard QUERY
Ted Ross created DISPATCH-19: Summary: Replace the non-standard GET with the standard QUERY Key: DISPATCH-19 URL: https://issues.apache.org/jira/browse/DISPATCH-19 Project: Qpid Dispatch Issue Type: Sub-task Affects Versions: 0.1 Reporter: Ted Ross Assignee: Ted Ross The GET operation currently implemented needs to be replaced with the QUERY operation now described in the management standard (draft 4). The qsstat tool (and the tests) will also need to be converted to use the new command. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-19) Replace the non-standard GET with the standard QUERY
[ https://issues.apache.org/jira/browse/DISPATCH-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-19: - Description: The GET operation currently implemented needs to be replaced with the QUERY operation now described in the management standard (draft 4). The qdstat tool (and the tests) will also need to be converted to use the new command. was: The GET operation currently implemented needs to be replaced with the QUERY operation now described in the management standard (draft 4). The qsstat tool (and the tests) will also need to be converted to use the new command. Replace the non-standard GET with the standard QUERY Key: DISPATCH-19 URL: https://issues.apache.org/jira/browse/DISPATCH-19 Project: Qpid Dispatch Issue Type: Sub-task Affects Versions: 0.1 Reporter: Ted Ross Assignee: Ted Ross The GET operation currently implemented needs to be replaced with the QUERY operation now described in the management standard (draft 4). The qdstat tool (and the tests) will also need to be converted to use the new command. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-20) Implement the discovery operations in the agent
Ted Ross created DISPATCH-20: Summary: Implement the discovery operations in the agent Key: DISPATCH-20 URL: https://issues.apache.org/jira/browse/DISPATCH-20 Project: Qpid Dispatch Issue Type: Sub-task Affects Versions: 0.1 Reporter: Ted Ross Assignee: Ted Ross The DISCOVER-* operations have been renamed GET-* in the newest specification (draft 4). This renaming must be reflected in the implementation. A new command, GET-ATTRIBUTES has been added to allow clients to query for the attributes of a type. This also needs to be added to the implementation. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-2) Adhere to the AMQP Management Specification for remote management
[ https://issues.apache.org/jira/browse/DISPATCH-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-2: Component/s: Management Agent Adhere to the AMQP Management Specification for remote management - Key: DISPATCH-2 URL: https://issues.apache.org/jira/browse/DISPATCH-2 Project: Qpid Dispatch Issue Type: Improvement Components: Management Agent Affects Versions: 0.1 Reporter: Ted Ross Assignee: Ted Ross Qpid Dispatch should adhere as closely as possible to the emerging Management specification from the AMQP technical committee. This issue will track work and comments related to compliance with the specification. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-19) Replace the non-standard GET with the standard QUERY
[ https://issues.apache.org/jira/browse/DISPATCH-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-19: - Component/s: Management Agent Replace the non-standard GET with the standard QUERY Key: DISPATCH-19 URL: https://issues.apache.org/jira/browse/DISPATCH-19 Project: Qpid Dispatch Issue Type: Sub-task Components: Management Agent Affects Versions: 0.1 Reporter: Ted Ross Assignee: Ted Ross The GET operation currently implemented needs to be replaced with the QUERY operation now described in the management standard (draft 4). The qdstat tool (and the tests) will also need to be converted to use the new command. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-20) Implement the discovery operations in the agent
[ https://issues.apache.org/jira/browse/DISPATCH-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-20: - Component/s: Management Agent Implement the discovery operations in the agent --- Key: DISPATCH-20 URL: https://issues.apache.org/jira/browse/DISPATCH-20 Project: Qpid Dispatch Issue Type: Sub-task Components: Management Agent Affects Versions: 0.1 Reporter: Ted Ross Assignee: Ted Ross The DISCOVER-* operations have been renamed GET-* in the newest specification (draft 4). This renaming must be reflected in the implementation. A new command, GET-ATTRIBUTES has been added to allow clients to query for the attributes of a type. This also needs to be added to the implementation. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-20) Implement the discovery operations in the agent
[ https://issues.apache.org/jira/browse/DISPATCH-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-20. -- Resolution: Fixed Fix Version/s: 0.2 Implement the discovery operations in the agent --- Key: DISPATCH-20 URL: https://issues.apache.org/jira/browse/DISPATCH-20 Project: Qpid Dispatch Issue Type: Sub-task Components: Management Agent Affects Versions: 0.1 Reporter: Ted Ross Assignee: Ted Ross Fix For: 0.2 The DISCOVER-* operations have been renamed GET-* in the newest specification (draft 4). This renaming must be reflected in the implementation. A new command, GET-ATTRIBUTES has been added to allow clients to query for the attributes of a type. This also needs to be added to the implementation. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
