Ted,
Thanks for the response.
I've taken on board the solution proposed in the post you directed me at.
I implemented the changes on Friday. Looking at it this morning the
broker is still consuming a large amount of memory, 30GBytes, but need
to at least give it until the end of the week befo
On 03/27/2017 12:53 PM, Robbie Gemmell wrote:
On 22 March 2017 at 13:43, Ted Ross wrote:
A couple of topics for discussion:
Qpid Dispatch Router 0.8.0 release
==
As of now, there are 116 resolved issues queued up for 0.8.0. I'd like to
wrap up this release i
On 20 March 2017 at 14:06, Justin Ross wrote:
> On Mon, Mar 20, 2017 at 6:59 AM, Adel Boutros wrote:
>
>> Could the issue be I am behind a proxy?
>>
>
> Yeah, that could definitely do it. The lua closer script uses a path that
> looks like just another file. If the proxy isn't forwarding the ul
On 22 March 2017 at 13:43, Ted Ross wrote:
> A couple of topics for discussion:
>
> Qpid Dispatch Router 0.8.0 release
> ==
>
> As of now, there are 116 resolved issues queued up for 0.8.0. I'd like to
> wrap up this release in the next week. I plan to defer all o
On 20 March 2017 at 20:07, Ken Giusti wrote:
>
>
> - Original Message -
>> From: "Robbie Gemmell"
>> To: users@qpid.apache.org
>> Sent: Friday, March 17, 2017 11:08:20 AM
>> Subject: Re: [HEADS UP] qpid-cpp 1.37.0
>>
>> I'm probably not going to get this started this week after all,
>> ht
On 22 March 2017 at 15:25, Keith W wrote:
> Resending... the previous mail hasn't seemed to have made it to the
> users@q.a.o list.
>
> On 22 March 2017 at 08:52, Keith W wrote:
>> Two JIRAs were raised for this work:
>>
>> QPID-7716 - Remove AMQP 0-10 based JCA/RA components from Qpid JMS 0-x C
On Fri, 2017-03-24 at 15:42 +0100, Rob Godfrey wrote:
>
> > Note that unsettled deliveries will outlive the link they were
> > created on, the AMQP spec allows settlement after the link has
> > closed.
> >
> >
>
> To be precise the spec allows for the state of the delivery to be
> updated
> aft
I like qpid-broker-j best of the alternatives proposed. I think
qpid-broker alone will cause a little confusion.
On Mon, Mar 27, 2017 at 3:41 AM, Rob Godfrey
wrote:
> On 27 March 2017 at 12:35, Robbie Gemmell
> wrote:
>
> > On 27 March 2017 at 10:47, Rob Godfrey wrote:
> > > On 27 March 2017
On 27 March 2017 at 12:35, Robbie Gemmell wrote:
> On 27 March 2017 at 10:47, Rob Godfrey wrote:
> > On 27 March 2017 at 11:31, Keith W wrote:
> >
> >> Hi all
> >>
> >> Now the Qpid Broker for Java and Qpid JMS AMQP 0-x Client are
> >> separated [1]/[2], I'd like to propose the final two remain
On 27 March 2017 at 10:47, Rob Godfrey wrote:
> On 27 March 2017 at 11:31, Keith W wrote:
>
>> Hi all
>>
>> Now the Qpid Broker for Java and Qpid JMS AMQP 0-x Client are
>> separated [1]/[2], I'd like to propose the final two remaining Qpid
>> components are migrated from SVN to GIT.
>>
>> * Qpid
On 27 March 2017 at 11:31, Keith W wrote:
> Hi all
>
> Now the Qpid Broker for Java and Qpid JMS AMQP 0-x Client are
> separated [1]/[2], I'd like to propose the final two remaining Qpid
> components are migrated from SVN to GIT.
>
> * Qpid Broker for Java
> * Qpid JMS AMQP 0-x Client
>
> This wi
Hi all
Now the Qpid Broker for Java and Qpid JMS AMQP 0-x Client are
separated [1]/[2], I'd like to propose the final two remaining Qpid
components are migrated from SVN to GIT.
* Qpid Broker for Java
* Qpid JMS AMQP 0-x Client
This will give us a consistent, Git based, version control approach
12 matches
Mail list logo