[jira] [Created] (QPID-3348) Qmf broker proxy method create() does not handle keyword arguments, only regular parameters

Qmf broker proxy method create() does not handle keyword arguments, only regular parameters --- Key: QPID-3348 URL: https://issues.apache.org/jira/browse/QPID-3348

[jira] [Assigned] (QPID-3348) Qmf broker proxy method create() does not handle keyword arguments, only regular parameters

[ https://issues.apache.org/jira/browse/QPID-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet reassigned QPID-3348: -- Assignee: Kim van der Riet > Qmf broker proxy method create() does not handle keyword ar

[jira] [Commented] (QPID-3348) Qmf broker proxy method create() does not handle keyword arguments, only regular parameters

[ https://issues.apache.org/jira/browse/QPID-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13061911#comment-13061911 ] Kim van der Riet commented on QPID-3348: The special "meta" keyword args "_timeout"

[jira] [Resolved] (QPID-3348) Qmf broker proxy method create() does not handle keyword arguments, only regular parameters

[ https://issues.apache.org/jira/browse/QPID-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPID-3348. Resolution: Fixed Fixed in r.1144302 > Qmf broker proxy method create() does not handle key

[jira] [Updated] (QPID-3350) Python federation tests (federation.FederationTests.*) leak connections

[ https://issues.apache.org/jira/browse/QPID-3350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPID-3350: --- Description: Several (but not all) the federation tests leak connection objects. This causes

[jira] [Created] (QPID-3350) Python federation tests (federation.FederationTests.*) leak connections

Python federation tests (federation.FederationTests.*) leak connections --- Key: QPID-3350 URL: https://issues.apache.org/jira/browse/QPID-3350 Project: Qpid Issue Type: Bug

[jira] [Updated] (QPID-3348) Qmf broker proxy method create() does not handle keyword arguments, only regular parameters

[ https://issues.apache.org/jira/browse/QPID-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPID-3348: --- Affects Version/s: 0.13 Fix Version/s: 0.14 > Qmf broker proxy method create() does no

[jira] [Updated] (QPID-3309) Management broker object port is not set if broker started with port number set to 0

[ https://issues.apache.org/jira/browse/QPID-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPID-3309: --- Affects Version/s: 0.13 Fix Version/s: 0.14 > Management broker object port is not set

[jira] [Commented] (QPID-3304) Tagged federation messages in a transaction can cause subsequent dequeue to fail

[ https://issues.apache.org/jira/browse/QPID-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067926#comment-13067926 ] Kim van der Riet commented on QPID-3304: Checked in Gordon's patch in r.1148503. Al

[jira] [Commented] (QPID-3304) Tagged federation messages in a transaction can cause subsequent dequeue to fail

[ https://issues.apache.org/jira/browse/QPID-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068300#comment-13068300 ] Kim van der Riet commented on QPID-3304: Further note on reproducing this error thr

[jira] [Resolved] (QPID-3304) Tagged federation messages in a transaction can cause subsequent dequeue to fail

[ https://issues.apache.org/jira/browse/QPID-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPID-3304. Resolution: Fixed Fix Version/s: (was: 0.11) 0.13 Assi

[jira] [Commented] (QPID-3419) qpid-config --file-size parameter's help text uses incorrect units

[ https://issues.apache.org/jira/browse/QPID-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090149#comment-13090149 ] Kim van der Riet commented on QPID-3419: Correct, the async store write page size i

[jira] [Commented] (QPID-3420) Make C++ broker's help text use consistent kibibyte abbreviations

[ https://issues.apache.org/jira/browse/QPID-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090981#comment-13090981 ] Kim van der Riet commented on QPID-3420: Thanks for the patch. Fixed on trunk r.447

[jira] Commented: (QPID-1891) fix declaration problems with boost 1_33_1

[ https://issues.apache.org/jira/browse/QPID-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716647#action_12716647 ] Kim van der Riet commented on QPID-1891: Patches applied (with minor updates) in r.7

[jira] Resolved: (QPID-1917) the java async profile is failing due to suspicous broker behavior when async store is loaded

[ https://issues.apache.org/jira/browse/QPID-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPID-1917. Resolution: Fixed Fix Version/s: 0.5 The C++ async store relies on the broker queue d

[jira] Created: (QPID-2017) Files for Async Store interface layer (NOTE, read carefully - license issues)

Files for Async Store interface layer (NOTE, read carefully - license issues) - Key: QPID-2017 URL: https://issues.apache.org/jira/browse/QPID-2017 Project: Qpid Iss

[jira] Updated: (QPID-2017) Files for Async Store interface layer (NOTE, read carefully - license issues)

[ https://issues.apache.org/jira/browse/QPID-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPID-2017: --- Attachment: MessageStoreImpl.cpp MessageStoreImpl.h StorePlugin

[jira] Updated: (QPID-2017) Files for Async Store interface layer (NOTE, read carefully - license issues)

[ https://issues.apache.org/jira/browse/QPID-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPID-2017: --- Attachment: BindingDbt.h TxnCtxt.cpp TxnCtxt.h See notes in th

[jira] Updated: (QPID-2017) Files for Async Store interface layer (NOTE, read carefully - license issues)

[ https://issues.apache.org/jira/browse/QPID-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPID-2017: --- Attachment: BufferValue.cpp BufferValue.h BindingDbt.cpp See n

[jira] Updated: (QPID-2017) Files for Async Store interface layer (NOTE, read carefully - license issues)

[ https://issues.apache.org/jira/browse/QPID-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPID-2017: --- Attachment: IdSequence.h IdDbt.cpp IdDbt.h > Files for Async S

[jira] Updated: (QPID-2017) Files for Async Store interface layer (NOTE, read carefully - license issues)

[ https://issues.apache.org/jira/browse/QPID-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPID-2017: --- Attachment: PreparedTransaction.cpp PreparedTransaction.h IdSeq

[jira] Updated: (QPID-2017) Files for Async Store interface layer (NOTE, read carefully - license issues)

[ https://issues.apache.org/jira/browse/QPID-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPID-2017: --- Attachment: JournalImpl.h StoreException.h > Files for Async Store interface l

[jira] Updated: (QPID-2076) C++ Broker assumes it can delete a pointer passed by message store plugin

[ https://issues.apache.org/jira/browse/QPID-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPID-2076: --- Attachment: steve_test_patch.txt I tested the patch, all seems to work ok. However, the tests

[jira] Created: (QPID-2171) No checks made for reserved exchange names "amq.*" and "qpid.*"

No checks made for reserved exchange names "amq.*" and "qpid.*" --- Key: QPID-2171 URL: https://issues.apache.org/jira/browse/QPID-2171 Project: Qpid Issue Type: Bug Compo

[jira] Closed: (QPID-2171) No checks made for reserved exchange names "amq.*" and "qpid.*"

[ https://issues.apache.org/jira/browse/QPID-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPID-2171. -- Resolution: Fixed Added the "amq." check in r.830930 and the "qpid." check in r.830930. Python

[jira] Commented: (QPID-2171) No checks made for reserved exchange names "amq.*" and "qpid.*"

[ https://issues.apache.org/jira/browse/QPID-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771413#action_12771413 ] Kim van der Riet commented on QPID-2171: Copy error above. First sentence should rea

[jira] Closed: (QPID-1727) C++ broker does support flow to disk for non durable queues

[ https://issues.apache.org/jira/browse/QPID-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPID-1727. -- Resolution: Fixed This was fixed over several checkins: r.817742 r.817748 r.818244 r.819505 r.81

[jira] Created: (QPID-2194) Universal store client test suite

Universal store client test suite - Key: QPID-2194 URL: https://issues.apache.org/jira/browse/QPID-2194 Project: Qpid Issue Type: Test Components: C++ Broker Reporter: Kim van der Riet

[jira] Commented: (QPID-2194) Universal store client test suite

[ https://issues.apache.org/jira/browse/QPID-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776965#action_12776965 ] Kim van der Riet commented on QPID-2194: I would like to propose that the Python tes

[jira] Created: (QPID-2278) Store recovery compatibility problem introduced by alternate-exchange fix

Store recovery compatibility problem introduced by alternate-exchange fix - Key: QPID-2278 URL: https://issues.apache.org/jira/browse/QPID-2278 Project: Qpid Issue Type:

[jira] Resolved: (QPID-2278) Store recovery compatibility problem introduced by alternate-exchange fix

[ https://issues.apache.org/jira/browse/QPID-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPID-2278. Resolution: Fixed Changing the order of the encoded items such that the alternate exchange i

[jira] Assigned: (QPID-2373) Durable exchange state not replicated to broker joining cluster

[ https://issues.apache.org/jira/browse/QPID-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet reassigned QPID-2373: -- Assignee: Kim van der Riet > Durable exchange state not replicated to broker joining clu

[jira] Created: (QPID-2373) Durable exchange state not replicated to broker joining cluster

Durable exchange state not replicated to broker joining cluster --- Key: QPID-2373 URL: https://issues.apache.org/jira/browse/QPID-2373 Project: Qpid Issue Type: Bug Compo

[jira] Resolved: (QPID-2373) Durable exchange state not replicated to broker joining cluster

[ https://issues.apache.org/jira/browse/QPID-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPID-2373. Resolution: Fixed Fixed in svn r.904154 > Durable exchange state not replicated to broker j

[jira] Commented: (QPID-2375) --load-module msgstore.so without --store-dir causes explosion

[ https://issues.apache.org/jira/browse/QPID-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806320#action_12806320 ] Kim van der Riet commented on QPID-2375: I have just tried this operation on trunk:

[jira] Created: (QPID-2384) Cluster recovers duplicate messages when using async store and --no-data-dir and --store-dir together

Cluster recovers duplicate messages when using async store and --no-data-dir and --store-dir together - Key: QPID-2384 URL: https://issues.apache.org/jira/browse/Q

[jira] Assigned: (QPID-2384) Cluster recovers duplicate messages when using async store and --no-data-dir and --store-dir together

[ https://issues.apache.org/jira/browse/QPID-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet reassigned QPID-2384: -- Assignee: Kim van der Riet > Cluster recovers duplicate messages when using async store

[jira] Resolved: (QPID-2384) Cluster recovers duplicate messages when using async store and --no-data-dir and --store-dir together

[ https://issues.apache.org/jira/browse/QPID-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPID-2384. Resolution: Fixed This is a logic flaw in the cluster store status. When --no-data-dir is s

[jira] Created: (QPID-2470) Broker does not honour flow-to-disk policy on recovery

Broker does not honour flow-to-disk policy on recovery -- Key: QPID-2470 URL: https://issues.apache.org/jira/browse/QPID-2470 Project: Qpid Issue Type: Bug Components: C++ Broker

[jira] Resolved: (QPID-2470) Broker does not honour flow-to-disk policy on recovery

[ https://issues.apache.org/jira/browse/QPID-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPID-2470. Resolution: Fixed Fixed in r.933711 and async store r.3905 (which adds new flow-to-disk test

[jira] Closed: (QPID-2456) Staged transient messages do not get deleted from store

[ https://issues.apache.org/jira/browse/QPID-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPID-2456. -- Resolution: Not A Problem The growth of BDB log files does not indicate that the messages are no

[jira] Created: (QPID-2509) Remove message staging from C++ broker

Remove message staging from C++ broker -- Key: QPID-2509 URL: https://issues.apache.org/jira/browse/QPID-2509 Project: Qpid Issue Type: Improvement Components: C++ Broker Reporter: Ki

[jira] Resolved: (QPID-2509) Remove message staging from C++ broker

[ https://issues.apache.org/jira/browse/QPID-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPID-2509. Resolution: Fixed The broker option for setting the staging threshold was removed, as was th

[jira] Commented: (QPID-2509) Remove message staging from C++ broker

[ https://issues.apache.org/jira/browse/QPID-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857369#action_12857369 ] Kim van der Riet commented on QPID-2509: Fixed in r.934463. > Remove message stagin

[jira] [Assigned] (QPID-3858) Develop asyncronous store interface for qpid

[ https://issues.apache.org/jira/browse/QPID-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet reassigned QPID-3858: -- Assignee: Kim van der Riet > Develop asyncronous store interface for qpid >

[jira] [Created] (QPID-4490) Durable messages with TTL do not expire after broker recovery (c++ store)

Kim van der Riet created QPID-4490: -- Summary: Durable messages with TTL do not expire after broker recovery (c++ store) Key: QPID-4490 URL: https://issues.apache.org/jira/browse/QPID-4490 Project: Qp

[jira] [Commented] (QPID-4490) Durable messages with TTL do not expire after broker recovery (c++ store)

[ https://issues.apache.org/jira/browse/QPID-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510503#comment-13510503 ] Kim van der Riet commented on QPID-4490: The fix for this bug requires changes to t

[jira] [Resolved] (QPID-4490) Durable messages with TTL do not expire after broker recovery (c++ store)

[ https://issues.apache.org/jira/browse/QPID-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPID-4490. Resolution: Fixed Fixed in r.1417511 (qpid) and r.4522 (store) > Durable me

[jira] [Commented] (QPID-4490) Durable messages with TTL do not expire after broker recovery (c++ store)

[ https://issues.apache.org/jira/browse/QPID-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510584#comment-13510584 ] Kim van der Riet commented on QPID-4490: New test: 1. Start broker: ./qpidd --load

[jira] Created: (QPID-2567) [c++] Timer - possible thread lock ordering violation

[c++] Timer - possible thread lock ordering violation - Key: QPID-2567 URL: https://issues.apache.org/jira/browse/QPID-2567 Project: Qpid Issue Type: Bug Components: C++ Broker

[jira] Commented: (QPID-2470) Broker does not honour flow-to-disk policy on recovery

[ https://issues.apache.org/jira/browse/QPID-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864290#action_12864290 ] Kim van der Riet commented on QPID-2470: Thank you for reporting this problem. Ther

[jira] Created: (QPID-2666) [C++ broker linux] Service init script does not handle config file with "log-to-file" and a relative path

[C++ broker linux] Service init script does not handle config file with "log-to-file" and a relative path - Key: QPID-2666 URL: https://issues.apache.org/jira/

[jira] Resolved: (QPID-2666) [C++ broker linux] Service init script does not handle config file with "log-to-file" and a relative path

[ https://issues.apache.org/jira/browse/QPID-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPID-2666. Resolution: Fixed Simple fix: add a '-' into the runuser statement that starts the "qpidd -

[jira] Commented: (QPID-2804) qpid-config timeout creating large journal

[ https://issues.apache.org/jira/browse/QPID-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916445#action_12916445 ] Kim van der Riet commented on QPID-2804: Use the --timeout option with a suitable va

[jira] [Created] (QPID-3191) C++ broker performance: scaling subs on single pub queue through direct exchange (mode 1-1-N) shows poor performance

C++ broker performance: scaling subs on single pub queue through direct exchange (mode 1-1-N) shows poor performance Key: QPID-3191 URL: https://i

[jira] [Commented] (QPID-3191) C++ broker performance: scaling subs on single pub queue through direct exchange (mode 1-1-N) shows poor performance

[ https://issues.apache.org/jira/browse/QPID-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017135#comment-13017135 ] Kim van der Riet commented on QPID-3191: Proposed patch at https://reviews.apache.o

[jira] [Updated] (QPID-3191) C++ broker performance: scaling subs on single pub queue through direct exchange (mode 1-1-N) shows poor performance

[ https://issues.apache.org/jira/browse/QPID-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPID-3191: --- Attachment: QueueListener vector vs deque comparison.pdf Performance graphs for original and p

[jira] [Commented] (QPID-3191) C++ broker performance: scaling subs on single pub queue through direct exchange (mode 1-1-N) shows poor performance

[ https://issues.apache.org/jira/browse/QPID-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017428#comment-13017428 ] Kim van der Riet commented on QPID-3191: Thanks for the comments on Review Board. I

[jira] [Resolved] (QPID-3191) C++ broker performance: scaling subs on single pub queue through direct exchange (mode 1-1-N) shows poor performance

[ https://issues.apache.org/jira/browse/QPID-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPID-3191. Resolution: Fixed Fixed with r.1090252. The QueueListeners std::vector was replaced with a

[jira] [Created] (QPID-3236) Add high-resolution timestamps to log files for debug situations

Add high-resolution timestamps to log files for debug situations Key: QPID-3236 URL: https://issues.apache.org/jira/browse/QPID-3236 Project: Qpid Issue Type: Task

[jira] [Commented] (QPID-3236) Add high-resolution timestamps to log files for debug situations

[ https://issues.apache.org/jira/browse/QPID-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026994#comment-13026994 ] Kim van der Riet commented on QPID-3236: The diff is located at https://reviews.apa

[jira] [Commented] (QPID-3236) Add high-resolution timestamps to log files for debug situations

[ https://issues.apache.org/jira/browse/QPID-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026996#comment-13026996 ] Kim van der Riet commented on QPID-3236: Adding options to autoconf and cmake is an

[jira] [Created] (QPID-3237) Python broker tests hang in environments where the available file handles > 1024

Python broker tests hang in environments where the available file handles > 1024 Key: QPID-3237 URL: https://issues.apache.org/jira/browse/QPID-3237 Project: Qpid

[jira] [Commented] (QPID-3236) Add high-resolution timestamps to log files for debug situations

[ https://issues.apache.org/jira/browse/QPID-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027644#comment-13027644 ] Kim van der Riet commented on QPID-3236: For completeness, the following comments w

[jira] [Assigned] (QPID-3236) Add high-resolution timestamps to log files for debug situations

[ https://issues.apache.org/jira/browse/QPID-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet reassigned QPID-3236: -- Assignee: Steve Huston (was: Kim van der Riet) Complete the Windows impl. of outputHire

[jira] [Commented] (QPID-3236) Add high-resolution timestamps to log files for debug situations

[ https://issues.apache.org/jira/browse/QPID-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027648#comment-13027648 ] Kim van der Riet commented on QPID-3236: Checked in as r.1098554. The Windows code

[jira] [Created] (QPID-3238) Refactor AMQContentBody::data from std::string to customizable typedef

Refactor AMQContentBody::data from std::string to customizable typedef -- Key: QPID-3238 URL: https://issues.apache.org/jira/browse/QPID-3238 Project: Qpid Issue Type: Task

[jira] [Created] (QPID-3287) [C++] Broker fails to set federation link flag on push links

[C++] Broker fails to set federation link flag on push links Key: QPID-3287 URL: https://issues.apache.org/jira/browse/QPID-3287 Project: Qpid Issue Type: Bug Components:

[jira] [Created] (QPID-3288) [C++] Broker sets federation link tag as empty string ("") when no tag is present in the client/server properties

[C++] Broker sets federation link tag as empty string ("") when no tag is present in the client/server properties - Key: QPID-3288 URL: https://issues.

[jira] [Resolved] (QPID-3287) [C++] Broker fails to set federation link flag on push links

[ https://issues.apache.org/jira/browse/QPID-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPID-3287. Resolution: Not A Problem This is in fact correct behaviour; the flag is never set in respon

[jira] [Commented] (QPID-3287) [C++] Broker fails to set federation link flag on push links

[ https://issues.apache.org/jira/browse/QPID-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042375#comment-13042375 ] Kim van der Riet commented on QPID-3287: The description above has the description

[jira] [Commented] (QPID-3288) [C++] Broker sets federation link tag as empty string ("") when no tag is present in the client/server properties

[ https://issues.apache.org/jira/browse/QPID-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043350#comment-13043350 ] Kim van der Riet commented on QPID-3288: Code review request is at https://reviews.

[jira] [Resolved] (QPID-3288) [C++] Broker sets federation link tag as empty string ("") when no tag is present in the client/server properties

[ https://issues.apache.org/jira/browse/QPID-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPID-3288. Resolution: Fixed Fixed in r.1132623 > [C++] Broker sets federation link tag as empty strin

[jira] [Created] (QPID-3309) Management broker object port is not set if broker started with port number set to 0

Management broker object port is not set if broker started with port number set to 0 Key: QPID-3309 URL: https://issues.apache.org/jira/browse/QPID-3309 Project: Qpi

[jira] [Assigned] (QPID-3309) Management broker object port is not set if broker started with port number set to 0

[ https://issues.apache.org/jira/browse/QPID-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet reassigned QPID-3309: -- Assignee: Kim van der Riet > Management broker object port is not set if broker started

[jira] [Commented] (QPID-3309) Management broker object port is not set if broker started with port number set to 0

[ https://issues.apache.org/jira/browse/QPID-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059927#comment-13059927 ] Kim van der Riet commented on QPID-3309: Fixed in rev 1143078. > Management broker

[jira] [Resolved] (QPID-3309) Management broker object port is not set if broker started with port number set to 0

[ https://issues.apache.org/jira/browse/QPID-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPID-3309. Resolution: Fixed > Management broker object port is not set if broker started with port num

[jira] [Resolved] (QPID-5480) [linearstore] Recovery of store failure with "JERR_MAP_NOTFOUND: Key not found in map." error message

[ https://issues.apache.org/jira/browse/QPID-5480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPID-5480. Resolution: Fixed Fixed in r.1564877. Several other recovery issues and boundary issues were

[jira] [Resolved] (QPID-5479) [linearstore] Using recovered store results in "JERR_JNLF_FILEOFFSOVFL: Attempted to increase submitted offset past file size. (JournalFile::submittedDblkCount)" error me

[ https://issues.apache.org/jira/browse/QPID-5479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPID-5479. Resolution: Fixed Fixed by the checkin to fix QPID-5480 (r. 1564877). Tested against reprodu

[jira] [Created] (QPID-5603) [Linearstore] Broker recovery fails with JERR_JREC_BADRECTAIL when record tail is partly or fully separated from rest of record by file boundary

Kim van der Riet created QPID-5603: -- Summary: [Linearstore] Broker recovery fails with JERR_JREC_BADRECTAIL when record tail is partly or fully separated from rest of record by file boundary Key: QPID-5603 URL:

[jira] [Commented] (QPID-5603) [Linearstore] Broker recovery fails with JERR_JREC_BADRECTAIL when record tail is partly or fully separated from rest of record by file boundary

[ https://issues.apache.org/jira/browse/QPID-5603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13920874#comment-13920874 ] Kim van der Riet commented on QPID-5603: Every record that contains either data and

[jira] [Resolved] (QPID-5603) [Linearstore] Broker recovery fails with JERR_JREC_BADRECTAIL when record tail is partly or fully separated from rest of record by file boundary

[ https://issues.apache.org/jira/browse/QPID-5603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPID-5603. Resolution: Fixed Fixed in r.15745143 > [Linearstore] Broker recovery fails with JERR_JREC_

[jira] [Comment Edited] (QPID-5603) [Linearstore] Broker recovery fails with JERR_JREC_BADRECTAIL when record tail is partly or fully separated from rest of record by file boundary

[ https://issues.apache.org/jira/browse/QPID-5603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13920908#comment-13920908 ] Kim van der Riet edited comment on QPID-5603 at 3/5/14 2:52 PM: -

[jira] [Created] (QPID-5607) [linearstore] Recovery of store results in jexception 0x010b LinearFileController::getCurrentSerial() threw JERR_NULL

Kim van der Riet created QPID-5607: -- Summary: [linearstore] Recovery of store results in jexception 0x010b LinearFileController::getCurrentSerial() threw JERR_NULL Key: QPID-5607 URL: https://issues.apache.org/ji

[jira] [Resolved] (QPID-5607) [linearstore] Recovery of store results in jexception 0x010b LinearFileController::getCurrentSerial() threw JERR_NULL

[ https://issues.apache.org/jira/browse/QPID-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPID-5607. Resolution: Fixed Fixed in r.1575009 > [linearstore] Recovery of store results in jexceptio

[jira] [Created] (QPID-5641) [legacystore] Valgrind reports memory leaks on older store tests

Kim van der Riet created QPID-5641: -- Summary: [legacystore] Valgrind reports memory leaks on older store tests Key: QPID-5641 URL: https://issues.apache.org/jira/browse/QPID-5641 Project: Qpid

[jira] [Commented] (QPID-5641) [legacystore] Valgrind reports memory leaks on older store tests

[ https://issues.apache.org/jira/browse/QPID-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943164#comment-13943164 ] Kim van der Riet commented on QPID-5641: Given the limited value of these older tes

[jira] [Resolved] (QPID-5641) [legacystore] Valgrind reports memory leaks on older store tests

[ https://issues.apache.org/jira/browse/QPID-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPID-5641. Resolution: Fixed Resolved in r.1582324 > [legacystore] Valgrind reports memory leaks on ol

[jira] [Created] (QPID-5654) [linearstore] Set default cmake build to exclude linearstore

Kim van der Riet created QPID-5654: -- Summary: [linearstore] Set default cmake build to exclude linearstore Key: QPID-5654 URL: https://issues.apache.org/jira/browse/QPID-5654 Project: Qpid

[jira] [Updated] (QPID-5654) [linearstore] Set default cmake build to exclude linearstore on 0.28 release

[ https://issues.apache.org/jira/browse/QPID-5654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPID-5654: --- Summary: [linearstore] Set default cmake build to exclude linearstore on 0.28 release (was: [

[jira] [Commented] (QPID-5654) [linearstore] Set default cmake build to exclude linearstore on 0.28 release

[ https://issues.apache.org/jira/browse/QPID-5654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13955599#comment-13955599 ] Kim van der Riet commented on QPID-5654: Review board for change: https://reviews.a

[jira] [Resolved] (QPID-5484) [linearstore] Poor performance relative to legacystore

[ https://issues.apache.org/jira/browse/QPID-5484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPID-5484. Resolution: Fixed Fixed by r.1558913, a fix for QPID-5487. > [linearstore] Poor performance

[jira] [Closed] (QPID-5317) Valgrind detects leaks in legacystore_OrderingTest unit test program

[ https://issues.apache.org/jira/browse/QPID-5317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPID-5317. -- Resolution: Duplicate Duplicate of QPID-5641 > Valgrind detects leaks in legacystore_OrderingTe

[jira] [Closed] (QPID-5492) Make install currently installs multiple store modules making qpidd fail by default

[ https://issues.apache.org/jira/browse/QPID-5492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed QPID-5492. -- Resolution: Duplicate Duplicate of / resolved by QPID-5654 > Make install currently installs mu

[jira] [Created] (QPID-5655) [linearstore] Installation and tests for new store analysis tool qpid-qls-analyze

Kim van der Riet created QPID-5655: -- Summary: [linearstore] Installation and tests for new store analysis tool qpid-qls-analyze Key: QPID-5655 URL: https://issues.apache.org/jira/browse/QPID-5655 Pro

[jira] [Created] (QPID-5660) [legacystore] Python tests fail with syntax error

Kim van der Riet created QPID-5660: -- Summary: [legacystore] Python tests fail with syntax error Key: QPID-5660 URL: https://issues.apache.org/jira/browse/QPID-5660 Project: Qpid Issue Type:

[jira] [Updated] (QPID-5660) [legacystore] Python tests fail with syntax error

[ https://issues.apache.org/jira/browse/QPID-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPID-5660: --- Description: Recent tests of legacystore on older versions of linux that use Python 2.4.x fai

[jira] [Updated] (QPID-5660) [legacystore] Python tests fail with syntax error

[ https://issues.apache.org/jira/browse/QPID-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPID-5660: --- Description: Recent tests of legacystore on older versions of linux that use Python 2.4.x fai

[jira] [Updated] (QPID-5660) [legacystore] Python tests fail with syntax error on Python 2.4

[ https://issues.apache.org/jira/browse/QPID-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPID-5660: --- Summary: [legacystore] Python tests fail with syntax error on Python 2.4 (was: [legacystore]

[jira] [Resolved] (QPID-5660) [legacystore] Python tests fail with syntax error on Python 2.4

[ https://issues.apache.org/jira/browse/QPID-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPID-5660. Resolution: Fixed Fixed in r.1584347. > [legacystore] Python tests fail with syntax error o

  1   2   3   4   5   6   7   8   9   10   >