[jira] [Resolved] (DISPATCH-522) Performance: Defer activation and driver-awakening
[ https://issues.apache.org/jira/browse/DISPATCH-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-522. --- Resolution: Fixed > Performance: Defer activation and driver-awakening > -- > > Key: DISPATCH-522 > URL: https://issues.apache.org/jira/browse/DISPATCH-522 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Router Node >Reporter: Ted Ross >Assignee: Ted Ross > Fix For: 0.7.0 > > > The router-core thread processes batches of actions (the size of the action > list) when it begins its main loop. When there is a large volume of traffic, > these batches can be quite large (over 1000 actions has been observed). It > is likely that the large batches are settlement or disposition updates of > ranges of deliveries which Proton serializes into individual events. > Each settlement action results in a connection activation. This means that > for large batches, the same connection may be activated hundreds of times > during the processing of a single batch of actions. > This improvement makes two significant changes: > - It defers the activations until after the processing of a batch, such that > each affected connection is only activated once. > - It holds off the awakening of the driver's poll loop until it has > activated all of the connections. > This will result in far fewer calls into the driver by the core thread during > times of high traffic volume. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-522) Performance: Defer activation and driver-awakening
[ https://issues.apache.org/jira/browse/DISPATCH-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15511966#comment-15511966 ] ASF subversion and git services commented on DISPATCH-522: -- Commit 152185eb91d58a924f982191bdf95d954199c47c in qpid-dispatch's branch refs/heads/master from [~tr...@redhat.com] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=152185e ] DISPATCH-522 - Reduce the number of times the core thread invokes connection activation during times of high traffic volume. > Performance: Defer activation and driver-awakening > -- > > Key: DISPATCH-522 > URL: https://issues.apache.org/jira/browse/DISPATCH-522 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Router Node >Reporter: Ted Ross >Assignee: Ted Ross > Fix For: 0.7.0 > > > The router-core thread processes batches of actions (the size of the action > list) when it begins its main loop. When there is a large volume of traffic, > these batches can be quite large (over 1000 actions has been observed). It > is likely that the large batches are settlement or disposition updates of > ranges of deliveries which Proton serializes into individual events. > Each settlement action results in a connection activation. This means that > for large batches, the same connection may be activated hundreds of times > during the processing of a single batch of actions. > This improvement makes two significant changes: > - It defers the activations until after the processing of a batch, such that > each affected connection is only activated once. > - It holds off the awakening of the driver's poll loop until it has > activated all of the connections. > This will result in far fewer calls into the driver by the core thread during > times of high traffic volume. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-522) Performance: Defer activation and driver-awakening
Ted Ross created DISPATCH-522: - Summary: Performance: Defer activation and driver-awakening Key: DISPATCH-522 URL: https://issues.apache.org/jira/browse/DISPATCH-522 Project: Qpid Dispatch Issue Type: Improvement Components: Router Node Reporter: Ted Ross Assignee: Ted Ross Fix For: 0.7.0 The router-core thread processes batches of actions (the size of the action list) when it begins its main loop. When there is a large volume of traffic, these batches can be quite large (over 1000 actions has been observed). It is likely that the large batches are settlement or disposition updates of ranges of deliveries which Proton serializes into individual events. Each settlement action results in a connection activation. This means that for large batches, the same connection may be activated hundreds of times during the processing of a single batch of actions. This improvement makes two significant changes: - It defers the activations until after the processing of a batch, such that each affected connection is only activated once. - It holds off the awakening of the driver's poll loop until it has activated all of the connections. This will result in far fewer calls into the driver by the core thread during times of high traffic volume. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-7432) Make python management tools work over AMQP 1.0
[ https://issues.apache.org/jira/browse/QPID-7432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved QPID-7432. --- Resolution: Fixed > Make python management tools work over AMQP 1.0 > --- > > Key: QPID-7432 > URL: https://issues.apache.org/jira/browse/QPID-7432 > Project: Qpid > Issue Type: Improvement > Components: C++ Broker >Affects Versions: qpid-cpp-1.35.0 >Reporter: Alan Conway >Assignee: Alan Conway > > The qpid management tools and the qpidtoollib python library should work over > AMQP 1.0. Verify and fix any issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7432) Make python management tools work over AMQP 1.0
[ https://issues.apache.org/jira/browse/QPID-7432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15511120#comment-15511120 ] ASF subversion and git services commented on QPID-7432: --- Commit 550b62723bb6b80035961c93c05de4cbd0ab170e in qpid-cpp's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-cpp.git;h=550b627 ] QPID-7432: Make python management tools work over AMQP 1.0 Two bugs in qpid_messaging found and fixed, required for qpidtoollibs to work: - incorrect encoding of python Unicode strings, assumed default-encoding=UTF8. - bug in Message.content decoding an empty list or map body. With those fixes, the existing qpidtoollibs works with AMQP 1.0 if you use a qpid_messaging.Connection instead of a qpid.messaging.Connection. qpid_messaging implements the same API as qpid.messaging, but using SWIG over the C++ codec which supports AMQP 1.0. An existing tool can be updated to prefer qpid_messaging as follows: try: from qpid_messaging import Connection except: from qpid.messaging import Connection Or if you don't care about qpid.messaging you can simply import qpid_messaging. NOTE: qpid-route does NOT work on AMQP1.0, as it is based on an older client. Raise a new issue if that also needs to be ported to qpidtoollibs for 1.0 support. > Make python management tools work over AMQP 1.0 > --- > > Key: QPID-7432 > URL: https://issues.apache.org/jira/browse/QPID-7432 > Project: Qpid > Issue Type: Improvement > Components: C++ Broker >Affects Versions: qpid-cpp-1.35.0 >Reporter: Alan Conway >Assignee: Alan Conway > > The qpid management tools and the qpidtoollib python library should work over > AMQP 1.0. Verify and fix any issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-22) Add ability to run on Jenkins CI
[ https://issues.apache.org/jira/browse/QPIDIT-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15511102#comment-15511102 ] ASF subversion and git services commented on QPIDIT-22: --- Commit c810fc3af4d7272158c19646e4da98418afb40e6 in qpid-interop-test's branch refs/heads/master from [~kpvdr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=c810fc3 ] QPIDIT-22: Updated JMS client dependencies for JMS 2.0 > Add ability to run on Jenkins CI > > > Key: QPIDIT-22 > URL: https://issues.apache.org/jira/browse/QPIDIT-22 > Project: Apache QPID IT > Issue Type: Improvement >Reporter: Kim van der Riet >Assignee: Kim van der Riet > > Run the tests on Jenkins continuous integration system. For this to be > realized, the location of dependent components needs to be parameterized, as > they can no longer be in the usual installed locations. This includes: > * qpid-proton > * qpid-jms -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-7432) Make python management tools work over AMQP 1.0
Alan Conway created QPID-7432: - Summary: Make python management tools work over AMQP 1.0 Key: QPID-7432 URL: https://issues.apache.org/jira/browse/QPID-7432 Project: Qpid Issue Type: Improvement Components: C++ Broker Affects Versions: qpid-cpp-1.35.0 Reporter: Alan Conway Assignee: Alan Conway The qpid management tools and the qpidtoollib python library should work over AMQP 1.0. Verify and fix any issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-508) Self tests use deprecated configuration objects
[ https://issues.apache.org/jira/browse/DISPATCH-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15510963#comment-15510963 ] Ganesh Murthy commented on DISPATCH-508: Moved all deprecated references into system_tests_deprecated.py which exclusively tests deprecated items. > Self tests use deprecated configuration objects > --- > > Key: DISPATCH-508 > URL: https://issues.apache.org/jira/browse/DISPATCH-508 > Project: Qpid Dispatch > Issue Type: Bug > Components: Tests >Affects Versions: 0.6.1 >Reporter: Chuck Rolke >Assignee: Ganesh Murthy > Fix For: 0.7.0 > > > Tests use: linkRoutePattern, container, fixedAddress, waypoint. Such usage > does not aid understanding of how configuration should be done. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-508) Self tests use deprecated configuration objects
[ https://issues.apache.org/jira/browse/DISPATCH-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-508. Resolution: Fixed Fix Version/s: 0.7.0 > Self tests use deprecated configuration objects > --- > > Key: DISPATCH-508 > URL: https://issues.apache.org/jira/browse/DISPATCH-508 > Project: Qpid Dispatch > Issue Type: Bug > Components: Tests >Affects Versions: 0.6.1 >Reporter: Chuck Rolke >Assignee: Ganesh Murthy > Fix For: 0.7.0 > > > Tests use: linkRoutePattern, container, fixedAddress, waypoint. Such usage > does not aid understanding of how configuration should be done. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-508) Self tests use deprecated configuration objects
[ https://issues.apache.org/jira/browse/DISPATCH-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15510959#comment-15510959 ] ASF subversion and git services commented on DISPATCH-508: -- Commit 118518516e143815767183adbb8ef25755b2488b in qpid-dispatch's branch refs/heads/master from [~ganeshmurthy] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=1185185 ] DISPATCH-508 - Removed deprecated entities and attributes from tests and moved it all to system_tests_deprecated > Self tests use deprecated configuration objects > --- > > Key: DISPATCH-508 > URL: https://issues.apache.org/jira/browse/DISPATCH-508 > Project: Qpid Dispatch > Issue Type: Bug > Components: Tests >Affects Versions: 0.6.1 >Reporter: Chuck Rolke > > Tests use: linkRoutePattern, container, fixedAddress, waypoint. Such usage > does not aid understanding of how configuration should be done. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (DISPATCH-508) Self tests use deprecated configuration objects
[ https://issues.apache.org/jira/browse/DISPATCH-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy reassigned DISPATCH-508: -- Assignee: Ganesh Murthy > Self tests use deprecated configuration objects > --- > > Key: DISPATCH-508 > URL: https://issues.apache.org/jira/browse/DISPATCH-508 > Project: Qpid Dispatch > Issue Type: Bug > Components: Tests >Affects Versions: 0.6.1 >Reporter: Chuck Rolke >Assignee: Ganesh Murthy > > Tests use: linkRoutePattern, container, fixedAddress, waypoint. Such usage > does not aid understanding of how configuration should be done. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-509) Improve the qdrouterd.conf man page
[ https://issues.apache.org/jira/browse/DISPATCH-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15510697#comment-15510697 ] Ganesh Murthy commented on DISPATCH-509: * connectionRole and addrPort have been removed and their attributes have been moved to the referencing attributes (please look here - http://qpid.apache.org/releases/qpid-dispatch-master/qdrouterd.conf.5.html) * All deprecated attributes have been moved to the bottom of every attribute list. Deprecated entities themselves have been moved to the bottom of the page (please see here - http://qpid.apache.org/releases/qpid-dispatch-master/qdrouterd.conf.5.html) * Examples have been modified to use new syntax > Improve the qdrouterd.conf man page > --- > > Key: DISPATCH-509 > URL: https://issues.apache.org/jira/browse/DISPATCH-509 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Documentation >Affects Versions: 0.6.1 >Reporter: Justin Ross > > * AFAICT, the addrPort and connectionRole annotation sections are not useful > to end users; the only one that people care about as an independent entity is > sslProfile > * A lot of space is spent documenting deprecated attributes, often first, > before the recommended ones; perhaps we should not document the deprecated > ones at all, or move them to a dedicated section > * The examples at the beginning use deprecated attribute syntax > * The router section mixes important attributes (id, mode) with a bunch of > tweakables; these are all presented as having equal importance; I recommend a > wholly distinct location for all the low-level knobs that users should not > have to care about -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1293) Support username and password in electron go binding
[ https://issues.apache.org/jira/browse/PROTON-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15510675#comment-15510675 ] Alan Conway commented on PROTON-1293: - Glad to hear it! Please don't be shy about reporting issues or asking on the dev@qpid list. I'm rather fond of the Go binding so any excuse to work on it is welcome. Also I'd someday like to bring the concurrent API ideas back to other bindings, so it's good to hear how hard/easy you find it to use in practice. NB: the "go get" version will be out of date for a while till we sort out some compatibility issues with the latest C library, so use the Git repo or source releases in the meantime. > Support username and password in electron go binding > > > Key: PROTON-1293 > URL: https://issues.apache.org/jira/browse/PROTON-1293 > Project: Qpid Proton > Issue Type: Improvement > Components: go-binding >Affects Versions: 0.15.0 >Reporter: Richard Laos >Assignee: Alan Conway >Priority: Minor > Fix For: 0.15.0 > > > It appears that the electron api does not support a username and password as > part of an amqp connection. However maybe the example just needs to included > this if it is supported. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPIDJMS-209) Failover Transport can hold completion of operations that it doesn't need to when the connection fails
[ https://issues.apache.org/jira/browse/QPIDJMS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved QPIDJMS-209. -- Resolution: Fixed > Failover Transport can hold completion of operations that it doesn't need to > when the connection fails > -- > > Key: QPIDJMS-209 > URL: https://issues.apache.org/jira/browse/QPIDJMS-209 > Project: Qpid JMS > Issue Type: Bug > Components: qpid-jms-client >Affects Versions: 0.11.0 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Minor > Fix For: 0.20.0 > > > When the connection fails during invocation of an operation the handler > doesn't trigger calls to check if the operation can complete in the offline > state leading to stalls waiting for reconnect when the operation can just > complete. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-209) Failover Transport can hold completion of operations that it doesn't need to when the connection fails
[ https://issues.apache.org/jira/browse/QPIDJMS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15510449#comment-15510449 ] ASF subversion and git services commented on QPIDJMS-209: - Commit cd90f6b070fe89342f805bf3ae69b6c1963575f8 in qpid-jms's branch refs/heads/master from [~tabish121] [ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=cd90f6b ] QPIDJMS-209 Update test to use correct method to clean up the Mock peer > Failover Transport can hold completion of operations that it doesn't need to > when the connection fails > -- > > Key: QPIDJMS-209 > URL: https://issues.apache.org/jira/browse/QPIDJMS-209 > Project: Qpid JMS > Issue Type: Bug > Components: qpid-jms-client >Affects Versions: 0.11.0 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Minor > Fix For: 0.20.0 > > > When the connection fails during invocation of an operation the handler > doesn't trigger calls to check if the operation can complete in the offline > state leading to stalls waiting for reconnect when the operation can just > complete. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-209) Failover Transport can hold completion of operations that it doesn't need to when the connection fails
[ https://issues.apache.org/jira/browse/QPIDJMS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15510315#comment-15510315 ] ASF subversion and git services commented on QPIDJMS-209: - Commit e9475b8677d36458649d2e9697b1e323f20bd5ae in qpid-jms's branch refs/heads/master from [~tabish121] [ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=e9475b8 ] QPIDJMS-209 Remove leftover logs used in debug > Failover Transport can hold completion of operations that it doesn't need to > when the connection fails > -- > > Key: QPIDJMS-209 > URL: https://issues.apache.org/jira/browse/QPIDJMS-209 > Project: Qpid JMS > Issue Type: Bug > Components: qpid-jms-client >Affects Versions: 0.11.0 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Minor > Fix For: 0.20.0 > > > When the connection fails during invocation of an operation the handler > doesn't trigger calls to check if the operation can complete in the offline > state leading to stalls waiting for reconnect when the operation can just > complete. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-209) Failover Transport can hold completion of operations that it doesn't need to when the connection fails
[ https://issues.apache.org/jira/browse/QPIDJMS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15510263#comment-15510263 ] ASF subversion and git services commented on QPIDJMS-209: - Commit 5bc391d014865384b51fb916fd982a45424aaa51 in qpid-jms's branch refs/heads/master from [~tabish121] [ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=5bc391d ] QPIDJMS-209 Give the operation a chance to complete on connection loss. > Failover Transport can hold completion of operations that it doesn't need to > when the connection fails > -- > > Key: QPIDJMS-209 > URL: https://issues.apache.org/jira/browse/QPIDJMS-209 > Project: Qpid JMS > Issue Type: Bug > Components: qpid-jms-client >Affects Versions: 0.11.0 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Minor > Fix For: 0.20.0 > > > When the connection fails during invocation of an operation the handler > doesn't trigger calls to check if the operation can complete in the offline > state leading to stalls waiting for reconnect when the operation can just > complete. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1293) Support username and password in electron go binding
[ https://issues.apache.org/jira/browse/PROTON-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15510253#comment-15510253 ] Richard Laos commented on PROTON-1293: -- Thank you! I was able to get this to work as expected with a PLAIN SASL authentication mech. > Support username and password in electron go binding > > > Key: PROTON-1293 > URL: https://issues.apache.org/jira/browse/PROTON-1293 > Project: Qpid Proton > Issue Type: Improvement > Components: go-binding >Affects Versions: 0.15.0 >Reporter: Richard Laos >Assignee: Alan Conway >Priority: Minor > Fix For: 0.15.0 > > > It appears that the electron api does not support a username and password as > part of an amqp connection. However maybe the example just needs to included > this if it is supported. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-207) Implement the JMS 2.0 API
[ https://issues.apache.org/jira/browse/QPIDJMS-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15510081#comment-15510081 ] ASF subversion and git services commented on QPIDJMS-207: - Commit 1daede27c01676c0b300b7af8a38475bdf19aa31 in qpid-jms's branch refs/heads/master from Robert Gemmell [ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=1daede2 ] QPIDJMS-207: consolidate a couple of tests > Implement the JMS 2.0 API > - > > Key: QPIDJMS-207 > URL: https://issues.apache.org/jira/browse/QPIDJMS-207 > Project: Qpid JMS > Issue Type: New Feature > Components: qpid-jms-client >Affects Versions: 0.11.0 >Reporter: Timothy Bish >Assignee: Timothy Bish > Fix For: 0.20.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPIDJMS-209) Failover Transport can hold completion of operations that it doesn't need to when the connection fails
Timothy Bish created QPIDJMS-209: Summary: Failover Transport can hold completion of operations that it doesn't need to when the connection fails Key: QPIDJMS-209 URL: https://issues.apache.org/jira/browse/QPIDJMS-209 Project: Qpid JMS Issue Type: Bug Components: qpid-jms-client Affects Versions: 0.11.0 Reporter: Timothy Bish Assignee: Timothy Bish Priority: Minor Fix For: 0.20.0 When the connection fails during invocation of an operation the handler doesn't trigger calls to check if the operation can complete in the offline state leading to stalls waiting for reconnect when the operation can just complete. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-521) Switch to verify qdrouterd installation
Jiri Danek created DISPATCH-521:
---
Summary: Switch to verify qdrouterd installation
Key: DISPATCH-521
URL: https://issues.apache.org/jira/browse/DISPATCH-521
Project: Qpid Dispatch
Issue Type: Improvement
Affects Versions: 0.7.0
Reporter: Jiri Danek
There should be a {{qdrouterd}} switch that can be used to verify that the
router is installed correctly. Its success should
# Give user opportunity to check that PATH is set correctly. It should print
full path to itself (qdrouterd binary) in the output.
# Print router version, so that user can check the version is correct.
# Ensure that all dynamically loaded libraries are present and qdrouterd can be
started.
# Ensure that PYTHONPATH is set correctly
Running just {{qdrouterd}} is not sufficient, because port 5672 may be
currently occupied. The command fails, even though router is installed
correctly.
Running {{qdrouterd \-h}} is also not adequate. Currently, on my machine,
qdrouterd is failing with {{Wed Sep 21 10:03:52 2016 ERROR (error) Python:
ImportError: No module named qpid_dispatch_site}} yet {{qdrouterd \-h}} is
working just fine.
I suggest adding a {{--version}} switch that would do what I listed above.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
