Re: Review Request: QPID-4559 Check the if_empty and if_unused flags when deleting a queue with deleteObject()

[Kenneth Giusti]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/9510/#review16790
---


These broker side changes look good, however, on trunk, qpid-config doesn't 
seem to pass along the if_empty or if_unused flags.

Specifically, when I:

qpid-config --force del queue ken

I get this on the broker log:

2013-02-20 15:19:39 [Management] debug RECV MethodRequest (v2) 
class=org.apache.qpid.broker:broker method=delete 
replyTo=qmf.default.topic/direct.3dcd54bb-44d2-4e26-b031-0e1c75a0851d 
objId=0-0-0--0(org.apache.qpid.broker:broker:amqp-broker) inArgs={name:ken, 
type:queue}
2013-02-20 15:19:39 [Broker] debug Broker::delete(queue, ken,{})

That empty map in the last log message should include those two flags, but 
they're not present.

Are changes needed in qpid-config to pass those flags to delete?


- Kenneth Giusti


On Feb. 20, 2013, 7:25 p.m., Ernie Allen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/9510/
> ---
> 
> (Updated Feb. 20, 2013, 7:25 p.m.)
> 
> 
> Review request for qpid and Ted Ross.
> 
> 
> Description
> ---
> 
> Adds a check() method to the broker and passes it to queueDelete to inspect 
> the if_unused and if_empty flags. 
> 
> 
> This addresses bug QPID-4559.
> https://issues.apache.org/jira/browse/QPID-4559
> 
> 
> Diffs
> -
> 
>   /trunk/qpid/cpp/src/qpid/broker/Broker.h 1447816 
>   /trunk/qpid/cpp/src/qpid/broker/Broker.cpp 1447816 
> 
> Diff: https://reviews.apache.org/r/9510/diff/
> 
> 
> Testing
> ---
> 
> unit tests: created queue, added messages, deleted queue with and without 
> flags and with and without messages and connections
> 
> 
> Thanks,
> 
> Ernie Allen
> 
>

Re: Review Request: PROTON-215: Add tests to verify AMQP 1.0 type support for all language bindings

[Kenneth Giusti]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/9413/#review16783
---

Ship it!


Ship It!

- Kenneth Giusti


On Feb. 19, 2013, 5:41 p.m., Alan Conway wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/9413/
> ---
> 
> (Updated Feb. 19, 2013, 5:41 p.m.)
> 
> 
> Review request for qpid, Kenneth Giusti and Rafael Schloming.
> 
> 
> Description
> ---
> 
> Python and Java tests in place, PHP, Perl and ruby to come.
> 
> 
> Diffs
> -
> 
>   
> /proton/trunk/proton-c/bindings/java/src/main/java/org/apache/qpid/proton/TestDecoder.java
>  PRE-CREATION 
>   
> /proton/trunk/proton-c/bindings/java/src/main/java/org/apache/qpid/proton/codec/jni/JNIData.java
>  1447222 
>   
> /proton/trunk/proton-j/proton/src/main/java/org/apache/qpid/proton/TestDecoder.java
>  PRE-CREATION 
>   /proton/trunk/tests/interop/message.amqp UNKNOWN 
>   /proton/trunk/tests/java/org/apache/qpid/proton/InteropTest.java 
> PRE-CREATION 
>   /proton/trunk/tests/python/interop-generate 1447222 
>   /proton/trunk/tests/python/proton_tests/interop.py 1447222 
> 
> Diff: https://reviews.apache.org/r/9413/diff/
> 
> 
> Testing
> ---
> 
> echo " python"
> tests/python/proton-test *.interop.* || EXIT=1
> echo " proton-jni"
> mvn -P proton-jni -Dtest=InteropTest -DfailIfNoTests=false test || EXIT=1
> echo " proton-j"
> mvn -P proton-j -Dtest=InteropTest -DfailIfNoTests=false test || EXIT=1
> 
> 
> Thanks,
> 
> Alan Conway
> 
>

[jira] [Commented] (QPID-4589) C++ client unable to connect to Java Broker

