[jira] [Updated] (QPID-3936) Add new framework for running distributed tests, eg for performance testing

[ https://issues.apache.org/jira/browse/QPID-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-3936: - Status: Ready To Review (was: In Progress) > Add new framework for running distributed tests, eg for

[jira] [Commented] (QPID-3936) Add new framework for running distributed tests, eg for performance testing

[ https://issues.apache.org/jira/browse/QPID-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283850#comment-13283850 ] Keith Wall commented on QPID-3936: -- Committed patch to change ProducerParticipant to cance

[jira] [Updated] (QPID-3936) Add new framework for running distributed tests, eg for performance testing

[ https://issues.apache.org/jira/browse/QPID-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-3936: - Attachment: (was: 0001-QPID-3936-producer-participant-can-be-interrupt-mess.patch) > Add new fram

[jira] [Updated] (QPID-3936) Add new framework for running distributed tests, eg for performance testing

[ https://issues.apache.org/jira/browse/QPID-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-3936: - Comment: was deleted (was: Patch: Producer participant can be interrupt message sends when maximumDuratio

[jira] [Assigned] (QPID-3983) Provides aliases in the Swig Ruby bindings for the C++ class names.

[ https://issues.apache.org/jira/browse/QPID-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned QPID-3983: -- Assignee: Ted Ross > Provides aliases in the Swig Ruby bindings for the C++ class names. > -

[jira] [Updated] (QPID-3983) Provides aliases in the Swig Ruby bindings for the C++ class names.

[ https://issues.apache.org/jira/browse/QPID-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Pierce updated QPID-3983: --- Attachment: 0001-Provide-a-prefix-in-Swig-to-differentiate-C-from-Rub.patch > Provides ali

[jira] [Commented] (QPID-4021) Badly behaved clients can still clog up the broker

[ https://issues.apache.org/jira/browse/QPID-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283723#comment-13283723 ] Andrew Stitcher commented on QPID-4021: --- This is CVE-2012-2145 > Bad

[jira] [Created] (QPID-4022) C++ Broker connection limits by host ip and by user name can get confused

Chuck Rolke created QPID-4022: - Summary: C++ Broker connection limits by host ip and by user name can get confused Key: QPID-4022 URL: https://issues.apache.org/jira/browse/QPID-4022 Project: Qpid

[jira] [Resolved] (QPID-3992) Removed the Boost license text from the Ruby LICENSE file.

[ https://issues.apache.org/jira/browse/QPID-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-3992. Resolution: Fixed Fix Version/s: 0.17 > Removed the Boost license text from the Ruby LICENSE file

[jira] [Assigned] (QPID-3992) Removed the Boost license text from the Ruby LICENSE file.

[ https://issues.apache.org/jira/browse/QPID-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned QPID-3992: -- Assignee: Ted Ross > Removed the Boost license text from the Ruby LICENSE file. > --

[jira] [Resolved] (QPID-3995) Cleans up queues created during Cucumber feature tests

[ https://issues.apache.org/jira/browse/QPID-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-3995. Resolution: Fixed Fix Version/s: 0.17 > Cleans up queues created during Cucumber feature tests >

[jira] [Commented] (QPID-4012) Qpid java Broker Priority Queue Runs into Exception(Metadata not found for message with id 1330312 [error code 541: internal error])

[ https://issues.apache.org/jira/browse/QPID-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283686#comment-13283686 ] Praveen Murugesan commented on QPID-4012: - Hi Robbie, Thanks for the quick update.

[jira] [Assigned] (QPID-3995) Cleans up queues created during Cucumber feature tests

[ https://issues.apache.org/jira/browse/QPID-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned QPID-3995: -- Assignee: Ted Ross > Cleans up queues created during Cucumber feature tests > --

Re: Review Request: QPID-3603: Allow Queue::setPosition() to truncate the queue.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/5231/ --- (Updated 2012-05-25 17:55:24.171088) Review request for qpid, Gordon Sim and Ken

Re: Review Request: QPID-3603: Allow Queue::setPosition() to truncate the queue.

> On 2012-05-25 14:49:56, Gordon Sim wrote: > > /trunk/qpid/cpp/src/qpid/broker/Messages.h, line 108 > > > > > > Is this still used? Yes. Even if you dequeue all the messages>=N you can't just push message N, you need

[jira] [Created] (QPID-4021) Badly behaved clients can still clog up the broker

Andrew Stitcher created QPID-4021: - Summary: Badly behaved clients can still clog up the broker Key: QPID-4021 URL: https://issues.apache.org/jira/browse/QPID-4021 Project: Qpid Issue Type: B

[jira] [Updated] (QPID-4021) Badly behaved clients can still clog up the broker

[ https://issues.apache.org/jira/browse/QPID-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated QPID-4021: -- Component/s: C++ Broker Affects Version/s: 0.17 > Badly behaved clients can still

Re: Apache CI Python against CPP (Qpid-Python-Cpp-Test) tests failing for the last few days

On 05/25/2012 05:08 PM, Andrew Stitcher wrote: On Fri, 2012-05-25 at 16:39 +0100, Gordon Sim wrote: ... FWIW I really don't like that code. Neither do I, possibly for different reasons. It doesn't actually protect from badly behaved client code anyway, only from one specific case. Provid

[jira] [Commented] (QPID-2518) Qpid C++ broker can easily be blocked by client trying to connect over SSL port

[ https://issues.apache.org/jira/browse/QPID-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283567#comment-13283567 ] Andrew Stitcher commented on QPID-2518: --- Good point - that'll teach me to actually re

Re: Apache CI Python against CPP (Qpid-Python-Cpp-Test) tests failing for the last few days

On Fri, 2012-05-25 at 16:39 +0100, Gordon Sim wrote: > ... > FWIW I really don't like that code. Neither do I, possibly for different reasons. > > It doesn't actually protect from badly behaved client code anyway, only > from one specific case. Provided you send a valid AMQP header you can >

Re: Apache CI Python against CPP (Qpid-Python-Cpp-Test) tests failing for the last few days

On 05/25/2012 03:59 PM, Andrew Stitcher wrote: On Thu, 2012-05-24 at 08:59 +0100, Keith W wrote: Hello The Qpid-Python-Cpp-Test started to fail on May 21st. Many tests are failing and others are begin skipped. I turned on DEBUG logging from the Python tests, and logging from the CPP Broker,

[jira] [Commented] (QPID-2518) Qpid C++ broker can easily be blocked by client trying to connect over SSL port

[ https://issues.apache.org/jira/browse/QPID-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283542#comment-13283542 ] Gordon Sim commented on QPID-2518: -- The bug as originally reported related to broker *thre

[jira] [Updated] (QPID-4012) Qpid java Broker Priority Queue Runs into Exception(Metadata not found for message with id 1330312 [error code 541: internal error])

[ https://issues.apache.org/jira/browse/QPID-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4012: - Fix Version/s: 0.17 > Qpid java Broker Priority Queue Runs into Exception(Metadata not found f

[jira] [Updated] (QPID-4012) Qpid java Broker Priority Queue Runs into Exception(Metadata not found for message with id 1330312 [error code 541: internal error])

[ https://issues.apache.org/jira/browse/QPID-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4012: - Status: Ready To Review (was: In Progress) > Qpid java Broker Priority Queue Runs into Except

[jira] [Commented] (QPID-4012) Qpid java Broker Priority Queue Runs into Exception(Metadata not found for message with id 1330312 [error code 541: internal error])

[ https://issues.apache.org/jira/browse/QPID-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283515#comment-13283515 ] Robbie Gemmell commented on QPID-4012: -- I have made an update to change how the priori

[jira] [Updated] (QPID-4012) Qpid java Broker Priority Queue Runs into Exception(Metadata not found for message with id 1330312 [error code 541: internal error])

[ https://issues.apache.org/jira/browse/QPID-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4012: - Attachment: 0001-QPID-4012-update-the-priority-queue-entry-sub-lists-.patch > Qpid java Broker

Re: Apache CI Python against CPP (Qpid-Python-Cpp-Test) tests failing for the last few days

On Thu, 2012-05-24 at 08:59 +0100, Keith W wrote: > Hello > > The Qpid-Python-Cpp-Test started to fail on May 21st. Many tests are > failing and others are begin skipped. I turned on DEBUG logging from the > Python tests, and logging from the CPP Broker, but it is no obvious to me > what has go

Re: Review Request: QPID-3603: Allow Queue::setPosition() to truncate the queue.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/5231/#review8108 --- /trunk/qpid/cpp/src/qpid/broker/Messages.h

[jira] [Assigned] (QPID-4012) Qpid java Broker Priority Queue Runs into Exception(Metadata not found for message with id 1330312 [error code 541: internal error])

[ https://issues.apache.org/jira/browse/QPID-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-4012: Assignee: Robbie Gemmell > Qpid java Broker Priority Queue Runs into Exception(Metadata

[jira] [Created] (QPID-4020) qpid-0.16 cpp/bindings/qmf/python error

sprasad created QPID-4020: - Summary: qpid-0.16 cpp/bindings/qmf/python error Key: QPID-4020 URL: https://issues.apache.org/jira/browse/QPID-4020 Project: Qpid Issue Type: Bug Components: C+

Re: Review Request: QPID-3603: Allow Queue::setPosition() to truncate the queue.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/5231/#review8107 --- Ship it! My paranoid side would want the various truncate() methods t

Re: Review Request: QPID-3603: Allow Queue::setPosition() to truncate the queue.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/5231/ --- (Updated 2012-05-25 13:56:33.796720) Review request for qpid, Gordon Sim and Ken

[jira] [Closed] (QPID-4018) AMQP 0-10: AMQSession.getQueueDepth() timed out because of "Received a response to a command that's no longer valid"

[ https://issues.apache.org/jira/browse/QPID-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy closed QPID-4018. Resolution: Not A Problem Assignee: Alex Rudyy JMS session cannot be used concurrently from multiple t

[jira] [Commented] (QPID-4018) AMQP 0-10: AMQSession.getQueueDepth() timed out because of "Received a response to a command that's no longer valid"

[ https://issues.apache.org/jira/browse/QPID-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283415#comment-13283415 ] Alex Rudyy commented on QPID-4018: -- The test application was sending messages with produce

Re: Review Request: QPID-3603: Allow Queue::setPosition() to truncate the queue.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/5231/ --- (Updated 2012-05-25 13:30:33.894584) Review request for qpid, Gordon Sim and Ken

[jira] [Updated] (QPID-4018) AMQP 0-10: AMQSession.getQueueDepth() timed out because of "Received a response to a command that's no longer valid"

[ https://issues.apache.org/jira/browse/QPID-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-4018: - Attachment: client.log Attached excerpts from client log reproducing the issue > AMQP 0-

[jira] [Updated] (QPID-4018) AMQP 0-10: AMQSession.getQueueDepth() timed out because of "Received a response to a command that's no longer valid"

[ https://issues.apache.org/jira/browse/QPID-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-4018: - Attachment: qpid.queue-query-error.log.gz broker log > AMQP 0-10: AMQSession.getQueueDept

[jira] [Created] (QPID-4019) connection/session close() blocks for default of 120 seconds while producer is blocked by flow control

Alex Rudyy created QPID-4019: Summary: connection/session close() blocks for default of 120 seconds while producer is blocked by flow control Key: QPID-4019 URL: https://issues.apache.org/jira/browse/QPID-4019

[jira] [Assigned] (QPID-4017) AMQP 0-9: Failover causes flow control blocked flag to get stuck

[ https://issues.apache.org/jira/browse/QPID-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-4017: Assignee: Philip Harvey (was: Alex Rudyy) > AMQP 0-9: Failover causes flow control blocked flag

[jira] [Updated] (QPID-4017) AMQP 0-9: Failover causes flow control blocked flag to get stuck

[ https://issues.apache.org/jira/browse/QPID-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-4017: - Status: Ready To Review (was: In Progress) > AMQP 0-9: Failover causes flow control blocked flag to g

[jira] [Assigned] (QPID-4017) AMQP 0-9: Failover causes flow control blocked flag to get stuck

[ https://issues.apache.org/jira/browse/QPID-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-4017: Assignee: Alex Rudyy > AMQP 0-9: Failover causes flow control blocked flag to get stuck > -

[jira] [Updated] (QPID-4017) AMQP 0-9: Failover causes flow control blocked flag to get stuck

[ https://issues.apache.org/jira/browse/QPID-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-4017: - Attachment: 0001-QPID-4017-reset-the-session-flow-control-blocked-sta.patch > AMQP 0-9: Failover cause

[jira] [Updated] (QPID-4018) AMQP 0-10: AMQSession.getQueueDepth() timed out because of "Received a response to a command that's no longer valid"

[ https://issues.apache.org/jira/browse/QPID-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-4018: - Description: When testing the disk quota functionality added in QPID-3986, our test program failed becaus

[jira] [Created] (QPID-4018) AMQP 0-10: AMQSession.getQueueDepth() timed out because of "Received a response to a command that's no longer valid"

Alex Rudyy created QPID-4018: Summary: AMQP 0-10: AMQSession.getQueueDepth() timed out because of "Received a response to a command that's no longer valid" Key: QPID-4018 URL: https://issues.apache.org/jira/browse/QPI

[jira] [Created] (QPID-4017) AMQP 0-9: Failover causes flow control blocked flag to get stuck

Alex Rudyy created QPID-4017: Summary: AMQP 0-9: Failover causes flow control blocked flag to get stuck Key: QPID-4017 URL: https://issues.apache.org/jira/browse/QPID-4017 Project: Qpid Issue T

[jira] [Updated] (QPID-4009) Make failover method invocation timeout configurable for 0-8/0-9/0-9-1 amqp clients

[ https://issues.apache.org/jira/browse/QPID-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-4009: - Attachment: 0001-QPID-4009-Make-failover-method-invocation-timeout-co.patch > Make failover method inv

[jira] [Updated] (QPID-4009) Make failover method invocation timeout configurable for 0-8/0-9/0-9-1 amqp clients

[ https://issues.apache.org/jira/browse/QPID-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-4009: - Attachment: (was: 0001-QPID-4009-Make-failover-method-invocation-timeout-co.patch) > Make failove

Re: Review Request: QPID-3603: Allow Queue::setPosition() to truncate the queue.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/5231/#review8098 --- /trunk/qpid/cpp/src/qpid/broker/Messages.h