Re: "it doesnt seem unusual to have a Dockerfile set up to pull the existing binary
release archive, verify its sigs, and extract+configure it in an appropriate
location."
Yes, it's certainly not unusual, but my personal view is that it isn't great
practice.
As I said in my earlier reply to I
er area which we might improve on as community. To
have also some nightly RPMs etc.
Regards
Jakub
On Tue, Jun 13, 2017 at 5:36 PM, Fraser Adams
wrote:
Hi Irina,
I think that this is an excellent idea and I totally agree with the
sentiment "Availability of Qpid images will make it easier to
con
Hi Irina,
I think that this is an excellent idea and I totally agree with the
sentiment "Availability of Qpid images will make it easier to
consume/deploy Qpid components and promote Qpid visibility." I think
that in 2017 it's really important for the project to be providing
official maintain
[X] Yes - Adopt semantic versioning for qpid-cpp after its components have been
moved to their own source tree. The first release using semantic versioning
will have the initial version number of 1.(N+1).0, where N comes from the last
stable release of qpid-cpp using the 0.N version format.
Hi Ernie,
It has been a little while since I tinkered around in this space (sorry
I've been so Qpid quiet recently BTW, I'm working on another project
that's turned into a bit of a time-sink), but the fact that you are
using websockify rings a few alarm bells with me.
Not that there's anythin
On 17/03/15 10:22, Gordon Sim wrote:
On 03/16/2015 06:12 PM, Keith W wrote:
Hello all,
I believe we reached agreement on the following thread [1] that we would
reorganise trunk (to support independent component releases) once the
0.32
was branched.
Justin previously published a source tree
[
https://issues.apache.org/jira/browse/QPID-6438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14355476#comment-14355476
]
Fraser Adams commented on QPID-6438:
RE: "In many REST best practi
OK too except in data.js 'format' and
message.js 'encode' too.
Nice work!
- Fraser Adams
On Feb. 1, 2015, 11:34 a.m., Rafael Schloming wrote:
>
> ---
> This is an automatically gene
Hi Dominic,
I guess that my main concern is the potential for confusion :-)
I'm actually a bit curious/confused - when I took a peek at the patch
there wasn't much in there and looked mostly makefile related, I was
aware that swig 3.x had node/JavaScript support but how exactly are the
binding
On 15/12/14 16:53, Alan Conway wrote:
I took out the GNU extension trick (didn't even know it was a GNU
extension) so it should be more portable now. I guess the javascript
cross-compiler uses a non-gnu CPP.
Yeah, emscripten is actually an LLVM backend, so actually under the hood
uses Clang as
On 28/11/14 16:26, Gordon Sim wrote:
On 11/28/2014 01:42 PM, r...@apache.org wrote:
Repository: qpid-proton
Updated Branches:
refs/heads/master df970a8fd -> db437cf4a
removed alan's extraneous colon
Don't you need a medical license to do that?
--
[
https://issues.apache.org/jira/browse/QPID-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams closed QPID-6244.
--
Resolution: Not a Problem
I'm afraid that I jumped the gun, it's not an issue it was
[
https://issues.apache.org/jira/browse/QPID-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14223260#comment-14223260
]
Fraser Adams commented on QPID-6244:
In that case it's probably my bad then.
Fraser Adams created QPID-6244:
--
Summary: /cpp/src/tests/sasl_test_setup.sh needs execute
permission
Key: QPID-6244
URL: https://issues.apache.org/jira/browse/QPID-6244
Project: Qpid
Issue
[
https://issues.apache.org/jira/browse/QPID-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14116328#comment-14116328
]
Fraser Adams commented on QPID-6060:
I think that a binding key containing a
[
https://issues.apache.org/jira/browse/QPID-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams closed QPID-6059.
--
> Java QMF2 Agent code made some now invalid assumptions about repl
[
https://issues.apache.org/jira/browse/QPID-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams resolved QPID-6059.
Resolution: Fixed
> Java QMF2 Agent code made some now invalid assumptions about repl
Fraser Adams created QPID-6059:
--
Summary: Java QMF2 Agent code made some now invalid assumptions
about replyTo
Key: QPID-6059
URL: https://issues.apache.org/jira/browse/QPID-6059
Project: Qpid
[
https://issues.apache.org/jira/browse/QPID-6041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14109191#comment-14109191
]
Fraser Adams commented on QPID-6041:
Looking a bit further at this it looks like
[
https://issues.apache.org/jira/browse/QPID-6041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams updated QPID-6041:
---
Description:
The exception message produced by the aclReloadFile QMF Method is a bit
unhelpful, for
[
https://issues.apache.org/jira/browse/QPID-6041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams updated QPID-6041:
---
Component/s: (was: C++ Broker)
> reloadAcl QMF Method exception message is a bit confus
Fraser Adams created QPID-6041:
--
Summary: reloadAcl QMF Method exception message is a bit
confusing/unhelpful
Key: QPID-6041
URL: https://issues.apache.org/jira/browse/QPID-6041
Project: Qpid
[
https://issues.apache.org/jira/browse/QPID-6025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams closed QPID-6025.
--
> Java port of QpidConfig give NPE when listing queue/exchan
[
https://issues.apache.org/jira/browse/QPID-6025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams resolved QPID-6025.
Resolution: Fixed
> Java port of QpidConfig give NPE when listing queue/exchan
Fraser Adams created QPID-6025:
--
Summary: Java port of QpidConfig give NPE when listing
queue/exchanges
Key: QPID-6025
URL: https://issues.apache.org/jira/browse/QPID-6025
Project: Qpid
Issue
[
https://issues.apache.org/jira/browse/QPID-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams closed QPID-6024.
--
> Changes tp Java Broker Model affected QMF2 plu
[
https://issues.apache.org/jira/browse/QPID-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams resolved QPID-6024.
Resolution: Fixed
> Changes tp Java Broker Model affected QMF2 plu
Fraser Adams created QPID-6024:
--
Summary: Changes tp Java Broker Model affected QMF2 plugin
Key: QPID-6024
URL: https://issues.apache.org/jira/browse/QPID-6024
Project: Qpid
Issue Type: Bug
[
https://issues.apache.org/jira/browse/QPID-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14067446#comment-14067446
]
Fraser Adams commented on QPID-3422:
I've had this conversation with Rob G
Welcome indeed Andrew!!
Frase
On 03/06/14 20:31, Gordon Sim wrote:
The Qpid PMC have voted to grant commit rights to Andrew MacBean in
recognition of his long-standing contributions to the project.
Welcome Andrew, and thank you for your continued support for Apache Qpid!
--Gordon.
---
Awesome!!
Though it would have been *even* better if this thread and the earlier
100,000 addresses thread had appeared on the users list to publicise it
even more :-)
Frase
On 03/05/14 00:59, Michael Goulish wrote:
I just had a successful test of the dispatch router
handling one million un
I'd say that the best approach would be to allow the listen backlog to be
configurable, dispatch is ultimately a piece of infrastructure so probably
shouldn't be making too many assumptions about client behaviour. I've been
bitten by this sort of thing with other server technologies - CORBA and
Hi Michael, I'm away from my PC so I can't take a look in the code, but at face
value I'd say that using pauses seems like a bad idea, users might have no
control of how connections are started. I'n many organisations brokers and
routers would be 'owned' by different parts of the organisation th
Looking at your stack trace I can see a
> Caused by: java.net.BindException: Address already in use
>at java.net.PlainSocketImpl.socketBind(Native Method)
So my guess is that you've either got something listening on port 5672, or more
likely on 8080 which I think the Java Broker uses by defa
going to the wrong
place. This change cannot go to trunk until the legacystore is deprecated
and then removed. Even then, it may be worth keeping the options around in
a less visible fashion to support deployments with the older store.
On Fri, Apr 11, 2014 at 1:29 PM, Fraser Adams <
fraser.ad
OK so I'm going to bite.
is legacystore as its name suggests going to be deprecated? At the
moment there seems to be two stores, neither of which seem to have any
documentation that a user might reasonably use in order to figure out
how on earth to get persistence to work with qpidd. Well that
[
https://issues.apache.org/jira/browse/QPID-5659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13958203#comment-13958203
]
Fraser Adams commented on QPID-5659:
Hi Andrew, have you also seen QPID-5609 raise
[
https://issues.apache.org/jira/browse/QPID-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams resolved QPID-5604.
Resolution: Fixed
> Bash scripts doesn't suppor
[
https://issues.apache.org/jira/browse/QPID-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams resolved QPID-5614.
Resolution: Fixed
> Fix Java Broker QMF2 Plugin problems caused by refactoring in QPID-5
[
https://issues.apache.org/jira/browse/QPID-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924924#comment-13924924
]
Fraser Adams commented on QPID-5611:
Yeah I am "bringing up your connection
[
https://issues.apache.org/jira/browse/QPID-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924891#comment-13924891
]
Fraser Adams edited comment on QPID-5611 at 3/8/14 3:0
[
https://issues.apache.org/jira/browse/QPID-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924891#comment-13924891
]
Fraser Adams commented on QPID-5611:
For info I've just updated to r15
[
https://issues.apache.org/jira/browse/QPID-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924863#comment-13924863
]
Fraser Adams commented on QPID-5611:
It mostly seems back to how it was now, th
[
https://issues.apache.org/jira/browse/QPID-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924833#comment-13924833
]
Fraser Adams commented on QPID-5611:
svn update
At revision 1575535.
> [Java
[
https://issues.apache.org/jira/browse/QPID-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924825#comment-13924825
]
Fraser Adams commented on QPID-5611:
Don't know if it's related to th
Fraser Adams created QPID-5614:
--
Summary: Fix Java Broker QMF2 Plugin problems caused by
refactoring in QPID-5578
Key: QPID-5614
URL: https://issues.apache.org/jira/browse/QPID-5614
Project: Qpid
Fraser Adams created QPID-5590:
--
Summary: It is trivially easy to fatally crash qpidd using a dodgy
exchange type in a TopicPolicy
Key: QPID-5590
URL: https://issues.apache.org/jira/browse/QPID-5590
Fraser Adams created QPID-5553:
--
Summary: cpp build fails on ha_test_max_queues.cpp
Key: QPID-5553
URL: https://issues.apache.org/jira/browse/QPID-5553
Project: Qpid
Issue Type: Bug
Fraser Adams created QPID-5493:
--
Summary: qpidd persistence needs documentation
Key: QPID-5493
URL: https://issues.apache.org/jira/browse/QPID-5493
Project: Qpid
Issue Type: Improvement
Fraser Adams created QPID-5492:
--
Summary: Make install currently installs multiple store modules
making qpidd fail by default
Key: QPID-5492
URL: https://issues.apache.org/jira/browse/QPID-5492
Project
[
https://issues.apache.org/jira/browse/QPID-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams closed QPID-5470.
--
> Improve QMF README documentation and update JavaDocs to reflect new location
> of QMF2 AP
[
https://issues.apache.org/jira/browse/QPID-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams resolved QPID-5470.
Resolution: Fixed
> Improve QMF README documentation and update JavaDocs to reflect new locat
Fraser Adams created QPID-5470:
--
Summary: Improve QMF README documentation and update JavaDocs to
reflect new location of QMF2 API docs
Key: QPID-5470
URL: https://issues.apache.org/jira/browse/QPID-5470
[
https://issues.apache.org/jira/browse/QPID-5332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13820341#comment-13820341
]
Fraser Adams commented on QPID-5332:
Re "As we found in IRC, the Java Qpid b
+1 from me on that train of thought.
I think that we should aspire wherever possible to maximise cohesion,
there has been a lot of divergence for various reasons but I think with
the increased moves to modularisation it's time to draw a line in the
sand and try to bring things together again.
On 07/11/13 18:22, Justin Ross wrote:
On Wed, Nov 6, 2013 at 2:52 PM, Fraser Adams
wrote:
Actually that reminds me. In a bunch of places in my JavaDoc I had
references to the QMF2 API (that never was :-)) which is what the Java API
actually implements:
https://cwiki.apache.org/qpid/qmfv2-api
On 06/11/13 23:29, Andrew Stitcher wrote:
On Wed, 2013-11-06 at 19:52 +, Fraser Adams wrote:
"The java broker no longer uses this. However I'm not sure whether the
Java based QMF API does?" no, none of the Java (or GUI stuff)
*explicitly* uses the management schema, but I
"I think its a bad idea to have duplicated files":
+1 agree with Gordon here, the source tree is already confusing enough
(I'd be keen to see a lot more of the "modularisation" that has begun
with proton/jms/dispatch etc. it'd be good to start to be able to put
together systems from pluggable c
[
https://issues.apache.org/jira/browse/QPID-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams resolved QPID-5259.
Resolution: Fixed
> cmake legacy store and linear store messages aren't very he
Fraser Adams created QPID-5259:
--
Summary: cmake legacy store and linear store messages aren't very
helpful if dependencies are missing.
Key: QPID-5259
URL: https://issues.apache.org/jira/browse/QPID
On 07/10/13 14:30, Alan Conway wrote:
Hi Fraser,
It's always a bit of a juggling act isn't it?
Yeah isn't it just :-)
My thinking was that since the feature is now gone on the broker, it
is confusing to keep it in the tools. However you have a point about
new tools against old brokers.
Yeah
;ve got no real issues myself, but thought it was worth mentioning it
as a bit of food for thought in case someone has any bright ideas how to
manage this sort of scenario (it's bound to crop up again).
Cheers,
Frase
On 01/10/13 22:43, Alan Conway wrote:
On October 1st, 2013, 6:47 p.m
> On Oct. 1, 2013, 6:47 p.m., Fraser Adams wrote:
> > Ship It!
Hi Alan, I've been tied up for ages on a bunch of other things so I probably
won't get a change to "fire it up" until the weekend to actually kick it,
however I have had a look through the diffs an
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14361/#review26572
---
Ship it!
Ship It!
- Fraser Adams
On Oct. 1, 2013, 2:04 p.m
That's fantastic news indeed!
Welcome Pavel, many congratulations.
Frase
On 04/09/13 16:17, Gordon Sim wrote:
The Qpid PMC have voted to grant commit rights to Pavel Moravec in
recognition of his long standing contributions to the project.
Welcome Pavel, and thank you for your continued supp
[
https://issues.apache.org/jira/browse/QPID-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748666#comment-13748666
]
Fraser Adams commented on QPID-5093:
Updated on trunk on revision r151
[
https://issues.apache.org/jira/browse/QPID-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams updated QPID-5093:
---
Attachment: licence.patch
> Adding ASF licence note to a bunch of html/css/js files that w
Fraser Adams created QPID-5093:
--
Summary: Adding ASF licence note to a bunch of html/css/js files
that were missing it
Key: QPID-5093
URL: https://issues.apache.org/jira/browse/QPID-5093
Project: Qpid
2. Keep the dev list but only for traffic not relevant to users of the code
But absolutely with the emphasis on "only for traffic not relevant to
users of the code". Personally I think it's worth erring on the side of
starting off threads on the user list.
I quite like the idea of an experime
FWIW I totally agree with Gordon here.
If you subscribe so the thinking of Gregorio Robles paper
http://www.opensourcejahrbuch.de/download/jb2004/chapter_03/III-3-Robles.pdf
among other things he says:
"
Users should be treated as co-developers
The users are treated like co-developers and
t's nice to bundle it with the jira it was originally intended for.
It makes tracking down a coherent set of changes easier.
Justin
On Fri, Jul 19, 2013 at 9:35 AM, Fraser Adams
wrote:
Thanks guys, I had indeed forgotten to add Session.java to source control
*shame* :-[
I've just don
kes tracking down a coherent set of changes easier.
Justin
On Fri, Jul 19, 2013 at 9:35 AM, Fraser Adams
wrote:
Thanks guys, I had indeed forgotten to add Session.java to source control
*shame* :-[
I've just done an svn add for Session.java and commited, *hopefully* you
can
see it on trunk
[
https://issues.apache.org/jira/browse/QPID-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams resolved QPID-5008.
Resolution: Fixed
Committed necessary fixes to 0.24 branch under r1504940
>
9/07/13 16:53, Justin Ross wrote:
Okay, if that's the case, that's fine by me. Thanks for getting me up
to speed on the situation. /me goes to approve it.
On Fri, Jul 19, 2013 at 11:49 AM, Fraser Adams
wrote:
heh heh heh
So that interface has been a source of some comedy between my
Fraser Adams created QPID-5008:
--
Summary: Add Session.java class to 0.24 branch and merge QPID-5005
fix from trunk to 0.24
Key: QPID-5008
URL: https://issues.apache.org/jira/browse/QPID-5008
Project
lds fine for me now...
-- Rob
On 19 July 2013 15:35, Fraser Adams wrote:
Thanks guys, I had indeed forgotten to add Session.java to source control
*shame* :-[
I've just done an svn add for Session.java and commited, *hopefully* you
can see it on trunk now? does ant all in /tools/src/jav
tive guide.
Robbie
On 19 July 2013 14:02, Fraser Adams wrote:
Hi Rob,
Just to check - are you saying that you can't see the file Session.java
in:
/tools/src/java/src/qpid-**broker-plugins-management-**
qmf2/java/org/apache/qpid/**server/qmf2/agentdata
on trunk?
Could you check and let me k
.24. Have you tried checking out a completely clean
version of trunk - it may be something messed up in your local checkout
which is causing it to work for you there.
-- Rob
On 19 July 2013 14:35, Fraser Adams wrote:
Hey again Justin,
With respect to the other two errors I noticed on 0.24 but not on
anch.
Am I losing my marbles?
Frase
On 19/07/13 13:14, Fraser Adams wrote:
Hi Justin,
I just noticed today that the Java Broker Plugin API has changed to
need overridden getType() method in instances of PluginFactory.
I raised QPID-5005 and fixed this on trunk with:
—
qpid/tools/sr
Hi Justin,
I just noticed today that the Java Broker Plugin API has changed to need
overridden getType() method in instances of PluginFactory.
I raised QPID-5005 and fixed this on trunk with:
—
qpid/tools/src/java/src/qpid-broker-plugins-management-qmf2/java/org/apache/qpid/server/qmf2/QmfMan
[
https://issues.apache.org/jira/browse/QPID-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams resolved QPID-5005.
Resolution: Fixed
Fixed on trunk
> Java Broker Plugin API has changed to n
Fraser Adams created QPID-5005:
--
Summary: Java Broker Plugin API has changed to need overridden
getType() method in instances of PluginFactory
Key: QPID-5005
URL: https://issues.apache.org/jira/browse/QPID-5005
Ahh, sorry I missed that - cheers guys.
F.
On 13/07/13 10:22, Robbie Gemmell wrote:
Ken's email went to the user list as well (via CC).
Robbie
On 13 July 2013 10:13, Fraser Adams wrote:
Hey Ken,
One key point is that I think it's important to get this message out on
the user li
Hey Ken,
One key point is that I think it's important to get this message out on
the user list as well as the dev list, indeed I suspect it's more
important. I know that you've mentioned to Justin for the announcement
mail, but this sort of thing is good to shout about from a few different
dir
[
https://issues.apache.org/jira/browse/QPID-4969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13698035#comment-13698035
]
Fraser Adams commented on QPID-4969:
Thanks guys, I've just rebuilt off
cidental.
In your example Address String I expect that if I were to stand up
multiple consumers using that Address they'd each receive a copy of any
given message matching the said headers as opposed to receiving some of
the messages depending on how many consumer instances were consuming.
[
https://issues.apache.org/jira/browse/QPID-4969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696128#comment-13696128
]
Fraser Adams commented on QPID-4969:
whoah there chuck. I think in principal thi
On 27/06/13 18:11, Andrew Stitcher wrote:
I may have been exaggerating for effect - I'll turn my trolling setting
down ;-) I'm not trying to offend anyone just to be a little light
hearted (I did say "somewhat" which I realise now can mean subtly
different things to different people).
No worries
On 27/06/13 06:10, Andrew Stitcher wrote:
Last week we has a small (number of people) but aomewhat heated
discussion about removing some pieces of deprecated and obsolete QMFv1
code; and removing the qpid::client header files so that no one can use
this API outside the qpid build itself.
I wouldn
[X] * When 0.25 opens after the 0.24 beta branch remove the C++
qpid autotools build infrastructure in favour of the cmake tools.
* A heads up message to the user mailing list.
* Add a release note to 0.24 to say it is the last release that will
contain an autotools build.
I agree with this middle ground (whilst of course mourning the tragedy
of poor qmfv2 prototype, alas I feel he is too unloved and
his memory must remain in our hearts as we journey towards AMQP 1.0
Management)
Frase
On 20/06/13 21:12, Kenneth Giusti wrote:
---
This looks good, but it seems to go way beyond the original "tidy up of
QMF" stuff that was talked about the other day and covers the execution
of qpid::client too does it not?
Now I won't personally shed any tears for qpid::client however I *know*
that there are plenty of people still using i
On 18/06/13 23:30, Ken Giusti wrote:
Folks,
There's some old QMF-related code in our repo that appears to be quite dead.
If said code is in fact "pushing up the daisies", I'd like to see removed prior
to the 0.24 release.
First, there's stuff that I'm almost certain is stone cold dead. AFAIK
[X] Yes, replace the existing site with the proposed site
[ ] No, the proposed site isn't ready
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
ce.
Regards,
Frase
On 12/06/13 19:09, Gordon Sim wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/11840/
---
Review request for qpid, Ted R
On 06/05/13 12:11, Gordon Sim wrote:
For my part, I am in favour of removing QMFv1 support, if necessary
providing some sort of adapter or plugin to deal with any use cases
for which this might prove problematic. I think QMFv2 is now firmly
established as the current management mechanism for
[
https://issues.apache.org/jira/browse/QPID-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams resolved QPID-4783.
Resolution: Fixed
Added change in r1476792
> Improve Connection statistics in J
[
https://issues.apache.org/jira/browse/QPID-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams closed QPID-4783.
--
> Improve Connection statistics in Java Broker QmfManagementAg
Fraser Adams created QPID-4783:
--
Summary: Improve Connection statistics in Java Broker
QmfManagementAgent
Key: QPID-4783
URL: https://issues.apache.org/jira/browse/QPID-4783
Project: Qpid
On 26/04/13 17:18, Ken Giusti wrote:
Hey Bill,
I first started to implement the additional objectUpdate callback as originally
proposed. Very easy to do. But that additional api required other tools to be
updated - and additional documentation changes, etc.
Hmm I remain a little baffled her
1 - 100 of 175 matches
Mail list logo
