[jira] Resolved: (QPID-3100) Excessive memory use per-connection
[ https://issues.apache.org/jira/browse/QPID-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3100. -- Resolution: Fixed Excessive memory use per-connection --- Key: QPID-3100 URL: https://issues.apache.org/jira/browse/QPID-3100 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.8 Reporter: Gordon Sim Assignee: Gordon Sim Priority: Minor Fix For: 0.9 Due to unnecessarily high number of buffers created initially -- 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-3101) qpid-tool does not allow maps to be passed as arguments
qpid-tool does not allow maps to be passed as arguments --- Key: QPID-3101 URL: https://issues.apache.org/jira/browse/QPID-3101 Project: Qpid Issue Type: Bug Components: Tools Affects Versions: 0.8 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.9 Which would be useful e.g. when using the new Broker::create() method -- 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-3101) qpid-tool does not allow maps to be passed as arguments
[ https://issues.apache.org/jira/browse/QPID-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13001418#comment-13001418 ] Gordon Sim commented on QPID-3101: -- Patch available for review: https://reviews.apache.org/r/454/ qpid-tool does not allow maps to be passed as arguments --- Key: QPID-3101 URL: https://issues.apache.org/jira/browse/QPID-3101 Project: Qpid Issue Type: Bug Components: Tools Affects Versions: 0.8 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.9 Which would be useful e.g. when using the new Broker::create() method -- 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-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:all-tabpanel ] Ken Giusti updated QPID-3081: - Attachment: QPID-3081.patch Proposed fix. 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] Updated: (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:all-tabpanel ] Ken Giusti updated QPID-3080: - Attachment: QPID-3080.patch Proposed fix. 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
Re: 0.10 release update - this week we branch for release
Seeking approval for inclusion in 0.10: https://issues.apache.org/jira/browse/QPID-3080 https://issues.apache.org/jira/browse/QPID-3081 Proposed patches attached to each. thanks, -K - Original Message - Hi, folks. Our schedule calls for us to create our release branch this Wednesday, 3 March. Trunk will remain open for forward development, but all changes to the release branch will require approval. I'd like to enlist your help with the approval process. When a potential fix comes in, it needs two forms of review: 1. Review by someone who focuses on the release goals and schedule 2. Review by someone (other than the author) who knows the code being patched and can speak to the change's significance and safety My job is item 1. For item 2, I need experts in the various components of qpid. So here's my proposal: approval of kinds 1 (from me) and 2 (from someone familiar with the code being changed) must be indicated in jira comments before a change may be committed to the release branch. In order to this efficiently, we need clear lines of responsibility. I'd like to use the (still emerging) list of component owners to map incoming changes to reviewers. In cases where the patch submitter is also the component owner, I'd ask that he or she find someone else with equivalent experience in that code to evaluate the change. The purpose of requiring approval is to ensure that, as we approach release, each change is *discussed*. I am continually impressed with how simple questions can lay bare important deficits. I don't expect this to be a big burden, though I am conscious of the extra coordination involved. I'll do my best to respond to change requests promptly. Here's what I have so far for component owners: C++ clustering Alan C++ client and broker Gordon Java client Rajith Java broker Robbie QMF Ted I just scanned that out of the Default assignees thread. Please reply on this thread if you'd like to volunteer to review changes for a particular component. Thanks, Justin --- https://cwiki.apache.org/qpid/010-release.html - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: 0.10 release update - this week we branch for release
Andrew, I say fire away. On Wed, 2 Mar 2011, Andrew Kennedy wrote: Justin, Also, I don't want this to interfere with the 0.10 release process, so let me know if you feel I ought to wait a bit longer so that my review request doesn't get lost in the noise of 0.10 release candidate bugfixes. As you can perhaps tell, I'm just anxious to get the code out there ;) Andrew. -- -- andrew d kennedy ? do not fold, bend, spindle, or mutilate ; -- http://grkvlt.blogspot.com/ ? edinburgh : +44 7582 293 255 ; On 1 Mar 2011, at 15:51, Justin Ross wrote: It should trouble all of you that I'm no good with dates. Thankfully, I have peers to point out my errors! The date I intended was Wednesday, 2 March, tomorrow--not 3 March. We may push this date a little later in the week to allow time for some fixes to land, but so far it's still set for tomorrow. Justin - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[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=13001439#comment-13001439 ] Ted Ross commented on QPID-3080: How frequently is this event likely to be raised? 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
Re: 0.10 bugs
One more thing on this topic. If in the course of scanning the candidate bug list you discover a bug that should be addressed, but not for 0.10, please set its fixVersion to Future. That way we know the bug has been triaged. When we prepare for 0.12, we'll selectively retarget Future bugs for the current release. And of course, conversely, if the bug no longer has any merit, close it! Thanks, Justin On Tue, 1 Mar 2011, Justin Ross wrote: Hello. I've updated the 0.10 release page [1] with two new links for jiras: * Bug jiras: issues that I'm relatively confident are updated and targeted correctly. There are currently 31 of these. http://bit.ly/e7tcBc * Candidate bug jiras: casting a wider net now, jiras that ought to be reviewed and considered for 0.10, of which there are 100. http://bit.ly/h8JiF2 Note that this query is easier to use if you use Tools - Configure Columns to add component to your view. The second query is not perfect. It reflects my attempt to winnow down to a reasonable set to draw from. I selected unresolved bugs with fixVersion unset and updated in 2010 or later. Please feel free to adjust the query parameters (and tell me if you make improvements). There is a large set of jiras that are unresolved and haven't been updated in more than a year. I'm cooking up a plan to clean those up, so more on that later. For the purposes of 0.10, I'd like contributors to take a look at bugs in the second list and consider promoting them to the first list by setting fixVersion to 0.9. Thanks, Justin - [1] https://cwiki.apache.org/confluence/display/qpid/0.10+release - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Closed: (QPID-2988) How to set Message Priority
[ https://issues.apache.org/jira/browse/QPID-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim closed QPID-2988. Resolution: Duplicate Dup of QPID-529 How to set Message Priority --- Key: QPID-2988 URL: https://issues.apache.org/jira/browse/QPID-2988 Project: Qpid Issue Type: Bug Components: AMQP Compliance Affects Versions: 0.8 Environment: VS 2008 Reporter: Sanath Prudhvi Priority: Critical Hi, I am new user to AMQP . I am using Apache Qpid implementation and it's really very good in working. But I need to set Priorities to the message I have to send to server and Server must accept the high prirority message and give reply immediately ( I mean server should process the messages based on their priorities). Please suggest me the way to set the priorities for message. I am using C#.Net as client. thanks, -Sanath -- 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-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=13001450#comment-13001450 ] Ken Giusti commented on QPID-3080: -- As implemented, there is no time-based dampening. But the events are governed by the same hysteresis that prevents the thrashing of flow control state (a separation between the 'active' and 'inactive' thresholds). So it depends - based on configuration and traffic flow, it has the potential of being quite frequent. To be honest, I'm not 100% convinced on the necessity of this feature - especially in light of Gordon's recent implementation of queue threshold events. If someone really wanted events on flow control changes, they _could_ be manually configured on a per-queue basis using the new queue threshold event feature. I'm leaning toward to deferring this, unless there is an overwhelming consensus to add it. Opinions? 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
Re: 0.10 release update - alpha is cut
On 02/23/2011 02:25 PM, Gordon Sim wrote: On 02/22/2011 08:21 PM, Justin Ross wrote: https://cwiki.apache.org/confluence/display/qpid/0.10+Release One of the things we missed in the last release was having downloads of the tools (including the dependencies). Would be nice to get something done there this time around if anyone has time to look at it. There is actually a setup.py already there for these tools, so we should just be able to use that to create the release artifacts (zip/tarball). These scripts have dependencies on the python client and also the qmf console library which is in extras/qmf and also has a setup.py script ready. Justin, can we include the extra/qmf and tools source dists for beta? Is there anything else you done in order for that to happen? - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: 0.10 release update - alpha is cut
On Wed, 2 Mar 2011, Gordon Sim wrote: On 02/23/2011 02:25 PM, Gordon Sim wrote: On 02/22/2011 08:21 PM, Justin Ross wrote: https://cwiki.apache.org/confluence/display/qpid/0.10+Release One of the things we missed in the last release was having downloads of the tools (including the dependencies). Would be nice to get something done there this time around if anyone has time to look at it. There is actually a setup.py already there for these tools, so we should just be able to use that to create the release artifacts (zip/tarball). These scripts have dependencies on the python client and also the qmf console library which is in extras/qmf and also has a setup.py script ready. Justin, can we include the extra/qmf and tools source dists for beta? Is there anything else you done in order for that to happen? Yes, thanks for reminding me. I think it will require only a small change to the release script. Justin - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Closed: (QPID-2961) Option to disable broker plugins on windows
[ https://issues.apache.org/jira/browse/QPID-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim closed QPID-2961. Resolution: Not A Problem This is already possible through the --no-module-dir option I believe. Option to disable broker plugins on windows --- Key: QPID-2961 URL: https://issues.apache.org/jira/browse/QPID-2961 Project: Qpid Issue Type: Improvement Components: C++ Broker Affects Versions: 0.7, 0.8, 0.9 Environment: Windows Reporter: Daniel Sack On the windows broker it would be fine if it's possible to disable plugins like acl or ssl if it's not needed. -- 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-2961) Option to disable broker plugins on windows
[ https://issues.apache.org/jira/browse/QPID-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13001454#comment-13001454 ] Daniel Sack commented on QPID-2961: --- The --no-module-dir option is for modules like the message store. Currently you have no possibility to disable acl or ssl support. These parts are pluged into the qpid broker. Option to disable broker plugins on windows --- Key: QPID-2961 URL: https://issues.apache.org/jira/browse/QPID-2961 Project: Qpid Issue Type: Improvement Components: C++ Broker Affects Versions: 0.7, 0.8, 0.9 Environment: Windows Reporter: Daniel Sack On the windows broker it would be fine if it's possible to disable plugins like acl or ssl if it's not needed. -- 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-3102) messaging API produces messages with ttl=0 by default
messaging API produces messages with ttl=0 by default - Key: QPID-3102 URL: https://issues.apache.org/jira/browse/QPID-3102 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.8 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.9 whereas the c++ broker ignores this, the java broker treats it (not unreasonably) as expiring immediately -- 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-3103) qpid-config doesn't handle null arguments for queues/exchanges
qpid-config doesn't handle null arguments for queues/exchanges -- Key: QPID-3103 URL: https://issues.apache.org/jira/browse/QPID-3103 Project: Qpid Issue Type: Bug Components: Tools Affects Versions: 0.8 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.9 E.g. when running against java broker this results in failures: Failed: TypeError: argument of type 'NoneType' is not iterable -- 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-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] Resolved: (QPID-3103) qpid-config doesn't handle null arguments for queues/exchanges
[ https://issues.apache.org/jira/browse/QPID-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3103. -- Resolution: Fixed qpid-config doesn't handle null arguments for queues/exchanges -- Key: QPID-3103 URL: https://issues.apache.org/jira/browse/QPID-3103 Project: Qpid Issue Type: Bug Components: Tools Affects Versions: 0.8 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.9 E.g. when running against java broker this results in failures: Failed: TypeError: argument of type 'NoneType' is not iterable -- 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] Resolved: (QPID-3102) messaging API produces messages with ttl=0 by default
[ https://issues.apache.org/jira/browse/QPID-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3102. -- Resolution: Fixed messaging API produces messages with ttl=0 by default - Key: QPID-3102 URL: https://issues.apache.org/jira/browse/QPID-3102 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.8 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.9 whereas the c++ broker ignores this, the java broker treats it (not unreasonably) as expiring immediately -- 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] Resolved: (QPID-3101) qpid-tool does not allow maps to be passed as arguments
[ https://issues.apache.org/jira/browse/QPID-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-3101. -- Resolution: Fixed qpid-tool does not allow maps to be passed as arguments --- Key: QPID-3101 URL: https://issues.apache.org/jira/browse/QPID-3101 Project: Qpid Issue Type: Bug Components: Tools Affects Versions: 0.8 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.9 Which would be useful e.g. when using the new Broker::create() method -- 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-3104) why is backport-util-concurrent.jar required when running on linux java 1.6 but not windows
why is backport-util-concurrent.jar required when running on linux java 1.6 but not windows --- Key: QPID-3104 URL: https://issues.apache.org/jira/browse/QPID-3104 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.5 Environment: Lunix, hotpsot server JVM 1.6.0_20 Windows XP. Hotspot client JVM 1.6.0_17 Qpid java client 0.5 Reporter: Jason Smith Priority: Minor The problem is when running my java application which includes the following Qpid jars and dependencies, it works on Windows but with the same deployment lib it fails when running on Linux. 1. I have to add backport 3.0 jar which Im not sure why since I didn't have to in my Windows sandbox. 2. apache mina 1.1.7 doesn't work with Qpid 0.5, I had to use mina 1.0.1 This is an acceptable solutions but I'm not sure why. Part of the reason is I have other libraries that will perform much better when using using the latest mina 1.1.7 on java 6. On Windows XP - these jars cause no problems mina-core-1.1.7.jar qpid-all.jar qpid-client-0.5.jar qpid-common-0.5.jar geronimo-jms_1.1_spec-1.0.jar On Linux - I have to add these jars in order for Qpid to work, backport was needed and mina needed a downgrade mina-core-1.0.1.jar backport-util-concurrent.jar qpid-all.jar qpid-client-0.5.jar qpid-common-0.5.jar geronimo-jms_1.1_spec-1.0.jar -- 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-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:all-tabpanel ] Ken Giusti updated QPID-3080: - Fix Version/s: (was: 0.9) Future 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: Future 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-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=13001481#comment-13001481 ] Ken Giusti commented on QPID-3080: -- Agreed - deferred to Future 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: Future 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] Resolved: (QPID-1353) xa.FaultTest.testRollback failure with CPP profile
[ https://issues.apache.org/jira/browse/QPID-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-1353. -- Resolution: Fixed xa.FaultTest.testRollback failure with CPP profile -- Key: QPID-1353 URL: https://issues.apache.org/jira/browse/QPID-1353 Project: Qpid Issue Type: Bug Components: C++ Broker, Java Client, Java Tests Affects Versions: M4 Reporter: Martin Ritchie Assignee: Rafael H. Schloming Attachments: TEST-org.apache.qpid.test.unit.xa.FaultTest.testRollback.out Summary: Picked up on an build system: Testcase: testRollback took 0.246 sec Caused an ERROR Error closing connection: org.apache.qpid.AMQException: javax.jms.JMSException: Error closing connection: org.apache.qpid.AMQException: at org.apache.qpid.client.AMQConnection.doClose(AMQConnection.java:936) at org.apache.qpid.client.AMQConnection.doClose(AMQConnection.java:887) at org.apache.qpid.client.AMQConnection.close(AMQConnection.java:874) at org.apache.qpid.client.AMQConnection.close(AMQConnection.java:867) at org.apache.qpid.client.AMQConnection.close(AMQConnection.java:862) at org.apache.qpid.test.unit.xa.FaultTest.tearDown(FaultTest.java:99) at org.apache.qpid.test.utils.QpidTestCase.runBare(QpidTestCase.java:186) at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:220) Full log attached in JIRA -- 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=13001503#comment-13001503 ] Ken Giusti commented on QPID-3081: -- Actually, Gordon has reviewed it (via Review Board): https://reviews.apache.org/r/453/ 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-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=13001513#comment-13001513 ] Gordon Sim commented on QPID-3081: -- Fine by me 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] Resolved: (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:all-tabpanel ] Ken Giusti resolved QPID-3081. -- Resolution: Fixed 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] Created: (QPID-3105) Alternate-Exchange configuration not communicated between nodes in a cluster
Alternate-Exchange configuration not communicated between nodes in a cluster Key: QPID-3105 URL: https://issues.apache.org/jira/browse/QPID-3105 Project: Qpid Issue Type: Bug Affects Versions: 0.9 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.9 When an exchange is declared with an alternate-exchange, the alternate-exchange is not communicated to new members joining the cluster. See https://bugzilla.redhat.com/show_bug.cgi?id=681331 -- 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] Resolved: (QPID-3105) Alternate-Exchange configuration not communicated between nodes in a cluster
[ https://issues.apache.org/jira/browse/QPID-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved QPID-3105. --- Resolution: Fixed Fix on trunk r1076375 Alternate-Exchange configuration not communicated between nodes in a cluster Key: QPID-3105 URL: https://issues.apache.org/jira/browse/QPID-3105 Project: Qpid Issue Type: Bug Affects Versions: 0.9 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.9 When an exchange is declared with an alternate-exchange, the alternate-exchange is not communicated to new members joining the cluster. See https://bugzilla.redhat.com/show_bug.cgi?id=681331 -- 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-3099) Java qpid-client ignores hostnames containing underscores
[ https://issues.apache.org/jira/browse/QPID-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13001667#comment-13001667 ] Rajith Attapattu commented on QPID-3099: I treated this as a bug based on a customer request. My first impression was that an underscore was a bit odd in a host name, but it seems they have named a host by that name. I would leave this fix as it is and leave the correct naming of hosts to the end users. Java qpid-client ignores hostnames containing underscores - Key: QPID-3099 URL: https://issues.apache.org/jira/browse/QPID-3099 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.5, 0.6, 0.8 Reporter: Rajith Attapattu Assignee: Rajith Attapattu Priority: Minor Fix For: 0.9 When defining a connection URL listing a broker that has an underscore the hostname results in the broker host being evaluated to localhost rather than the intended host. e.g. amqp://guest:guest@clientid/test?brokerlist='tcp://under_score:5672' amqp://guest:guest@clientid/test?brokerlist='tcp://under_score' -- 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-3106) QueueReceiver and TopicSubscriber does not work with new addressing
QueueReceiver and TopicSubscriber does not work with new addressing --- Key: QPID-3106 URL: https://issues.apache.org/jira/browse/QPID-3106 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.8 Reporter: Rajith Attapattu Assignee: Rajith Attapattu Fix For: 0.9 The QueueReceiver and TopicSubscriber interfaces are part of JMS. However this part of the API cannot be used with Destinations defined using the new addressing scheme. This is due to the code trying to check if the the Queue implementation is of type AMQQueue and Topic implementation is of type AMQTopic. -- 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-2930) JMS msg.getPropertyNames() method should not return x-amqp-0-10.routing-key
[
https://issues.apache.org/jira/browse/QPID-2930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13001875#comment-13001875
]
Rajith Attapattu commented on QPID-2930:
The JMS specification allows any message property to be retrieved as a string.
However the the valid types are boolean, byte, short, int, long, float, double,
and String.
Therefore in JMS, the property value cannot be a byte[] as it's not a valid
type.
However in AMQP you are allowed to have byte arrays,lists, maps, UUID's etc..
as property values.
So a broker or a non JMS client could set such a property in a message that
will be consumed by a JMS consumer.
In such a case there are two possible ways of handling it.
1) Ignore the properties (from the list provided in response to
getPropertyNames() method) that does not have a value allowed by the JMS spec.
2) Provide the standard string representation of the value.
Option #2 is fairly useless if the value is of type array, list or map.
I think option #1 is probably the best as a JMS client will not expect to
receive any property with a value that is not valid as per the spec. Therefore
it does not need to even know the name of a property that it cannot access.
JMS msg.getPropertyNames() method should not return x-amqp-0-10.routing-key
Key: QPID-2930
URL: https://issues.apache.org/jira/browse/QPID-2930
Project: Qpid
Issue Type: Bug
Components: Java Client
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Priority: Minor
Fix For: 0.9
Description of problem:
JMS msg.getPropertyNames() method should not return x-amqp-0-10.routing-key,
x-amqp-0-10.routing-key is internal property. It cause exception if loop via
ProertyName enumeration.
Code:
===
EnumerationString enu = msg.getPropertyNames();
while (enu.hasMoreElements()) {
String name = (String) enu.nextElement();
String value = msg.getStringProperty(name);
}
Exception
=
Caused by: javax.jms.MessageFormatException:
getString(x-amqp-0-10.routing-key) failed as value of type class [B is an
array.
at
org.apache.qpid.client.message.AMQMessageDelegate_0_10.getStringProperty(AMQMessageDelegate_0_10.java:639)
at
org.apache.qpid.client.message.AbstractJMSMessage.getStringProperty(AbstractJMSMessage.java:254)
--
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-2930) JMS msg.getPropertyNames() method should not return x-amqp-0-10.routing-key
[
https://issues.apache.org/jira/browse/QPID-2930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13001887#comment-13001887
]
Rajith Attapattu commented on QPID-2930:
The Qpid implementation does allow a byte[] to be set using the
setObjectProperty method, which is not correct as per the JMS specification.
I am actually fine with utilizing the set/getObjectProperty method as an
extension point to allow maps, lists, UUID, arrays etc to be used.
But we need to ensure that we have a sane way of handling these extensions
while ensure we are also spec complaint.
Maybe if getStringProperty is called we could print something like, list
please use getObjectProperty to retrieve this value correctly.
For things like UUID we could provide the toString representation of it.
Thoughts ?
JMS msg.getPropertyNames() method should not return x-amqp-0-10.routing-key
Key: QPID-2930
URL: https://issues.apache.org/jira/browse/QPID-2930
Project: Qpid
Issue Type: Bug
Components: Java Client
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Priority: Minor
Fix For: 0.9
Description of problem:
JMS msg.getPropertyNames() method should not return x-amqp-0-10.routing-key,
x-amqp-0-10.routing-key is internal property. It cause exception if loop via
ProertyName enumeration.
Code:
===
EnumerationString enu = msg.getPropertyNames();
while (enu.hasMoreElements()) {
String name = (String) enu.nextElement();
String value = msg.getStringProperty(name);
}
Exception
=
Caused by: javax.jms.MessageFormatException:
getString(x-amqp-0-10.routing-key) failed as value of type class [B is an
array.
at
org.apache.qpid.client.message.AMQMessageDelegate_0_10.getStringProperty(AMQMessageDelegate_0_10.java:639)
at
org.apache.qpid.client.message.AbstractJMSMessage.getStringProperty(AbstractJMSMessage.java:254)
--
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