[James Belch (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582463#comment-13582463
 ] 

James Belch commented on QPID-4589:
---

Keith,

  Thanks for the quick response.  I do see a clearer message using the Qpid .20 
release.  When no sasl-mechanism is specified, that error is returned to the 
C++ client.  When I set the sasl-mechanism option to "PLAIN" on the Qpid 
Connection class, I get the same error as I was seeing with the .18 
release("Reonnect disabled").  I checked the Redhat 6.3 machine where the C++ 
client is running and I see the following cyrus-sasl packages installed:

cyrus-sasl-2.1.23-13.el6.x86_64
cyrus-sasl-plain-2.1.23-13.el6.x86_64
cyrus-sasl-lib-2.1.23-13.el6.x86_64
cyrus-sasl-gsapi-2.1.23-13.el6.x86_64

Our Redhat 5.4 machine from which the client connects successfully, we have the 
following cyrus-sasl packages installed:

cyrus-sasl-2.1.22-5.el5
cyrus-sasl-plain-2.1.22-5.el5
cyrus-sasl-md5-2.1.22-5.el5
cyrus-sasl-devel-2.1.22-5.el5
cyrus-sasl-lib-2.1.22-5.el5

Do you recommend trying to install the cyrus-sasl-devel and cyrus-sasl-md5 on 
the 6.3 machine?


> C++ client unable to connect to Java Broker
> ---
>
> Key: QPID-4589
> URL: https://issues.apache.org/jira/browse/QPID-4589
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.18
> Environment: C++ client and Java Broker running on Redhat 6.3
>Reporter: James Belch
>Assignee: Keith Wall
>Priority: Minor
>
> Our C++ clients were initially running on Redhat 5.4 and communicating with a 
> Java Broker running on Redhat 6.3.  Everything was working fine.  We need to 
> move our C++ development over to another network which use Redhat 6.3.  
> Because of this, we needed to rebuild our C++ executables on Redhat 6.3.  
> When attempting to connect with a 6.3 C++ client, we get an error while 
> trying connect to the Java Broker.  It returns an error saying "Reconnect 
> disabled".  It appears to be similar to the following issue, 
> "https://issues.apache.org/jira/browse/QPID-4419";. I am able to connect to 
> the C++ broker successfully from the Redhat 6.3 client.  My questions are:
> 1.  Is this a bug that has been fixed or is there something that we can do in 
> our .18 Java Broker configuration to solve this problem?  We are currently 
> using the default Java Broker configuration.
> 2.  Do you think this is related to QPID-4419 from above?  If so, should we 
> upgrade to Qpid .20 to solve this problem?
> 3.  Do you recommend using the Java Broker or the C++ Broker?  We have 
> thought about switching over to the C++ Broker, but we wanted to know if you 
> could answer the following questions:
> a.  Do you know how many of your Redhat customers use the Java Broker?   
> Do you think the Java Broker and C++ Broker are used equally 
> or is one preferred over the other?
> b.  Which Broker (Java or C++) offers better performance?
> c.  Do you offer the same support for the Java and C++ Brokers.  Do bugs 
> written against the Java Broker and C++ Broker get the same priority?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Re: Review Request: QPID-4559 Check the if_empty and if_unused flags when deleting a queue with deleteObject()

[Ernie Allen]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/9510/
---

(Updated Feb. 20, 2013, 7:25 p.m.)


Review request for qpid and Ted Ross.


Changes
---

Initialized ifUnused to false.


Description
---

Adds a check() method to the broker and passes it to queueDelete to inspect the 
if_unused and if_empty flags. 


This addresses bug QPID-4559.
https://issues.apache.org/jira/browse/QPID-4559


Diffs (updated)
-

  /trunk/qpid/cpp/src/qpid/broker/Broker.h 1447816 
  /trunk/qpid/cpp/src/qpid/broker/Broker.cpp 1447816 

Diff: https://reviews.apache.org/r/9510/diff/


Testing
---

unit tests: created queue, added messages, deleted queue with and without flags 
and with and without messages and connections


Thanks,

Ernie Allen

Re: Review Request: QPID-4559 Check the if_empty and if_unused flags when deleting a queue with deleteObject()

[Kenneth Giusti]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/9510/#review16780
---



/trunk/qpid/cpp/src/qpid/broker/Broker.cpp


is ifUnused uninitialized here?


- Kenneth Giusti


On Feb. 19, 2013, 6:14 p.m., Ernie Allen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/9510/
> ---
> 
> (Updated Feb. 19, 2013, 6:14 p.m.)
> 
> 
> Review request for qpid and Ted Ross.
> 
> 
> Description
> ---
> 
> Adds a check() method to the broker and passes it to queueDelete to inspect 
> the if_unused and if_empty flags. 
> 
> 
> This addresses bug QPID-4559.
> https://issues.apache.org/jira/browse/QPID-4559
> 
> 
> Diffs
> -
> 
>   /trunk/qpid/cpp/src/qpid/broker/Broker.h 1447816 
>   /trunk/qpid/cpp/src/qpid/broker/Broker.cpp 1447816 
> 
> Diff: https://reviews.apache.org/r/9510/diff/
> 
> 
> Testing
> ---
> 
> unit tests: created queue, added messages, deleted queue with and without 
> flags and with and without messages and connections
> 
> 
> Thanks,
> 
> Ernie Allen
> 
>

[jira] [Resolved] (QPID-3620) time conversions fail on solaris

[Cliff Jansen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cliff Jansen resolved QPID-3620.


Resolution: Fixed

fixed.  r1242406

> time conversions fail on solaris
> 
>
> Key: QPID-3620
> URL: https://issues.apache.org/jira/browse/QPID-3620
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Broker, C++ Client
>Affects Versions: 0.15
> Environment: Solaris sparc 64
>Reporter: Cliff Jansen
>Assignee: Cliff Jansen
> Attachments: QPID-3620-0.patch
>
>
> Condition::wait(Mutex&, const AbsTime& absoluteTime) fails for far future 
> time during cast/truncation from 64 bit int to posix timespec.tv_sec.  The 
> time is actually in the past and the wait times out instantly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (QPID-3621) Basic Solaris porting 0.15

[Cliff Jansen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cliff Jansen resolved QPID-3621.


Resolution: Fixed

Fixed. r1242411

> Basic Solaris porting 0.15
> --
>
> Key: QPID-3621
> URL: https://issues.apache.org/jira/browse/QPID-3621
> Project: Qpid
>  Issue Type: Improvement
>  Components: C++ Broker, C++ Client
>Affects Versions: 0.15
> Environment: Solaris
>Reporter: Cliff Jansen
>Assignee: Cliff Jansen
> Attachments: QPID-3621-0.patch
>
>
> A continuation of previous work to port Qpid to Solaris.  This is for 
> non-substantive build and compile/link issues that pertain only to the 
> solaris port, i.e. cmake directives, compiler warnings, linker directives.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Assigned] (QPID-4593) [Java Broker] Add a command line option to define file used for initial values

[Alex Rudyy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy reassigned QPID-4593:


Assignee: Robbie Gemmell  (was: Alex Rudyy)

Robbie,
Could you please review the changes committed at revision  
https://svn.apache.org/repos/asf/qpid/trunk@1448306 ?

> [Java Broker] Add a command line option to define file used for initial values
> --
>
> Key: QPID-4593
> URL: https://issues.apache.org/jira/browse/QPID-4593
> Project: Qpid
>  Issue Type: Task
>  Components: Java Broker
>Affects Versions: 0.21
>Reporter: Alex Rudyy
>Assignee: Robbie Gemmell
> Fix For: 0.21
>
>
> We need a command line option to specify an location of a file with initial 
> broker configuration to copy it into the broker store

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPID-4593) [Java Broker] Add a command line option to define file used for initial values

[Alex Rudyy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-4593:
-

Status: Ready To Review  (was: In Progress)

> [Java Broker] Add a command line option to define file used for initial values
> --
>
> Key: QPID-4593
> URL: https://issues.apache.org/jira/browse/QPID-4593
> Project: Qpid
>  Issue Type: Task
>  Components: Java Broker
>Affects Versions: 0.21
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
> Fix For: 0.21
>
>
> We need a command line option to specify an location of a file with initial 
> broker configuration to copy it into the broker store

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Re: Review Request: PROTON-199: provide UUID and other fixes to support Python version 2.4

[Rafael Schloming]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/9526/#review16770
---

Ship it!


Ship It!

- Rafael Schloming


On Feb. 20, 2013, 5:10 p.m., Kenneth Giusti wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/9526/
> ---
> 
> (Updated Feb. 20, 2013, 5:10 p.m.)
> 
> 
> Review request for qpid, Rafael Schloming and Philip Harvey.
> 
> 
> Description
> ---
> 
> Just a quick update to the python patch.   Shall we include this in 0.4?
> 
> 
> This addresses bug proton-199.
> https://issues.apache.org/jira/browse/proton-199
> 
> 
> Diffs
> -
> 
>   /proton/trunk/proton-c/bindings/python/proton.py 1448220 
>   /proton/trunk/tests/python/proton-test 1448220 
>   /proton/trunk/tests/python/proton_tests/codec.py 1448220 
>   /proton/trunk/tests/python/proton_tests/message.py 1448220 
> 
> Diff: https://reviews.apache.org/r/9526/diff/
> 
> 
> Testing
> ---
> 
> tested against Centos-5, python version 2.4.3
> 
> 
> Thanks,
> 
> Kenneth Giusti
> 
>

Review Request: PROTON-199: provide UUID and other fixes to support Python version 2.4

[Kenneth Giusti]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/9526/
---

Review request for qpid, Rafael Schloming and Philip Harvey.


Description
---

Just a quick update to the python patch.   Shall we include this in 0.4?


This addresses bug proton-199.
https://issues.apache.org/jira/browse/proton-199


Diffs
-

  /proton/trunk/proton-c/bindings/python/proton.py 1448220 
  /proton/trunk/tests/python/proton-test 1448220 
  /proton/trunk/tests/python/proton_tests/codec.py 1448220 
  /proton/trunk/tests/python/proton_tests/message.py 1448220 

Diff: https://reviews.apache.org/r/9526/diff/


Testing
---

tested against Centos-5, python version 2.4.3


Thanks,

Kenneth Giusti

[jira] [Created] (QPID-4593) [Java Broker] Add a command line option to define file used for initial values

[Alex Rudyy (JIRA)]

Alex Rudyy created QPID-4593:


 Summary: [Java Broker] Add a command line option to define file 
used for initial values
 Key: QPID-4593
 URL: https://issues.apache.org/jira/browse/QPID-4593
 Project: Qpid
  Issue Type: Task
  Components: Java Broker
Affects Versions: 0.21
Reporter: Alex Rudyy
Assignee: Alex Rudyy
 Fix For: 0.21


We need a command line option to specify an location of a file with initial 
broker configuration to copy it into the broker store

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Re: Proton routing prototype.

[Alan Conway]

On Wed, 2013-02-20 at 07:20 -0800, Rafael Schloming wrote:
> Where's the attachment?

Doh!

https://cwiki.apache.org/confluence/display/qpid/Proton+routing
+prototype

> 
> --Rafael
> 
> On Wed, Feb 20, 2013 at 7:15 AM, Alan Conway  wrote:
> 
> > Attached a brief proposal for an initial prototype for "proton routing".
> > No attempt is made to enumerate all the uses cases we should/couuld
> > cover. Instead it proposes a basic framework and 2 interesting use cases
> > to drive the initial prototype. Implementing those 2 cases will give us
> > some insight into what is needed for a production version.
> >
> > Any comments very welcome.
> >
> > Cheers,
> > Alan.
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
> > For additional commands, e-mail: dev-h...@qpid.apache.org
> >
> >



-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Re: Proton routing prototype.

[Rafael Schloming]

Where's the attachment?

--Rafael

On Wed, Feb 20, 2013 at 7:15 AM, Alan Conway  wrote:

> Attached a brief proposal for an initial prototype for "proton routing".
> No attempt is made to enumerate all the uses cases we should/couuld
> cover. Instead it proposes a basic framework and 2 interesting use cases
> to drive the initial prototype. Implementing those 2 cases will give us
> some insight into what is needed for a production version.
>
> Any comments very welcome.
>
> Cheers,
> Alan.
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
> For additional commands, e-mail: dev-h...@qpid.apache.org
>
>

Proton routing prototype.

[Alan Conway]

Attached a brief proposal for an initial prototype for "proton routing".
No attempt is made to enumerate all the uses cases we should/couuld
cover. Instead it proposes a basic framework and 2 interesting use cases
to drive the initial prototype. Implementing those 2 cases will give us
some insight into what is needed for a production version.

Any comments very welcome.

Cheers,
Alan.


-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Re: Review Request: PROTON-200: messenger::recv(-1) allows unlimited credit to all receivers.

[Kenneth Giusti]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/9503/
---

(Updated Feb. 20, 2013, 2:28 p.m.)


Review request for qpid, mick goulish, Rafael Schloming, Rob Godfrey, and 
Philip Harvey.


Description
---

This implements the "recv(-1) api change:  passing -1 to messenger::recv() 
causes messenger to grant one credit to every active receiver link.

Note this does not implement the same behavior for the Java implementation of 
messenger - not sure even if the same bug is present with that implementation.


This addresses bug proton-200.
https://issues.apache.org/jira/browse/proton-200


Diffs
-

  /proton/trunk/proton-c/bindings/python/proton.py 1447222 
  /proton/trunk/proton-c/include/proton/cproton.i 1447222 
  /proton/trunk/proton-c/include/proton/messenger.h 1447222 
  /proton/trunk/proton-c/src/messenger.c 1447222 
  
/proton/trunk/proton-j/proton/src/main/java/org/apache/qpid/proton/messenger/impl/MessengerImpl.java
 1447222 
  /proton/trunk/tests/python/proton_tests/messenger.py 1447222 

Diff: https://reviews.apache.org/r/9503/diff/


Testing
---

additional python unit test to exercise this problem.


Thanks,

Kenneth Giusti

[jira] [Updated] (QPID-4592) Add ability to suppress the automatic promotion of non-durable queues to durable during automated store upgrade

[Keith Wall (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-4592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keith Wall updated QPID-4592:
-

Labels: BDB  (was: )

> Add ability to suppress the automatic promotion of non-durable queues to 
> durable during automated store upgrade
> ---
>
> Key: QPID-4592
> URL: https://issues.apache.org/jira/browse/QPID-4592
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Affects Versions: 0.18, 0.20
>Reporter: Keith Wall
>  Labels: BDB
> Fix For: 0.21
>
>
> QPID-3913 introduced the ability for the Java Broker to automatically upgrade 
> bdb-stores that were created by earlier versions of the Broker (rather than 
> having to run the separate bin/storeUpgrade.sh tool).
> In this change, the user lost the the ability to control how the broker 
> handles the existence of persistent messages on non-durable queues.  
> Currently, the Broker always promotes these queues to durable so that the 
> messages may be recovered.  The user has no ability to override this 
> behaviour.  Additionally, the fact that a durable queue has been created is 
> not recorded in the log.
> We should consider:
> * logging the fact that a non-durable queue has been promoted to durable by 
> the auto upgrade process
> * allow this behaviour to be suppressed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPID-4592) Add ability to suppress the automatic promotion of non-durable queues to durable during store upgrade

[Keith Wall (JIRA)]

Keith Wall created QPID-4592:


 Summary: Add ability to suppress the automatic promotion of 
non-durable queues to durable during store upgrade
 Key: QPID-4592
 URL: https://issues.apache.org/jira/browse/QPID-4592
 Project: Qpid
  Issue Type: Improvement
  Components: Java Broker
Affects Versions: 0.20, 0.18
Reporter: Keith Wall
 Fix For: 0.21


QPID-3913 introduced the ability for the Java Broker to automatically upgrade 
bdb-stores that were created by earlier versions of the Broker (rather than 
having to run the separate bin/storeUpgrade.sh tool).

In this change, the user lost the the ability to control how the broker handles 
the existence of persistent messages on non-durable queues.  Currently, the 
Broker always promotes these queues to durable so that the messages may be 
recovered.  The user has no ability to override this behaviour.  Additionally, 
the fact that a durable queue has been created is not recorded in the log.

We should consider:

* logging the fact that a non-durable queue has been promoted to durable by the 
auto upgrade process
* allow this behaviour to be suppressed.



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPID-4592) Add ability to suppress the automatic promotion of non-durable queues to durable during automated store upgrade

[Keith Wall (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-4592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keith Wall updated QPID-4592:
-

Summary: Add ability to suppress the automatic promotion of non-durable 
queues to durable during automated store upgrade  (was: Add ability to suppress 
the automatic promotion of non-durable queues to durable during store upgrade)

> Add ability to suppress the automatic promotion of non-durable queues to 
> durable during automated store upgrade
> ---
>
> Key: QPID-4592
> URL: https://issues.apache.org/jira/browse/QPID-4592
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Affects Versions: 0.18, 0.20
>Reporter: Keith Wall
> Fix For: 0.21
>
>
> QPID-3913 introduced the ability for the Java Broker to automatically upgrade 
> bdb-stores that were created by earlier versions of the Broker (rather than 
> having to run the separate bin/storeUpgrade.sh tool).
> In this change, the user lost the the ability to control how the broker 
> handles the existence of persistent messages on non-durable queues.  
> Currently, the Broker always promotes these queues to durable so that the 
> messages may be recovered.  The user has no ability to override this 
> behaviour.  Additionally, the fact that a durable queue has been created is 
> not recorded in the log.
> We should consider:
> * logging the fact that a non-durable queue has been promoted to durable by 
> the auto upgrade process
> * allow this behaviour to be suppressed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org