[
https://issues.apache.org/jira/browse/QPID-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPID-2250:
-
Status: Ready To Review (was: In Progress)
> copying messages to a new queue only works with a pe
[
https://issues.apache.org/jira/browse/QPID-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPID-2177:
-
Status: Ready To Review (was: In Progress)
> Allow for configuration of producer flow control que
I have created a new 08InVMExcludes file and added it to the
profile.excludes property in default.testprofile, enabling exclusion of the
test only for the InVM testing. I didn't make the other changes I suggested
to correct the usage of the 08Excludes file, so it is currently still
excluding tests
copying messages to a new queue only works with a persistent message and a
durable queue
Key: QPID-2250
URL: https://issues.apache.org/jira/browse/QPID-2250
Proj
[
https://issues.apache.org/jira/browse/QPID-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787228#action_12787228
]
Aidan Skinner commented on QPID-2240:
-
I think this patch is OK in principle, a couple o
[
https://issues.apache.org/jira/browse/QPID-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aidan Skinner updated QPID-2238:
Fix Version/s: 0.6
> [.Net 0-10] Recursive call to ToString method causes a stack overflow
> except
[
https://issues.apache.org/jira/browse/QPID-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aidan Skinner resolved QPID-2237.
-
Resolution: Fixed
Fix Version/s: 0.6
comitted, thanks for the patch!
> UUID are not decode
[
https://issues.apache.org/jira/browse/QPID-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aidan Skinner resolved QPID-2238.
-
Resolution: Fixed
Commited, thanks for the patch!
> [.Net 0-10] Recursive call to ToString method
[
https://issues.apache.org/jira/browse/QPID-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated QPID-2245:
---
Attachment: QPID-2245-Dotnet.patch
QPID-2245-Ruby.patch
QPID-2245-Python.patch
[
https://issues.apache.org/jira/browse/QPID-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated QPID-2245:
---
Attachment: (was: QPID-2245-Python.patch)
> QMF protocol changes will make 0.6 incompatible with 0.5
> ---
[
https://issues.apache.org/jira/browse/QPID-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated QPID-2249:
---
Attachment: QPID-2249.patch
Headers example plus update to README.
> Python Headers Exchange Example
> -
Python Headers Exchange Example
---
Key: QPID-2249
URL: https://issues.apache.org/jira/browse/QPID-2249
Project: Qpid
Issue Type: New Feature
Components: Qpid Examples
Reporter: Ted Ross
At
On Mon, Dec 7, 2009 at 2:54 PM, Aidan Skinner wrote:
> On Mon, Dec 7, 2009 at 5:16 PM, Rajith Attapattu wrote:
>
>> However I'd like to see similar functionality/behaviour implemented by
>> our brokers for a given requirement where possible.
>> The Java brokers ip-whitelisting feature is standalo
Existing users of the ACLs have had to suffer quite a bit (see the JIRAs
fixed in the last couple of releases), thus my impression is that
there is/was a real motivation for not making big changes there.
We need to maintain (at least) backward compatibility so that we don't cause
users with produc
Aidan Skinner wrote:
On Mon, Dec 7, 2009 at 5:16 PM, Rajith Attapattu wrote:
However I'd like to see similar functionality/behaviour implemented by
our brokers for a given requirement where possible.
The Java brokers ip-whitelisting feature is standalone atm.
So wondering if there is any in
On Mon, Dec 7, 2009 at 5:16 PM, Rajith Attapattu wrote:
> However I'd like to see similar functionality/behaviour implemented by
> our brokers for a given requirement where possible.
> The Java brokers ip-whitelisting feature is standalone atm.
> So wondering if there is any interest in combining
[
https://issues.apache.org/jira/browse/QPID-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher updated QPID-2214:
--
Fix Version/s: 0.6
> memory leak in qpid::client::Connection
> -
[
https://issues.apache.org/jira/browse/QPID-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved QPID-2214.
---
Resolution: Fixed
The growth in memory for each open/close of a connection has been removed.
[
https://issues.apache.org/jira/browse/QPID-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787069#action_12787069
]
Andrew Stitcher commented on QPID-2214:
---
The committed fix isn't the amended patch for
Hi Kerry,
> -Original Message-
> From: Kerry Bonin [mailto:kerrybo...@gmail.com]
> Sent: Monday, December 07, 2009 2:25 PM
> To: dev@qpid.apache.org
> Cc: qpid-...@incubator.apache.org
> Subject: Re: Building C++\Windows trunk?
>
>
> On Thu, Dec 3, 2009 at 5:23 PM, Steve Huston
> wrot
[
https://issues.apache.org/jira/browse/QPID-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787067#action_12787067
]
Andrew Stitcher commented on QPID-2214:
---
I've committed a change on the trunk branch f
On Thu, Dec 3, 2009 at 5:23 PM, Steve Huston wrote:
> Hi Kerry,
>
> > I'm having some issues getting the trunk to build - most
> > notably namespace
> > collisions between the global namespace types in
> > qpid/sys/windows.IntegerTypes.h and those defined in boost
> > cstdint - first
> > hit is i
On Mon, Dec 7, 2009 at 1:39 PM, Robbie Gemmell wrote:
> My understanding of it was that the default profile was for InVM testing and
> pulling in the global excludes, with other broker profiles (java standalone,
> cpp etc) based off that and pulling in any profile specific excludes. I
> think that
My understanding of it was that the default profile was for InVM testing and
pulling in the global excludes, with other broker profiles (java standalone,
cpp etc) based off that and pulling in any profile specific excludes. I
think thats a god system to keep..it just isn't quite working like that a
[
https://issues.apache.org/jira/browse/QPID-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell reassigned QPID-2244:
Assignee: Robbie Gemmell
> AMQQueueMBean.viewMessages does not show 0-10 protocol
> Message
Robbie,
The current excludes files needs a bit or re-org for sure.
I think two types of exclusions are needed.
1. Tests that run on either c++ , java broker or in-vm broker.
2. Tests that are specific to a particular protocol version.
3. Tests that are for a particular feature like clustering,
per
Hi all,
I have written a test that should only be run against the Java broker, but
cant currently be run against the InVM broker. As a result I am looking to
exclude it only from the InVM tests, but looking at the test profiles I dont
think this is currently possible. There are some tests in th
Hi All,
Currently the Java broker implements IP white-lists where using
firewall rules is not an option.
http://qpid.apache.org/ip-whitelisting.html
There is an email on the user list which has a similar requirement,
where a certain user is allowed to connect via an approved list of IP
addresses.
On Mon, 2009-12-07 at 10:28 -0500, Alan Conway wrote:
> On 12/04/2009 12:20 PM, Andrew Stitcher wrote:
> > On Fri, 2009-12-04 at 11:07 -0500, Alan Conway wrote:
> >> ...On 12/02/2009 07:53 PM, Andrew Stitcher wrote:
> >>
> >>> Cmake build is mostly fine - however the clustering module doesn't build
[
https://issues.apache.org/jira/browse/QPID-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated QPID-2245:
---
Attachment: QPID-2245-Cpp.patch
QPID-2245-Python.patch
Python and C++ patches.
> QMF protoco
[
https://issues.apache.org/jira/browse/QPID-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated QPID-2245:
---
Attachment: QPID-2245-QMan.patch
QPID-2245-JavaConsole.patch
Java patches for review.
> QMF
On 12/04/2009 12:20 PM, Andrew Stitcher wrote:
On Fri, 2009-12-04 at 11:07 -0500, Alan Conway wrote:
...On 12/02/2009 07:53 PM, Andrew Stitcher wrote:
Cmake build is mostly fine - however the clustering module doesn't build
due to a complication of recent versions of boost.
The cluster& clu
I did the removal as a single commit (r887951) so if we want it back
it is easy to do, but thought it best to keep the 'seemingly dead
code' to a minimum.
Cheers
Martin
2009/12/7 Martin Ritchie :
> Hi,
>
> I'm working on QPID-2242 and notice that whilst the 0-10 code path has
> a solution to the
[
https://issues.apache.org/jira/browse/QPID-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786940#action_12786940
]
Ted Ross commented on QPID-2248:
A couple of reasons:
First, the distinction was used to se
[
https://issues.apache.org/jira/browse/QPID-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786938#action_12786938
]
Ken Giusti commented on QPID-2248:
--
My summary is a bit oversimplified: I'm proposing that
>> Things that concern me are the:
>> inability to view/manage messages via the console.
>>
>
> Agreed this would be desirable, though I made the decision that I would
> leave JMX support of 0-10 to post 0.6 releases. In particular I want to
> explore how we do our management a little more with a
[
https://issues.apache.org/jira/browse/QPID-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Doerfler updated QPID-2214:
--
Attachment: qpid-memleak2.patch
Fixed version: now the destructor gets called
> memory leak in
[
https://issues.apache.org/jira/browse/QPID-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway resolved QPID-2231.
---
Resolution: Fixed
Fixed in r886899
> Cluster + store fails with default data-directory
>
[
https://issues.apache.org/jira/browse/QPID-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786914#action_12786914
]
Martin Ritchie commented on QPID-2242:
--
0-10 code has an ExchangeQuery method that allo
Hi,
I'm working on QPID-2242 and notice that whilst the 0-10 code path has
a solution to the problem it is not used.
This constructor:
protected AMQMessageDelegate_0_10(long deliveryTag, MessageProperties
messageProps, DeliveryProperties deliveryProps,-
AMQShortString routingKey) t
[
https://issues.apache.org/jira/browse/QPID-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786847#action_12786847
]
Rob Godfrey commented on QPID-2234:
---
> What was the reasoning behind the new PrincipalHold
Hi Martin
2009/12/4 Martin Ritchie
> Hi Rob,
>
> Just wondered what the state was of the 0-10 implementation on the Java
> broker.
>
> I see that there are quite a few todo's still in the code base. Do you
> think it is ready to be the default protocol for 0.6?
>
>
I think the quality of the cod
42 matches
Mail list logo
