[jira] Commented: (QPID-2861) JMS client needs to handle duplicate commands replayed after failover

2010-09-20 Thread Rajith Attapattu (JIRA)
[ https://issues.apache.org/jira/browse/QPID-2861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912816#action_12912816 ] Rajith Attapattu commented on QPID-2861: After investigation I found that the JMS cl

[jira] Created: (QPID-2876) Design issues in Java client failover

2010-09-20 Thread Rajith Attapattu (JIRA)
Design issues in Java client failover - Key: QPID-2876 URL: https://issues.apache.org/jira/browse/QPID-2876 Project: Qpid Issue Type: Bug Components: Java Client Reporter: Rajith Atta

[jira] Commented: (QPID-2860) C++ hello_xml example receives all message content, not just what's wanted

2010-09-20 Thread Steve Huston (JIRA)
[ https://issues.apache.org/jira/browse/QPID-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912704#action_12912704 ] Steve Huston commented on QPID-2860: I think I know what's going on with this, but could

Re: qpid C++ broker cluster in centos 5.5

2010-09-20 Thread Alan Conway
On 09/20/2010 03:50 PM, Tim Chen wrote: Hi all, I'm trying to test qpid C++ broker clustering using a VM hosting centOS 5.5. Just running qpidd directly runs fine, so I did the following 1. install corosync/corosynclib/corosynclib-devel (1.2.7) from clusterlabs rhel 5 repository 2. rebuilt q

qpid C++ broker cluster in centos 5.5

2010-09-20 Thread Tim Chen
Hi all, I'm trying to test qpid C++ broker clustering using a VM hosting centOS 5.5. Just running qpidd directly runs fine, so I did the following 1. install corosync/corosynclib/corosynclib-devel (1.2.7) from clusterlabs rhel 5 repository 2. rebuilt qpid so it includes clustering support 3.

[jira] Created: (QPID-2875) Federation route propagation tests fail occassionally.

2010-09-20 Thread Ken Giusti (JIRA)
Federation route propagation tests fail occassionally. -- Key: QPID-2875 URL: https://issues.apache.org/jira/browse/QPID-2875 Project: Qpid Issue Type: Bug Components: Python Test

Re: Implementing clustering support for Qpid Java broker

2010-09-20 Thread Etienne Antoniutti Di Muro
That would be very helpful to define either clustering goals, and what/how to replicate. Thank you! Etienne On Mon, Sep 20, 2010 at 5:23 PM, Alan Conway wrote: > On 09/20/2010 11:05 AM, Kerry Bonin wrote: > On portability: I think it would not be difficult to abstract the C++ > cluster to run

[jira] Created: (QPID-2874) Clustered broker crashes in assertion in cluster/ExpiryPolicy.cpp

2010-09-20 Thread Alan Conway (JIRA)
Clustered broker crashes in assertion in cluster/ExpiryPolicy.cpp - Key: QPID-2874 URL: https://issues.apache.org/jira/browse/QPID-2874 Project: Qpid Issue Type: Bug C

Re: Implementing clustering support for Qpid Java broker

2010-09-20 Thread Lahiru Gunathilake
On Mon, Sep 20, 2010 at 8:55 PM, Etienne Antoniutti Di Muro < etienne.antoniu...@adaptivebytes.com> wrote: > So maybe we ca do the reverse, i.e. build a single replication > middleware serving both the C++ and Java > brokers. > > +1 I am not that happy with the C++ clustering implementation sinc

Re: Implementing clustering support for Qpid Java broker

2010-09-20 Thread Etienne Antoniutti Di Muro
So maybe we ca do the reverse, i.e. build a single replication middleware serving both the C++ and Java brokers. Such middleware can be built on top of a specific communication service layer, i.e. spread. Regards Etienne On Mon, Sep 20, 2010 at 5:05 PM, Kerry Bonin wrote: > On the C++ Broker

Re: Implementing clustering support for Qpid Java broker

2010-09-20 Thread Alan Conway
On 09/20/2010 11:05 AM, Kerry Bonin wrote: On the C++ Broker, just remember that the technology choice made for clustering (OpenAIS/Corosync) is a Linux only solution, and that codebase (~100k SLOC) was not written for portability. Our project needs a Windows option, and this is already hurting

Re: Implementing clustering support for Qpid Java broker

2010-09-20 Thread Kerry Bonin
On the C++ Broker, just remember that the technology choice made for clustering (OpenAIS/Corosync) is a Linux only solution, and that codebase (~100k SLOC) was not written for portability. Our project needs a Windows option, and this is already hurting us. I (and my team) would be willing to spen

[jira] Updated: (QPID-2858) Implement FilterManager for 0-10 subscriptions

2010-09-20 Thread Sorin Suciu (JIRA)
[ https://issues.apache.org/jira/browse/QPID-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sorin Suciu updated QPID-2858: -- Attachment: (was: qpid-2858.patch) > Implement FilterManager for 0-10 subscriptions > --

[jira] Updated: (QPID-2858) Implement FilterManager for 0-10 subscriptions

2010-09-20 Thread Sorin Suciu (JIRA)
[ https://issues.apache.org/jira/browse/QPID-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sorin Suciu updated QPID-2858: -- Attachment: (was: qpid-2858_1.patch) > Implement FilterManager for 0-10 subscriptions >

[jira] Updated: (QPID-2858) Implement FilterManager for 0-10 subscriptions

2010-09-20 Thread Sorin Suciu (JIRA)
[ https://issues.apache.org/jira/browse/QPID-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sorin Suciu updated QPID-2858: -- Attachment: qpid-2858_1.patch > Implement FilterManager for 0-10 subscriptions > ---

[jira] Reopened: (QPID-2858) Implement FilterManager for 0-10 subscriptions

2010-09-20 Thread Robbie Gemmell (JIRA)
[ https://issues.apache.org/jira/browse/QPID-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reopened QPID-2858: -- Assignee: Andrew Kennedy The newly created FilterManager is not used, so the patches amount to