Re: [Carbon-dev] Qpid Java broker recent changes
+1. In fact even now the broker architecture is neat but having to support multiple protocol versions has made it little sloppy. On a side note I suggest you involve personally in 1.0 design/review work to get it right. Danushka On Mon, Oct 31, 2011 at 5:22 PM, Paul Fremantle wrote: > Danushka > > My main thought right now is that we need to move to 1.0 support for the > standard. I think one of the issues with Qpid - and I may be wrong - is > that the changing set of specs has meant too many updates to the core. I'd > love to see some stability around 1.0 and maybe even a plan to deprecate > and remove old spec versions. What do you think? > > Paul > > > On 31 October 2011 11:37, Danushka Menikkumbura < > danushka.menikkumb...@gmail.com> wrote: > >> Hi Paul, >> >> Yes that I've heard. >> >> My concern was OOM issues. The ones we identified and submitted patches >> for were mainly at the transport/session layer and had nothing to do with >> the underlying data store. Also as I understand the Cassandra store is for >> broker scaling (?). >> >> Robbie has done lots of changes to the broker code in recent past >> invalidating bulk of the patches that we submitted. My gut feeling is that >> the broker is better of in terms of memory usage with these changes. I can >> give it a try too at least with the standalone broker. >> >> Thanks, >> Danushka >> >> >> On Mon, Oct 31, 2011 at 3:41 PM, Paul Fremantle wrote: >> >>> Danushka >>> >>> Thanks! We'll take a look. We have also been trying out a Cassandra >>> store if you are interested. >>> >>> Paul >>> >>> On 31 October 2011 06:01, Danushka Menikkumbura < >>> danushka.menikkumb...@gmail.com> wrote: >>> Hi, Apparently Robbie has done certain changes to the broker which claim to have fixed some serious OOM issues. Specially [1] looks appealing. Can someone working on Qpid bits please check?. [1] - http://apache-qpid-users.2158936.n2.nabble.com/What-is-the-memory-footprint-of-an-Apache-qpid-queue-td6893642.html Danushka ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >>> -- >>> Paul Fremantle >>> CTO and Co-Founder, WSO2 >>> OASIS WS-RX TC Co-chair, VP, Apache Synapse >>> >>> UK: +44 207 096 0336 >>> US: +1 646 595 7614 >>> >>> blog: http://pzf.fremantle.org >>> twitter.com/pzfreo >>> p...@wso2.com >>> >>> wso2.com Lean Enterprise Middleware >>> >>> Disclaimer: This communication may contain privileged or other >>> confidential information and is intended exclusively for the addressee/s. >>> If you are not the intended recipient/s, or believe that you may have >>> received this communication in error, please reply to the sender indicating >>> that fact and delete the copy you received and in addition, you should not >>> print, copy, retransmit, disseminate, or otherwise use the information >>> contained in this communication. Internet communications cannot be >>> guaranteed to be timely, secure, error or virus-free. The sender does not >>> accept liability for any errors or omissions. >>> >>> >>> ___ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> ___ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > Paul Fremantle > CTO and Co-Founder, WSO2 > OASIS WS-RX TC Co-chair, VP, Apache Synapse > > UK: +44 207 096 0336 > US: +1 646 595 7614 > > blog: http://pzf.fremantle.org > twitter.com/pzfreo > p...@wso2.com > > wso2.com Lean Enterprise Middleware > > Disclaimer: This communication may contain privileged or other > confidential information and is intended exclusively for the addressee/s. > If you are not the intended recipient/s, or believe that you may have > received this communication in error, please reply to the sender indicating > that fact and delete the copy you received and in addition, you should not > print, copy, retransmit, disseminate, or otherwise use the information > contained in this communication. Internet communications cannot be > guaranteed to be timely, secure, error or virus-free. The sender does not > accept liability for any errors or omissions. > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Qpid Java broker recent changes
Danushka My main thought right now is that we need to move to 1.0 support for the standard. I think one of the issues with Qpid - and I may be wrong - is that the changing set of specs has meant too many updates to the core. I'd love to see some stability around 1.0 and maybe even a plan to deprecate and remove old spec versions. What do you think? Paul On 31 October 2011 11:37, Danushka Menikkumbura < danushka.menikkumb...@gmail.com> wrote: > Hi Paul, > > Yes that I've heard. > > My concern was OOM issues. The ones we identified and submitted patches > for were mainly at the transport/session layer and had nothing to do with > the underlying data store. Also as I understand the Cassandra store is for > broker scaling (?). > > Robbie has done lots of changes to the broker code in recent past > invalidating bulk of the patches that we submitted. My gut feeling is that > the broker is better of in terms of memory usage with these changes. I can > give it a try too at least with the standalone broker. > > Thanks, > Danushka > > > On Mon, Oct 31, 2011 at 3:41 PM, Paul Fremantle wrote: > >> Danushka >> >> Thanks! We'll take a look. We have also been trying out a Cassandra store >> if you are interested. >> >> Paul >> >> On 31 October 2011 06:01, Danushka Menikkumbura < >> danushka.menikkumb...@gmail.com> wrote: >> >>> Hi, >>> >>> Apparently Robbie has done certain changes to the broker which claim to >>> have fixed some serious OOM issues. Specially [1] looks appealing. Can >>> someone working on Qpid bits please check?. >>> >>> [1] - >>> http://apache-qpid-users.2158936.n2.nabble.com/What-is-the-memory-footprint-of-an-Apache-qpid-queue-td6893642.html >>> >>> Danushka >>> >>> ___ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> Paul Fremantle >> CTO and Co-Founder, WSO2 >> OASIS WS-RX TC Co-chair, VP, Apache Synapse >> >> UK: +44 207 096 0336 >> US: +1 646 595 7614 >> >> blog: http://pzf.fremantle.org >> twitter.com/pzfreo >> p...@wso2.com >> >> wso2.com Lean Enterprise Middleware >> >> Disclaimer: This communication may contain privileged or other >> confidential information and is intended exclusively for the addressee/s. >> If you are not the intended recipient/s, or believe that you may have >> received this communication in error, please reply to the sender indicating >> that fact and delete the copy you received and in addition, you should not >> print, copy, retransmit, disseminate, or otherwise use the information >> contained in this communication. Internet communications cannot be >> guaranteed to be timely, secure, error or virus-free. The sender does not >> accept liability for any errors or omissions. >> >> >> ___ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Qpid Java broker recent changes
Hi Paul, Yes that I've heard. My concern was OOM issues. The ones we identified and submitted patches for were mainly at the transport/session layer and had nothing to do with the underlying data store. Also as I understand the Cassandra store is for broker scaling (?). Robbie has done lots of changes to the broker code in recent past invalidating bulk of the patches that we submitted. My gut feeling is that the broker is better of in terms of memory usage with these changes. I can give it a try too at least with the standalone broker. Thanks, Danushka On Mon, Oct 31, 2011 at 3:41 PM, Paul Fremantle wrote: > Danushka > > Thanks! We'll take a look. We have also been trying out a Cassandra store > if you are interested. > > Paul > > On 31 October 2011 06:01, Danushka Menikkumbura < > danushka.menikkumb...@gmail.com> wrote: > >> Hi, >> >> Apparently Robbie has done certain changes to the broker which claim to >> have fixed some serious OOM issues. Specially [1] looks appealing. Can >> someone working on Qpid bits please check?. >> >> [1] - >> http://apache-qpid-users.2158936.n2.nabble.com/What-is-the-memory-footprint-of-an-Apache-qpid-queue-td6893642.html >> >> Danushka >> >> ___ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > Paul Fremantle > CTO and Co-Founder, WSO2 > OASIS WS-RX TC Co-chair, VP, Apache Synapse > > UK: +44 207 096 0336 > US: +1 646 595 7614 > > blog: http://pzf.fremantle.org > twitter.com/pzfreo > p...@wso2.com > > wso2.com Lean Enterprise Middleware > > Disclaimer: This communication may contain privileged or other > confidential information and is intended exclusively for the addressee/s. > If you are not the intended recipient/s, or believe that you may have > received this communication in error, please reply to the sender indicating > that fact and delete the copy you received and in addition, you should not > print, copy, retransmit, disseminate, or otherwise use the information > contained in this communication. Internet communications cannot be > guaranteed to be timely, secure, error or virus-free. The sender does not > accept liability for any errors or omissions. > > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Qpid Java broker recent changes
Danushka Thanks! We'll take a look. We have also been trying out a Cassandra store if you are interested. Paul On 31 October 2011 06:01, Danushka Menikkumbura < danushka.menikkumb...@gmail.com> wrote: > Hi, > > Apparently Robbie has done certain changes to the broker which claim to > have fixed some serious OOM issues. Specially [1] looks appealing. Can > someone working on Qpid bits please check?. > > [1] - > http://apache-qpid-users.2158936.n2.nabble.com/What-is-the-memory-footprint-of-an-Apache-qpid-queue-td6893642.html > > Danushka > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
