[jira] [Created] (QPID-6112) [C++ broker] Incoming QMF objects dont update transfers counter

Pavel Moravec created QPID-6112: --- Summary: [C++ broker] Incoming QMF objects dont update transfers counter Key: QPID-6112 URL: https://issues.apache.org/jira/browse/QPID-6112 Project: Qpid

[jira] [Closed] (QPID-6112) [C++ broker] Incoming QMF objects dont update transfers counter

[ https://issues.apache.org/jira/browse/QPID-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec closed QPID-6112. --- Resolution: Fixed Committed revision 1626808. [C++ broker] Incoming QMF objects dont update

[jira] [Closed] (QPID-6087) QMF Session name to contain user ID for AMQP 0-10

[ https://issues.apache.org/jira/browse/QPID-6087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec closed QPID-6087. --- QMF Session name to contain user ID for AMQP 0-10 --

[jira] [Resolved] (QPID-6087) QMF Session name to contain user ID for AMQP 0-10

[ https://issues.apache.org/jira/browse/QPID-6087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec resolved QPID-6087. - Resolution: Fixed Fix Version/s: 0.31 Committed revision 1624473. QMF Session name to

[jira] [Resolved] (QPID-2305) Remote IP authentication

[ https://issues.apache.org/jira/browse/QPID-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec resolved QPID-2305. - Resolution: Fixed Fix Version/s: 0.29 QPID-4947 implements basically the same RFE as raised

[jira] [Commented] (QPID-6091) Qpid should configure SASL

[ https://issues.apache.org/jira/browse/QPID-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14129749#comment-14129749 ] Pavel Moravec commented on QPID-6091: - FYI one can use ANONYMOUS mechanism that does

[jira] [Created] (QPID-6087) QMF Session name to contain user ID for AMQP 0-10

Pavel Moravec created QPID-6087: --- Summary: QMF Session name to contain user ID for AMQP 0-10 Key: QPID-6087 URL: https://issues.apache.org/jira/browse/QPID-6087 Project: Qpid Issue Type: Bug

[jira] [Updated] (QPID-6033) [C++ broker] Session statistics sessUnacked wrongly updated

[ https://issues.apache.org/jira/browse/QPID-6033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec updated QPID-6033: Description: sessUnacked counter for a subscriber gets updated only when re-issuing credit on the

[jira] [Created] (QPID-6033) [C++ broker] Session statistics sessUnacked wrongly updated

Pavel Moravec created QPID-6033: --- Summary: [C++ broker] Session statistics sessUnacked wrongly updated Key: QPID-6033 URL: https://issues.apache.org/jira/browse/QPID-6033 Project: Qpid Issue

[jira] [Commented] (QPID-6033) [C++ broker] Session statistics sessUnacked wrongly updated

[ https://issues.apache.org/jira/browse/QPID-6033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14106788#comment-14106788 ] Pavel Moravec commented on QPID-6033: - Something like: DeliveryRecords::iterator

[jira] [Commented] (QPID-6007) qpid-route uses machine hostname if host not given

[ https://issues.apache.org/jira/browse/QPID-6007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14099945#comment-14099945 ] Pavel Moravec commented on QPID-6007: - Works well on RHEL[5-6] where hostname does not

[jira] [Resolved] (QPID-5938) qpid-stat: remove dead code relevant to active-active cluster

[ https://issues.apache.org/jira/browse/QPID-5938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec resolved QPID-5938. - Resolution: Fixed Fix Version/s: Future qpid-stat: remove dead code relevant to

[jira] [Closed] (QPID-5938) qpid-stat: remove dead code relevant to active-active cluster

[ https://issues.apache.org/jira/browse/QPID-5938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec closed QPID-5938. --- qpid-stat: remove dead code relevant to active-active cluster

[jira] [Created] (QPID-5945) qpid-config to pass integer arguments whenever possible

Pavel Moravec created QPID-5945: --- Summary: qpid-config to pass integer arguments whenever possible Key: QPID-5945 URL: https://issues.apache.org/jira/browse/QPID-5945 Project: Qpid Issue Type:

[jira] [Resolved] (QPID-5945) qpid-config to pass integer arguments whenever possible

[ https://issues.apache.org/jira/browse/QPID-5945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec resolved QPID-5945. - Resolution: Fixed Fix Version/s: Future Fix based on Zdenek Kraus's idea in

[jira] [Closed] (QPID-5945) qpid-config to pass integer arguments whenever possible

[ https://issues.apache.org/jira/browse/QPID-5945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec closed QPID-5945. --- qpid-config to pass integer arguments whenever possible

[jira] [Closed] (QPID-5929) [C++ broker] Mark deprecated QMF fields as Deprecated in management-schema.xml

[ https://issues.apache.org/jira/browse/QPID-5929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec closed QPID-5929. --- [C++ broker] Mark deprecated QMF fields as Deprecated in management-schema.xml

[jira] [Resolved] (QPID-5929) [C++ broker] Mark deprecated QMF fields as Deprecated in management-schema.xml

[ https://issues.apache.org/jira/browse/QPID-5929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec resolved QPID-5929. - Resolution: Fixed Fix Version/s: Future Committed as r1614301. [C++ broker] Mark

[jira] [Commented] (QPID-5933) Python client infinite recursion if connection dropped

[ https://issues.apache.org/jira/browse/QPID-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14077594#comment-14077594 ] Pavel Moravec commented on QPID-5933: - There was a regression caused by wrong fix of

[jira] [Created] (QPID-5938) qpid-stat: remove dead code relevant to active-active cluster

Pavel Moravec created QPID-5938: --- Summary: qpid-stat: remove dead code relevant to active-active cluster Key: QPID-5938 URL: https://issues.apache.org/jira/browse/QPID-5938 Project: Qpid

[jira] [Commented] (QPID-5929) [C++ broker] Mark deprecated QMF fields as Deprecated in management-schema.xml

[ https://issues.apache.org/jira/browse/QPID-5929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076140#comment-14076140 ] Pavel Moravec commented on QPID-5929: - Review request:

[jira] [Created] (QPID-5931) [Java client] JMSException instead of InvalidDestinationException raised when sending to temporary destination after session closure

Pavel Moravec created QPID-5931: --- Summary: [Java client] JMSException instead of InvalidDestinationException raised when sending to temporary destination after session closure Key: QPID-5931 URL:

[jira] [Resolved] (QPID-5931) [Java client] JMSException instead of InvalidDestinationException raised when sending to temporary destination after session closure

[ https://issues.apache.org/jira/browse/QPID-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec resolved QPID-5931. - Resolution: Fixed Fix Version/s: 0.29 [Java client] JMSException instead of

[jira] [Closed] (QPID-5931) [Java client] JMSException instead of InvalidDestinationException raised when sending to temporary destination after session closure

[ https://issues.apache.org/jira/browse/QPID-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec closed QPID-5931. --- [Java client] JMSException instead of InvalidDestinationException raised when sending to temporary

[jira] [Created] (QPID-5929) [C++ broker] Mark deprecated QMF fields as Deprecated in management-schema.xml

Pavel Moravec created QPID-5929: --- Summary: [C++ broker] Mark deprecated QMF fields as Deprecated in management-schema.xml Key: QPID-5929 URL: https://issues.apache.org/jira/browse/QPID-5929 Project:

[jira] [Commented] (QPID-5642) Message sequence numbers (enabled with qpid.msg_sequence) should be persistent across broker restarts

[ https://issues.apache.org/jira/browse/QPID-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074137#comment-14074137 ] Pavel Moravec commented on QPID-5642: - Review https://reviews.apache.org/r/19566/

[jira] [Resolved] (QPID-5852) [Python client] connection.opened() returns True after unsuccessful connection

[ https://issues.apache.org/jira/browse/QPID-5852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec resolved QPID-5852. - Resolution: Fixed Fix Version/s: (was: 0.29) Future Fixed the

[jira] [Created] (QPID-5895) [C++ client] Allow consumer flow control based on #bytes

Pavel Moravec created QPID-5895: --- Summary: [C++ client] Allow consumer flow control based on #bytes Key: QPID-5895 URL: https://issues.apache.org/jira/browse/QPID-5895 Project: Qpid Issue

[jira] [Updated] (QPID-5895) [C++ client] Allow consumer flow control based on #bytes

[ https://issues.apache.org/jira/browse/QPID-5895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec updated QPID-5895: Issue Type: New Feature (was: Improvement) [C++ client] Allow consumer flow control based on

[jira] [Created] (QPID-5896) [C++ client] Out of Bounds received when message is bigger than remaining TCP frame size

Pavel Moravec created QPID-5896: --- Summary: [C++ client] Out of Bounds received when message is bigger than remaining TCP frame size Key: QPID-5896 URL: https://issues.apache.org/jira/browse/QPID-5896

[jira] [Closed] (QPID-4524) Java client timeouts after sending huge message to existing durable queue

[ https://issues.apache.org/jira/browse/QPID-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec closed QPID-4524. --- Resolution: Not a Problem It is expected behaviour. Client timeouts after (default) 60 seconds. It is

[jira] [Commented] (QPID-5872) [C++ client] Memory leak in qpid::messaging::amqp::ConnectionContext::ConnectionContext when using qpid-receive

[ https://issues.apache.org/jira/browse/QPID-5872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14054922#comment-14054922 ] Pavel Moravec commented on QPID-5872: - Some other leaks when closing session with open

[jira] [Closed] (QPID-5823) Python client should create a node with name starting '#'

[ https://issues.apache.org/jira/browse/QPID-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec closed QPID-5823. --- Python client should create a node with name starting '#'

[jira] [Resolved] (QPID-5823) Python client should create a node with name starting '#'

[ https://issues.apache.org/jira/browse/QPID-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec resolved QPID-5823. - Resolution: Fixed Committed revision 1608350. Python client should create a node with name

[jira] [Created] (QPID-5880) [C++ broker] Make memory usage consistent after broker restart

Pavel Moravec created QPID-5880: --- Summary: [C++ broker] Make memory usage consistent after broker restart Key: QPID-5880 URL: https://issues.apache.org/jira/browse/QPID-5880 Project: Qpid

[jira] [Updated] (QPID-5880) [C++ broker] Make memory usage consistent after broker restart

[ https://issues.apache.org/jira/browse/QPID-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec updated QPID-5880: Attachment: QPID-5880.patch Simple idea: - in Queue::enqueue, set PersistableMessage::persistencyID

[jira] [Commented] (QPID-5880) [C++ broker] Make memory usage consistent after broker restart

[ https://issues.apache.org/jira/browse/QPID-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14053707#comment-14053707 ] Pavel Moravec commented on QPID-5880: - Just FYI, another attempt in adding a message

[jira] [Resolved] (QPID-5866) [C++ client] AMQP 1.0 closing session without closing receiver first marks further messages as redelivered

[ https://issues.apache.org/jira/browse/QPID-5866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec resolved QPID-5866. - Resolution: Fixed Fix Version/s: Future Committed revision 1607562. [C++ client] AMQP

[jira] [Closed] (QPID-5866) [C++ client] AMQP 1.0 closing session without closing receiver first marks further messages as redelivered

[ https://issues.apache.org/jira/browse/QPID-5866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec closed QPID-5866. --- [C++ client] AMQP 1.0 closing session without closing receiver first marks further messages as

[jira] [Created] (QPID-5872) [C++ client] Memory leak in qpid::messaging::amqp::ConnectionContext::ConnectionContext when using qpid-receive

Pavel Moravec created QPID-5872: --- Summary: [C++ client] Memory leak in qpid::messaging::amqp::ConnectionContext::ConnectionContext when using qpid-receive Key: QPID-5872 URL:

[jira] [Updated] (QPID-5872) [C++ client] Memory leak in qpid::messaging::amqp::ConnectionContext::ConnectionContext when using qpid-receive

[ https://issues.apache.org/jira/browse/QPID-5872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec updated QPID-5872: Description: valgrind shows a memory leak like below: {noformat} qpid-send --messages 3000

[jira] [Updated] (QPID-5872) [C++ client] Memory leak in qpid::messaging::amqp::ConnectionContext::ConnectionContext when using qpid-receive

[ https://issues.apache.org/jira/browse/QPID-5872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec updated QPID-5872: Description: valgrind shows a memory leak like below: ~~~ qpid-send --messages 3000 --address

[jira] [Created] (QPID-5866) [C++ client] AMQP 1.0 closing session without closing receiver first marks further messages as redelivered

Pavel Moravec created QPID-5866: --- Summary: [C++ client] AMQP 1.0 closing session without closing receiver first marks further messages as redelivered Key: QPID-5866 URL:

[jira] [Created] (QPID-5863) qpid-config does not throws correct exception when binding nonexisting exchange

Pavel Moravec created QPID-5863: --- Summary: qpid-config does not throws correct exception when binding nonexisting exchange Key: QPID-5863 URL: https://issues.apache.org/jira/browse/QPID-5863 Project:

[jira] [Resolved] (QPID-5863) qpid-config does not throws correct exception when binding nonexisting exchange

[ https://issues.apache.org/jira/browse/QPID-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec resolved QPID-5863. - Resolution: Fixed Author of the fix: Zdenek Kraus (zkr...@redhat.com). qpid-config does not

[jira] [Closed] (QPID-5863) qpid-config does not throws correct exception when binding nonexisting exchange

[ https://issues.apache.org/jira/browse/QPID-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec closed QPID-5863. --- qpid-config does not throws correct exception when binding nonexisting exchange

[jira] [Created] (QPID-5864) [Python client] Provide better error description when SASL required but no credentials provided

Pavel Moravec created QPID-5864: --- Summary: [Python client] Provide better error description when SASL required but no credentials provided Key: QPID-5864 URL: https://issues.apache.org/jira/browse/QPID-5864

[jira] [Resolved] (QPID-5864) [Python client] Provide better error description when SASL required but no credentials provided

[ https://issues.apache.org/jira/browse/QPID-5864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec resolved QPID-5864. - Resolution: Fixed [Python client] Provide better error description when SASL required but no

[jira] [Closed] (QPID-5864) [Python client] Provide better error description when SASL required but no credentials provided

[ https://issues.apache.org/jira/browse/QPID-5864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec closed QPID-5864. --- [Python client] Provide better error description when SASL required but no credentials provided

[jira] [Resolved] (QPID-5836) [Python client] Report error when encountering unrecognized connection option

[ https://issues.apache.org/jira/browse/QPID-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec resolved QPID-5836. - Resolution: Fixed Fix Version/s: 0.29 To let automated tests passed, previous commit

[jira] [Closed] (QPID-5836) [Python client] Report error when encountering unrecognized connection option

[ https://issues.apache.org/jira/browse/QPID-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec closed QPID-5836. --- [Python client] Report error when encountering unrecognized connection option

[jira] [Created] (QPID-5852) [Python client] connection.opened() returns True after unsuccessful connection

Pavel Moravec created QPID-5852: --- Summary: [Python client] connection.opened() returns True after unsuccessful connection Key: QPID-5852 URL: https://issues.apache.org/jira/browse/QPID-5852 Project:

[jira] [Closed] (QPID-5852) [Python client] connection.opened() returns True after unsuccessful connection

[ https://issues.apache.org/jira/browse/QPID-5852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec closed QPID-5852. --- [Python client] connection.opened() returns True after unsuccessful connection

[jira] [Resolved] (QPID-5852) [Python client] connection.opened() returns True after unsuccessful connection

[ https://issues.apache.org/jira/browse/QPID-5852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec resolved QPID-5852. - Resolution: Fixed Fix Version/s: 0.29 The patch comes from me with a help of Ernie.

[jira] [Created] (QPID-5839) [C++ broker] Broker does not set lifetime-policy in AMQP1.0 attach performative

Pavel Moravec created QPID-5839: --- Summary: [C++ broker] Broker does not set lifetime-policy in AMQP1.0 attach performative Key: QPID-5839 URL: https://issues.apache.org/jira/browse/QPID-5839 Project:

[jira] [Closed] (QPID-5839) [C++ broker] Broker does not set lifetime-policy in AMQP1.0 attach performative

[ https://issues.apache.org/jira/browse/QPID-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec closed QPID-5839. --- [C++ broker] Broker does not set lifetime-policy in AMQP1.0 attach performative

[jira] [Resolved] (QPID-5839) [C++ broker] Broker does not set lifetime-policy in AMQP1.0 attach performative

[ https://issues.apache.org/jira/browse/QPID-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec resolved QPID-5839. - Resolution: Fixed [C++ broker] Broker does not set lifetime-policy in AMQP1.0 attach

[jira] [Created] (QPID-5836) [Python client] Report error when encountering unrecognized connection option

Pavel Moravec created QPID-5836: --- Summary: [Python client] Report error when encountering unrecognized connection option Key: QPID-5836 URL: https://issues.apache.org/jira/browse/QPID-5836 Project:

[jira] [Closed] (QPID-5835) [C++ broker] Broker recovery forgets auto-delete flag on queues and exchanges

[ https://issues.apache.org/jira/browse/QPID-5835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec closed QPID-5835. --- [C++ broker] Broker recovery forgets auto-delete flag on queues and exchanges

[jira] [Resolved] (QPID-5835) [C++ broker] Broker recovery forgets auto-delete flag on queues and exchanges

[ https://issues.apache.org/jira/browse/QPID-5835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec resolved QPID-5835. - Resolution: Fixed Fix Version/s: 0.29 Committed revision 1604455. [C++ broker] Broker

[jira] [Created] (QPID-5835) [C++ broker] Broker recovery forgets auto-delete flag on queues and exchanges

Pavel Moravec created QPID-5835: --- Summary: [C++ broker] Broker recovery forgets auto-delete flag on queues and exchanges Key: QPID-5835 URL: https://issues.apache.org/jira/browse/QPID-5835 Project:

[jira] [Resolved] (QPID-5817) [C++ broker] Improve ACL authorisation of QMF methods and queries

[ https://issues.apache.org/jira/browse/QPID-5817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec resolved QPID-5817. - Resolution: Fixed Fix Version/s: 0.29 Committed as r1603364. [C++ broker] Improve ACL

[jira] [Closed] (QPID-5817) [C++ broker] Improve ACL authorisation of QMF methods and queries

[ https://issues.apache.org/jira/browse/QPID-5817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec closed QPID-5817. --- [C++ broker] Improve ACL authorisation of QMF methods and queries

[jira] [Created] (QPID-5830) [Python client] Unable to create bindings on already existing broker objects using addressing

Pavel Moravec created QPID-5830: --- Summary: [Python client] Unable to create bindings on already existing broker objects using addressing Key: QPID-5830 URL: https://issues.apache.org/jira/browse/QPID-5830

[jira] [Closed] (QPID-5830) [Python client] Unable to create bindings on already existing broker objects using addressing

[ https://issues.apache.org/jira/browse/QPID-5830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec closed QPID-5830. --- [Python client] Unable to create bindings on already existing broker objects using addressing

[jira] [Resolved] (QPID-5830) [Python client] Unable to create bindings on already existing broker objects using addressing

[ https://issues.apache.org/jira/browse/QPID-5830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec resolved QPID-5830. - Resolution: Fixed Fix Version/s: 0.29 Committed as r1603448. [Python client] Unable to

[jira] [Created] (QPID-5823) Python client should create a node with name starting '#'

Pavel Moravec created QPID-5823: --- Summary: Python client should create a node with name starting '#' Key: QPID-5823 URL: https://issues.apache.org/jira/browse/QPID-5823 Project: Qpid Issue

[jira] [Closed] (QPID-5823) Python client should create a node with name starting '#'

[ https://issues.apache.org/jira/browse/QPID-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec closed QPID-5823. --- Resolution: Fixed Fix Version/s: 0.29 Python client should create a node with name starting

[jira] [Reopened] (QPID-5823) Python client should create a node with name starting '#'

[ https://issues.apache.org/jira/browse/QPID-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec reopened QPID-5823: - Reopened as after original patch, any application lost the ability to retrieve the name of the

[jira] [Created] (QPID-5827) [C++ broker] sporadic tests failures of qpid_tests.broker_0_10.management.ManagementTest.test_connection_stats

Pavel Moravec created QPID-5827: --- Summary: [C++ broker] sporadic tests failures of qpid_tests.broker_0_10.management.ManagementTest.test_connection_stats Key: QPID-5827 URL:

[jira] [Resolved] (QPID-3389) Provide more descriptive error text when sasl config. file is malformed

[ https://issues.apache.org/jira/browse/QPID-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec resolved QPID-3389. - Resolution: Fixed Fix Version/s: (was: Future) 0.29

[jira] [Created] (QPID-5817) [C++ broker] Improve ACL authorisation of QMF methods and queries

Pavel Moravec created QPID-5817: --- Summary: [C++ broker] Improve ACL authorisation of QMF methods and queries Key: QPID-5817 URL: https://issues.apache.org/jira/browse/QPID-5817 Project: Qpid

[jira] [Created] (QPID-5812) python high level API client receiver.fetch(timeout=N) blocks forever in select() if broker is stopped (kill -STOP)

Pavel Moravec created QPID-5812: --- Summary: python high level API client receiver.fetch(timeout=N) blocks forever in select() if broker is stopped (kill -STOP) Key: QPID-5812 URL:

[jira] [Commented] (QPID-5812) python high level API client receiver.fetch(timeout=N) blocks forever in select() if broker is stopped (kill -STOP)

[ https://issues.apache.org/jira/browse/QPID-5812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14029327#comment-14029327 ] Pavel Moravec commented on QPID-5812: - Traceback: File string, line 6, in fetch

[jira] [Closed] (QPID-5812) python high level API client receiver.fetch(timeout=N) blocks forever in select() if broker is stopped (kill -STOP)

[ https://issues.apache.org/jira/browse/QPID-5812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec closed QPID-5812. --- Resolution: Fixed python high level API client receiver.fetch(timeout=N) blocks forever in

[jira] [Closed] (QPID-5797) [qpid-tools]: inability to call some QMF methods (queueMoveMessages / setLogLevel or so)

[ https://issues.apache.org/jira/browse/QPID-5797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec closed QPID-5797. --- [qpid-tools]: inability to call some QMF methods (queueMoveMessages / setLogLevel or so)

[jira] [Resolved] (QPID-5797) [qpid-tools]: inability to call some QMF methods (queueMoveMessages / setLogLevel or so)

[ https://issues.apache.org/jira/browse/QPID-5797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec resolved QPID-5797. - Resolution: Fixed Fix Version/s: 0.29 Automated tests passed. [qpid-tools]: inability to

[jira] [Created] (QPID-5797) [qpid-tools]: inability to call some QMF methods (queueMoveMessages / setLogLevel or so)

Pavel Moravec created QPID-5797: --- Summary: [qpid-tools]: inability to call some QMF methods (queueMoveMessages / setLogLevel or so) Key: QPID-5797 URL: https://issues.apache.org/jira/browse/QPID-5797

[jira] [Created] (QPID-5793) [C++ broker] Memory leak _and_ deadlock due to qpid.auto_delete_timeout queues

Pavel Moravec created QPID-5793: --- Summary: [C++ broker] Memory leak _and_ deadlock due to qpid.auto_delete_timeout queues Key: QPID-5793 URL: https://issues.apache.org/jira/browse/QPID-5793 Project:

[jira] [Updated] (QPID-5278) Queue flow limit validation ignores size parameters

[ https://issues.apache.org/jira/browse/QPID-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec updated QPID-5278: Affects Version/s: 0.26 Queue flow limit validation ignores size parameters

[jira] [Updated] (QPID-5278) Queue flow limit validation ignores size parameters

[ https://issues.apache.org/jira/browse/QPID-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec updated QPID-5278: Affects Version/s: (was: 0.26) Queue flow limit validation ignores size parameters

[jira] [Assigned] (QPID-5748) [C++ broker] Make Queue::purgeExpired more efficient by calling AbsTime::now() just once

[ https://issues.apache.org/jira/browse/QPID-5748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec reassigned QPID-5748: --- Assignee: Pavel Moravec [C++ broker] Make Queue::purgeExpired more efficient by calling

[jira] [Resolved] (QPID-5748) [C++ broker] Make Queue::purgeExpired more efficient by calling AbsTime::now() just once

[ https://issues.apache.org/jira/browse/QPID-5748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec resolved QPID-5748. - Resolution: Fixed Fix Version/s: 0.29 Fixed together with removal of ExpiryPolicy that

[jira] [Closed] (QPID-5748) [C++ broker] Make Queue::purgeExpired more efficient by calling AbsTime::now() just once

[ https://issues.apache.org/jira/browse/QPID-5748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec closed QPID-5748. --- [C++ broker] Make Queue::purgeExpired more efficient by calling AbsTime::now() just once

[jira] [Closed] (QPID-5778) CRAM-MD5 mechanism does not work in python-client

[ https://issues.apache.org/jira/browse/QPID-5778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec closed QPID-5778. --- Resolution: Not a Problem Fix Version/s: Future It is a problem of saslwrapper that needs to

[jira] [Resolved] (QPID-5767) [C++ broker][linearstore] broker segfaults when recovering journal file with damaged header

[ https://issues.apache.org/jira/browse/QPID-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec resolved QPID-5767. - Resolution: Fixed Fix Version/s: 0.29 [C++ broker][linearstore] broker segfaults when

[jira] [Closed] (QPID-5767) [C++ broker][linearstore] broker segfaults when recovering journal file with damaged header

[ https://issues.apache.org/jira/browse/QPID-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec closed QPID-5767. --- [C++ broker][linearstore] broker segfaults when recovering journal file with damaged header

[jira] [Commented] (QPID-5767) [C++ broker][linearstore] broker segfaults when recovering journal file with damaged header

[ https://issues.apache.org/jira/browse/QPID-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14004486#comment-14004486 ] Pavel Moravec commented on QPID-5767: - Just to clarify contribution: the patch was

[jira] [Created] (QPID-5778) CRAM-MD5 mechanism does not work in python-client

Pavel Moravec created QPID-5778: --- Summary: CRAM-MD5 mechanism does not work in python-client Key: QPID-5778 URL: https://issues.apache.org/jira/browse/QPID-5778 Project: Qpid Issue Type: Bug

[jira] [Commented] (QPID-5767) [C++ broker][linearstore] broker segfaults when recovering journal file with damaged header

[ https://issues.apache.org/jira/browse/QPID-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998809#comment-13998809 ] Pavel Moravec commented on QPID-5767: - Relevant review request:

[jira] [Created] (QPID-5767) [C++ broker][linearstore] broker segfaults when recovering journal file with damaged header

Pavel Moravec created QPID-5767: --- Summary: [C++ broker][linearstore] broker segfaults when recovering journal file with damaged header Key: QPID-5767 URL: https://issues.apache.org/jira/browse/QPID-5767

[jira] [Created] (QPID-5747) Federated link ends up in Connecting state forever after connecting to shutting down broker

Pavel Moravec created QPID-5747: --- Summary: Federated link ends up in Connecting state forever after connecting to shutting down broker Key: QPID-5747 URL: https://issues.apache.org/jira/browse/QPID-5747

[jira] [Commented] (QPID-5747) Federated link ends up in Connecting state forever after connecting to shutting down broker

[ https://issues.apache.org/jira/browse/QPID-5747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13990642#comment-13990642 ] Pavel Moravec commented on QPID-5747: - Possible workaround in deleting the link does

[jira] [Created] (QPID-5701) [AMQP 1.0] C++ client should notify broker about session.sync() invoked by application

Pavel Moravec created QPID-5701: --- Summary: [AMQP 1.0] C++ client should notify broker about session.sync() invoked by application Key: QPID-5701 URL: https://issues.apache.org/jira/browse/QPID-5701

[jira] [Updated] (QPID-5651) [C++ broker] segfault in qpid::linearstore::journal::jdir::clear_dir when declaring durable queue

[ https://issues.apache.org/jira/browse/QPID-5651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec updated QPID-5651: Description: Affected version: 0.28 / current upstream (svn revision 1582719). Creating a durable

[jira] [Closed] (QPID-5651) [C++ broker] segfault in qpid::linearstore::journal::jdir::clear_dir when declaring durable queue

[ https://issues.apache.org/jira/browse/QPID-5651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec closed QPID-5651. --- Resolution: Fixed Fix Version/s: 0.29 Assignee: Pavel Moravec Fixed a flaw introduced

[jira] [Commented] (QPID-4922) If Consumer close() method is invoked while inside onMessage(), it should be excuted after onMessage() has completed.

[ https://issues.apache.org/jira/browse/QPID-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13949081#comment-13949081 ] Pavel Moravec commented on QPID-4922: - I tried to apply the patch to upstream client

[jira] [Commented] (DISPATCH-1) Use Target Address from the link if there is no To field in a message from a producer

[ https://issues.apache.org/jira/browse/DISPATCH-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13949143#comment-13949143 ] Pavel Moravec commented on DISPATCH-1: -- Reopening the issue. Dispatch does not ever

[jira] [Commented] (DISPATCH-1) Use Target Address from the link if there is no To field in a message from a producer

[ https://issues.apache.org/jira/browse/DISPATCH-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13949144#comment-13949144 ] Pavel Moravec commented on DISPATCH-1: -- FYI it seems I dont have permissions to

[jira] [Created] (DISPATCH-37) Various memory leaks

Pavel Moravec created DISPATCH-37: - Summary: Various memory leaks Key: DISPATCH-37 URL: https://issues.apache.org/jira/browse/DISPATCH-37 Project: Qpid Dispatch Issue Type: Bug

<    1   2   3   4   5   >