[jira] [Updated] (QPID-7187) Memory leak when calling qpid::messaging::Connection::open()

[ https://issues.apache.org/jira/browse/QPID-7187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Yeoh updated QPID-7187: Summary: Memory leak when calling qpid::messaging::Connection::open() (was: Memory leak when calling in qpid

[jira] [Created] (QPID-7187) Memory leak when calling in qpid::messaging::Connection::open()

Jeff Yeoh created QPID-7187: --- Summary: Memory leak when calling in qpid::messaging::Connection::open() Key: QPID-7187 URL: https://issues.apache.org/jira/browse/QPID-7187 Project: Qpid Issue Type:

[jira] [Commented] (QPID-2410) perftest hang in SSL on Windows with large buffers

[ https://issues.apache.org/jira/browse/QPID-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229168#comment-15229168 ] Tobias Nöll commented on QPID-2410: --- Actually it does not make a difference. If I e.g. se

[jira] [Commented] (DISPATCH-257) Policy miscounts sender/receiver links; no link count tests

[ https://issues.apache.org/jira/browse/DISPATCH-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229163#comment-15229163 ] ASF subversion and git services commented on DISPATCH-257: -- Com

[jira] [Commented] (DISPATCH-264) printf formats for 64-bit quantities need to be 64/32-bit safe

[ https://issues.apache.org/jira/browse/DISPATCH-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229006#comment-15229006 ] ASF subversion and git services commented on DISPATCH-264: -- Com

[jira] [Created] (DISPATCH-264) printf formats for 64-bit quantities need to be 64/32-bit safe

Ted Ross created DISPATCH-264: - Summary: printf formats for 64-bit quantities need to be 64/32-bit safe Key: DISPATCH-264 URL: https://issues.apache.org/jira/browse/DISPATCH-264 Project: Qpid Dispatch

[jira] [Created] (DISPATCH-263) Router crash when requesting log

Ernest Allen created DISPATCH-263: - Summary: Router crash when requesting log Key: DISPATCH-263 URL: https://issues.apache.org/jira/browse/DISPATCH-263 Project: Qpid Dispatch Issue Type: Bug

[jira] [Comment Edited] (DISPATCH-262) oslo.messaging RPC fanout crashes qdrouterd

[ https://issues.apache.org/jira/browse/DISPATCH-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228795#comment-15228795 ] Ken Giusti edited comment on DISPATCH-262 at 4/6/16 6:16 PM: -

[jira] [Resolved] (QPID-7182) [C++ broker] high CPU usage on backup brokers following QPID-7149 scenario

[ https://issues.apache.org/jira/browse/QPID-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Moravec resolved QPID-7182. - Resolution: Fixed Fix Version/s: qpid-cpp-next > [C++ broker] high CPU usage on backup broke

[jira] [Commented] (QPID-7182) [C++ broker] high CPU usage on backup brokers following QPID-7149 scenario

[ https://issues.apache.org/jira/browse/QPID-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228796#comment-15228796 ] Pavel Moravec commented on QPID-7182: - I agree the CPU increase over time is gone on cu

[jira] [Commented] (DISPATCH-262) oslo.messaging RPC fanout crashes qdrouterd

[ https://issues.apache.org/jira/browse/DISPATCH-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228795#comment-15228795 ] Ken Giusti commented on DISPATCH-262: - To reproduce: Be sure to build with asserts

[jira] [Created] (DISPATCH-262) oslo.messaging RPC fanout crashes qdrouterd

Ken Giusti created DISPATCH-262: --- Summary: oslo.messaging RPC fanout crashes qdrouterd Key: DISPATCH-262 URL: https://issues.apache.org/jira/browse/DISPATCH-262 Project: Qpid Dispatch Issue Typ

[jira] [Commented] (QPIDJMS-166) Revisit some of the TODOs in the code around error messages and exception types.

[ https://issues.apache.org/jira/browse/QPIDJMS-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228775#comment-15228775 ] ASF subversion and git services commented on QPIDJMS-166: - Commit

[jira] [Commented] (QPID-2410) perftest hang in SSL on Windows with large buffers

[ https://issues.apache.org/jira/browse/QPID-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228708#comment-15228708 ] Maxim Rydkin commented on QPID-2410: max-frame-size:16384 or max-frame-size:16383 ? Al

[jira] [Commented] (QPID-2410) perftest hang in SSL on Windows with large buffers

[ https://issues.apache.org/jira/browse/QPID-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228615#comment-15228615 ] Tobias Nöll commented on QPID-2410: --- Meanwhile I got it working: Solution was: 1.) No n

[jira] [Updated] (QPID-7097) [Java Broker, HA] Broker configuration thread is used to perform notifications about removal of BDB HA VirtualHost when VH is closed in response to environment state trans

[ https://issues.apache.org/jira/browse/QPID-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-7097: - Affects Version/s: (was: 0.32) > [Java Broker, HA] Broker configuration thread is used to perform > no

[jira] [Resolved] (QPIDJMS-170) Simplify the dispatching logic in the connection

[ https://issues.apache.org/jira/browse/QPIDJMS-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved QPIDJMS-170. -- Resolution: Fixed > Simplify the dispatching logic in the connection >

[jira] [Commented] (QPIDJMS-170) Simplify the dispatching logic in the connection

[ https://issues.apache.org/jira/browse/QPIDJMS-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228443#comment-15228443 ] ASF subversion and git services commented on QPIDJMS-170: - Commit

[jira] [Commented] (DISPATCH-245) Various Bugs found by Coverity

[ https://issues.apache.org/jira/browse/DISPATCH-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228419#comment-15228419 ] ASF subversion and git services commented on DISPATCH-245: -- Com

[jira] [Created] (QPIDJMS-170) Simplify the dispatching logic in the connection

Timothy Bish created QPIDJMS-170: Summary: Simplify the dispatching logic in the connection Key: QPIDJMS-170 URL: https://issues.apache.org/jira/browse/QPIDJMS-170 Project: Qpid JMS Issue Typ

[jira] [Commented] (QPID-7186) CancelledKeyException from the accepting thread during Broker shutdown

[ https://issues.apache.org/jira/browse/QPID-7186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228407#comment-15228407 ] ASF subversion and git services commented on QPID-7186: --- Commit 17379

[jira] [Updated] (QPID-7097) [Java Broker, HA] Broker configuration thread is used to perform notifications about removal of BDB HA VirtualHost when VH is closed in response to environment state trans

[ https://issues.apache.org/jira/browse/QPID-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7097: - Fix Version/s: qpid-java-6.0.2 > [Java Broker, HA] Broker configuration thread is used to perform > notifi

[jira] [Resolved] (QPID-7097) [Java Broker, HA] Broker configuration thread is used to perform notifications about removal of BDB HA VirtualHost when VH is closed in response to environment state tran

[ https://issues.apache.org/jira/browse/QPID-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-7097. -- Resolution: Fixed Changes seems reasonable. > [Java Broker, HA] Broker configuration thread is used to p

[jira] [Commented] (QPID-7023) BDB HA: JE Cleaner warnings written to qpid log during apparently normal operation

[ https://issues.apache.org/jira/browse/QPID-7023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228386#comment-15228386 ] Keith Wall commented on QPID-7023: -- Change looks reasonable for now. The façade specific

[jira] [Resolved] (QPID-7023) BDB HA: JE Cleaner warnings written to qpid log during apparently normal operation

[ https://issues.apache.org/jira/browse/QPID-7023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-7023. -- Resolution: Fixed > BDB HA: JE Cleaner warnings written to qpid log during apparently normal > operation

[jira] [Commented] (QPID-7023) BDB HA: JE Cleaner warnings written to qpid log during apparently normal operation

[ https://issues.apache.org/jira/browse/QPID-7023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228366#comment-15228366 ] ASF subversion and git services commented on QPID-7023: --- Commit 17379

Fwd: New Defects reported by Coverity Scan for Apache Qpid dispatch-router

All, Ran coverity against our 0.6.0 Beta 1. Follow the link https://scan.coverity.com/projects/apache-qpid-dispatch-router?tab=overview And hit the View Defects button to open the code browser. If you'd like to fix a defect, please assign it to yourself first so we don't duplicate effort. Yo

[jira] [Commented] (QPID-7154) Dead lettering of a message may timeout at store level, causing unexpected Broker shutdown

[ https://issues.apache.org/jira/browse/QPID-7154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228316#comment-15228316 ] ASF subversion and git services commented on QPID-7154: --- Commit 17379

[jira] [Updated] (QPID-7186) CancelledKeyException from the accepting thread during Broker shutdown

[ https://issues.apache.org/jira/browse/QPID-7186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7186: - Description: The following failure occurred during an Apache CI run: https://builds.apache.org/view/M-R/vi

[jira] [Created] (QPID-7186) CancelledKeyException from the accepting thread during Broker shutdown

Keith Wall created QPID-7186: Summary: CancelledKeyException from the accepting thread during Broker shutdown Key: QPID-7186 URL: https://issues.apache.org/jira/browse/QPID-7186 Project: Qpid Is

[jira] [Commented] (QPID-7182) [C++ broker] high CPU usage on backup brokers following QPID-7149 scenario

[ https://issues.apache.org/jira/browse/QPID-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228244#comment-15228244 ] Alan Conway commented on QPID-7182: --- I can't reproduce on present trunk: eb1e785 origin/t

[jira] [Updated] (QPID-7154) Dead lettering of a message may timeout at store level, causing unexpected Broker shutdown

[ https://issues.apache.org/jira/browse/QPID-7154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-7154: - Attachment: (was: 0001-QPID-7154-Java-Broker-Ensure-that-acquisition-is-loc.patch) > Dead lettering of

[jira] [Updated] (QPID-7154) Dead lettering of a message may timeout at store level, causing unexpected Broker shutdown

[ https://issues.apache.org/jira/browse/QPID-7154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-7154: - Attachment: 0001-QPID-7154-Java-Broker-Ensure-that-acquisition-is-loc.patch > Dead lettering of a message m

[jira] [Updated] (QPID-7154) Dead lettering of a message may timeout at store level, causing unexpected Broker shutdown

[ https://issues.apache.org/jira/browse/QPID-7154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-7154: - Attachment: 0001-QPID-7154-Java-Broker-Ensure-that-acquisition-is-loc.patch > Dead lettering of a message m

[jira] [Assigned] (DISPATCH-261) Bind error on one port causes bind error on other ports

[ https://issues.apache.org/jira/browse/DISPATCH-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned DISPATCH-261: - Assignee: Ted Ross > Bind error on one port causes bind error on other ports >

[jira] [Commented] (DISPATCH-261) Bind error on one port causes bind error on other ports

[ https://issues.apache.org/jira/browse/DISPATCH-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228130#comment-15228130 ] Ted Ross commented on DISPATCH-261: --- Furthermore, the socket on the second listener is

[jira] [Comment Edited] (QPIDJMS-169) SASL Plain Mechanism should be enforcing UTF-8 encoding

[ https://issues.apache.org/jira/browse/QPIDJMS-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15227915#comment-15227915 ] Keith Wall edited comment on QPIDJMS-169 at 4/6/16 8:03 AM: H

[jira] [Commented] (QPIDJMS-169) SASL Plain Mechanism should be enforcing UTF-8 encoding

[ https://issues.apache.org/jira/browse/QPIDJMS-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15227915#comment-15227915 ] Keith Wall commented on QPIDJMS-169: Hi Tim, I am not sure about this change. The