Re: 0.10 release update - generally available
On 04/28/2011 10:32 PM, Justin Ross wrote: This is to make it official: Qpid 0.10 is released. Justin, Thanks for all your work in managing this release! Really appreciated. Thanks also to all others who have been contributing through comments, doc changes, bug fixes etc. --Gordon. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Closed] (QPID-425) Implement python interop test clients.
[ https://issues.apache.org/jira/browse/QPID-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim closed QPID-425. --- Resolution: Won't Fix Interop testing of this sort needs a rethink. Implement python interop test clients. -- Key: QPID-425 URL: https://issues.apache.org/jira/browse/QPID-425 Project: Qpid Issue Type: Improvement Components: Python Client Reporter: Alan Conway Implement python equivalents for the Java interop test client, comitted by Rupert Smith, mail below: rupertlssm...@googlemail.com Skeleton of the interop test is checked in under qpid/java/integrationtests for a Java coordinator and test client. *Only the test client needs to be ported to every other language*. The outline of this may be found under the org...interop.testclient package. There is no need for other language implementations to closely follow this exampe (I used some Java enum syntax anyway, I don't know if C++ or C# has similar syntax, python/ruby probably has funky ways of doing it better). Something broadly similar would be nice, so that moving between the different implementation is easy. In particular the InteropClientTestCase interface might be worth standardizing on. Will flesh this out over the week, depending on other priorities. Also, I forgot to put the test case names in the spec, so that clients can tell which test case the invites are for. I went for: TC1_DummyRun TC2_BasicP2P TC3_BasicPubSub Will add these to the spec. Rupert -- 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] [Closed] (QPID-1041) Sources and sinks should all have names ( a problem in at least the Python client )
[ https://issues.apache.org/jira/browse/QPID-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim closed QPID-1041. Resolution: Won't Fix No longer relevant to messaging API Sources and sinks should all have names ( a problem in at least the Python client ) --- Key: QPID-1041 URL: https://issues.apache.org/jira/browse/QPID-1041 Project: Qpid Issue Type: New Feature Components: Python Client Affects Versions: M3 Reporter: Jonathan Robie Assignee: Rafael H. Schloming I would like to be able to access names for queues and exchanges: queue.name, exchange.name, analogous to session.name. This is useful for debugging, and for printing output in examples. -- 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-3240) SSL headers are not distributed
[ https://issues.apache.org/jira/browse/QPID-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028142#comment-13028142 ] Gordon Sim commented on QPID-3240: -- I'm not convinced any of the headers in qpid::sys::ssl should be public. There is only any value in exposing the ssl options (specifically the NSS SSL options I should also add) if you are initialising NSS. The initNSS method must only be called once (there must then be one shutdowm call as well) and currently the form in that header is not intended as public. I think what is needed is a high level abstraction to process level settings in general for the client or messaging apis. SSL headers are not distributed --- Key: QPID-3240 URL: https://issues.apache.org/jira/browse/QPID-3240 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.10 Reporter: Ted Ross Assignee: Ted Ross Fix For: 0.11 The header files in qpid/cpp/src/sys/ssl are not distributed and are therefore not available for developers. This is a problem for anyone who wishes to expose the SSL client options in their application because they can't include sys/ssl/util.h -- 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-3240) SSL headers are not distributed
[ https://issues.apache.org/jira/browse/QPID-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028152#comment-13028152 ] Ted Ross commented on QPID-3240: Gordon, Are you suggesting that options like certificate-path, password-file, etc. be set as connection options or is another mechanism needed? All that is needed is a way for a client application to access the SSL options supported by the ssl connector plugin. SSL headers are not distributed --- Key: QPID-3240 URL: https://issues.apache.org/jira/browse/QPID-3240 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.10 Reporter: Ted Ross Assignee: Ted Ross Fix For: 0.11 The header files in qpid/cpp/src/sys/ssl are not distributed and are therefore not available for developers. This is a problem for anyone who wishes to expose the SSL client options in their application because they can't include sys/ssl/util.h -- 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-3214) Deadlock between the failover mutex (in AMQConnection.java) and the current_exception_lock (in AMQSession.java)
[ https://issues.apache.org/jira/browse/QPID-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028247#comment-13028247 ] Rajith Attapattu commented on QPID-3214: Committed Gordon's suggested fix. It seems for some situations the exception listener is the only way to get notified about a session exception. However there was a bug which prevented exceptions being notified in some cases(see QPID-3233) and has since been fixed. Therefore I believe Gordon's suggestion is probably the correct way to go. Deadlock between the failover mutex (in AMQConnection.java) and the current_exception_lock (in AMQSession.java) --- Key: QPID-3214 URL: https://issues.apache.org/jira/browse/QPID-3214 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.10 Reporter: Rajith Attapattu Assignee: Rajith Attapattu Priority: Critical Fix For: 0.11 Attachments: QPID-3214.patch As per the following thread dump you can clearly see the deadlock between the failover mutex in AMQConnection.java and the current_exception_lock in AMQSession.java This is a regression and was introduced in rev 985262 Found one Java-level deadlock: = IoReceiver - localhost/127.0.0.1:15672: waiting to lock monitor 0x002ac2ea3b70 (object 0x002ab70156b0, a java.lang.Object), which is held by main main: waiting to lock monitor 0x002ac28db1b8 (object 0x002ab7048d70, a java.lang.Object), which is held by IoReceiver - localhost/127.0.0.1:15672 Java stack information for the threads listed above: === IoReceiver - localhost/127.0.0.1:15672: at org.apache.qpid.client.AMQConnection.exceptionReceived(AMQConnection.java:1297) - waiting to lock0x002ab70156b0 (a java.lang.Object) at org.apache.qpid.client.AMQSession_0_10.setCurrentException(AMQSession_0_10.java:1033) - locked0x002ab7048d70 (a java.lang.Object) at org.apache.qpid.client.AMQSession_0_10.exception(AMQSession_0_10.java:913) at org.apache.qpid.transport.SessionDelegate.executionException(SessionDelegate.java:156) at org.apache.qpid.transport.SessionDelegate.executionException(SessionDelegate.java:32) at org.apache.qpid.transport.ExecutionException.dispatch(ExecutionException.java:112) at org.apache.qpid.transport.SessionDelegate.command(SessionDelegate.java:50) at org.apache.qpid.transport.SessionDelegate.command(SessionDelegate.java:32) at org.apache.qpid.transport.Method.delegate(Method.java:159) at org.apache.qpid.transport.Session.received(Session.java:528) at org.apache.qpid.transport.Connection.dispatch(Connection.java:404) at org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:64) at org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:40) at org.apache.qpid.transport.MethodDelegate.executionException(MethodDelegate.java:110) at org.apache.qpid.transport.ExecutionException.dispatch(ExecutionException.java:112) at org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:54) at org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:40) at org.apache.qpid.transport.Method.delegate(Method.java:159) at org.apache.qpid.transport.Connection.received(Connection.java:369) at org.apache.qpid.transport.Connection.received(Connection.java:59) at org.apache.qpid.transport.network.Assembler.emit(Assembler.java:95) at org.apache.qpid.transport.network.Assembler.assemble(Assembler.java:196) at org.apache.qpid.transport.network.Assembler.frame(Assembler.java:129) at org.apache.qpid.transport.network.Frame.delegate(Frame.java:133) at org.apache.qpid.transport.network.Assembler.received(Assembler.java:100) at org.apache.qpid.transport.network.Assembler.received(Assembler.java:42) at org.apache.qpid.transport.network.InputHandler.next(InputHandler.java:187) at org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:103) at org.apache.qpid.transport.network.InputHandler.received(InputHandler.java:42) at org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:128) at java.lang.Thread.run(Thread.java:619) main: at org.apache.qpid.client.AMQSession_0_10.setCurrentException(AMQSession_0_10.java:1025) - waiting to lock0x002ab7048d70 (a java.lang.Object) at
Re: 0.10 release update - generally available
On Mon, 2 May 2011, Robbie Gemmell wrote: On 2 May 2011 18:01, Rajith Attapattu rajit...@gmail.com wrote: http://qpid.apache.org/release_notes_0.10.html Justin, the above link does not seem to contain the following sections. Changes requiring user attention Known issues Is this deliberate or was this an oversight ? I would prefer if we can include the above in our release notes as well. My bad, I simply put together a similar page to the one I did previously to consolidate the JIRA issues. I have applied Justin's patch to update it. Thank you, Robbie. I have one more thing to ask. I sampled some previous announcements, and they're all from @apache.org mail addresses. I don't have one of those to send from, and I want to avoid any faux pas. Would you post the release announcement to annou...@apache.org? Justin --- The Apache Qpid community is pleased to announce the immediate availability of Apache Qpid 0.10. Apache Qpid (http://qpid.apache.org) is a cross-platform enterprise messaging solution which implements the Advanced Message Queuing Protocol (AMQP, http://www.amqp.org). It provides brokers written in C++ and Java, along with clients for C++, Java JMS, .Net, Python, and Ruby. Qpid 0.10 is available from our website: http://qpid.apache.org/download.cgi The 0.10 release has undergone a lot of bug fixing and feature enhancement. We recommend that all users upgrade. A few changes of note: - The C++ broker now supports priority-ordered message queueing - The C++ broker and client now implement producer flow control - The Java JMS client is now available via Maven A comprehensive list of features, improvements, and bugs resolved in the 0.10 release is available here: http://qpid.apache.org/release_notes_0.10.html Thanks to all the users and contributors who have helped to improve Apache Qpid. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
RE: 0.10 release update - generally available
On Mon, 2011-05-02 at 15:35 -0400, Sean MacDonald wrote: Hello, I was wondering if there is going to be a tagged release of the persistence store for this release? Thanks and have a great day, Sean Yes, it is r.4446, also tagged as qpid-1.10-release. The FAQ has been updated with this information: https://cwiki.apache.org/confluence/display/qpid/FAQ#FAQ-WhichversionofthestoreshouldIusewhenbuildingagainstqpid0.X%3F Kim - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[ANNOUNCE] Apache Qpid 0.10 released
The Apache Qpid community is pleased to announce the immediate availability of Apache Qpid 0.10. Apache Qpid (http://qpid.apache.org) is a cross-platform enterprise messaging solution which implements the Advanced Message Queuing Protocol (AMQP, http://www.amqp.org). It provides brokers written in C++ and Java, along with clients for C++, Java JMS, .Net, Python, and Ruby. Qpid 0.10 is available from our website: http://qpid.apache.org/download.cgi The 0.10 release has undergone a lot of bug fixing and feature enhancement. We recommend that all users upgrade. A few changes of note: - The C++ broker now supports priority-ordered message queuing - The C++ broker and client now implement producer flow control - The Java JMS client is now available via Maven A comprehensive list of features, improvements, and bugs resolved in the 0.10 release is available here: http://qpid.apache.org/release_notes_0.10.html - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: 0.10 release update - generally available
Done, its just waiting for moderation onto the list and so should hopefully show up shortly. I bungled the email and forgot to add our user and dev lists to it, so I sent that on separately :) Robbie On 3 May 2011 15:37, Justin Ross jr...@redhat.com wrote: Thank you, Robbie. I have one more thing to ask. I sampled some previous announcements, and they're all from @apache.org mail addresses. I don't have one of those to send from, and I want to avoid any faux pas. Would you post the release announcement to annou...@apache.org? Justin - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Created] (QPID-3241) Deadlock in qmf agent triggered by producer flow control
Deadlock in qmf agent triggered by producer flow control Key: QPID-3241 URL: https://issues.apache.org/jira/browse/QPID-3241 Project: Qpid Issue Type: Bug Components: Qpid Managment Framework Affects Versions: 0.10 Reporter: Ted Ross Assignee: Ted Ross Fix For: 0.11 The remote agent (cpp/src/qpid/agent) occasionally holds a mutex while calling message_transfer. If the message send is blocked waiting for a completion, the agent can deadlock because a received message callback that causes the lock to be acquired will never return and the callback thread is needed to process completions. -- 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-3227) rdma layer may allow overrun of send buffers
[ https://issues.apache.org/jira/browse/QPID-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved QPID-3227. -- Resolution: Fixed rdma layer may allow overrun of send buffers Key: QPID-3227 URL: https://issues.apache.org/jira/browse/QPID-3227 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.10 Reporter: Ken Giusti Assignee: Ken Giusti Fix For: 0.11 Attachments: QPID-3227.patch The rdma driver adds a small trailer to outbound buffers, however the size of this header is not accounted for when the buffer's size is passed to the codec. If the codec fills all available buffer space, the rdma driver will overwrite the end of the buffer when adding the trailer. Kudos to Chuck Rolke for helping root-cause this bug! -- 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-3076) Enable producer flow control (QPID-2935) in a cluster
[ https://issues.apache.org/jira/browse/QPID-3076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved QPID-3076. -- Resolution: Fixed Enable producer flow control (QPID-2935) in a cluster - Key: QPID-3076 URL: https://issues.apache.org/jira/browse/QPID-3076 Project: Qpid Issue Type: New Feature Components: C++ Clustering Affects Versions: 0.9, 0.10 Reporter: Alan Conway Assignee: Ken Giusti Fix For: 0.11 Attachments: QPID-3076-2.patch QPID-2935 adds producer flow control to the broker, but it is disabled in a cluster. Flow control adds additional broker state that must be replicated in a cluster in order to maintain cluster consistency. Add this replication and enable flow control in a cluster. -- 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: [ANNOUNCE] Apache Qpid 0.10 released
As a first-time release manager who needed help and advice at many turns, I'd like to especially thank Robbie Gemmell and Andrew Stitcher for taking on tasks I couldn't perform, picking up things I missed, and guiding me along. It's a pleasure to work with thoughtful people. Justin On Tue, 3 May 2011, Robbie Gemmell wrote: The Apache Qpid community is pleased to announce the immediate availability of Apache Qpid 0.10. Apache Qpid (http://qpid.apache.org) is a cross-platform enterprise messaging solution which implements the Advanced Message Queuing Protocol (AMQP, http://www.amqp.org). It provides brokers written in C++ and Java, along with clients for C++, Java JMS, .Net, Python, and Ruby. Qpid 0.10 is available from our website: http://qpid.apache.org/download.cgi The 0.10 release has undergone a lot of bug fixing and feature enhancement. We recommend that all users upgrade. A few changes of note: - The C++ broker now supports priority-ordered message queuing - The C++ broker and client now implement producer flow control - The Java JMS client is now available via Maven A comprehensive list of features, improvements, and bugs resolved in the 0.10 release is available here: http://qpid.apache.org/release_notes_0.10.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
[jira] [Commented] (QPID-3240) SSL headers are not distributed
[ https://issues.apache.org/jira/browse/QPID-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028343#comment-13028343 ] Gordon Sim commented on QPID-3240: -- The only NSS/SSL option that is per-connection is the certificate name which is now settable as a connection option. The other options for NSS are per-process. Those are passed to NSS on first initialising it, and cannt be modified subsequently. SSL headers are not distributed --- Key: QPID-3240 URL: https://issues.apache.org/jira/browse/QPID-3240 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.10 Reporter: Ted Ross Assignee: Ted Ross Fix For: 0.11 The header files in qpid/cpp/src/sys/ssl are not distributed and are therefore not available for developers. This is a problem for anyone who wishes to expose the SSL client options in their application because they can't include sys/ssl/util.h -- 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-3242) Unexplained behaviour when assertions and auto-delete are combined
Unexplained behaviour when assertions and auto-delete are combined -- Key: QPID-3242 URL: https://issues.apache.org/jira/browse/QPID-3242 Project: Qpid Issue Type: Bug Components: Python Client Affects Versions: 0.11 Reporter: Gordon Sim Attached test results in a not-found exception on reusing an address that is set to an auto-created queue with server side auto-delete as well as a delete policy set. The assertion step is needed to trigger the issue, but I can't explain the behaviour. May not be a bug per-se, just not obvious why it is doing what it is doing. Appears that second time round the auto-creation is not triggered on sender and so the subscription for the receiver fails. Guessing that it is due to the address resolution cache being used as there does not appear to be another queue/exchange query. However I don't get why the assertion is the triggering of that. -- 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-3242) Unexplained behaviour when assertions and auto-delete are combined
[ https://issues.apache.org/jira/browse/QPID-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated QPID-3242: - Attachment: test.py Test program Unexplained behaviour when assertions and auto-delete are combined -- Key: QPID-3242 URL: https://issues.apache.org/jira/browse/QPID-3242 Project: Qpid Issue Type: Bug Components: Python Client Affects Versions: 0.11 Reporter: Gordon Sim Attachments: test.py Attached test results in a not-found exception on reusing an address that is set to an auto-created queue with server side auto-delete as well as a delete policy set. The assertion step is needed to trigger the issue, but I can't explain the behaviour. May not be a bug per-se, just not obvious why it is doing what it is doing. Appears that second time round the auto-creation is not triggered on sender and so the subscription for the receiver fails. Guessing that it is due to the address resolution cache being used as there does not appear to be another queue/exchange query. However I don't get why the assertion is the triggering of that. -- 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-3218) AttributeError: 'NoneType' object has no attribute 'write_cmds'
[ https://issues.apache.org/jira/browse/QPID-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated QPID-3218: - Attachment: test.py The attached simple test results in a similar error: qpid.messaging.exceptions.InternalError: Traceback (most recent call last): File /home/gordon/projects/qpid-svn-trunk/python/qpid/messaging/driver.py, line 507, in dispatch self.engine.dispatch() File /home/gordon/projects/qpid-svn-trunk/python/qpid/messaging/driver.py, line 810, in dispatch self.attach(ssn) File /home/gordon/projects/qpid-svn-trunk/python/qpid/messaging/driver.py, line 851, in attach self.link(snd, self._out, snd.target) File /home/gordon/projects/qpid-svn-trunk/python/qpid/messaging/driver.py, line 894, in link self.resolve_declare(sst, _lnk, dir.DIR_NAME, resolved) File /home/gordon/projects/qpid-svn-trunk/python/qpid/messaging/driver.py, line 955, in resolve_declare self.resolve(sst, lnk.name, do_resolved, force=declare) File /home/gordon/projects/qpid-svn-trunk/python/qpid/messaging/driver.py, line 981, in resolve sst.write_query(ExchangeQuery(name), do_result) AttributeError: 'NoneType' object has no attribute 'write_query' Attaching in case reproducing that sheds light on the larger issue. (note this is the same test as for the unrelated QPID-3242 but with the actual send/fetch commented out). AttributeError: 'NoneType' object has no attribute 'write_cmds' --- Key: QPID-3218 URL: https://issues.apache.org/jira/browse/QPID-3218 Project: Qpid Issue Type: Bug Components: Python Client Affects Versions: 0.7 Environment: OS=RHEL6 python-qpid-0.7.946106-12.el6.noarch qpid-cpp-client-0.7.946106-5.el6.x86_64 qpid-cpp-server-0.7.946106-5.el6.x86_64 qpid broker on main server and all the nodes are vm's with bridged configuration in a single network. Reporter: Jeff Ortel Attachments: test.py 2011-04-19 22:05:07,321 [ERROR][asynctaskreplyqueue] __fetch() @ consumer.py:90 - asynctaskreplyqueue Traceback (most recent call last): File /usr/lib/python2.6/site-packages/gofer/messaging/consumer.py, line 86, in __fetch return self.receiver.fetch(timeout=self.WAIT) File string, line 6, in fetch File /usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py, line 994, in fetch self._ecwait(lambda: self.linked) File /usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py, line 50, in _ecwait result = self._ewait(lambda: self.closed or predicate(), timeout) File /usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py, line 957, in _ewait result = self.session._ewait(lambda: self.error or predicate(), timeout) File /usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py, line 550, in _ewait result = self.connection._ewait(lambda: self.error or predicate(), timeout) File /usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py, line 194, in _ewait self.check_error() File /usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py, line 187, in check_error raise self.error InternalError: Traceback (most recent call last): File /usr/lib/python2.6/site-packages/qpid/messaging/driver.py, line 496, in dispatch self.engine.dispatch() File /usr/lib/python2.6/site-packages/qpid/messaging/driver.py, line 791, in dispatch self.attach(ssn) File /usr/lib/python2.6/site-packages/qpid/messaging/driver.py, line 834, in attach self.link(rcv, self._in, rcv.source) File /usr/lib/python2.6/site-packages/qpid/messaging/driver.py, line 885, in link dir.do_unlink(sst, lnk, _lnk) File /usr/lib/python2.6/site-packages/qpid/messaging/driver.py, line 261, in do_unlink sst.write_cmds(cmds, action) AttributeError: 'NoneType' object has no attribute 'write_cmds' -- 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
workaround for buggy persistent limit-policy ring?
This message[0] seems to confirm that persistent ring queues break hard when they reach capacity, rather than wrapping gracefully. Further, that breaking point is rather difficult to compute in advance. Is there a practicable workaround for those who want persistent storage and a ring limit policy for a broker's queue? -Mike [0]: http://mail-archives.apache.org/mod_mbox/qpid-dev/201104.mbox/%3c4db92366.8090...@redhat.com%3E
[jira] [Commented] (QPID-3240) SSL headers are not distributed
[ https://issues.apache.org/jira/browse/QPID-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028368#comment-13028368 ] Ted Ross commented on QPID-3240: Then that would suggest that exposing util.h is the right way to go. This way, an application developer can add command-line options to his program so they could be passed in per-process. SSL headers are not distributed --- Key: QPID-3240 URL: https://issues.apache.org/jira/browse/QPID-3240 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.10 Reporter: Ted Ross Assignee: Ted Ross Fix For: 0.11 The header files in qpid/cpp/src/sys/ssl are not distributed and are therefore not available for developers. This is a problem for anyone who wishes to expose the SSL client options in their application because they can't include sys/ssl/util.h -- 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-3240) SSL headers are not distributed
[ https://issues.apache.org/jira/browse/QPID-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028394#comment-13028394 ] Gordon Sim commented on QPID-3240: -- I disagree. Firstly, that is likely to result in duplicate calls to initNSS(), secondly I think it ties applications to a particular module. I believe the right solution is an abstraction of per process settings that underneath can handle setting the NSS variables etc. SSL headers are not distributed --- Key: QPID-3240 URL: https://issues.apache.org/jira/browse/QPID-3240 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.10 Reporter: Ted Ross Assignee: Ted Ross Fix For: 0.11 The header files in qpid/cpp/src/sys/ssl are not distributed and are therefore not available for developers. This is a problem for anyone who wishes to expose the SSL client options in their application because they can't include sys/ssl/util.h -- 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-3243) C++ broker ignores --max-queue-count queue size parameter when setting default queue flow limits.
C++ broker ignores --max-queue-count queue size parameter when setting default queue flow limits. - Key: QPID-3243 URL: https://issues.apache.org/jira/browse/QPID-3243 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.10 Reporter: Ken Giusti Assignee: Ken Giusti Priority: Minor Fix For: 0.11 If a user configures a maximum queue size based on message count via qpid-config, the default producer flow control limits are not correctly computed. Steps to Reproduce: 1. qpid-config add queue fleabag --max-queue-count=1000 Actual results: Queue is created without msg-count based flow control limits: 2011-05-03 16:15:57 info Queue fleabag: Policy created: type=reject; maxCount=1000; maxSize=104857600 2011-05-03 16:15:57 info Queue fleabag: Flow limit created: flowStopCount=0, flowResumeCount=0, flowStopSize=83886080, flowResumeSize=73400320 Expected results: Queue should be created with flowStopCount=800 flowResumeCount=700 (using broker-wide default ratios). -- 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-3244) C++ broker should release flow control for a queue when it is deleted.
C++ broker should release flow control for a queue when it is deleted. -- Key: QPID-3244 URL: https://issues.apache.org/jira/browse/QPID-3244 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.10 Reporter: Ken Giusti Assignee: Ken Giusti Fix For: 0.11 When deleting a queue that contains messages that are pending flow control, the flow control should be released. -- 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-3245) AMQSession_0_10 ack flusher timer task should be canceled when the underlying session is closed.
AMQSession_0_10 ack flusher timer task should be canceled when the underlying session is closed. Key: QPID-3245 URL: https://issues.apache.org/jira/browse/QPID-3245 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.10, 0.8 Reporter: Rajith Attapattu Assignee: Rajith Attapattu Priority: Minor Fix For: 0.11 The ack flusher timer task continues to fire even after a session is closed due to an error. This results in errors being logged repeatedly due to the ssn acknowledge call failing. The timer task should be cancelled when the session is closed. -- 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
