[jira] [Commented] (QPID-4717) QMF issue on exchange: update timestamp doesn't seem to be getting updated
[ https://issues.apache.org/jira/browse/QPID-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13625543#comment-13625543 ] Justin Ross commented on QPID-4717: --- Tested by Fraser. Approved for 0.22. QMF issue on exchange: update timestamp doesn't seem to be getting updated -- Key: QPID-4717 URL: https://issues.apache.org/jira/browse/QPID-4717 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.21 Reporter: Fraser Adams Assignee: Ted Ross Priority: Blocker Fix For: 0.23 I've just noticed an issue with QMF2 statistics on trunk (0.23). I'm pretty sure it didn't exist in 0.20 and below, but not sure about what's gone off to the 0.22 branch. The issue is that exchange object update timestamps are not being updated. The objects in question definitely have statistics updates as I'm seeing changes to msgReceives and msgRoutes but each exchange now has an _update_ts that isn't getting updated when the statistics change. This only seems to be affecting exchange objects, queue and connection objects still seem to be OK. I noticed this when I pointed the GUI at qpidd 0.23 and tried to look at the graph for qmf.default.direct msgReceives, the graph wasn't updating despite the msgReceives value updating (the graph uses the actual timestamp to derive its x index). I also tried adding console.log to display exchange._update_ts and I'm getting the same value each object update. Any idea what might have changed? I personally think this is a 0.22 blocker. It certainly prevents graphs of exchange statistics being displayed properly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4698) Fixes needed for the CMake build system when installing files.
[ https://issues.apache.org/jira/browse/QPID-4698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13625603#comment-13625603 ] Justin Ross commented on QPID-4698: --- Rejected for 0.22. It's tool late to change build metadata unless it's a blocker. Fixes needed for the CMake build system when installing files. -- Key: QPID-4698 URL: https://issues.apache.org/jira/browse/QPID-4698 Project: Qpid Issue Type: Bug Components: Build Tools Reporter: Darryl L. Pierce Assignee: Darryl L. Pierce Fix For: 0.23 Some of the installed files are going into the wrong directories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4705) [Java Broker] anonymous users are able to view and update broker configuration via the web console by default
[ https://issues.apache.org/jira/browse/QPID-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13627726#comment-13627726 ] Justin Ross commented on QPID-4705: --- Reviewed by Robbie. Approved for 0.22. [Java Broker] anonymous users are able to view and update broker configuration via the web console by default - Key: QPID-4705 URL: https://issues.apache.org/jira/browse/QPID-4705 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.18, 0.20, 0.22 Reporter: Alex Rudyy Assignee: Robbie Gemmell Priority: Blocker Fix For: 0.23 In previous releases the default configuration allowed anonymous users to view and perform a limited set of operations via the new web management interface, with ability to restrict these via the ACLs. For the 0.22 release, the broker-level configuration model has been replaced and is now entirely configurable via the web management interface, exposing additional configuration for viewing and/or manipulation that was previously either not exposed via HTTP or only read-only. Now that functionality such as configuring the used authentication providers, ports, SSL, etc can done via the web interface it should be authenticated by default, with anonymous access only being provided where the user explicitly assigns the anonymous authentication provider to the HTTP(S) port/ports in use. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4725) [Java Broker] HTTP Managament Plugin GUI doesn't show user on connection
[ https://issues.apache.org/jira/browse/QPID-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13627728#comment-13627728 ] Justin Ross commented on QPID-4725: --- Rejected for 0.22. Unless it's an important exception, improvements can't go in after Beta. [Java Broker] HTTP Managament Plugin GUI doesn't show user on connection Key: QPID-4725 URL: https://issues.apache.org/jira/browse/QPID-4725 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Rob Godfrey Assignee: Rob Godfrey Priority: Minor Fix For: 0.23 Both the Connection tab itself, and the table of connections on the VirtualHost tab fail to display the authenticated principal associated with a connection. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4734) Release builds fail on GCC 4.4.7 / Boost 1.41
[ https://issues.apache.org/jira/browse/QPID-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13633033#comment-13633033 ] Justin Ross commented on QPID-4734: --- Andrew requested this for 0.22. I've taken a look at the delta, and it's correct wrt the gcc documentation for such pragmas. One question came to mind: should we make the version less precise, instead targeting, say, 4.4? The change is harmless, and it may help users with other minor versions of gcc. Release builds fail on GCC 4.4.7 / Boost 1.41 - Key: QPID-4734 URL: https://issues.apache.org/jira/browse/QPID-4734 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.21, 0.22, 0.23 Environment: gcc 4.4.7 and boost 1.41 on RHEL 6 Reporter: Andrew Stitcher Assignee: Andrew Stitcher Fix For: 0.23 build fails with warnings turned to errors when compiling SocketTransport.cpp: These are potentially uninitialised variable warnings in boost::bind and boost::function templates and so the underlying code can't be changed by us. It appears that the cause here is either (or some combination): * The compiler's flow analysis is incorrect. * The compiler misinterprets the warning as being in the location that the template instantiation happened (our code) and so ignores the -Wno-system-headers flag which should stop it reporting warnings in the system headers. * There is an issue in the boost code. In any of these cases there is little that we can do except suppress the warning. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3584) qpid-config SPECIAL_ARGS list should include FLOW_RESUME_COUNT
[ https://issues.apache.org/jira/browse/QPID-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-3584: -- Assignee: Ted Ross qpid-config SPECIAL_ARGS list should include FLOW_RESUME_COUNT -- Key: QPID-3584 URL: https://issues.apache.org/jira/browse/QPID-3584 Project: Qpid Issue Type: Bug Components: Python Tools Affects Versions: 0.10 Environment: All - this relates to a feature that was added to qpid-config in Qpid 0.10 Reporter: Fraser Adams Assignee: Ted Ross Priority: Trivial qpid-config added a feature in 0.10 of a --argument option, a generic mechanism for passing arguments. As part of the implementation of this constants relating to specific program options are contained in a list called SPECIAL_ARGS. It looks like FLOW_RESUME_COUNT is missing from this list which causes an incorrect display with qpid-config queues e.g. qpid-config add queue test0 --flow-resume-count=10 gives test0 --flow-resume-count=10 --argument qpid.flow_resume_count=10 A trivial fix is to add FLOW_RESUME_COUNT to the SPECIAL_ARGS definition -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-1562) Better separation of 0-10 and 0-8/0-9 support in test framework
[ https://issues.apache.org/jira/browse/QPID-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed QPID-1562. - Resolution: Won't Fix Fix Version/s: JIRA Cleanup This issue has not been updated in more than a year. We've reviewed it and decided to close it, as part of an effort to keep our issue database clean and current. If this issue is still affecting you, please reopen it. See https://issues.apache.org/jira/browse/QPID-4585 for more information. Better separation of 0-10 and 0-8/0-9 support in test framework --- Key: QPID-1562 URL: https://issues.apache.org/jira/browse/QPID-1562 Project: Qpid Issue Type: Bug Components: Python Client Affects Versions: M4 Reporter: Gordon Sim Assignee: Rafael H. Schloming Priority: Minor Fix For: JIRA Cleanup From r732760 the python test suite cannot be run without either the spec refered to from qpid_config available in the expected location or the AMQP_SPEC env var set to an 0-10 format spec. Setting AMQP_SPEC to an 0-8 format spec file causes: Traceback (most recent call last): File ./run-tests, line 22, in ? from qpid.testlib import testrunner File /home/gordon/temp/python/qpid/__init__.py, line 20, in ? import spec, codec, connection, content, peer, delegate, client File /home/gordon/temp/python/qpid/connection.py, line 20, in ? import datatypes, session, socket File /home/gordon/temp/python/qpid/session.py, line 47, in ? class Session(command_invoker(SPEC)): File /home/gordon/temp/python/qpid/generator.py, line 56, in command_invoker return invoker(CommandInvoker, spec, is_command) File /home/gordon/temp/python/qpid/generator.py, line 52, in invoker (), generate(spec, invoker.__module__, predicate)) File /home/gordon/temp/python/qpid/generator.py, line 35, in generate for name, enum in spec.enums.items(): AttributeError: Spec instance has no attribute 'enums' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4585) JIRA Clean up for a number of commponents
[ https://issues.apache.org/jira/browse/QPID-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13633234#comment-13633234 ] Justin Ross commented on QPID-4585: --- The previous similar work done for java components: https://issues.apache.org/jira/browse/QPID-3469 JIRA Clean up for a number of commponents - Key: QPID-4585 URL: https://issues.apache.org/jira/browse/QPID-4585 Project: Qpid Issue Type: Task Components: C++ Broker, C++ Client, C++ Clustering, Dot Net Client, JCA, Perl Client, Python Client, Python Test Suite, Python Tools, Qpid Examples, Qpid Managment Framework, Ruby Client, WCF/C++ Client Affects Versions: JIRA Cleanup Reporter: Irina Boverman Assignee: Alan Conway Labels: cleanup Fix For: JIRA Cleanup Original Estimate: 336h Remaining Estimate: 336h Currently there are 300 unresolved and not scheduled to be resolved issues affecting these components. It will help the community to maintain focus if we can review and update them. If the issue is no longer relevant, was already resolved or unlikely to be resolved at all, the issue should be marked as resolved or closed, otherwise it should be updated with a note and/or scheduled for resolution (fix versions .21 or future). There are 155 issues created before Jan. 1, 2012, and not updated after this date. I would like to ask all to review them by March 1, 2013 and update them as needed. I would like to propose closing any issues that do not get updated by this date. Corresponding query: https://issues.apache.org/jira/issues/?filter=-4jql=project%20%3D%20QPID%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20EMPTY%20AND%20component%20in%20(%22C%2B%2B%20Broker%22%2C%20%22C%2B%2B%20Client%22%2C%20%22C%2B%2B%20Clustering%22%2C%20%22Dot%20Net%20Client%22%2C%20JCA%2C%20%22Perl%20Client%22%2C%20%22Python%20Client%22%2C%20%22Python%20Test%20Suite%22%2C%20%22Python%20Tools%22%2C%20%22Qpid%20Examples%22%2C%20%22Qpid%20Managment%20Framework%22%2C%20%22Ruby%20Client%22%2C%20%22WCF%2FC%2B%2B%20Client%22)%20AND%20updated%20%3C%3D%202012-01-01%20ORDER%20BY%20priority%20DESC Please also take time to review any other open issues that are either assigned to you or were created by you, and take appropriate actions. Thank you for your contribution! Regards, Irina. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4585) JIRA Clean up for a number of commponents
[ https://issues.apache.org/jira/browse/QPID-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4585: -- Fix Version/s: (was: JIRA Cleanup) 0.23 JIRA Clean up for a number of commponents - Key: QPID-4585 URL: https://issues.apache.org/jira/browse/QPID-4585 Project: Qpid Issue Type: Task Components: C++ Broker, C++ Client, C++ Clustering, Dot Net Client, JCA, Perl Client, Python Client, Python Test Suite, Python Tools, Qpid Examples, Qpid Managment Framework, Ruby Client, WCF/C++ Client Affects Versions: JIRA Cleanup Reporter: Irina Boverman Assignee: Alan Conway Labels: cleanup Fix For: 0.23 Original Estimate: 336h Remaining Estimate: 336h Currently there are 300 unresolved and not scheduled to be resolved issues affecting these components. It will help the community to maintain focus if we can review and update them. If the issue is no longer relevant, was already resolved or unlikely to be resolved at all, the issue should be marked as resolved or closed, otherwise it should be updated with a note and/or scheduled for resolution (fix versions .21 or future). There are 155 issues created before Jan. 1, 2012, and not updated after this date. I would like to ask all to review them by March 1, 2013 and update them as needed. I would like to propose closing any issues that do not get updated by this date. Corresponding query: https://issues.apache.org/jira/issues/?filter=-4jql=project%20%3D%20QPID%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20EMPTY%20AND%20component%20in%20(%22C%2B%2B%20Broker%22%2C%20%22C%2B%2B%20Client%22%2C%20%22C%2B%2B%20Clustering%22%2C%20%22Dot%20Net%20Client%22%2C%20JCA%2C%20%22Perl%20Client%22%2C%20%22Python%20Client%22%2C%20%22Python%20Test%20Suite%22%2C%20%22Python%20Tools%22%2C%20%22Qpid%20Examples%22%2C%20%22Qpid%20Managment%20Framework%22%2C%20%22Ruby%20Client%22%2C%20%22WCF%2FC%2B%2B%20Client%22)%20AND%20updated%20%3C%3D%202012-01-01%20ORDER%20BY%20priority%20DESC Please also take time to review any other open issues that are either assigned to you or were created by you, and take appropriate actions. Thank you for your contribution! Regards, Irina. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-1553) qpidd does not output an error when certain invalid command-line arguments are used
[ https://issues.apache.org/jira/browse/QPID-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-1553: -- Assignee: michael goulish qpidd does not output an error when certain invalid command-line arguments are used --- Key: QPID-1553 URL: https://issues.apache.org/jira/browse/QPID-1553 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: M4 Reporter: Robert Greig Assignee: michael goulish Priority: Minor Certain command-line options that are invalid do not trigger warnings for the user. For example, on Windows it is reasonable for a user to type: qpidd /help but that just starts the broker. This could mean that typos go unnoticed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-1553) qpidd does not output an error when certain invalid command-line arguments are used
[ https://issues.apache.org/jira/browse/QPID-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-1553: -- Issue Type: Improvement (was: Bug) qpidd does not output an error when certain invalid command-line arguments are used --- Key: QPID-1553 URL: https://issues.apache.org/jira/browse/QPID-1553 Project: Qpid Issue Type: Improvement Components: C++ Broker Affects Versions: M4 Reporter: Robert Greig Assignee: michael goulish Priority: Minor Certain command-line options that are invalid do not trigger warnings for the user. For example, on Windows it is reasonable for a user to type: qpidd /help but that just starts the broker. This could mean that typos go unnoticed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-1423) Logging to Windows Event Log - needs specific message def
[ https://issues.apache.org/jira/browse/QPID-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed QPID-1423. - Resolution: Won't Fix Fix Version/s: JIRA Cleanup This issue has not been updated in more than a year. We've reviewed it and decided to close it, as part of an effort to keep our issue database clean and current. If this issue is still affecting you, please reopen it. See https://issues.apache.org/jira/browse/QPID-4585 for more information. Logging to Windows Event Log - needs specific message def - Key: QPID-1423 URL: https://issues.apache.org/jira/browse/QPID-1423 Project: Qpid Issue Type: Bug Components: C++ Broker, C++ Client Environment: Windows Reporter: Steve Huston Assignee: Steve Huston Priority: Minor Fix For: JIRA Cleanup Original Estimate: 24h Remaining Estimate: 24h When logging to the Windows Event Log, there's not a specific message def file for Qpid, so when looking in the event viewer, there's a lot of text about not having enough information to view the message, etc., then the real qpid message appears at the end of that text. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4585) JIRA Clean up for a number of commponents
[ https://issues.apache.org/jira/browse/QPID-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13633240#comment-13633240 ] Justin Ross commented on QPID-4585: --- Irina's post to the devel list summarizing the effort: http://qpid.2158936.n2.nabble.com/Qpid-JIRA-Cleanup-td7588638.html#a7589317 JIRA Clean up for a number of commponents - Key: QPID-4585 URL: https://issues.apache.org/jira/browse/QPID-4585 Project: Qpid Issue Type: Task Components: C++ Broker, C++ Client, C++ Clustering, Dot Net Client, JCA, Perl Client, Python Client, Python Test Suite, Python Tools, Qpid Examples, Qpid Managment Framework, Ruby Client, WCF/C++ Client Affects Versions: JIRA Cleanup Reporter: Irina Boverman Assignee: Alan Conway Labels: cleanup Fix For: 0.23 Original Estimate: 336h Remaining Estimate: 336h Currently there are 300 unresolved and not scheduled to be resolved issues affecting these components. It will help the community to maintain focus if we can review and update them. If the issue is no longer relevant, was already resolved or unlikely to be resolved at all, the issue should be marked as resolved or closed, otherwise it should be updated with a note and/or scheduled for resolution (fix versions .21 or future). There are 155 issues created before Jan. 1, 2012, and not updated after this date. I would like to ask all to review them by March 1, 2013 and update them as needed. I would like to propose closing any issues that do not get updated by this date. Corresponding query: https://issues.apache.org/jira/issues/?filter=-4jql=project%20%3D%20QPID%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20EMPTY%20AND%20component%20in%20(%22C%2B%2B%20Broker%22%2C%20%22C%2B%2B%20Client%22%2C%20%22C%2B%2B%20Clustering%22%2C%20%22Dot%20Net%20Client%22%2C%20JCA%2C%20%22Perl%20Client%22%2C%20%22Python%20Client%22%2C%20%22Python%20Test%20Suite%22%2C%20%22Python%20Tools%22%2C%20%22Qpid%20Examples%22%2C%20%22Qpid%20Managment%20Framework%22%2C%20%22Ruby%20Client%22%2C%20%22WCF%2FC%2B%2B%20Client%22)%20AND%20updated%20%3C%3D%202012-01-01%20ORDER%20BY%20priority%20DESC Please also take time to review any other open issues that are either assigned to you or were created by you, and take appropriate actions. Thank you for your contribution! Regards, Irina. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-923) Python tests are not spec version aware
[ https://issues.apache.org/jira/browse/QPID-923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed QPID-923. Resolution: Won't Fix Fix Version/s: JIRA Cleanup This issue has not been updated in more than a year. We've reviewed it and decided to close it, as part of an effort to keep our issue database clean and current. If this issue is still affecting you, please reopen it. See https://issues.apache.org/jira/browse/QPID-4585 for more information. Python tests are not spec version aware --- Key: QPID-923 URL: https://issues.apache.org/jira/browse/QPID-923 Project: Qpid Issue Type: Bug Components: Python Test Suite Affects Versions: M2.1 Reporter: Martin Ritchie Assignee: Rafael H. Schloming Priority: Minor Fix For: JIRA Cleanup Summary: When running the M2.1 python run-tests script the default is to use the 0-8 Spec file. This means that the unbind tests fail as there is no unbind methods in 0-8. The tests need to be aware that they are not valid for the specified spec file. The tests should print a 'S' to signify that they have been skipped rather than a pass '.' or an 'E'rror. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-1772) Management - The exclusive attribute remains on a queue after exclusive ownership is released
[ https://issues.apache.org/jira/browse/QPID-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed QPID-1772. - Resolution: Won't Fix Fix Version/s: JIRA Cleanup This issue has not been updated in more than a year. We've reviewed it and decided to close it, as part of an effort to keep our issue database clean and current. If this issue is still affecting you, please reopen it. See https://issues.apache.org/jira/browse/QPID-4585 for more information. Management - The exclusive attribute remains on a queue after exclusive ownership is released --- Key: QPID-1772 URL: https://issues.apache.org/jira/browse/QPID-1772 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.5 Reporter: Ted Ross Assignee: Ted Ross Priority: Minor Fix For: JIRA Cleanup The exclusive attribute on a queue is set at declare time and never revisited thereafter. This boolean attribute must be cleared when exclusive access to the queue is released. It should also be re-set if a subsequent session gains exclusive access to the queue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-3328) Undefined reference when building with poller
[ https://issues.apache.org/jira/browse/QPID-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed QPID-3328. - Resolution: Won't Fix Fix Version/s: JIRA Cleanup This issue has not been updated in more than a year. We've reviewed it and decided to close it, as part of an effort to keep our issue database clean and current. If this issue is still affecting you, please reopen it. See https://issues.apache.org/jira/browse/QPID-4585 for more information. Undefined reference when building with poller - Key: QPID-3328 URL: https://issues.apache.org/jira/browse/QPID-3328 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.10 Environment: Linux 2.6.39-gentoo-r2 gcc 4.4.5 glibc 2.12.2 Reporter: Dmitry Potapov Priority: Minor Fix For: JIRA Cleanup Linker reports error when compiling Qpid C++ broker client with poller: qpidc-0.10/src/.libs/libqpidcommon.so: undefined reference to `qpid::sys::Poller::interrupt(qpid::sys::PollerHandle)' ... more errors Steps to reproduce: 1. wget http://www.apache.org/dyn/closer.cgi/qpid/0.10/qpid-cpp-0.10.tar.gz; 2. tar zxf qpid-cpp-0.10.tar.gz 3. cd qpidc-0.10 4. CXXFLAGS=-Wno-error ./configure --with-poller 5. make -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-3327) gcc error: dereferencing pointer 'pretmp.2013' does break strict-aliasing rules
[ https://issues.apache.org/jira/browse/QPID-3327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed QPID-3327. - Resolution: Won't Fix Fix Version/s: JIRA Cleanup This issue has not been updated in more than a year. We've reviewed it and decided to close it, as part of an effort to keep our issue database clean and current. If this issue is still affecting you, please reopen it. See https://issues.apache.org/jira/browse/QPID-4585 for more information. gcc error: dereferencing pointer 'pretmp.2013' does break strict-aliasing rules - Key: QPID-3327 URL: https://issues.apache.org/jira/browse/QPID-3327 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.10 Environment: Linux 2.6.39-gentoo-r2 gcc 4.4.5 glibc 2.12.2 Reporter: Dmitry Potapov Priority: Minor Fix For: JIRA Cleanup GCC reports error when compiling Qpid C++ broker client: ../include/qpid/framing/DeliveryProperties.h: In member function 'bool qpid::client::LocalQueueImpl::get(qpid::client::Message, qpid::sys::Duration)': ../include/qpid/framing/DeliveryProperties.h:38: error: dereferencing pointer 'pretmp.2013' does break strict-aliasing rules ... more errors Steps to reproduce: 1. wget http://www.apache.org/dyn/closer.cgi/qpid/0.10/qpid-cpp-0.10.tar.gz; 2. tar zxf qpid-cpp-0.10.tar.gz 3. cd qpidc-0.10 4. ./configure 5. make -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-3223) Setting TTL to 0 internally set it forever
[ https://issues.apache.org/jira/browse/QPID-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed QPID-3223. - Resolution: Won't Fix Fix Version/s: JIRA Cleanup This issue has not been updated in more than a year. We've reviewed it and decided to close it, as part of an effort to keep our issue database clean and current. If this issue is still affecting you, please reopen it. See https://issues.apache.org/jira/browse/QPID-4585 for more information. Setting TTL to 0 internally set it forever -- Key: QPID-3223 URL: https://issues.apache.org/jira/browse/QPID-3223 Project: Qpid Issue Type: Bug Components: C++ Client Reporter: Jerome Ajot Priority: Minor Labels: ttl Fix For: JIRA Cleanup Setting the Message TTL is 0 via the Client API, sets it internally to never expired. The AMQP spec (0.10 and 1.0) does not define zero as a special value. An easy way to fix this will be to define TTL as a boost::optionalboost::uint64_t, that way it can be optional/never expire and have 0 as valid value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3262) Remove support for archaic Boost version 103200
[ https://issues.apache.org/jira/browse/QPID-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-3262: -- Fix Version/s: 0.23 Remove support for archaic Boost version 103200 --- Key: QPID-3262 URL: https://issues.apache.org/jira/browse/QPID-3262 Project: Qpid Issue Type: Bug Components: C++ Broker Reporter: michael j. goulish Assignee: michael j. goulish Priority: Minor Fix For: 0.23 Remove support for antique Boost version -- no one wants this any more, and I promised. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3262) Remove support for archaic Boost version 103200
[ https://issues.apache.org/jira/browse/QPID-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-3262: -- Issue Type: Improvement (was: Bug) Remove support for archaic Boost version 103200 --- Key: QPID-3262 URL: https://issues.apache.org/jira/browse/QPID-3262 Project: Qpid Issue Type: Improvement Components: C++ Broker Reporter: michael j. goulish Assignee: michael j. goulish Priority: Minor Fix For: 0.23 Remove support for antique Boost version -- no one wants this any more, and I promised. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-3250) Deletion of queues/exchanges invalidates resolution cache
[ https://issues.apache.org/jira/browse/QPID-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed QPID-3250. - Resolution: Won't Fix Fix Version/s: JIRA Cleanup This issue has not been updated in more than a year. We've reviewed it and decided to close it, as part of an effort to keep our issue database clean and current. If this issue is still affecting you, please reopen it. See https://issues.apache.org/jira/browse/QPID-4585 for more information. Deletion of queues/exchanges invalidates resolution cache - Key: QPID-3250 URL: https://issues.apache.org/jira/browse/QPID-3250 Project: Qpid Issue Type: Bug Components: Python Client Affects Versions: 0.10, 0.11 Reporter: Gordon Sim Priority: Minor Fix For: JIRA Cleanup The python client maintains a resolution cache per connection that tracks the type (if any) of a given node on the broker it is connected to. If nodes that have already been resolved are subsequently deleted, the cache becomes stale. This can result in some unexpected behaviour. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-2592) Builds w/ TR1-capable compiler have some clashes with Boost
[ https://issues.apache.org/jira/browse/QPID-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed QPID-2592. - Resolution: Won't Fix Fix Version/s: JIRA Cleanup This issue has not been updated in more than a year. We've reviewed it and decided to close it, as part of an effort to keep our issue database clean and current. If this issue is still affecting you, please reopen it. See https://issues.apache.org/jira/browse/QPID-4585 for more information. Builds w/ TR1-capable compiler have some clashes with Boost --- Key: QPID-2592 URL: https://issues.apache.org/jira/browse/QPID-2592 Project: Qpid Issue Type: Bug Components: C++ Broker, C++ Client Affects Versions: 0.7 Reporter: Steve Huston Priority: Minor Fix For: JIRA Cleanup Trying a build with Visual Studio 2010 tripped a few places where the new TR1 classes/algorithms clash with the Boost equivalents from which they were inspired. Although I saw this with VS2010, it's not a Windows/VS-specific problem - that's just where it was seen first. Ones I've seen... cpp/src/tests/SessionState.cpp use of ref, bind cpp/src/tests/perftest.cpp use of bind This could be remedied by removing the using boost statements (and/or using std statements). Also possible is a config check for presence of the TR1 stuff and use the TR1 if available, else Boost. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-2457) configure.ac doesn't check all required headers - breaks Debian derivatives.
[ https://issues.apache.org/jira/browse/QPID-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed QPID-2457. - Resolution: Won't Fix Fix Version/s: JIRA Cleanup This issue has not been updated in more than a year. We've reviewed it and decided to close it, as part of an effort to keep our issue database clean and current. If this issue is still affecting you, please reopen it. See https://issues.apache.org/jira/browse/QPID-4585 for more information. configure.ac doesn't check all required headers - breaks Debian derivatives. Key: QPID-2457 URL: https://issues.apache.org/jira/browse/QPID-2457 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Environment: Ubuntu 8.04 - hardy Reporter: Neil Wilson Priority: Minor Fix For: JIRA Cleanup Debian splits out the libboost library into several separate packages. The configure.ac needs to check more headers in boost to make sure that the Debian splits are catered for. (Note these may be Debian dependencies that aren't handled properly - however if configure handles it, it looks better than a make failure). Headers that currently fail are: boost/program_options.hpp boost/serialization/split_member.hpp boost/filesystem/operations.hpp boost/filesystem/path.hpp boost/test/unit_test.hpp boost/regex.hpp -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-3529) Errors During Compilation on SLES 11.1
[ https://issues.apache.org/jira/browse/QPID-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed QPID-3529. - Resolution: Won't Fix Fix Version/s: JIRA Cleanup This issue has not been updated in more than a year. We've reviewed it and decided to close it, as part of an effort to keep our issue database clean and current. If this issue is still affecting you, please reopen it. See https://issues.apache.org/jira/browse/QPID-4585 for more information. Errors During Compilation on SLES 11.1 -- Key: QPID-3529 URL: https://issues.apache.org/jira/browse/QPID-3529 Project: Qpid Issue Type: Bug Components: C++ Broker, C++ Client Affects Versions: 0.12 Environment: SUSE Linux Enterprise Server 11 SP1 (x86_64) gcc version 4.3.4 [gcc-4_3-branch revision 152973] (SUSE Linux) boost version 1.36.0-11.17 Reporter: Kevin Douglas Priority: Minor Labels: compilation, compile Fix For: JIRA Cleanup I'm creating this ticket at the request of Steve on behalf of Greg based on the mailing list discussion that started with this thread: http://mail-archives.apache.org/mod_mbox/qpid-users/201108.mbox/%3c662ffefc60e8d040b9b1b4ac67c186ce0bbd0...@alpmlvem11.e2k.ad.ge.com%3E - I downloaded the latest release 0.12. During compilation on SLES11.1 (boost 1.36) the following error occurs: libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../include -I../include -I. -I=. -Werror -pedantic -Wall -Wextra -Wno-shadow -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long -Wvolatile-register-var -Winvalid-pch -Wno-system-headers -Woverloaded-virtual -DQPID_LIBEXEC_DIR=\/usr/lib64/qpid\ -DBOOST_FILESYSTEM_VERSION=2 -O2 -g -m64 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -MT qpid/management/Mutex.lo -MD -MP -MF qpid/management/.deps/Mutex.Tpo -c qpid/management/Mutex.cpp -fPIC -DPIC -o qpid/management/.libs/Mutex.o ./qpid/RefCounted.h: In function 'void boost::intrusive_ptr_release(const T*) [with T = boost::exception_detail::error_info_container]': /usr/include/boost/intrusive_ptr.hpp:101: instantiated from 'boost::intrusive_ptrT::~intrusive_ptr() [with T = boost::exception_detail::error_info_container]' /usr/include/boost/exception/exception.hpp:60: instantiated from here ./qpid/RefCounted.h:59: error: 'qpid::RefCounted' is not a base of 'const boost::exception_detail::error_info_container' ./qpid/RefCounted.h: In function 'void boost::intrusive_ptr_add_ref(const T*) [with T = boost::exception_detail::error_info_container]': /usr/include/boost/intrusive_ptr.hpp:96: instantiated from 'boost::intrusive_ptrT::intrusive_ptr(const boost::intrusive_ptrT) [with T = boost::exception_detail::error_info_container]' /usr/include/boost/exception/exception.hpp:64: instantiated from here ./qpid/RefCounted.h:57: error: 'qpid::RefCounted' is not a base of 'const boost::exception_detail::error_info_container' - The problem seems related to this change: http://svn.apache.org/viewvc/qpid/trunk/qpid/cpp/src/qpid/RefCounted.h?r1=1101181r2=1101180pathrev=1101181 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3470) ACL handling and documentation differ
[
https://issues.apache.org/jira/browse/QPID-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-3470:
--
Assignee: Chuck Rolke
ACL handling and documentation differ
-
Key: QPID-3470
URL: https://issues.apache.org/jira/browse/QPID-3470
Project: Qpid
Issue Type: Bug
Components: C++ Broker, Documentation
Affects Versions: 0.12
Environment: Debian GNU Linux, 32 and 64 bit
Reporter: Cajus Pollmeier
Assignee: Chuck Rolke
Priority: Minor
The documentation states:
{quote}
user = username[/domain[@realm]]
user-list = user1 user2 user3 ...
group-name-list = group1 group2 group3 ...
group group-name = [user-list] [group-name-list]
{quote}
But the code does not support group nesting. An exception is thrown,
detailing that stuff behind the *group* keyword needs to have a realm.
Example:
{quote}
group admins admin@QPID me@QPID
group agents amqp@QPID
group clients whatever@QPID
group event-publisher agents admins
group event-consumer clients admins
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-1983) Python examples hung on Mac OSX
[ https://issues.apache.org/jira/browse/QPID-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed QPID-1983. - Resolution: Won't Fix Fix Version/s: JIRA Cleanup This issue has not been updated in more than a year. We've reviewed it and decided to close it, as part of an effort to keep our issue database clean and current. If this issue is still affecting you, please reopen it. See https://issues.apache.org/jira/browse/QPID-4585 for more information. Python examples hung on Mac OSX --- Key: QPID-1983 URL: https://issues.apache.org/jira/browse/QPID-1983 Project: Qpid Issue Type: Test Components: Qpid Examples Affects Versions: 0.5 Environment: Mac OS X 10.5.7 Hardware Overview: Model Name: MacBook Pro Model Identifier: MacBookPro4,1 Processor Name: Intel Core 2 Duo Processor Speed:2.4 GHz Number Of Processors: 1 Total Number Of Cores: 2 L2 Cache: 3 MB Memory: 4 GB Bus Speed: 800 MHz Boot ROM Version: MBP41.00C1.B03 SMC Version (system): 1.27f2 Serial Number (system): W88222HKYJZ Sudden Motion Sensor: State: Enabled Reporter: Chee-wai Ho Priority: Minor Fix For: JIRA Cleanup Attachments: hello-world-0-8, hello-world-0-9 I downloaded the python qpid libraries from thew qpid web site. I did a run-tests and had the following result ./run-tests .. -- Ran 126 tests in 45.567s OK Next, I ran the ./hello_world example. The script is hung. There no activity on the logs. The script seem to be stuck at conn.start() The broker was started successfully. In the logs, it says 2009-07-14 11:16:43,827 INFO [main] server.Main (Main.java:387) - Qpid.AMQP listening on non-SSL address 0.0.0.0/0.0.0.0:5672 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2022) Bug in C# request-response example client program
[ https://issues.apache.org/jira/browse/QPID-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2022: -- Assignee: Chuck Rolke Bug in C# request-response example client program - Key: QPID-2022 URL: https://issues.apache.org/jira/browse/QPID-2022 Project: Qpid Issue Type: Bug Components: Qpid Examples Environment: VS 2008, Windows XP Reporter: Jan Matti Assignee: Chuck Rolke Priority: Minor Original Estimate: 5m Remaining Estimate: 5m instead string response_queue = client + session.getName(); you must write ASCIIEncoding enc = new ASCIIEncoding(); string response_queue = client + enc.GetString(session.getName()); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-2166) Memory leak in C++ Windows client - AsynchConnector
[ https://issues.apache.org/jira/browse/QPID-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed QPID-2166. - Resolution: Won't Fix Fix Version/s: JIRA Cleanup This issue has not been updated in more than a year. We've reviewed it and decided to close it, as part of an effort to keep our issue database clean and current. If this issue is still affecting you, please reopen it. See https://issues.apache.org/jira/browse/QPID-4585 for more information. Memory leak in C++ Windows client - AsynchConnector --- Key: QPID-2166 URL: https://issues.apache.org/jira/browse/QPID-2166 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.6 Environment: Windows Reporter: Steve Huston Assignee: Steve Huston Priority: Minor Fix For: JIRA Cleanup Simple example to set up a connection, session and declare a queue yields a memory leak reported by Purify: Distribution of leaked blocks 80 bytes from 1 block of 80 bytes (0x026b9978) Allocation location new(UINT) [f:\dd\vctools\crt_bld\self_x86\crt\src\new.cpp:57] qpid::sys::AsynchConnector::create(Socket::sys::qpid const,shared_ptrPoller::sys::qpid::boost,basic_stringchar,char_traitschar::std,allocatorchar::std::std,WORD,function1void,Socket::sys::qpid const::boost,function3void,Socket::sys::qpid const,int,basic_stringchar,char_traitschar::std,allocatorchar::std::std const::boost) [C:\ACE\EXPORTED\QPID\QCREATE\RELEASE\QPIDCOMMON.DLL] main [c:\ace\exported\qpid\qcreate\qcreate.cpp:43] _tmainCRTStartup [f:\dd\vctools\crt_bld\self_x86\crt\src\crtexe.c:586] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-1734) Garbled error messages on Windows example programs
[ https://issues.apache.org/jira/browse/QPID-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed QPID-1734. - Resolution: Won't Fix Fix Version/s: JIRA Cleanup This issue has not been updated in more than a year. We've reviewed it and decided to close it, as part of an effort to keep our issue database clean and current. If this issue is still affecting you, please reopen it. See https://issues.apache.org/jira/browse/QPID-4585 for more information. Garbled error messages on Windows example programs -- Key: QPID-1734 URL: https://issues.apache.org/jira/browse/QPID-1734 Project: Qpid Issue Type: Bug Components: Qpid Examples Environment: Windows XP SP3 Visual C++ 9.0 Reporter: Pete MacKinnon Fix For: JIRA Cleanup Some of the example programs on Windows have garbled error messages returned from the Windows broker. For example, the following should be an auth error from the broker: C:\devel\redhat\mrg\qpid\qpid\cpp\examples\request-responseserver connec2t0i0o9n--mfaorr-c1e3d :1 1U:n1s3u:p5p9o rwteadr nmiencgh aBnrioskmer -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3357) Broker should purge more aggressively before invoking queue limit policy
[ https://issues.apache.org/jira/browse/QPID-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-3357: -- Assignee: Ken Giusti Broker should purge more aggressively before invoking queue limit policy Key: QPID-3357 URL: https://issues.apache.org/jira/browse/QPID-3357 Project: Qpid Issue Type: Bug Components: C++ Broker Reporter: Andy Goldstein Assignee: Ken Giusti When enqueuing a message, the broker checks the message/byte count in the queue and ensures the new message will not violate the queue's limits and limit policy (reject, ring, etc). It does not take into account messages still in the queue that have expired, which could result in a message being dropped or the oldest message being removed unnecessarily. For example, create a queue with a max count of 2 messages. Send 1 message with no ttl. Send a 2nd message with a small ttl e.g. 1 second. Wait longer then the ttl so the 2nd message expires. Try to send a 3rd message to the queue. If the queue policy is reject, you will get an exception that the queue is full. If the queue policy is ring, it will discard the 1st message (no ttl so unexpired) to make room for the new message. One possible solution would be to try to purge expired messages more aggressively, e.g. when an enqueue would exceed the limit, try to purge any expired messages, and then re-check the limit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4733) Fix cmake installation of init scripts
[ https://issues.apache.org/jira/browse/QPID-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13634046#comment-13634046 ] Justin Ross commented on QPID-4733: --- Reviewed by Darryl. Approved for 0.22. Fix cmake installation of init scripts -- Key: QPID-4733 URL: https://issues.apache.org/jira/browse/QPID-4733 Project: Qpid Issue Type: Bug Reporter: Alan Conway Assignee: Alan Conway The cmake build does not correctly substitute and install the init scripts qpidd and qpidd-primary. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-4750) Python example server fails
Justin Ross created QPID-4750:
-
Summary: Python example server fails
Key: QPID-4750
URL: https://issues.apache.org/jira/browse/QPID-4750
Project: Qpid
Issue Type: Bug
Components: Python Client
Reporter: Justin Ross
Assignee: Justin Ross
Priority: Minor
[root@hostname api]# /usr/share/doc/python-qpid-0.10/examples/api/server
ADDR;{create:always}
Traceback (most recent call last):
File /usr/share/doc/python-qpid-0.10/examples/api/server, line 90, in ?
except ReceiveError, e:
NameError: name 'ReceiveError' is not defined
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4750) Python example server fails
[
https://issues.apache.org/jira/browse/QPID-4750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13635209#comment-13635209
]
Justin Ross commented on QPID-4750:
---
To reproduce:
[root@hostname api]# /usr/share/doc/python-qpid-0.10/examples/api/server
ADDR;{create:always}
Traceback (most recent call last):
File /usr/share/doc/python-qpid-0.10/examples/api/server, line 90, in ?
except ReceiveError, e:
NameError: name 'ReceiveError' is not defined
Fixed at http://svn.apache.org/viewvc?view=revisionrevision=1469345 .
Python example server fails
-
Key: QPID-4750
URL: https://issues.apache.org/jira/browse/QPID-4750
Project: Qpid
Issue Type: Bug
Components: Python Client
Reporter: Justin Ross
Assignee: Justin Ross
Priority: Minor
[root@hostname api]# /usr/share/doc/python-qpid-0.10/examples/api/server
ADDR;{create:always}
Traceback (most recent call last):
File /usr/share/doc/python-qpid-0.10/examples/api/server, line 90, in ?
except ReceiveError, e:
NameError: name 'ReceiveError' is not defined
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-4750) Python example server fails
[
https://issues.apache.org/jira/browse/QPID-4750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross resolved QPID-4750.
---
Resolution: Fixed
Fix Version/s: 0.23
Fixed with a patch courtesy of Ernie Allen.
Python example server fails
-
Key: QPID-4750
URL: https://issues.apache.org/jira/browse/QPID-4750
Project: Qpid
Issue Type: Bug
Components: Python Client
Reporter: Justin Ross
Assignee: Justin Ross
Priority: Minor
Fix For: 0.23
[root@hostname api]# /usr/share/doc/python-qpid-0.10/examples/api/server
ADDR;{create:always}
Traceback (most recent call last):
File /usr/share/doc/python-qpid-0.10/examples/api/server, line 90, in ?
except ReceiveError, e:
NameError: name 'ReceiveError' is not defined
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4734) Release builds fail on GCC 4.4.7 / Boost 1.41
[ https://issues.apache.org/jira/browse/QPID-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13635699#comment-13635699 ] Justin Ross commented on QPID-4734: --- Reviewed by me. Approved for 0.22. Release builds fail on GCC 4.4.7 / Boost 1.41 - Key: QPID-4734 URL: https://issues.apache.org/jira/browse/QPID-4734 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.21, 0.22, 0.23 Environment: gcc 4.4.7 and boost 1.41 on RHEL 6 Reporter: Andrew Stitcher Assignee: Andrew Stitcher Fix For: 0.23 build fails with warnings turned to errors when compiling SocketTransport.cpp: These are potentially uninitialised variable warnings in boost::bind and boost::function templates and so the underlying code can't be changed by us. It appears that the cause here is either (or some combination): * The compiler's flow analysis is incorrect. * The compiler misinterprets the warning as being in the location that the template instantiation happened (our code) and so ignores the -Wno-system-headers flag which should stop it reporting warnings in the system headers. * There is an issue in the boost code. In any of these cases there is little that we can do except suppress the warning. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4724) qpid-cpp-0.22-rc1 RHEL6 cmake issues
[ https://issues.apache.org/jira/browse/QPID-4724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4724: -- Assignee: Darryl L. Pierce qpid-cpp-0.22-rc1 RHEL6 cmake issues Key: QPID-4724 URL: https://issues.apache.org/jira/browse/QPID-4724 Project: Qpid Issue Type: Bug Components: Perl Client Affects Versions: 0.22 Environment: RHEL6 Reporter: Jimmy Jones Assignee: Darryl L. Pierce Running mkdir BLD; cd BLD; cmake .. -- Could NOT find PerlLibs (missing: PERL_LIBRARY PERL_INCLUDE_PATH) -- Configuring incomplete, errors occurred! should it autodetect this (automake does)? If then run: cmake .. -DPERL_LIBRARY=/usr/lib64/perl5/CORE/libperl.so -DPERL_INCLUDE_PATH=/usr/lib64/perl5 errors with: -- Found Perl: /usr/bin/perl -- Found PerlLibs: /usr/lib64/perl5/CORE/libperl.so CMake Error at bindings/CMakeLists.txt:62 (string): string sub-command REPLACE requires four arguments. CMake Error at bindings/qpid/perl/CMakeLists.txt:38 (install): install FILES given no DESTINATION! -- Configuring incomplete, errors occurred! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4771) Add --broker and --sasl-mechanism command line options to qpid-tool
[ https://issues.apache.org/jira/browse/QPID-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4771: -- Assignee: Justin Ross Add --broker and --sasl-mechanism command line options to qpid-tool Key: QPID-4771 URL: https://issues.apache.org/jira/browse/QPID-4771 Project: Qpid Issue Type: Bug Components: Python Tools Reporter: Ernest Allen Assignee: Justin Ross For consistency across the python tools, qpid-tool needs to support the --broker and --sasl-mechanism command line options. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-4771) Add --broker and --sasl-mechanism command line options to qpid-tool
[ https://issues.apache.org/jira/browse/QPID-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross resolved QPID-4771. --- Resolution: Fixed Fix Version/s: 0.23 http://svn.apache.org/viewvc?view=revisionrevision=1471120 Patch courtesy of Ernie Allen. Add --broker and --sasl-mechanism command line options to qpid-tool Key: QPID-4771 URL: https://issues.apache.org/jira/browse/QPID-4771 Project: Qpid Issue Type: Bug Components: Python Tools Reporter: Ernest Allen Assignee: Justin Ross Fix For: 0.23 Attachments: bz710429.patch For consistency across the python tools, qpid-tool needs to support the --broker and --sasl-mechanism command line options. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4771) Add --broker and --sasl-mechanism command line options to qpid-tool
[ https://issues.apache.org/jira/browse/QPID-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4771: -- Issue Type: Improvement (was: Bug) Add --broker and --sasl-mechanism command line options to qpid-tool Key: QPID-4771 URL: https://issues.apache.org/jira/browse/QPID-4771 Project: Qpid Issue Type: Improvement Components: Python Tools Reporter: Ernest Allen Assignee: Justin Ross Fix For: 0.23 Attachments: bz710429.patch For consistency across the python tools, qpid-tool needs to support the --broker and --sasl-mechanism command line options. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-4772) Message sent by python producer can't be read with java consumer
[ https://issues.apache.org/jira/browse/QPID-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross resolved QPID-4772. --- Resolution: Fixed Fix Version/s: 0.23 Assignee: Justin Ross http://svn.apache.org/viewvc?view=revisionrevision=1471146 Patch courtesy of Ernie Allen. Message sent by python producer can't be read with java consumer Key: QPID-4772 URL: https://issues.apache.org/jira/browse/QPID-4772 Project: Qpid Issue Type: Bug Components: Python Tools Reporter: Ernest Allen Assignee: Justin Ross Fix For: 0.23 Attachments: bz696919.patch The java consumer app assumes messages without an explicit content_type are text/plain. The python spout app needs to set the content_type to text/plain unless a map is provided. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-4140) receiver.unsettled() throws exception
[
https://issues.apache.org/jira/browse/QPID-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross resolved QPID-4140.
---
Resolution: Fixed
Fix Version/s: 0.23
Assignee: Justin Ross
http://svn.apache.org/viewvc?view=revisionrevision=1471150
Patch courtesy of Ernie Allen.
receiver.unsettled() throws exception
-
Key: QPID-4140
URL: https://issues.apache.org/jira/browse/QPID-4140
Project: Qpid
Issue Type: Bug
Components: Python Client
Affects Versions: 0.16
Environment: python-qpid-0.16-1.fc16.noarch
qpid-tools-0.16-1.fc16.1.noarch
qpid-cpp-server-0.16-1.fc16.1.i686
Reporter: Joshua Wulf
Assignee: Justin Ross
Fix For: 0.23
Attachments: unsettled.py
[jwulf@radhe unsettled]$ python unsettled.py
Traceback (most recent call last):
File unsettled.py, line 12, in module
msgs=rx.unsettled()
File string, line 6, in unsettled
File /usr/lib/python2.7/site-packages/qpid/messaging/endpoints.py, line
986, in unsettled
return len([m for m in self.acked if m._receiver is self])
AttributeError: 'Receiver' object has no attribute 'acked'
Reproducer:
import sys
from qpid.messaging import *
connection=Connection(localhost:5672)
connection.open()
try:
ssn=connection.session()
rx=ssn.receiver(test; {create:always})
tx=ssn.sender(test)
tx.send(hello)
rx.fetch()
msgs=rx.unsettled()
print msgs
ssn.acknowledge()
finally:
connection.close()
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-2453) Python messaging client unusable after receiving a malformed message
[ https://issues.apache.org/jira/browse/QPID-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross resolved QPID-2453. --- Resolution: Fixed Fix Version/s: 0.23 http://svn.apache.org/viewvc?view=revisionrevision=1471158 Patch courtesy of Ernie Allen. Python messaging client unusable after receiving a malformed message Key: QPID-2453 URL: https://issues.apache.org/jira/browse/QPID-2453 Project: Qpid Issue Type: Bug Components: Python Client Reporter: Ted Ross Fix For: 0.23 Attachments: python-tests.patch, qpid-2453.patch, test.py Description of problem: This bug is in reference to the new messaging API. If the Python messaging client (qpid.messaging) receives a message which is in any way malformed (i.e. improper UTF8 encoding in strings, unknown content-type), it throws an exception on the receiver.fetch call. From this point forward, the API is unusable. Any attempt to recover or call methods in the API (session.close, connection.close, fetch on other receivers, etc.) will result in the same exception repeating itself. Version-Release number of selected component (if applicable): Development trunk. How reproducible: 100% Steps to Reproduce: 1. Produce a message with a content-type of amqp/xxx 2. Send this message to a queue 3. Set up a receiver to receive the message from the queue 4. Call fetch on the receiver Actual results: An exception is thrown and subsequent calls repeat the exception (i.e. trying to close the receiver, session, or connection). The only way out is to kill the client process. Expected/Desired results: The malformed messages should be received normally. Perhaps there should be a malformed flag on the message that can be checked, or an exception should be thrown when attempting to access the content of the message. In no case should this cause an unrecoverable condition. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-1880) The new unmanaged objects are confusing
[ https://issues.apache.org/jira/browse/QPID-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross resolved QPID-1880. --- Resolution: Won't Fix Fix Version/s: JIRA Cleanup Assignee: Ted Ross This issue has not been updated in more than a year. We've reviewed it and decided to close it, as part of an effort to keep our issue database clean and current. If this issue is still affecting you, please reopen it. See https://issues.apache.org/jira/browse/QPID-4585 for more information. The new unmanaged objects are confusing --- Key: QPID-1880 URL: https://issues.apache.org/jira/browse/QPID-1880 Project: Qpid Issue Type: Improvement Components: Qpid Managment Framework Reporter: Ian Main Assignee: Ted Ross Fix For: JIRA Cleanup IMO the newly added managed objects are confusing in that they return and look just like the managed objects, but you are unable to call methods on them, nor use eg the refresh() method to get a newly updated instance. QMF up until this point has made all objects managed and backed by an implementation. The addition of a data structure type could be very useful but I don't think it should share the same name as the managed objects around which QMF revolves. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-2144) Need consistent design / rationalized features across Python tools
[ https://issues.apache.org/jira/browse/QPID-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross resolved QPID-2144. --- Resolution: Won't Fix Fix Version/s: JIRA Cleanup Assignee: Ted Ross This issue has not been updated in more than a year. We've reviewed it and decided to close it, as part of an effort to keep our issue database clean and current. If this issue is still affecting you, please reopen it. See https://issues.apache.org/jira/browse/QPID-4585 for more information. An additional note: this one may be partially addressed by the work that's been done to use common command-line UI idioms across tools. Need consistent design / rationalized features across Python tools -- Key: QPID-2144 URL: https://issues.apache.org/jira/browse/QPID-2144 Project: Qpid Issue Type: Improvement Components: Python Tools Reporter: Jonathan Robie Assignee: Ted Ross Fix For: JIRA Cleanup The Python tools need to use similar design, and we need to consider how functionality is distributed among the tools, so we have a rational set of tools. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2197) Python testing qc_ clients available to community
[ https://issues.apache.org/jira/browse/QPID-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2197: -- Assignee: Justin Ross Python testing qc_ clients available to community - Key: QPID-2197 URL: https://issues.apache.org/jira/browse/QPID-2197 Project: Qpid Issue Type: Test Components: Python Tools Environment: testing tool Reporter: Frantisek Reznicek Assignee: Justin Ross Please find below attached python qc_ clients, which are currently used in testing qpid: qc_sender.py general sender app qc_receiver.py general receiver app qc_queue.py queue manipulation app qc_exchange.py exchange manipulation app qc_list_objects.py qpid broker qmf queue/exchange lister app MIME stream of qc_python_clients_091112.tar.bz2 goes below (seems I cannot easily attach file) ... begin-base64 664 qc_python_clients_091112.tar.bz2 QlpoOTFBWSZTWWheFegAkVx/zP7///8gAAIAAAiACGBg 3nnJOmvdmzVL7A+7X29vE0I977sNFPvat7N9u9mtttsQJsm1EhKxsgkgr21V vudfZaHcCOwZtppEAdzferfefXt9Wy3t9u9yt4++br1fEeewXBGvvW1X2rWs qztrusqZt83O7tq6j7d5t9m22tdjNvd1fZvaqndhhGuTpq576AAA++owQuff e++PPR7nbFbvdXnebWiL2wHQK7dys7zdIs29gsezju3vdz3PZvt5fTx9560A B5eh7u7Nhrcfd3lVIW3vTun0BoXo+tw8AQl3bfPR9731qfTPd9B7bfTfY33D hs7Pu8EdMzreGBJCCAJoCaNBAhtTT0nqmyRsSZTRoeiaBoaYRo00yBkZNGmT TQBIggiaTQiDKaPUUP1T1PE2pphJtT000ymgB6INABoaAAMIAASCSIRqp+ka aekap6j9FPap4k9qek9T1Q/RDFGamIP1Q/UEwARo0whoZGQHpBCkRCIMhGSY JqnmkzE1TzU2lB5TT0anqBoxB6T1Gg0NNPU0PUD0QAARJJpNNEGhpEzEniAo /SbVT9U/J6KeqbTTNU09MUBp6j1NAAepk0DQGEDQRJECATIDRJ6NJNtFU9ia n6pPTR6kyeTahpp6j1P1RAGj0gAwBMR6TQb+odX6PyD5xq0wGmhAlxQDpBQi +r0eqZFxMSAiSD6roHr9frwytVqvWWcEMqkCRYQWgQGFSyFFggUChFF/rHdM tP630w/wnpw67w5jX6cPuz9Efhjc/i74hFfvo6A8eVmWZiE2/1FqDvhH78pF tmD3e5n+iSxWP0P+S9LCm5XaGuCcF0wPNnd+Bg2p/axdEzOrtOWRsttsl8OP te5rk4T1QOiDI1IVzHb28P7M8cYPEeS5qOt6qkfPqP+bDDDmrWNw3PfHyuqN AdoIh4m5pys31JY7pxgcJMMVTqhkphZPYlSN3Fub1RYVkRTxOB5GEQTnujJv zNjghylm1+k/elEZjx+F2TUfS9noTx641MPOZOi5z+7JaDxUGGBiXCgaA95R j1o7mOHK5/3ZoNDTHziCU4GjSnLkek99036tHNR+vLlVBN4cZReTHCiCYzMJ nMDTloGMC5IR+92jgfd6Gvew2ejF2OQuY3hMZK4f7RWpQ7jgNNVuQ061DF1m jY3ykbG7I2xnFru12+WJyaSYTUxJu9cX0oYVOeT97NQZ/3664oxmoPXgIRnt /sRIb3FNMeDpwbH0DtftxQM+y41YS22GIXL5Boww+m15u16TEXjTrM5IjcgN yTslghuwOXxOrcbc3HqwzltwZ2cwDBmMmcg5Tmflk+Lrom9wMcL7YOZ7YdlU Y3ZGw1/ko1C6nNVGnBsNg4xY8xkDsI/Zcnn39TPyfd2QNMZqKj3UVP4IUoY2 yL+/fnh7Su2AJNPB91Y2EhyyOc2T1nIoYYMYeCR3b9+Nl1DnfMQPk8rFPXIf FHr0FhyPIaYS/YwKZETOJK74ppVBRIziGjI3Xtq1NP9DZFIyw34W2X3ui0vH LCow9phADkOMqOeVKEZv2m0tKVqDYZc0BlpTlfV04Na9TJ1xowf2o5psbQA2 JMPspVqIGRBMaCxaQjAPk/qPvY+4x6S3LjJ3rM16LsNm9YOzFmGpmFr/M4h2 BGwYCU2c4/Y8PqiPib6Eb7LBhlrZIzfqNj8Fk+2e5cfHQ+ltdv+uuA7CmEFL 73xld3J+5jU1jGwoaXGy+VFOB7yQGwKMGzSnK2d+pxWMrGSSd76YTw0nLwfp sRW1h0hjpYUDAmgcZHNn938Xs9TtLK21q/l/D+OZM/G5lWMPxmOP6yl1oK3U hwzdwwkSz7PcpVVX6+hFgvNJmOw6ukVOpuPvy/Lj7vTka8ajzmegITpOJ3d6 MjIpJ0EQ9kFuXtuZl+IVEwAxoqI9/x74Urynvt+a1sL+qiFCh3R3LYqyNotW 3FXjLJiHejIirxJmeJIj9EpgrfnBn2XZK4yssNmSMa2uCRSNtCclI0bcMSJL aaz9auU19ROE8kmjYxCGUIoauGnuudPi+nYWXXx1qh2XhCoDpMrqjLJpnubh yMXu2VNi0BlzLG0b0egg0MuU0cYcBVR3xsj08aNOd937NifcfbmgaDS4O9SN BjZzfuOkvixozPXA1TVh1dDrLmkNBdtiH2sxSubCqqwZERAXmGIIyKAqFoAZ 82jp98txK+2F2HRrpOaLq1YxQXYRVUHkYRFXxFpUSKFARaAAElUT2+MCkBDv YVX9EI6+Qvn+S6gsgAwgB8sEA7bUbao0dKVEvPtyifihQ6Hd5Od9XeUCh6JR NxqE2yp7feb0CH3oAD2yU3CPdCZIplxaZNQCagAaPrSouSKlIfyjhwYh7t46 hIgA4slXUtK8SUphBtAV5InhHgXmPH40KcEyEiQBaiI8oIWWAQMpUPMyIFy1 wxcykTEnmDnBpSDlshm3FziDKpExg1EXmVMgANB8UIgJhF57yimCVtNoen9r 49nw2N4+PKSwNDuwjQv7KfgCFsEXMAb9EbISnCIenpm61hjI5YMf52QGPQyN moAHYle1XCyA+MRZEbkAqA74gdGoSnzTMY8o7iHYYZB2xmo6BqBcG/KkXjo5 fA1FcNQszNYWOs/vui/Tc8LYywCeG43NR5lhTEHPGEeC8uFzyvovcO3om7Bp hdgNLc/4D7xhuRdWCwbWQZd5dNSxOd8lLUyZg8WwRnmisfnQ0DqiyzHqwUMh Q6r1ekjgXbr7vN2QoyPus6uUyy2svES6t1J1EANoHpoY1eQ3PVaWyenv4W5k za8QUghvJClJrBiY0A5vHUBwBAuo1R99rc52X+SCzma2BrH4UguHk9uNptmZ /HrqMmF9EtlXUKa8AtGHn8uqRq7NoXkx9ggeceIXI9Vbv8K6rRv1kalYDGx+ 1oXcJd6oDoCmInFWt7vVOZQ8HuDve7Z8MP4FRdadVFC4yi5dA0d6i/ErOtT4 A0cozSJnjc7nmegg2O2eU8x+EsFgh6DLdCao6nTTuQKCso+EXc9J7/HrcOpZ CeCx4f4TKy8vT5DRRJsJHKSZfoNneRzqtCEqnMDSJDruL3Ika3WFiHLTyxQq BnhkvRksEVMM2M+4o+VjDgt/bZRh4tRZDcGone/04BXtZT3JlhndisQGYaHA Nf4h0D6YDbAj5x/Hfqx6PiHm0vjcc0miU8d9w8WNkhhGlMSQ1EwzEPoY5Nsh 9hOZ5DpiaMRnKlAQSRKRd0uShM023PiMLAAPHeCizsMII8LOi1lgLAw6RpDY zz0Vb11p0Kuq0WhIXuyfTG7F/MVdMYOnIzHxDBwHJNLahygQPMnlaAjZ/My1 YR/sMwwpmICjZmRNS/hlWPJ3o8H0gdHMJXn4kcwtZxMgZQk4cYcgiHidjyMr liIU+ZqExLrrCJipTAyFZ4ISsWlx7qD5fw3KvuOSAb3o73K9g5p9hiuwkve9 DBWZIt8odlsg6WPhmUFroL5cfCNrorWY1rcPAmE0iTxfag2qXpVtMdq2qL4M ZP3sK1OMfMPaZhz0rgTPTAzQ3pp2Bxsu/0kYSE9RtKGo5XDEu3xMZbZCjNYS nDC1G8kCixWcsfPN6K84KOfVDGN6cNMiFAxro1wdFny/j/F2N8/Doq8icPio 77m7Dftbpi+PG9kLUU1EJc2TWh1tOxhFFYXqlC+RXw7o3bh6usRYy3Xv8bNV
[jira] [Updated] (QPID-3471) ACL: accept wildcards for user names
[
https://issues.apache.org/jira/browse/QPID-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-3471:
--
Assignee: Chuck Rolke
ACL: accept wildcards for user names
Key: QPID-3471
URL: https://issues.apache.org/jira/browse/QPID-3471
Project: Qpid
Issue Type: Wish
Components: C++ Broker
Affects Versions: 0.12
Environment: Debian GNU Linux, 32/64 bit
Reporter: Cajus Pollmeier
Assignee: Chuck Rolke
Priority: Minor
In some cases it would be nice to specify ACLs depending on which user name
is sending a request.
Example:
{quote}
group service admin@QPID service*@QPID
acl allow client* all queue name=client.queue.*
acl allow service consume queue name=service.queue
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3472) ACL: allow placeholder for currently logged in user
[
https://issues.apache.org/jira/browse/QPID-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-3472:
--
Assignee: Chuck Rolke
ACL: allow placeholder for currently logged in user
---
Key: QPID-3472
URL: https://issues.apache.org/jira/browse/QPID-3472
Project: Qpid
Issue Type: Wish
Components: C++ Broker
Affects Versions: 0.12
Reporter: Cajus Pollmeier
Assignee: Chuck Rolke
Priority: Minor
Make it possible to define ACLs that have an element named after the logged
in user.
Example:
{quote}
acl allow all all queue name=user.queue.%uid%
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-1766) Implemention of selector using Xquery
[ https://issues.apache.org/jira/browse/QPID-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-1766: -- Assignee: Andrew Stitcher Implemention of selector using Xquery - Key: QPID-1766 URL: https://issues.apache.org/jira/browse/QPID-1766 Project: Qpid Issue Type: Improvement Components: C++ Broker, C++ Client Environment: Linux Reporter: chenta lee Assignee: Andrew Stitcher Attachments: chenta.diff, Makefile.patch, Makefile.patch, message_selector_pytest.patch, prime_number.diff, selector_broker.patch, selector_client.patch, selector_client.patch, selector.diff, selector.diff, selector_example.zip, selector_new.diff, selector.patch, selector.patch, selector_patch_20090922.diff, selector_pytest.diff I implemented the message selector for C++ broker and client using Xquery. I will attach an example later. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3276) Connection Memory leaks
[
https://issues.apache.org/jira/browse/QPID-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-3276:
--
Assignee: Chuck Rolke
Connection Memory leaks
---
Key: QPID-3276
URL: https://issues.apache.org/jira/browse/QPID-3276
Project: Qpid
Issue Type: Bug
Components: C++ Broker, C++ Client
Affects Versions: 0.8, 0.10
Environment: windows broker,windows client
Reporter: creator wang
Assignee: Chuck Rolke
Priority: Critical
code:
while(1)
{
Connection connection;
connection.open(host,port);
conect.close();
}
when use this code run in VS2008 on windows,
and connect to windows broker,memory leaks very fast;
but connect to linux broker ,no memory leaks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3276) Connection Memory leaks
[
https://issues.apache.org/jira/browse/QPID-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-3276:
--
Labels: memory-leak (was: )
Connection Memory leaks
---
Key: QPID-3276
URL: https://issues.apache.org/jira/browse/QPID-3276
Project: Qpid
Issue Type: Bug
Components: C++ Broker, C++ Client
Affects Versions: 0.8, 0.10
Environment: windows broker,windows client
Reporter: creator wang
Assignee: Chuck Rolke
Priority: Critical
Labels: memory-leak
code:
while(1)
{
Connection connection;
connection.open(host,port);
conect.close();
}
when use this code run in VS2008 on windows,
and connect to windows broker,memory leaks very fast;
but connect to linux broker ,no memory leaks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2368) Exception Thrown at qpid/sys/epoll/EpollPoller.cpp:254 Leaves Orphan File Descriptor
[
https://issues.apache.org/jira/browse/QPID-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-2368:
--
Labels: leak (was: )
Exception Thrown at qpid/sys/epoll/EpollPoller.cpp:254 Leaves Orphan File
Descriptor
Key: QPID-2368
URL: https://issues.apache.org/jira/browse/QPID-2368
Project: Qpid
Issue Type: Bug
Components: C++ Client
Affects Versions: 0.5
Environment: c++ client
Reporter: Jason Schlauch
Assignee: Andrew Stitcher
Priority: Minor
Labels: leak
While researching JIRA QPID-2367 I noticed a pileup of file descriptors in
/proc/PID/fd. I traced the creation of these descriptors back to this chunk
of code in qpid/sys/epoll/EpollPoller.cpp:
244 PollerPrivate() :
245 epollFd(::epoll_create(DefaultFds)),
246 isShutdown(false) {
247 QPID_POSIX_CHECK(epollFd);
248 ::sigemptyset(sigMask);
249 // Add always readable fd into our set (but not listening to it
yet)
250 ::epoll_event epe;
251 epe.events = 0;
252 epe.data.u64 = 0;
253 QPID_POSIX_CHECK(::epoll_ctl(epollFd, EPOLL_CTL_ADD,
alwaysReadableFd, epe));
254 }
The problem is with the second QPID_POSIX_CHECK -- a macro that throws an
exception. If an exception is thrown then the file descriptor allocated by
epollFd(::epoll_create(DefaultFds)) is left dangling. A ::close(epollFd)
would be needed in the catch() block to free it.
There are a number of functions with a similar design in EpollPoller.cpp that
might be similarly affected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2556) QMF: signed integer in map and list types incorrectly converted to unsigned 64
[
https://issues.apache.org/jira/browse/QPID-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-2556:
--
Assignee: Ken Giusti
QMF: signed integer in map and list types incorrectly converted to unsigned 64
--
Key: QPID-2556
URL: https://issues.apache.org/jira/browse/QPID-2556
Project: Qpid
Issue Type: Bug
Components: Qpid Managment Framework
Environment: Ruby QMF Console (wrapper)
Reporter: Ken Giusti
Assignee: Ken Giusti
Priority: Minor
A management object that contains a list or a map which contains a signed
integer incorrectly converts the integer to unsigned.
Example: {'a' = -1} is received at the Ruby console as {'a' =
4294967295}; ['a', -1] is received as ['a', 4294967295]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2004) On shutting down the broker, the connection state of active connections is not freed
[ https://issues.apache.org/jira/browse/QPID-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2004: -- Labels: leak (was: ) On shutting down the broker, the connection state of active connections is not freed Key: QPID-2004 URL: https://issues.apache.org/jira/browse/QPID-2004 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.5 Environment: Linux Reporter: Gordon Sim Assignee: Andrew Stitcher Priority: Minor Labels: leak The IO layer (e.g. AsynchIOHandler for TCP) creates and holds a ConnectionCodec object by pointer for each connection. All connection state is rooted in that object. However for connections that are active when the broker is shutdown, those objects and all their internal state, is not freed but is leaked. As the broker is shutting down anyway, the leak is not nice but not critical (henc I've marked this as minor rather than major). However it can lead to e.g. Queue destructors not being called etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-1939) Accept user:password in python client URL
[
https://issues.apache.org/jira/browse/QPID-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-1939:
--
Summary: Accept user:password in python client URL (was: util.URL
mis-parses username:password)
Accept user:password in python client URL
-
Key: QPID-1939
URL: https://issues.apache.org/jira/browse/QPID-1939
Project: Qpid
Issue Type: Bug
Components: Python Client
Environment: any.
Reporter: mARK bLOORE
in python/qpid/util.py, lines 84-87 are
RE = re.compile(r
# [ scheme:// ] [user [ / password ] @] host
[ :port ]
^ (?: ([^:/@]+)://)? (?: ([^:/@]+) (?: / ([^:/@]+) )? @)? ([^@:/]+)
(?: :([0-9]+))?$
, re.X)
this matches user/password in a (partial) URL. it should be user:password.
qpid.util.URL('scheme://user:pass@host:12')
raises a ValueError.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-1939) Accept user:password in python client URL
[
https://issues.apache.org/jira/browse/QPID-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-1939:
--
Issue Type: Improvement (was: Bug)
Accept user:password in python client URL
-
Key: QPID-1939
URL: https://issues.apache.org/jira/browse/QPID-1939
Project: Qpid
Issue Type: Improvement
Components: Python Client
Environment: any.
Reporter: mARK bLOORE
in python/qpid/util.py, lines 84-87 are
RE = re.compile(r
# [ scheme:// ] [user [ / password ] @] host
[ :port ]
^ (?: ([^:/@]+)://)? (?: ([^:/@]+) (?: / ([^:/@]+) )? @)? ([^@:/]+)
(?: :([0-9]+))?$
, re.X)
this matches user/password in a (partial) URL. it should be user:password.
qpid.util.URL('scheme://user:pass@host:12')
raises a ValueError.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-1896) No-auth Windows broker fails client connection with Selected mechanism not supported
[
https://issues.apache.org/jira/browse/QPID-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross resolved QPID-1896.
---
Resolution: Duplicate
The diff suggested by Gordon was introduced as part of the fix for QPID-2979.
No-auth Windows broker fails client connection with Selected mechanism not
supported
--
Key: QPID-1896
URL: https://issues.apache.org/jira/browse/QPID-1896
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Environment: Windows XP SP 3, VC++ 9.0
Reporter: Pete MacKinnon
Assignee: Steve Huston
Attachments: windows-sasl-noauth.patch
If a client offers any non-empty auth mechanism (e.g., PLAIN), the windows
C++ broker will fail to start/tune the connection with Selected mechanism
not supported eventhough it has authorization disabled (--auth=no).
void ConnectionHandler::start(const FieldTable /*serverProps*/, const Array
mechanisms, const Array /*locales*/)
{
checkState(NOT_STARTED, INVALID_STATE_START);
setState(NEGOTIATING);
sasl = SaslFactory::getInstance().create(*this);
std::string mechlist;
bool chosenMechanismSupported = mechanism.empty();
for (Array::const_iterator i = mechanisms.begin(); i != mechanisms.end();
++i) {
if (!mechanism.empty() mechanism == (*i)-getstd::string()) {
chosenMechanismSupported = true;
mechlist = (*i)-getstd::string() + SPACE + mechlist;
} else {
if (i != mechanisms.begin()) mechlist += SPACE;
mechlist += (*i)-getstd::string();
}
}
if (!chosenMechanismSupported) {
fail(Selected mechanism not supported: + mechanism);
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-1939) Accept user:password in python client URL
[
https://issues.apache.org/jira/browse/QPID-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-1939:
--
Priority: Minor (was: Major)
Accept user:password in python client URL
-
Key: QPID-1939
URL: https://issues.apache.org/jira/browse/QPID-1939
Project: Qpid
Issue Type: Improvement
Components: Python Client
Environment: any.
Reporter: mARK bLOORE
Priority: Minor
in python/qpid/util.py, lines 84-87 are
RE = re.compile(r
# [ scheme:// ] [user [ / password ] @] host
[ :port ]
^ (?: ([^:/@]+)://)? (?: ([^:/@]+) (?: / ([^:/@]+) )? @)? ([^@:/]+)
(?: :([0-9]+))?$
, re.X)
this matches user/password in a (partial) URL. it should be user:password.
qpid.util.URL('scheme://user:pass@host:12')
raises a ValueError.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-1895) qpidc: Solaris 10 Build Incorrectly Assumes Sun Compiler
[ https://issues.apache.org/jira/browse/QPID-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-1895: -- Assignee: Cliff Jansen qpidc: Solaris 10 Build Incorrectly Assumes Sun Compiler Key: QPID-1895 URL: https://issues.apache.org/jira/browse/QPID-1895 Project: Qpid Issue Type: Bug Components: Build Tools, C++ Broker, C++ Client Affects Versions: 0.5 Environment: Solaris 10 Sparcv9 GCC-4.3.2 (Blastwave) Boost-1.38.0 Reporter: Rob Riggs Assignee: Cliff Jansen When building on Solaris 10/sparcv9 with GCC-4.3.2, the autoconf system adds -lCrun and $(SUN_CC_RUNTIMELIBS) to the linker args. These are compiler-dependent libraries, not OS-specific ones. This is only appropriate when compiling with Sun Studio. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-2136) tests_0-9.QueueTests.test_unbind_* reuses exclusive queues
[
https://issues.apache.org/jira/browse/QPID-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross resolved QPID-2136.
---
Resolution: Won't Fix
Fix Version/s: JIRA Cleanup
Assignee: Rafael H. Schloming
This issue has not been updated in more than a year. We've reviewed
it and decided to close it, as part of an effort to keep our issue
database clean and current. If this issue is still affecting you,
please reopen it.
See https://issues.apache.org/jira/browse/QPID-4585 for more
information.
tests_0-9.QueueTests.test_unbind_* reuses exclusive queues
--
Key: QPID-2136
URL: https://issues.apache.org/jira/browse/QPID-2136
Project: Qpid
Issue Type: Bug
Components: Python Test Suite
Reporter: Michael Bridgen
Assignee: Rafael H. Schloming
Fix For: JIRA Cleanup
The test_unbind_{direct, topic, fanout, headers} tests all go through the
method unbind_test, which declares two exclusive queues. Since they are
exclusive, and not explicitly deleted after the test, the next such test can
fail with a 405 RESOURCE_LOCKED.
In AMQP 0-9 the exclusive queues should be deleted when the connection is
closed (which happens in TestBase.tearDown). I would prefer not to rely on
this though, since there is a race between the server deleting the queue and
the next test running.
The solution is to register the queues to be explicitly deleted after the
test is run:
Index: tests_0-9/queue.py
===
--- tests_0-9/queue.py (revision 822337)
+++ tests_0-9/queue.py (working copy)
@@ -40,8 +40,8 @@
#bind two queues and consume from them
channel = self.channel
-channel.queue_declare(queue=queue-1, exclusive=True)
-channel.queue_declare(queue=queue-2, exclusive=True)
+self.queue_declare(queue=queue-1, exclusive=True)
+self.queue_declare(queue=queue-2, exclusive=True)
channel.basic_consume(queue=queue-1, consumer_tag=queue-1,
no_ack=True)
channel.basic_consume(queue=queue-2, consumer_tag=queue-2,
no_ack=True)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-2129) GSSAPI auth. with broker issue
[ https://issues.apache.org/jira/browse/QPID-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross resolved QPID-2129. --- Resolution: Won't Fix Fix Version/s: JIRA Cleanup This issue has not been updated in more than a year. We've reviewed it and decided to close it, as part of an effort to keep our issue database clean and current. If this issue is still affecting you, please reopen it. See https://issues.apache.org/jira/browse/QPID-4585 for more information. GSSAPI auth. with broker issue -- Key: QPID-2129 URL: https://issues.apache.org/jira/browse/QPID-2129 Project: Qpid Issue Type: Bug Components: C++ Broker Environment: SVN rev. 819819 on Fedora 11. Reporter: Arjun Roy Assignee: Ted Ross Fix For: JIRA Cleanup Original Estimate: 4h Remaining Estimate: 4h Using qpidd with ovirt. Ovirt uses kerberos/gssapi for authentication. The following is a description of what happens when a ruby console tries to connect: Connecting to amqp://srv.ovirt-demo.com:5672 Console Connection Established... 2009-10-01 20:35:10 warning Exception received from broker: unauthorized-access: unauthorized-access: authorised user id : qpidd/srv.ovirt-demo.com@QPID but user id in message declared as qpidd/srv.ovirt-demo@ovirt-demo.com (qpid/broker/SemanticState.cpp:385) [caused by 11 \x00:\x00] 2009-10-01 20:35:10 error Session Exception during message-transfer: unauthorized-access: unauthorized-access: authorised user id : qpidd/srv.ovirt-demo.com@QPID but user id in message declared as qpidd/srv.ovirt-demo@ovirt-demo.com (qpid/broker/SemanticState.cpp:385) terminate called after throwing an instance of 'qpid::framing::UnauthorizedAccessException' what(): unauthorized-access: unauthorized-access: authorised user id : qpidd/srv.ovirt-demo.com@QPID but user id in message declared as qpidd/srv.ovirt-demo@ovirt-demo.com (qpid/broker/SemanticState.cpp:385) Aborted Expected behavior: qpidd should use principal qpidd/srv.ovirt-demo@ovirt-demo.com instead of qpidd/srv.ovirt-demo.com@QPID. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-2088) any service on windows vista linking with c++ qpid client (common clinet) and calling CoInitializeEx to use COM fails to start with Error 1053 ...
[ https://issues.apache.org/jira/browse/QPID-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross resolved QPID-2088. --- Resolution: Won't Fix Fix Version/s: JIRA Cleanup Assignee: Chuck Rolke This issue has not been updated in more than a year. We've reviewed it and decided to close it, as part of an effort to keep our issue database clean and current. If this issue is still affecting you, please reopen it. See https://issues.apache.org/jira/browse/QPID-4585 for more information. any service on windows vista linking with c++ qpid client (common clinet) and calling CoInitializeEx to use COM fails to start with Error 1053 ... -- Key: QPID-2088 URL: https://issues.apache.org/jira/browse/QPID-2088 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.5 Environment: Windows Vista Reporter: Nicolae Claudius Assignee: Chuck Rolke Fix For: JIRA Cleanup Original Estimate: 336h Remaining Estimate: 336h Steps that reproduce the problem: 1. Create an skeleton widows service ( with main() , ServiceMain(int argc, char** argv) , InitService() , ControlHandler(DWORD request) ) i used the template here: http://www.devx.com/cplus/Article/9857 2. Add to the linker the qpid libs (common.lib and client.lib) in Project - Properties - Linker ( include path and libs ) 3. Call CoInitializeEx to initialize windows COM with your desired parameters (any of them for our purpose), anywhere in your program (for example in main or servicemain) 4. Register the service with the following console command sc create your_service_name binPath= C:\\path_to_your_compiled_exe\your_service.exe 4. Open services.msc from run or console, and start your service (right click - start) *** At this point the service tries to start but after about 2 seconds fails with the error: Error 1053: The service did not respond to the start or control request in a timeley fashion NOTICE The error is *only* on Windows Vista, on Windows XP works as desired (Notice that you only have to link the libs not necesarily use qpid functions, strange...) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2182) Default exchange binding lost on broker restart
[ https://issues.apache.org/jira/browse/QPID-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2182: -- Assignee: Kim van der Riet (was: Steve Huston) Default exchange binding lost on broker restart --- Key: QPID-2182 URL: https://issues.apache.org/jira/browse/QPID-2182 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Environment: Client and broker running on Windows 7. SQL Express used for the broker store. Python 2.5 used for Python QMF management tools. Reporter: David Ingham Assignee: Kim van der Riet The default exchange binding to a durable queue is not restored on broker restart. Here are the repro steps: * Start with a clean database. * Create a durable queue, message_queue python qpid-config add queue message_queue -durable * Create a binding to message_queue from the amq_direct exchange python qpid-config bind amq.direct message_queue routing_key * Check the queues registered with the broker C:\depots\trunk\qpid\python\commandspython qpid-config -b queues Queue 'message_queue' bind [message_queue] = '' bind [routing_key] = amq.direct Queue 'reply-DINGHAM4.8724.1' bind [reply-DINGHAM4.8724.1] = '' bind [reply-DINGHAM4.8724.1] = amq.direct Queue 'topic-DINGHAM4.8724.1' bind [topic-DINGHAM4.8724.1] = '' bind [schema.#] = qpid.management bind [console.obj.*.*.org.apache.qpid.broker.agent] = qpid.management * Check the exchanges registered with the broker C:\depots\trunk\qpid\python\commandspython qpid-config -b exchanges Exchange '' (direct) bind [message_queue] = message_queue bind [reply-DINGHAM4.10156.1] = reply-DINGHAM4.10156.1 bind [topic-DINGHAM4.10156.1] = topic-DINGHAM4.10156.1 Exchange 'qpid.management' (topic) bind [schema.#] = topic-DINGHAM4.10156.1 bind [console.obj.*.*.org.apache.qpid.broker.agent] = topic-DINGHAM4.10156.1 Exchange 'amq.direct' (direct) bind [routing_key] = message_queue bind [reply-DINGHAM4.10156.1] = reply-DINGHAM4.10156.1 Exchange 'amq.topic' (topic) Exchange 'amq.fanout' (fanout) Exchange 'amq.match' (headers) * Restart the broker and use qpid-config to list the queues and exchanges, I get this: C:\depots\trunk\qpid\python\commandspython qpid-config -b queues Queue 'message_queue' bind [routing_key] = amq.direct Queue 'reply-DINGHAM4.9900.1' bind [reply-DINGHAM4.9900.1] = '' bind [reply-DINGHAM4.9900.1] = amq.direct Queue 'topic-DINGHAM4.9900.1' bind [topic-DINGHAM4.9900.1] = '' bind [schema.#] = qpid.management bind [console.obj.*.*.org.apache.qpid.broker.agent] = qpid.management C:\depots\trunk\qpid\python\commandspython qpid-config -b exchanges Exchange '' (direct) bind [message_queue] = unknown bind [reply-DINGHAM4.7980.1] = reply-DINGHAM4.7980.1 bind [topic-DINGHAM4.7980.1] = topic-DINGHAM4.7980.1 Exchange 'qpid.management' (topic) bind [schema.#] = topic-DINGHAM4.7980.1 bind [console.obj.*.*.org.apache.qpid.broker.agent] = topic-DINGHAM4.7980.1 Exchange 'amq.direct' (direct) bind [routing_key] = message_queue bind [reply-DINGHAM4.7980.1] = reply-DINGHAM4.7980.1 Exchange 'amq.topic' (topic) Exchange 'amq.fanout' (fanout) Exchange 'amq.match' (headers) * Note how the default exchange binding to message_queue now states unknown -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3276) Connection Memory leaks
[
https://issues.apache.org/jira/browse/QPID-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-3276:
--
Labels: leak (was: memory-leak)
Connection Memory leaks
---
Key: QPID-3276
URL: https://issues.apache.org/jira/browse/QPID-3276
Project: Qpid
Issue Type: Bug
Components: C++ Broker, C++ Client
Affects Versions: 0.8, 0.10
Environment: windows broker,windows client
Reporter: creator wang
Assignee: Chuck Rolke
Priority: Critical
Labels: leak
code:
while(1)
{
Connection connection;
connection.open(host,port);
conect.close();
}
when use this code run in VS2008 on windows,
and connect to windows broker,memory leaks very fast;
but connect to linux broker ,no memory leaks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-2180) Broker hangs on shutdown if Windows SQL-based store gets a timeout initializing
[ https://issues.apache.org/jira/browse/QPID-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-2180: -- Labels: deadlock (was: ) Broker hangs on shutdown if Windows SQL-based store gets a timeout initializing --- Key: QPID-2180 URL: https://issues.apache.org/jira/browse/QPID-2180 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Environment: Windows XP-64 w/ SQL Express Reporter: Steve Huston Assignee: Steve Huston Labels: deadlock If the C++ broker startup tries to load the store and ms-sql provider, but the initial connection to SQL times out like this: 2009-10-30 11:31:46 error MSSQL can't open at Provider=SQLOLEDB;Data Source=LILY\SQLEXPRESS;Integrated Security=SSPI: Unspecified error: Timeout expired the broker may hang on shutdown. The main thread is the only one left and it's hung on a call to CoUninitialize(). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-3966) Add missing license headers to project files
[ https://issues.apache.org/jira/browse/QPID-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13640824#comment-13640824 ] Justin Ross commented on QPID-3966: --- From our last release: http://people.apache.org/~robbie/qpid/0.20/0.20rc2_rat_output.txt Add missing license headers to project files Key: QPID-3966 URL: https://issues.apache.org/jira/browse/QPID-3966 Project: Qpid Issue Type: Improvement Components: Packaging Affects Versions: 0.16 Reporter: Justin Ross Assignee: Justin Ross Fix For: 0.21 Attachments: 0.16rc2_rat_output.txt To make it easier to audit the project for license headers, add at least minimal license headers to many of the project files. See attachment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4714) AMQConnection close can leak socket connections if exceptions occur earlier in the process
[ https://issues.apache.org/jira/browse/QPID-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644479#comment-13644479 ] Justin Ross commented on QPID-4714: --- Reviewed by Robbie. Approved for 0.22. AMQConnection close can leak socket connections if exceptions occur earlier in the process -- Key: QPID-4714 URL: https://issues.apache.org/jira/browse/QPID-4714 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.20 Reporter: Rajith Attapattu Fix For: Future If any of the operations throws an exception before the call to _delegate.closeConnection(timeout); then we will leak socket connections. I already see this happening when running performance tests, where session/connection close operations are timing out. The number of connections keeps growing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4724) qpid-cpp-0.22-rc1 RHEL6 cmake issues
[ https://issues.apache.org/jira/browse/QPID-4724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644491#comment-13644491 ] Justin Ross commented on QPID-4724: --- Reviewed by me. Approved for 0.22. qpid-cpp-0.22-rc1 RHEL6 cmake issues Key: QPID-4724 URL: https://issues.apache.org/jira/browse/QPID-4724 Project: Qpid Issue Type: Bug Components: Perl Client Affects Versions: 0.22 Environment: RHEL6 Reporter: Jimmy Jones Assignee: Darryl L. Pierce Fix For: 0.22 Attachments: 0001-QPID-4724-Fixes-Perl-bindings-for-Cmake-2.8.patch Running mkdir BLD; cd BLD; cmake .. -- Could NOT find PerlLibs (missing: PERL_LIBRARY PERL_INCLUDE_PATH) -- Configuring incomplete, errors occurred! should it autodetect this (automake does)? If then run: cmake .. -DPERL_LIBRARY=/usr/lib64/perl5/CORE/libperl.so -DPERL_INCLUDE_PATH=/usr/lib64/perl5 errors with: -- Found Perl: /usr/bin/perl -- Found PerlLibs: /usr/lib64/perl5/CORE/libperl.so CMake Error at bindings/CMakeLists.txt:62 (string): string sub-command REPLACE requires four arguments. CMake Error at bindings/qpid/perl/CMakeLists.txt:38 (install): install FILES given no DESTINATION! -- Configuring incomplete, errors occurred! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4776) Unable to build Ruby language bindings with Cmake 2.6
[ https://issues.apache.org/jira/browse/QPID-4776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644561#comment-13644561 ] Justin Ross commented on QPID-4776: --- Patch from Irina reviewed by Darryl. Approved for 0.22. Unable to build Ruby language bindings with Cmake 2.6 - Key: QPID-4776 URL: https://issues.apache.org/jira/browse/QPID-4776 Project: Qpid Issue Type: Bug Components: Ruby Client Reporter: Darryl L. Pierce Assignee: Darryl L. Pierce Fix For: 0.22 Cmake 2.6 does not include the RUBY_FOUND macro. We need to provide this check for older versions of Cmake. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4759) qpidd --help should show sasl config path default
[ https://issues.apache.org/jira/browse/QPID-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4759: -- Fix Version/s: (was: 0.22) 0.23 qpidd --help should show sasl config path default - Key: QPID-4759 URL: https://issues.apache.org/jira/browse/QPID-4759 Project: Qpid Issue Type: Bug Reporter: michael goulish Assignee: michael goulish Fix For: 0.23 --help output does not show the sasl config path default, which the Cyrus SASL library sets as /etc/sasl2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4759) qpidd --help should show sasl config path default
[ https://issues.apache.org/jira/browse/QPID-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645458#comment-13645458 ] Justin Ross commented on QPID-4759: --- I'd put it differently: Qpidd's use of sasl should honor the build-time determined system-config prefix. The standard system config prefix is indeed /etc, but it isn't always. For instance, a user with a locally built cyrus sasl may have it at /usr/local/etc, and another unix variant may have it somewhere else altogether. If there's any impact on upgrade from this, that's a bug. qpidd --help should show sasl config path default - Key: QPID-4759 URL: https://issues.apache.org/jira/browse/QPID-4759 Project: Qpid Issue Type: Bug Reporter: michael goulish Assignee: michael goulish Fix For: 0.23 --help output does not show the sasl config path default, which the Cyrus SASL library sets as /etc/sasl2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4759) qpidd --help should show sasl config path default
[ https://issues.apache.org/jira/browse/QPID-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645466#comment-13645466 ] Justin Ross commented on QPID-4759: --- For reference: http://www.gnu.org/prep/standards/html_node/Directory-Variables.html qpidd --help should show sasl config path default - Key: QPID-4759 URL: https://issues.apache.org/jira/browse/QPID-4759 Project: Qpid Issue Type: Bug Reporter: michael goulish Assignee: michael goulish Fix For: 0.23 --help output does not show the sasl config path default, which the Cyrus SASL library sets as /etc/sasl2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4698) Fixes needed for the CMake build system when installing files.
[ https://issues.apache.org/jira/browse/QPID-4698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645770#comment-13645770 ] Justin Ross commented on QPID-4698: --- Subsequent fix: http://svn.apache.org/viewvc?view=revisionrevision=1477267 Fixes needed for the CMake build system when installing files. -- Key: QPID-4698 URL: https://issues.apache.org/jira/browse/QPID-4698 Project: Qpid Issue Type: Bug Components: Build Tools Reporter: Darryl L. Pierce Assignee: Darryl L. Pierce Fix For: 0.23 Some of the installed files are going into the wrong directories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4698) Fixes needed for the CMake build system when installing files.
[ https://issues.apache.org/jira/browse/QPID-4698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645774#comment-13645774 ] Justin Ross commented on QPID-4698: --- I've received some feedback that this is more important than I initially judged it to be. Reviewed by Irina; approved for 0.22. Fixes needed for the CMake build system when installing files. -- Key: QPID-4698 URL: https://issues.apache.org/jira/browse/QPID-4698 Project: Qpid Issue Type: Bug Components: Build Tools Reporter: Darryl L. Pierce Assignee: Darryl L. Pierce Fix For: 0.23 Some of the installed files are going into the wrong directories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] Created: (QPID-2730) Add a Session.close() to the console API
Add a Session.close() to the console API Key: QPID-2730 URL: https://issues.apache.org/jira/browse/QPID-2730 Project: Qpid Issue Type: Improvement Components: Qpid Managment Framework Reporter: Justin Ross Right now the user of the console api needs to keep whatever brokers it adds in a collection so it can later delBroker each. The console API has enough info to put this behavior behind a close method. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2978) Disconnected operation is a pain
Disconnected operation is a pain Key: QPID-2978 URL: https://issues.apache.org/jira/browse/QPID-2978 Project: Qpid Issue Type: Improvement Components: C++ Client, Python Client Reporter: Justin Ross If you're writing a program that doesn't expect a tcp connection to be present all the time, the messaging API currently gives you some unattractive options. If you set conn.reconnect = True, conn.open() will block, and you'll never get to all the other code you'd prefer to have executed. If you leave conn.reconnect = False, conn.open(), session.sender(), and conn.close() will throw exceptions that have to be caught and ignored. In either case, session.send() will throw an exception. I'd like some way to tell the connection that I'm really quite indifferent to whether or not the underlying tcp connection is active. I did this testing using the python api, but word has it that this may be the case for the C++ api as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-1916) Maven artifacts for the client
[
https://issues.apache.org/jira/browse/QPID-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12996056#comment-12996056
]
Justin Ross commented on QPID-1916:
---
When I tested the release scripts, I had to make a minor change to release.sh
for the maven artifacts:
[jross@nicaea ~]$ cd ~/qpid
[jross@nicaea qpid]$ svn diff
Index: bin/release.sh
===
--- bin/release.sh (revision 1071633)
+++ bin/release.sh (working copy)
@@ -218,8 +218,8 @@
cp qpid-${VER}/java/management/eclipse-plugin/release/*.tar.gz
qpid-${VER}/java/management/eclipse-plugin/release/*.zip artifacts/
# copy the Maven artifacts
- cp qpid-${VER}/java/client/release/maven artifacts/
- cp qpid-${VER}/java/common/release/maven artifacts/
+ cp -a qpid-${VER}/java/client/release/maven artifacts/
+ cp -a qpid-${VER}/java/common/release/maven artifacts/
fi
if [ DOTNET == $DOTNET ] ; then
[jross@nicaea qpid]$
Maven artifacts for the client
--
Key: QPID-1916
URL: https://issues.apache.org/jira/browse/QPID-1916
Project: Qpid
Issue Type: New Feature
Components: Ant Build System, Build Tools, Java Client, Java Common,
Java Tools, Maven build system, Qpid Managment Framework
Affects Versions: M3, M4, 0.5, 0.6, 0.7, 0.8
Reporter: Bryan Kearney
Assignee: Andrew Kennedy
Fix For: 0.9
Attachments: genpom.patch, maven.patch, mavenize3.patch
The attached patch files adds the maven ant tasks to the build system. It
allows, on a per-module basis, to support creating a pom file and exporting
the jars to a maven repository. This is not a very DRY solution, as it
requires copying the dependency information from the build.deps file. I have
only added the pom files for the client bits, since i believe these are the
most likely to be required by folks using QMF.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-3074) object creation and deletion via QMF for java broker
[ https://issues.apache.org/jira/browse/QPID-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12997456#comment-12997456 ] Justin Ross commented on QPID-3074: --- I worked on a piece of software that consumed qmf data, and the vhost vs. broker problem came up a lot. In particular, for users of a console, the two concepts are difficult to distinguish and introduce undesirable navigation problems. It introduces confursion for developers as well, evidenced by the presence of qmf methods across both types without a clear rationale. I personally favor removing vhost from the model altogether. Under this scheme, a server process that supports vhosts exports multiple qmf Broker objects. I believe this is closer to the original intention behind vhosts (in httpd, for instance). It makes the question of whether you use one process or multiple processes to support n brokers a matter of implementation preference. If otoh you expose brokers *and* vhosts, you're married to that model, whether or not you use it. That said, I agree with Robbie's comment. If you keep vhosts in the model, these methods make more sense on vhost. object creation and deletion via QMF for java broker Key: QPID-3074 URL: https://issues.apache.org/jira/browse/QPID-3074 Project: Qpid Issue Type: New Feature Components: C++ Broker, Java Broker Affects Versions: 0.8 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: Future ## Problem At present queues and exchanges cannot be created via QMFv2. Having a means to do so would allow for more unified broker management. It would also allow applications that have a need to do this sort of broker manipulation to utilise a protocol independent, message-driven approach (as used in QMFv2 method invocation for example). ## Solution Define create() and delete() methods in the broker class in the management schema method name=create desc=Create an object of the specified type arg name=type dir=I type=sstr desc=The type of object to create/ arg name=name dir=I type=sstr desc=The name of the object to create/ arg name=properties dir=I type=map desc=Type specific object properties/ arg name=lenient dir=I type=bool desc=If specified, ignore unrecognised object properties as long as type is recognised/ /method method name=delete desc=Delete an object of the specified type arg name=type dir=I type=sstr desc=The type of object to delete/ arg name=name dir=I type=sstr desc=The name of the object to delete/ arg name=options dir=I type=map desc=Type specific object options for deletion/ /method These would then be invoked like any other QMFv2 method. The types of object supported and the various properties these recognise will be documented. I propose initially to support creation and deletion of three basic object types through this mechanism: queue, exchange and binding. Exchanges will have 'topic' as a type alias and will also recognise a sub-type property, corresponding to the AMQP 0-10 exchange type. The default will be topic exchanges. This matches the current usage in the addressing syntax for the messaging API. ## Rationale There are alternative approaches to message based creation and deletion that could be taken. For example: (1) Augment the QMFv2 protocol definition with opcodes for creation and deletion requests rather than using schema specific methods. (2) Define a mechanism for message based creation or deletion of objects that is entirely independent of QMFv2. The different approaches really only involve slightly different formats to the map messages sent and received, and perhaps the exact address to which they are sent. The basic mechanism would remain the same. However, I do not want to commit to altering the design of QMFv2 whose scope is broader than the basic broker management which qpidd requires. Neither do I want, at this stage at least, to replace QMFv2 entirely. I chose the solution above as, for now, it seems like the most consistent option within the scope of Qpid 0.10. Likewise there are alternative ontologies for the objects thus created (or deleted). While 'queue' is probably obvious and uncontroversial, exposing exchanges and bindings are possibly less so. The rationale here is to find a simple solution that adequately (and intuitively) supports the AMQP 0-8 to 0-10 model for those familiar with it (which is after all the only model currently supported), while alluding to a transition to one where the pub-sub topic concept is more completely and explicitly supported. The set of types will be easily extensible (e.g. could
[jira] Issue Comment Edited: (QPID-3074) object creation and deletion via QMF for java broker
[ https://issues.apache.org/jira/browse/QPID-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12997456#comment-12997456 ] Justin Ross edited comment on QPID-3074 at 2/21/11 3:57 PM: I worked on a piece of software that consumed qmf data, and the vhost vs. broker problem came up a lot. In particular, for users of a console, the two concepts are difficult to distinguish and introduce navigation problems. It means confusion for developers as well, evidenced by the presence of qmf methods across both types without a clear rationale. I personally favor removing vhost from the model altogether. Under this scheme, a server process that supports vhosts exports multiple qmf Broker objects. I believe this is closer to the original intention behind vhosts (in httpd, for instance). It makes the question of whether you use one process or multiple processes to support n brokers a matter of implementation preference. If otoh you expose brokers *and* vhosts, you're married to that model, whether or not you use it. That said, I agree with Robbie's comment. If you keep vhosts in the model, these methods make more sense on vhost. was (Author: justi9): I worked on a piece of software that consumed qmf data, and the vhost vs. broker problem came up a lot. In particular, for users of a console, the two concepts are difficult to distinguish and introduce undesirable navigation problems. It introduces confursion for developers as well, evidenced by the presence of qmf methods across both types without a clear rationale. I personally favor removing vhost from the model altogether. Under this scheme, a server process that supports vhosts exports multiple qmf Broker objects. I believe this is closer to the original intention behind vhosts (in httpd, for instance). It makes the question of whether you use one process or multiple processes to support n brokers a matter of implementation preference. If otoh you expose brokers *and* vhosts, you're married to that model, whether or not you use it. That said, I agree with Robbie's comment. If you keep vhosts in the model, these methods make more sense on vhost. object creation and deletion via QMF for java broker Key: QPID-3074 URL: https://issues.apache.org/jira/browse/QPID-3074 Project: Qpid Issue Type: New Feature Components: C++ Broker, Java Broker Affects Versions: 0.8 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: Future ## Problem At present queues and exchanges cannot be created via QMFv2. Having a means to do so would allow for more unified broker management. It would also allow applications that have a need to do this sort of broker manipulation to utilise a protocol independent, message-driven approach (as used in QMFv2 method invocation for example). ## Solution Define create() and delete() methods in the broker class in the management schema method name=create desc=Create an object of the specified type arg name=type dir=I type=sstr desc=The type of object to create/ arg name=name dir=I type=sstr desc=The name of the object to create/ arg name=properties dir=I type=map desc=Type specific object properties/ arg name=lenient dir=I type=bool desc=If specified, ignore unrecognised object properties as long as type is recognised/ /method method name=delete desc=Delete an object of the specified type arg name=type dir=I type=sstr desc=The type of object to delete/ arg name=name dir=I type=sstr desc=The name of the object to delete/ arg name=options dir=I type=map desc=Type specific object options for deletion/ /method These would then be invoked like any other QMFv2 method. The types of object supported and the various properties these recognise will be documented. I propose initially to support creation and deletion of three basic object types through this mechanism: queue, exchange and binding. Exchanges will have 'topic' as a type alias and will also recognise a sub-type property, corresponding to the AMQP 0-10 exchange type. The default will be topic exchanges. This matches the current usage in the addressing syntax for the messaging API. ## Rationale There are alternative approaches to message based creation and deletion that could be taken. For example: (1) Augment the QMFv2 protocol definition with opcodes for creation and deletion requests rather than using schema specific methods. (2) Define a mechanism for message based creation or deletion of objects that is entirely independent of QMFv2. The different approaches really only involve slightly different
[jira] Commented: (QPID-3080) Broker should issue QMF event on queue flow control state change
[ https://issues.apache.org/jira/browse/QPID-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13001471#comment-13001471 ] Justin Ross commented on QPID-3080: --- As Ken mentioned, since (a) these might be very frequent, which could threaten their utility and affect broker scale, and since (b) the already included queue threshold alerts can address the monitoring concern, this change should wait for 0.12. Broker should issue QMF event on queue flow control state change Key: QPID-3080 URL: https://issues.apache.org/jira/browse/QPID-3080 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.9 Environment: all Reporter: Ken Giusti Assignee: Ken Giusti Priority: Trivial Fix For: 0.9 Attachments: QPID-3080.patch When a queue's flow control state changes, the broker should issue an QMF event to notify management clients. A rough sketch of a possible schema implementation for the event: eventArguments arg name=qName type=sstr desc=Name of a queue/ arg name=msgDepth type=count32 desc=Current size of queue in messages/ arg name=byteDepth type=count32 desc=Current size of queue in bytes/ arg name=active type=bool desc=True if flow stopped, else flow allowed/ /eventArguments event name=queueFlowControl sev=inform args=qName, active, msgDepth, byteDepth/ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-3081) Maintain a per-queue counter for flow control state change
[ https://issues.apache.org/jira/browse/QPID-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13001483#comment-13001483 ] Justin Ross commented on QPID-3081: --- I'll wait for Gordon to reply, but for my part, this change looks good for 0.10. Maintain a per-queue counter for flow control state change -- Key: QPID-3081 URL: https://issues.apache.org/jira/browse/QPID-3081 Project: Qpid Issue Type: Improvement Components: C++ Broker Affects Versions: 0.9 Reporter: Ken Giusti Assignee: Ken Giusti Priority: Trivial Fix For: 0.9 Attachments: QPID-3081.patch Request for a feature: Create a new per-queue QMF statistic that counts the number of times a queue enters the flow control state. This could be helpful to determine the utilization of a queue for tuning a queue's capacity. May also need the ability to reset the counter via a QMF management method. Opinions? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-3110) JMX Management console does not show aggregate virtual host notifications
[ https://issues.apache.org/jira/browse/QPID-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13002632#comment-13002632 ] Justin Ross commented on QPID-3110: --- Approved for 0.10. JMX Management console does not show aggregate virtual host notifications - Key: QPID-3110 URL: https://issues.apache.org/jira/browse/QPID-3110 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Affects Versions: 0.9 Reporter: Alex Rudyy Assignee: Andrew Kennedy Priority: Minor Fix For: 0.9 JMX Management console does not show aggregate virtual host notifications. Notifications are shown for individual queues but not shown on virtual host notifications UI. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-3118) cpp/examples/CMakeLists.txt tries to install non-existant files
[ https://issues.apache.org/jira/browse/QPID-3118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13002837#comment-13002837 ] Justin Ross commented on QPID-3118: --- For my part, approved for 0.10. I searched for past discussions on the question of including the old examples, and I found QPID-3067 but nothing else. I think this change should go in, and we can treat the fate of the old api examples as a separate issue. cpp/examples/CMakeLists.txt tries to install non-existant files --- Key: QPID-3118 URL: https://issues.apache.org/jira/browse/QPID-3118 Project: Qpid Issue Type: Bug Components: Packaging Affects Versions: 0.9 Environment: CMake builds Reporter: Steve Huston Assignee: Steve Huston Fix For: 0.9 Attachments: QPID-3118.diff The examples revision in QPID-3097 moved some files; the CMakeLists.txt still refers to them. This prevents the Windows installer from generating a package correctly. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-3120) Queue reroute doesn't honor alternate exchange
[ https://issues.apache.org/jira/browse/QPID-3120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13003397#comment-13003397 ] Justin Ross commented on QPID-3120: --- Approved for 0.10. Queue reroute doesn't honor alternate exchange -- Key: QPID-3120 URL: https://issues.apache.org/jira/browse/QPID-3120 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.8 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.9 When invoking the reroute method on a queue, messages delivered to an exchange are dropped instead of being delivered to the exchange's alternate exchange if no bindings match. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-3122) backward compatibility problem with 0.9 agents
[ https://issues.apache.org/jira/browse/QPID-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13003553#comment-13003553 ] Justin Ross commented on QPID-3122: --- Approved for 0.10. Also reviewed and approved by Ken Giusti. backward compatibility problem with 0.9 agents -- Key: QPID-3122 URL: https://issues.apache.org/jira/browse/QPID-3122 Project: Qpid Issue Type: Bug Components: Qpid Managment Framework Affects Versions: 0.8 Reporter: Ted Ross Assignee: Ted Ross Priority: Minor Fix For: 0.10 The QMF console needs to accept older agent-map keywords as well as the newer ones. The attributes advertised in the agent heartbeat include the following keys that were changed in 0.10 for consistency: timestamp = _timestamp heartbeat_interval = _heartbeat_interval epoch = _epoch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-3124) Update release script for new build artifacts
Update release script for new build artifacts - Key: QPID-3124 URL: https://issues.apache.org/jira/browse/QPID-3124 Project: Qpid Issue Type: Improvement Components: Build Tools Affects Versions: 0.10, 0.11 Reporter: Justin Ross Fix For: 0.10, 0.11 Attachments: release.sh.patch This patch (1) fixes the scripting for maven artifacts and (2) adds scripting for the qmf and tools components. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-3124) Update release script for new build artifacts
[ https://issues.apache.org/jira/browse/QPID-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-3124: -- Attachment: release.sh.patch Patch to bin/release.sh Update release script for new build artifacts - Key: QPID-3124 URL: https://issues.apache.org/jira/browse/QPID-3124 Project: Qpid Issue Type: Improvement Components: Build Tools Affects Versions: 0.10, 0.11 Reporter: Justin Ross Fix For: 0.10, 0.11 Attachments: release.sh.patch This patch (1) fixes the scripting for maven artifacts and (2) adds scripting for the qmf and tools components. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-3121) Cluster management inconsistency when using persistent store.
[ https://issues.apache.org/jira/browse/QPID-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13003602#comment-13003602 ] Justin Ross commented on QPID-3121: --- Approved for 0.10. Also reviewed on reviewboard by Ken Giusti. Cluster management inconsistency when using persistent store. - Key: QPID-3121 URL: https://issues.apache.org/jira/browse/QPID-3121 Project: Qpid Issue Type: Bug Components: C++ Clustering Affects Versions: 0.9 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.9 Attachments: durable-test-mgmt.patch If cluster_tests.py, test_management is modified to enable durable messages, it fails the log comparison test shows messages like this on one broker but not the others: trace Changed V1 statistics org.apache.qpid.broker:connection:127.0.0.1:52742-127.0.0.1:44104 len=NN trace Changed V2 statistics org.apache.qpid.broker:connection:127.0.0.1:52742-127.0.0.1:44104 To date this hasn't been seen to actually cause a cluster crash but in principle it is possible it could. To reproduce, build the message store at: http://anonsvn.jboss.org/repos/rhmessaging/store/ In the tests/cluster directory, run this in a loop: make check TESTS=run_python_cluster_tests CLUSTER_TESTS='*.test_management* -DDURATION=2' It will fail, usually on the first iteration, showing the log files that don't match. Use diff or other such tool to confirm that the mismatched lines are as above. The file may also contain some other mismatches showing a different number of stats in a periodic update - that is a consequence of the above. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-3130) slow codec
[ https://issues.apache.org/jira/browse/QPID-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13004061#comment-13004061 ] Justin Ross commented on QPID-3130: --- Approved for 0.10. I also reviewed this with my python hat on, so it's ready to go. slow codec -- Key: QPID-3130 URL: https://issues.apache.org/jira/browse/QPID-3130 Project: Qpid Issue Type: Bug Components: Python Client Affects Versions: 0.10 Reporter: Rafael H. Schloming Assignee: Rafael H. Schloming Fix For: 0.10 See https://bugzilla.redhat.com/show_bug.cgi?id=681166 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-3127) Accept mode should be NONE for 0-10 NO_ACKNOWLEDGE subscriptions
[ https://issues.apache.org/jira/browse/QPID-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13004103#comment-13004103 ] Justin Ross commented on QPID-3127: --- Approved for 0.10, and with Rajith's review, ready to go. Accept mode should be NONE for 0-10 NO_ACKNOWLEDGE subscriptions Key: QPID-3127 URL: https://issues.apache.org/jira/browse/QPID-3127 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.10 Reporter: Andrew Kennedy Assignee: Rajith Attapattu Priority: Minor Fix For: 0.10, 0.11 When creating a subscription for a consumer in a 0-10 session, the accept mode is always set to EXPLICIT unless an unreliable connection is specified using the ADDR syntax. If a session is created as NO_ACKNOWLEDGE, the accept mode should also be NONE. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2732) JMS Client should implement the reliability option from the new addressing scheme
[ https://issues.apache.org/jira/browse/QPID-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13004164#comment-13004164 ] Justin Ross commented on QPID-2732: --- Approved for 0.10. Reviewed by Rafi. JMS Client should implement the reliability option from the new addressing scheme - Key: QPID-2732 URL: https://issues.apache.org/jira/browse/QPID-2732 Project: Qpid Issue Type: Improvement Components: Java Client Reporter: Rajith Attapattu Assignee: Rajith Attapattu Priority: Minor The new addressing scheme defines the following reliability modes. unreliable: there may be duplicate messages, and there may also be missing messages at-most-once: there may be missing messages, but there will be no duplicate messages at-least-once: there may be duplicate messages, but there will be no missing messages exactly-once: there will be no missing or duplicate messages The mapping to the 0-10 protocol is as follows. 1. For at-most-once (and unreliable) we need to use accept-mode=none. 2. For at-least-once we use non auto-delete (i.e. auto-delete=*false*), and accept-mode=explicit 3. exactly-once is not yet supported. The default reliability mode is at-least-once. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-3128) Update CPP broker documentation with producer flow control user api.
[ https://issues.apache.org/jira/browse/QPID-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13004577#comment-13004577 ] Justin Ross commented on QPID-3128: --- Approved for 0.10. Reviewed by Gordon. Update CPP broker documentation with producer flow control user api. Key: QPID-3128 URL: https://issues.apache.org/jira/browse/QPID-3128 Project: Qpid Issue Type: Improvement Components: C++ Broker, Documentation Affects Versions: 0.9 Reporter: Ken Giusti Assignee: Ken Giusti Priority: Minor Fix For: 0.9 Need to add the new producer flow control feature to the user documentation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-3132) Threshold alert on a queue used to receive alerts causes broker crash
[ https://issues.apache.org/jira/browse/QPID-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13004712#comment-13004712 ] Justin Ross commented on QPID-3132: --- Approved for 0.10. Reviewed by Ken. Threshold alert on a queue used to receive alerts causes broker crash - Key: QPID-3132 URL: https://issues.apache.org/jira/browse/QPID-3132 Project: Qpid Issue Type: Bug Affects Versions: 0.10 Reporter: Gordon Sim Assignee: Gordon Sim Priority: Blocker Fix For: 0.10 If a queue bound to the QMF exchange for receiving events reaches a configured threhold and generates an alert, the alert will result in an infinite recursion where the message for the event is enqueued triggering a further event etc etc -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-3135) cpp/bld-winsdk.ps1 tries to install non-existant files
[ https://issues.apache.org/jira/browse/QPID-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13005320#comment-13005320 ] Justin Ross commented on QPID-3135: --- Approved for 0.10. cpp/bld-winsdk.ps1 tries to install non-existant files -- Key: QPID-3135 URL: https://issues.apache.org/jira/browse/QPID-3135 Project: Qpid Issue Type: Bug Components: Packaging Affects Versions: 0.9 Environment: bld-winsdk builds Reporter: Chuck Rolke Assignee: Chuck Rolke Attachments: QPID-3118_AdjustWinSdkInstallation.patch The examples revision in QPID-3067 moved some files and bld-winsdk.ps1 still refers to them in their old directories. This prevents bld-winsdk from building a package correctly. This same problem is in QPID-3118 as it applies to CMakeLists. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-3136) Add option to disable defaults for queue threshold alerts
[ https://issues.apache.org/jira/browse/QPID-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13005670#comment-13005670 ] Justin Ross commented on QPID-3136: --- Approved for 0.10. Reviewed by Ken Giusti. Add option to disable defaults for queue threshold alerts - Key: QPID-3136 URL: https://issues.apache.org/jira/browse/QPID-3136 Project: Qpid Issue Type: Improvement Components: C++ Broker Affects Versions: 0.10 Reporter: Gordon Sim Assignee: Gordon Sim By default any queue with a limit set will generate threshold events at 80% of that limit. This is designed to be simple for out-of-the-box use, but is not always desirable (and is a change in behaviour) and so would be nice to be able to turn off. The proposal is to add a broker level option to control the ratio used for determining an alert threshold from a queue limit. If set to 0 this would disable threshold events by default. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-3144) qpidd --check does not work with info logging and --log-to-stdout=yes
[ https://issues.apache.org/jira/browse/QPID-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13007477#comment-13007477 ] Justin Ross commented on QPID-3144: --- Approved for 0.10. Reviewed by Mick Goulish. qpidd --check does not work with info logging and --log-to-stdout=yes - Key: QPID-3144 URL: https://issues.apache.org/jira/browse/QPID-3144 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.9 Reporter: Alan Conway Assignee: Alan Conway Priority: Minor Fix For: 0.10 qpidd --check is supposed to print the PID of a running qpidd --daemon, for use in scripts and the like. However with info logging and log-to-stdout enabled this does not work because log messages of the form: 2011-03-14 16:21:05 info Loaded Module: /usr/lib64/qpid/daemon/cluster.so precede the port number. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2560) WCF to WCF PubSub sample is mis-named or needs to be re-designed
[ https://issues.apache.org/jira/browse/QPID-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13008064#comment-13008064 ] Justin Ross commented on QPID-2560: --- Hi, Cliff. Any updates for this one? If it makes sense, please set Fix Version to 0.11 or Future so we know this issue is triaged. WCF to WCF PubSub sample is mis-named or needs to be re-designed Key: QPID-2560 URL: https://issues.apache.org/jira/browse/QPID-2560 Project: Qpid Issue Type: Bug Components: WCF/C++ Client Affects Versions: 0.9 Environment: Windows WCF Reporter: Ted Ross The WCF sample called WCFToWCFPubSub does not use actual AMQP topic routing and therefore is not an accurate illustration of the publication-subscription pattern. The environment in which this was tested was: Two instances of Topic_Consumer and a single instance of Topic_Producer running. The producer sends ten messages and the two consumers receive a subset (partition of the set) of the messages. This is actually using a shared queue and balancing the traffic between the two consumers, not broadcasting the messages equally to the two consumers as it should. Another, more fundamental, problem is that the message transfer is layered on top of a remote procedure call handled by a service associated with the consumer. This is why this code example balances the sent messages. It is only possible for an RPC to be handled by a single server. RPC is not appropriate for pub-sub since the producer doesn't know, when it produces, how many consumers, if any, there are for each produced message. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2656) Verify/correct error handling on 0-10 broker codepath
[ https://issues.apache.org/jira/browse/QPID-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13008080#comment-13008080 ] Justin Ross commented on QPID-2656: --- Hi, Andrew. Any updates here? Verify/correct error handling on 0-10 broker codepath - Key: QPID-2656 URL: https://issues.apache.org/jira/browse/QPID-2656 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.7 Reporter: Andrew Kennedy Fix For: 0.9 Verify existing error handling on 0-10 BROKER codepath and how it compares with the 0-9 codepath. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-3151) Remove dotnet and ruby from the --all release artifacts
Remove dotnet and ruby from the --all release artifacts --- Key: QPID-3151 URL: https://issues.apache.org/jira/browse/QPID-3151 Project: Qpid Issue Type: Improvement Components: Build Tools Affects Versions: 0.10, 0.11 Reporter: Justin Ross Fix For: 0.10, 0.11 Attachments: release.sh.patch Since these components are no longer supported, drop them from the release artifacts. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-3151) Remove dotnet and ruby from the --all release artifacts
[ https://issues.apache.org/jira/browse/QPID-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-3151: -- Attachment: release.sh.patch Remove dotnet and ruby from the --all release artifacts --- Key: QPID-3151 URL: https://issues.apache.org/jira/browse/QPID-3151 Project: Qpid Issue Type: Improvement Components: Build Tools Affects Versions: 0.10, 0.11 Reporter: Justin Ross Fix For: 0.10, 0.11 Attachments: release.sh.patch Since these components are no longer supported, drop them from the release artifacts. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Commented] (QPID-3116) rubygen with ruby 1.9
[ https://issues.apache.org/jira/browse/QPID-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009149#comment-13009149 ] Justin Ross commented on QPID-3116: --- Approved for 0.10. Reviewed by Alan Conway. rubygen with ruby 1.9 - Key: QPID-3116 URL: https://issues.apache.org/jira/browse/QPID-3116 Project: Qpid Issue Type: Bug Components: Build Tools Affects Versions: 0.9 Environment: Ruby 1.9.2 Reporter: Geoffrey Clements Assignee: Alan Conway Priority: Minor Fix For: 0.10 Attachments: amqpgen.rb.patch Original Estimate: 1h Remaining Estimate: 1h The ampqgen.rb script appends an underscore to attributes that may conflict with attributes that may already exist in object. The issue is with 'type'. It is an attribute in ruby 1.8.x but not in 1.9.x. The code accesses a type_ attribute in the code which doesn't actually exist when running under 1.9.x because type isn't an attribute. The fis is a simple special case for the type symbol. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
