Re: Review Request: Get cmake package working.

[Andrew Stitcher]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/10348/#review18828
---


I don't think make package is worth getting working if it will complicate the 
build files at all. Apache releases are purely source and we leave packaging to 
downstream packagers, so (with the exception of the windows packages, which 
already work as far as I know) this wouldn't be valuable to anyone.

However it is important that "make package_source" under cmake works as well as 
"make dist" under autotools. This is nearly there in my testing, but needs some 
work to either pull in the xml spec files (in the correct place) or to 
pre-generate the generated files.

- Andrew Stitcher


On April 8, 2013, 9:53 p.m., Alan Conway wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/10348/
> ---
> 
> (Updated April 8, 2013, 9:53 p.m.)
> 
> 
> Review request for qpid, Andrew Stitcher and Steve Huston.
> 
> 
> Description
> ---
> 
> Get cmake package working.
> 
> "make package" currently is broken, it gives lots of errors like:
> 
> CMake Error at 
> /home/aconway/qpid/build/bindings/qpid/python/cmake_install.cmake:70 (FILE):
>   file INSTALL cannot copy file
>   "/home/aconway/qpid/build/bindings/qpid/python/_cqpid_python.so" to
>   "/usr/local/lib64/python2.7/site-packages/_cqpid.so".
> Call Stack (most recent call first):
>   /home/aconway/qpid/build/bindings/cmake_install.cmake:37 (INCLUDE)
>   /home/aconway/qpid/build/cmake_install.cmake:63 (INCLUDE)
> 
> Look at the comments in the diff, they explain what I've figured out so far.
> 
> 
> Diffs
> -
> 
>   /trunk/qpid/cpp/BuildInstallSettings.cmake 1465590 
>   /trunk/qpid/cpp/bindings/CMakeLists.txt 1465590 
> 
> Diff: https://reviews.apache.org/r/10348/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Alan Conway
> 
>

[jira] [Comment Edited] (QPID-4730) Bug for qpid perl binding. The object is overwritten by the return value when a function return an integer.

[Hao Chang Yu (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-4730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626071#comment-13626071
 ] 

Hao Chang Yu edited comment on QPID-4730 at 4/9/13 1:24 AM:


This can be fixed in 'swig_perl_typemaps.i' file. Diff is provided below.

@@ -183,7 +183,9 @@
 }
 
 %typemap (out) uint16_t, uint32_t, uint64_t {
-sv_setuv($result, (UV)$1);
+SV *tmp = sv_newmortal();
+sv_setuv(tmp, (UV)$1);
+$result = tmp;
 argvi++;
 }
 
@@ -197,7 +199,9 @@
 }
 
 %typemap (out) int32_t, int64_t {
-sv_setiv($result, (IV)$1);
+SV *tmp = sv_newmortal();
+sv_setiv(tmp, (IV)$1);
+$result = tmp;
 argvi++;
 }

  was (Author: hyu):
This can be fixed in 'swig_perl_typemaps.i' file. Diff is provided below.

%typemap (out) uint16_t, uint32_t, uint64_t {
-sv_setuv($result, (UV)$1);
+SV *tmp = sv_newmortal();
+sv_setuv(tmp, (UV)$1);
+$result = tmp;
 argvi++;
 }
 
@@ -197,7 +199,9 @@
 }
 
 %typemap (out) int32_t, int64_t {
-sv_setiv($result, (IV)$1);
+SV *tmp = sv_newmortal();
+sv_setiv(tmp, (IV)$1);
+$result = tmp;
 argvi++;
 }
  
> Bug for qpid perl binding. The object is overwritten by the return value when 
> a function return an integer.
> ---
>
> Key: QPID-4730
> URL: https://issues.apache.org/jira/browse/QPID-4730
> Project: Qpid
>  Issue Type: Bug
>  Components: Perl Client
>Affects Versions: 0.18
>Reporter: Hao Chang Yu
> Fix For: 0.18
>
>
> As per subject. Please read the example below for more details.
> print("receiver: " . $receiver . "\n");
> print("getCapacity; " . $receiver->getCapacity() . "\n");
> print("receiver: " . $receiver . "\n");
> print("getAvailable: " . $receiver->getAvailable() . "\n");
> receiver: cqpid::Receiver=HASH(0xc0fbb8)
> getCapacity: 0
> receiver: 0
> 0: Operation now in progress: Can't call method "getAvailable" without a 
> package or object reference at ./consumer.pl line 109.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-4730) Bug for qpid perl binding. The object is overwritten by the return value when a function return an integer.

[Hao Chang Yu (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-4730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626071#comment-13626071
 ] 

Hao Chang Yu commented on QPID-4730:


This can be fixed in 'swig_perl_typemaps.i' file. Diff is provided below.

%typemap (out) uint16_t, uint32_t, uint64_t {
-sv_setuv($result, (UV)$1);
+SV *tmp = sv_newmortal();
+sv_setuv(tmp, (UV)$1);
+$result = tmp;
 argvi++;
 }
 
@@ -197,7 +199,9 @@
 }
 
 %typemap (out) int32_t, int64_t {
-sv_setiv($result, (IV)$1);
+SV *tmp = sv_newmortal();
+sv_setiv(tmp, (IV)$1);
+$result = tmp;
 argvi++;
 }

> Bug for qpid perl binding. The object is overwritten by the return value when 
> a function return an integer.
> ---
>
> Key: QPID-4730
> URL: https://issues.apache.org/jira/browse/QPID-4730
> Project: Qpid
>  Issue Type: Bug
>  Components: Perl Client
>Affects Versions: 0.18
>Reporter: Hao Chang Yu
> Fix For: 0.18
>
>
> As per subject. Please read the example below for more details.
> print("receiver: " . $receiver . "\n");
> print("getCapacity; " . $receiver->getCapacity() . "\n");
> print("receiver: " . $receiver . "\n");
> print("getAvailable: " . $receiver->getAvailable() . "\n");
> receiver: cqpid::Receiver=HASH(0xc0fbb8)
> getCapacity: 0
> receiver: 0
> 0: Operation now in progress: Can't call method "getAvailable" without a 
> package or object reference at ./consumer.pl line 109.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Comment Edited] (QPID-4730) Bug for qpid perl binding. The object is overwritten by the return value when a function return an integer.

[Hao Chang Yu (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-4730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626071#comment-13626071
 ] 

Hao Chang Yu edited comment on QPID-4730 at 4/9/13 1:22 AM:


This can be fixed in 'swig_perl_typemaps.i' file. Diff is provided below.

%typemap (out) uint16_t, uint32_t, uint64_t {
-sv_setuv($result, (UV)$1);
+SV *tmp = sv_newmortal();
+sv_setuv(tmp, (UV)$1);
+$result = tmp;
 argvi++;
 }
 
@@ -197,7 +199,9 @@
 }
 
 %typemap (out) int32_t, int64_t {
-sv_setiv($result, (IV)$1);
+SV *tmp = sv_newmortal();
+sv_setiv(tmp, (IV)$1);
+$result = tmp;
 argvi++;
 }

  was (Author: hyu):
This can be fixed in 'swig_perl_typemaps.i' file. Diff is provided below.

%typemap (out) uint16_t, uint32_t, uint64_t {
-sv_setuv($result, (UV)$1);
+SV *tmp = sv_newmortal();
+sv_setuv(tmp, (UV)$1);
+$result = tmp;
 argvi++;
 }
 
@@ -197,7 +199,9 @@
 }
 
 %typemap (out) int32_t, int64_t {
-sv_setiv($result, (IV)$1);
+SV *tmp = sv_newmortal();
+sv_setiv(tmp, (IV)$1);
+$result = tmp;
 argvi++;
 }
  
> Bug for qpid perl binding. The object is overwritten by the return value when 
> a function return an integer.
> ---
>
> Key: QPID-4730
> URL: https://issues.apache.org/jira/browse/QPID-4730
> Project: Qpid
>  Issue Type: Bug
>  Components: Perl Client
>Affects Versions: 0.18
>Reporter: Hao Chang Yu
> Fix For: 0.18
>
>
> As per subject. Please read the example below for more details.
> print("receiver: " . $receiver . "\n");
> print("getCapacity; " . $receiver->getCapacity() . "\n");
> print("receiver: " . $receiver . "\n");
> print("getAvailable: " . $receiver->getAvailable() . "\n");
> receiver: cqpid::Receiver=HASH(0xc0fbb8)
> getCapacity: 0
> receiver: 0
> 0: Operation now in progress: Can't call method "getAvailable" without a 
> package or object reference at ./consumer.pl line 109.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPID-4730) Bug for qpid perl binding. The object is overwritten by the return value when a function return an integer.

[Hao Chang Yu (JIRA)]

Hao Chang Yu created QPID-4730:
--

 Summary: Bug for qpid perl binding. The object is overwritten by 
the return value when a function return an integer.
 Key: QPID-4730
 URL: https://issues.apache.org/jira/browse/QPID-4730
 Project: Qpid
  Issue Type: Bug
  Components: Perl Client
Affects Versions: 0.18
Reporter: Hao Chang Yu
 Fix For: 0.18


As per subject. Please read the example below for more details.


print("receiver: " . $receiver . "\n");
print("getCapacity; " . $receiver->getCapacity() . "\n");
print("receiver: " . $receiver . "\n");
print("getAvailable: " . $receiver->getAvailable() . "\n");


receiver: cqpid::Receiver=HASH(0xc0fbb8)
getCapacity: 0
receiver: 0
0: Operation now in progress: Can't call method "getAvailable" without a 
package or object reference at ./consumer.pl line 109.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Review Request: Get cmake package working.

[Alan Conway]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/10348/
---

Review request for qpid, Andrew Stitcher and Steve Huston.


Description
---

Get cmake package working.

"make package" currently is broken, it gives lots of errors like:

CMake Error at 
/home/aconway/qpid/build/bindings/qpid/python/cmake_install.cmake:70 (FILE):
  file INSTALL cannot copy file
  "/home/aconway/qpid/build/bindings/qpid/python/_cqpid_python.so" to
  "/usr/local/lib64/python2.7/site-packages/_cqpid.so".
Call Stack (most recent call first):
  /home/aconway/qpid/build/bindings/cmake_install.cmake:37 (INCLUDE)
  /home/aconway/qpid/build/cmake_install.cmake:63 (INCLUDE)

Look at the comments in the diff, they explain what I've figured out so far.


Diffs
-

  /trunk/qpid/cpp/BuildInstallSettings.cmake 1465590 
  /trunk/qpid/cpp/bindings/CMakeLists.txt 1465590 

Diff: https://reviews.apache.org/r/10348/diff/


Testing
---


Thanks,

Alan Conway

Re: 0.22 inclusion requests

[Justin Ross]

On Mon, Apr 8, 2013 at 4:09 PM, Rob Godfrey  wrote:
> The other changes (which I made) I can take or leave... the GUI change is
> obviously trivial, but clearly not a blocker.  The SASL for AMQP 1.0 would
> be nice to have in terms of improving 1.0 support, but again clearly not a
> blocker.
>
> As an aside, do we have a document somewhere describing our policy for what
> is or is not acceptable in each RC version?

No, there isn't, and that's my fault.  I'll add this to the standard
release page content, but to summarize my thoughts here:

 - Trunk open to alpha - Go wild, cowboy
 - Alpha to beta - Major features, improvements, or refactorings need
discussion before they can go in
 - Beta to RC1 - This should be bug fixes only; I tend to be more
lenient in this phase as long as there are other positive indications
(isolation, minimal diff)
 - RC1 to GA - Bug fixes only, and they really ought to be important
defects (build failures, regressions, vulnerabilities)

Justin

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Re: 0.22 inclusion requests

[Justin Ross]

On Mon, Apr 8, 2013 at 3:36 PM, Robbie Gemmell  wrote:
> On 8 April 2013 18:17, Justin Ross  wrote:
>
>> These are all improvements, even the first one.  No doubt it's an
>> important security enhancement, but it's not a regression,
>
>
> Some might argue there is a regression or sorts as you couldnt previously
> do things like change the SSL, authentication, ACL, etc settings that you
> can now.

Yes, I agree, it is a regression in that sense.

>> and it
>> seems reasonable to release note that you should enable acls if you
>> wish to use the web console.  I'd be more inclined to accept it if the
>> change were small, but it isn't.
>>
> For what its worth, the changes really are quite 'small'. Much of the diff
> is simply moving code that would have otherwise had to be needlesly
> duplicated into a utility class and so isn't actually all that great of a
> change.

Okay.  If you think the risk to stability and the schedule is minimal,
then I defer to you.

> It's hard for me to reconcile these changes with the goals for a
>> second release candidate.  I hope you can tell that I ordinarily try
>> to be very flexible, but this doesn't make sense.
>>
>> Honest question: if you have a compelling reason to introduce these
>> changes into a stable stream before 0.24, should we have a distinct
>> branch for that purpose?
>
> I'm a little unclear on what you mean here, is it a '0.22.1' release or
> simply putting the changes on a branch before introducing them to 0.22?

Sorry, I meant the former, 0.22.1.  I mention it because it's a way to
deliver something out of sync with the current cadence, if that's what
you need.

Justin

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Re: 0.22 inclusion requests

[Rob Godfrey]

So - personally I'd not be happy releasing the Java Broker without the
first change (or some other remediation for the defect) in.  I'd consider
the defect a blocker for the release given the sort of changes that can now
be made through the management GUI.

The other changes (which I made) I can take or leave... the GUI change is
obviously trivial, but clearly not a blocker.  The SASL for AMQP 1.0 would
be nice to have in terms of improving 1.0 support, but again clearly not a
blocker.

As an aside, do we have a document somewhere describing our policy for what
is or is not acceptable in each RC version?

-- Rob



On 8 April 2013 19:17, Justin Ross  wrote:

> These are all improvements, even the first one.  No doubt it's an
> important security enhancement, but it's not a regression, and it
> seems reasonable to release note that you should enable acls if you
> wish to use the web console.  I'd be more inclined to accept it if the
> change were small, but it isn't.
>
> It's hard for me to reconcile these changes with the goals for a
> second release candidate.  I hope you can tell that I ordinarily try
> to be very flexible, but this doesn't make sense.
>
> Honest question: if you have a compelling reason to introduce these
> changes into a stable stream before 0.24, should we have a distinct
> branch for that purpose?
>
> Justin
>
> On Mon, Apr 8, 2013 at 9:45 AM, Oleksandr Rudyy  wrote:
> > Hi Justin,
> >
> > Could you please approve the inclusion of the following into 0.22:
> >
> > JIRA: QPID-4705
> > Revision: http://svn.apache.org/r1465590
> > Description:
> > It fixes the potential security hole with an access to the web management
> > console and rest interfaces. Without the fix if ACL is not configured (by
> > default no ACL is configured) it is possible to access the web management
> > console anonymously and do any configuration changes including password
> > change,  configure authentication providers etc. The commit in revision
> > r1465590  stops this from happening by
> > adding functionality to check whether the request is authenticated or
> > authorised and send the redirect to the login page (for web management
> > console) or send the error status codes (401,403) for rest requests. The
> > changes are isolated to the http management plugin and do not affect the
> > broker core functionality.
> >
> >
> > JIRA: QPID-4725 
> > Revision: http://svn.apache.org/r1465457
> > Description: Enhances the web management console to display a principal
> > associated with a connection on connection and virtualhost tabs. The
> > changes are isolated to web console UI and of low risk.
> >
> >
> > JIRA: QPID-4726 
> > Revision: http://svn.apache.org/r1465459
> > Description: Improves SASL support for AMQP 1.0 client. The changes
> affect
> > only 1.0 AMQP functionality and of low risk.
> >
> > Kind Regards,
> > Alex
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
> For additional commands, e-mail: dev-h...@qpid.apache.org
>
>

Re: 0.22 inclusion requests

[Robbie Gemmell]

On 8 April 2013 18:17, Justin Ross  wrote:

> These are all improvements, even the first one.  No doubt it's an
> important security enhancement, but it's not a regression,


Some might argue there is a regression or sorts as you couldnt previously
do things like change the SSL, authentication, ACL, etc settings that you
can now.


> and it
> seems reasonable to release note that you should enable acls if you
> wish to use the web console.  I'd be more inclined to accept it if the
> change were small, but it isn't.
>
>
For what its worth, the changes really are quite 'small'. Much of the diff
is simply moving code that would have otherwise had to be needlesly
duplicated into a utility class and so isn't actually all that great of a
change.

It's hard for me to reconcile these changes with the goals for a
> second release candidate.  I hope you can tell that I ordinarily try
> to be very flexible, but this doesn't make sense.
>
> Honest question: if you have a compelling reason to introduce these
> changes into a stable stream before 0.24, should we have a distinct
> branch for that purpose?
>


I'm a little unclear on what you mean here, is it a '0.22.1' release or
simply putting the changes on a branch before introducing them to 0.22?

If the latter, its worth mentioning these changes compose basically the
entire set of difference in the Java tree between trunk and 0.22 RC1
currently, so that has already occured in a way.


>
> Justin
>
> On Mon, Apr 8, 2013 at 9:45 AM, Oleksandr Rudyy  wrote:
> > Hi Justin,
> >
> > Could you please approve the inclusion of the following into 0.22:
> >
> > JIRA: QPID-4705
> > Revision: http://svn.apache.org/r1465590
> > Description:
> > It fixes the potential security hole with an access to the web management
> > console and rest interfaces. Without the fix if ACL is not configured (by
> > default no ACL is configured) it is possible to access the web management
> > console anonymously and do any configuration changes including password
> > change,  configure authentication providers etc. The commit in revision
> > r1465590  stops this from happening by
> > adding functionality to check whether the request is authenticated or
> > authorised and send the redirect to the login page (for web management
> > console) or send the error status codes (401,403) for rest requests. The
> > changes are isolated to the http management plugin and do not affect the
> > broker core functionality.
> >
> >
> > JIRA: QPID-4725 
> > Revision: http://svn.apache.org/r1465457
> > Description: Enhances the web management console to display a principal
> > associated with a connection on connection and virtualhost tabs. The
> > changes are isolated to web console UI and of low risk.
> >
> >
> > JIRA: QPID-4726 
> > Revision: http://svn.apache.org/r1465459
> > Description: Improves SASL support for AMQP 1.0 client. The changes
> affect
> > only 1.0 AMQP functionality and of low risk.
> >
> > Kind Regards,
> > Alex
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
> For additional commands, e-mail: dev-h...@qpid.apache.org
>
>

[jira] [Updated] (QPID-4717) QMF issue on exchange: update timestamp doesn't seem to be getting updated

[Ted Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Ross updated QPID-4717:
---

Fix Version/s: (was: 0.23)
   0.22

> QMF issue on exchange: update timestamp doesn't seem to be getting updated
> --
>
> Key: QPID-4717
> URL: https://issues.apache.org/jira/browse/QPID-4717
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Broker
>Affects Versions: 0.21
>Reporter: Fraser Adams
>Assignee: Ted Ross
>Priority: Blocker
> Fix For: 0.22
>
>
> I've just noticed an issue with QMF2 statistics on trunk (0.23).
> I'm pretty sure it didn't exist in 0.20 and below, but not sure about what's 
> gone off to the 0.22 branch.
> The issue is that exchange object update timestamps are not being updated. 
> The objects in question definitely have statistics updates as I'm seeing 
> changes to msgReceives and msgRoutes but each exchange now has an _update_ts 
> that isn't getting updated when the statistics change.
> This only seems to be affecting exchange objects, queue and connection 
> objects still seem to be OK.
> I noticed this when I pointed the GUI at qpidd 0.23 and tried to look at the 
> graph for qmf.default.direct msgReceives, the graph wasn't updating despite 
> the msgReceives value updating (the graph uses the actual timestamp to derive 
> its x index).
> I also tried adding console.log to display exchange._update_ts and I'm 
> getting the same value each object update.
> Any idea what might have changed?
> I personally think this is a 0.22 blocker. It certainly prevents graphs of 
> exchange statistics being displayed properly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPID-4729) 0.22 cpp tarball missing a file that breaks cmake

[Chuck Rolke (JIRA)]

Chuck Rolke created QPID-4729:
-

 Summary: 0.22 cpp tarball missing a file that breaks cmake
 Key: QPID-4729
 URL: https://issues.apache.org/jira/browse/QPID-4729
 Project: Qpid
  Issue Type: Bug
  Components: Packaging
Affects Versions: 0.22
Reporter: Chuck Rolke
Assignee: Chuck Rolke


Building from qpid-cpp-0.22-rc1.tar.gz fails because file 
cmake_uninstall.cmake.in is missing.

Copying only this file from qpid-0.22-rc1.tar.gz fixes the build.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (QPID-4727) C++ Broker ACL rules provide no way to match default exchange

[Chuck Rolke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chuck Rolke resolved QPID-4727.
---

   Resolution: Fixed
Fix Version/s: 0.23

Fixed at Committed revision 1465719.


> C++ Broker ACL rules provide no way to match default exchange
> -
>
> Key: QPID-4727
> URL: https://issues.apache.org/jira/browse/QPID-4727
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Broker
>Affects Versions: 0.20
>Reporter: Chuck Rolke
>Assignee: Chuck Rolke
> Fix For: 0.23
>
>
> ACL rules use 'name=value' formatting. In the case of ACL rule PUBLISH 
> EXCHANGE the exchange name must be specified with a name= setting. However, 
> in the case of the default exchange the exchange name is blank. There is no 
> way to specify a blank exchange name and there is no acceptable workaround.
> The proposal is to add keyword *amq.default* to the ACL syntax so that when a 
> PUBLISH EXCHANGE rule exchange name is specified with this keyword then the 
> run-time rule will actually match a blank exchange name.
> {noformat}
>  acl allow bob publish exchange name=amq.default routingkey=bobPrivate
>  acl deny  all publish exchange name=amq.default routingkey=bobPrivate
> {noformat}
> Impact assessment:
> ||Design consideration||Proposed feature||
> |Threading model|n/a|
> |Memory management|n/a|
> |Automated testing approach|easy to test|
> |Impact on public API|Adds new keyword to ACL file syntax|
> |- Interoperability with implementations in other languages|n/a|
> |- Backwards compatibility|No. Old code will try to match literal 
> 'amq.default' text|
> |Performance implications|Per-message publish exchange lookup tests a bool in 
> the rule before checking that the name in the lookup is blank|
> |Security implications|New method already protected by ACL|
> |Platform support|n/a|
> |Logging|no change|
> |Monitoring|no change|
> |Management|no change|

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-4698) Fixes needed for the CMake build system when installing files.

[Justin Ross (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-4698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625603#comment-13625603
 ] 

Justin Ross commented on QPID-4698:
---

Rejected for 0.22.  It's tool late to change build metadata unless it's a 
blocker.

> Fixes needed for the CMake build system when installing files.
> --
>
> Key: QPID-4698
> URL: https://issues.apache.org/jira/browse/QPID-4698
> Project: Qpid
>  Issue Type: Bug
>  Components: Build Tools
>Reporter: Darryl L. Pierce
>Assignee: Darryl L. Pierce
> Fix For: 0.23
>
>
> Some of the installed files are going into the wrong directories.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-4728) Allow option to configure credit on Federation sessions.

[Fraser Adams (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625581#comment-13625581
 ] 

Fraser Adams commented on QPID-4728:


If this relates to what I think it does (I've never been able to articulate the 
problem very well!!) then this sounds *extremely* useful for increasing the 
reliability of federation links.

I've had an issue for ages where there "appeared" to be a memory leak on some 
of our source brokers, but after a lot of head scratching it turned out to be 
an issue due to there being "unbounded buffers" on the federation links.

In my scenario we run a topology whereby a real time producer writes to a 
co-located broker and that broker is federated to another broker etc.

In most cases this works very well but in one particular set of nodes in our 
topology the producer is particularly high rate and quite "bursty" and what 
we'd see is the memory utilisation of the source broker start to increase 
noticeably and eventually we'd hit swap.

What ultimately appeared to be causing the issue was that the network between 
the brokers was "throttling" the communication (I did say it was a fast bursty 
producer) so from the perspective of the source broker we appeared to have a 
fast producer with a slow consumer.

As I was trying to get to the bottom of this I ended up trying to reproduce it 
at the lowest level I could, so wrote simple qpid::messaging and qpid::client 
producer consumer clients to try and "emulate" the federation bridge code and 
found that the qpid::client code appeared to "leak" but the "equivalent" 
qpid::messaging code didn't - then it dawned on me that by default 
qpid::messaging has consumer capacity of 1 (so I generally set it to something 
that gives reasonable prefetch) whereas qpid::client defaults to unlimited.

Our eventual workaround was to have this particular fast bursty producer 
deliver directly to the second stage broker rather than to its co-located 
broker, the theory being that by doing this the rate limiting effect of the 
network actually becomes our friend, so rather than the fast data source 
hitting a broker pretty much as fast as it can it now hits it as fast as the 
network supports, which then generally avoids the unbounded buffer growing in 
an unmanageable way.


It's a pretty subtle issue that took us ages to diagnose and caused more than a 
few sleepless nights, so I'm pretty much +1 million :-) on adding the ability 
to make the federation link capacity bounded.






> Allow option to configure credit on Federation sessions.
> 
>
> Key: QPID-4728
> URL: https://issues.apache.org/jira/browse/QPID-4728
> Project: Qpid
>  Issue Type: Improvement
>  Components: C++ Broker
>Affects Versions: 0.23
>Reporter: Ken Giusti
>Assignee: Ken Giusti
> Fix For: Future
>
>
> By default, sessions created for Federation links use unlimited credit.  This 
> JIRA requests the ability to configure the credit used by a Federation link.  
> E.g.:
> qpid-route --credit 100  route add 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Re: 0.22 inclusion requests

[Justin Ross]

These are all improvements, even the first one.  No doubt it's an
important security enhancement, but it's not a regression, and it
seems reasonable to release note that you should enable acls if you
wish to use the web console.  I'd be more inclined to accept it if the
change were small, but it isn't.

It's hard for me to reconcile these changes with the goals for a
second release candidate.  I hope you can tell that I ordinarily try
to be very flexible, but this doesn't make sense.

Honest question: if you have a compelling reason to introduce these
changes into a stable stream before 0.24, should we have a distinct
branch for that purpose?

Justin

On Mon, Apr 8, 2013 at 9:45 AM, Oleksandr Rudyy  wrote:
> Hi Justin,
>
> Could you please approve the inclusion of the following into 0.22:
>
> JIRA: QPID-4705
> Revision: http://svn.apache.org/r1465590
> Description:
> It fixes the potential security hole with an access to the web management
> console and rest interfaces. Without the fix if ACL is not configured (by
> default no ACL is configured) it is possible to access the web management
> console anonymously and do any configuration changes including password
> change,  configure authentication providers etc. The commit in revision
> r1465590  stops this from happening by
> adding functionality to check whether the request is authenticated or
> authorised and send the redirect to the login page (for web management
> console) or send the error status codes (401,403) for rest requests. The
> changes are isolated to the http management plugin and do not affect the
> broker core functionality.
>
>
> JIRA: QPID-4725 
> Revision: http://svn.apache.org/r1465457
> Description: Enhances the web management console to display a principal
> associated with a connection on connection and virtualhost tabs. The
> changes are isolated to web console UI and of low risk.
>
>
> JIRA: QPID-4726 
> Revision: http://svn.apache.org/r1465459
> Description: Improves SASL support for AMQP 1.0 client. The changes affect
> only 1.0 AMQP functionality and of low risk.
>
> Kind Regards,
> Alex

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-4717) QMF issue on exchange: update timestamp doesn't seem to be getting updated

[Justin Ross (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625543#comment-13625543
 ] 

Justin Ross commented on QPID-4717:
---

Tested by Fraser.  Approved for 0.22.

> QMF issue on exchange: update timestamp doesn't seem to be getting updated
> --
>
> Key: QPID-4717
> URL: https://issues.apache.org/jira/browse/QPID-4717
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Broker
>Affects Versions: 0.21
>Reporter: Fraser Adams
>Assignee: Ted Ross
>Priority: Blocker
> Fix For: 0.23
>
>
> I've just noticed an issue with QMF2 statistics on trunk (0.23).
> I'm pretty sure it didn't exist in 0.20 and below, but not sure about what's 
> gone off to the 0.22 branch.
> The issue is that exchange object update timestamps are not being updated. 
> The objects in question definitely have statistics updates as I'm seeing 
> changes to msgReceives and msgRoutes but each exchange now has an _update_ts 
> that isn't getting updated when the statistics change.
> This only seems to be affecting exchange objects, queue and connection 
> objects still seem to be OK.
> I noticed this when I pointed the GUI at qpidd 0.23 and tried to look at the 
> graph for qmf.default.direct msgReceives, the graph wasn't updating despite 
> the msgReceives value updating (the graph uses the actual timestamp to derive 
> its x index).
> I also tried adding console.log to display exchange._update_ts and I'm 
> getting the same value each object update.
> Any idea what might have changed?
> I personally think this is a 0.22 blocker. It certainly prevents graphs of 
> exchange statistics being displayed properly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-4704) Legacy store is building as a shared library rather than a module

[Justin Ross (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-4704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625540#comment-13625540
 ] 

Justin Ross commented on QPID-4704:
---

Committed to the release branch at http://svn.apache.org/r1465621 .

This should have gotten approval first, however!  Reviewed by Chuck, and 
retroactively approved for 0.22.

> Legacy store is building as a shared library rather than a module
> -
>
> Key: QPID-4704
> URL: https://issues.apache.org/jira/browse/QPID-4704
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Broker
>Affects Versions: 0.20
>Reporter: Darryl L. Pierce
>Assignee: Darryl L. Pierce
> Fix For: Future
>
>
> The store builds as a shared library rather than a module. A simple fix would 
> be to change the library type in the Cmake build files to fix this issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPID-4728) Allow option to configure credit on Federation sessions.

[Ken Giusti (JIRA)]

Ken Giusti created QPID-4728:


 Summary: Allow option to configure credit on Federation sessions.
 Key: QPID-4728
 URL: https://issues.apache.org/jira/browse/QPID-4728
 Project: Qpid
  Issue Type: Improvement
  Components: C++ Broker
Affects Versions: 0.23
Reporter: Ken Giusti
Assignee: Ken Giusti
 Fix For: Future


By default, sessions created for Federation links use unlimited credit.  This 
JIRA requests the ability to configure the credit used by a Federation link.  
E.g.:

qpid-route --credit 100  route add 



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Re: GCC 4.8.0 build fails...

[Andrew Stitcher]

On Mon, 2013-04-08 at 10:52 -0400, Darryl L. Pierce wrote:
> In doing a test build of qpid-cpp on F19 with GCC 4.8.0 I'm still
> getting build failures:

This seems to be a bug in the systemtap header files. Turn off probes to
work around it and report the bug to the systemtap dev list.

Andrew


> 
> Building CXX object
> src/CMakeFiles/qpidcommon.dir/qpid/sys/posix/BSDSocket.o
> In file included from 
> /home/mcpierce/Programming/Qpid/qpid/cpp/src/qpid/sys/Probes.h:27:0,
>  from 
> /home/mcpierce/Programming/Qpid/qpid/cpp/src/qpid/sys/posix/AsynchIO.cpp:26:
> /home/mcpierce/Programming/Qpid/qpid/cpp/src/qpid/sys/posix/AsynchIO.cpp: In 
> member function ‘void 
> qpid::sys::posix::AsynchIO::readable(qpid::sys::DispatchHandle&)’:
> /home/mcpierce/Programming/Qpid/qpid/cpp/src/qpid/sys/Probes.h:41:44: error: 
> impossible constraint in ‘asm’
>  #define QPID_PROBE4(probe, p1, p2, p3, p4) DTRACE_PROBE4(qpid, probe, p1, 
> p2, p3, p4)
> ^
> /home/mcpierce/Programming/Qpid/qpid/cpp/src/qpid/sys/posix/AsynchIO.cpp:456:21:
>  note: in expansion of macro ‘QPID_PROBE4’
>  QPID_PROBE4(asynchio_read_finished_done, &h, duration, 
> total, readCalls);
>  ^
> /home/mcpierce/Programming/Qpid/qpid/cpp/src/qpid/sys/Probes.h:41:44: error: 
> impossible constraint in ‘asm’
>  #define QPID_PROBE4(probe, p1, p2, p3, p4) DTRACE_PROBE4(qpid, probe,
> p1, p2, p3, p4)
> ^
> /home/mcpierce/Programming/Qpid/qpid/cpp/src/qpid/sys/posix/AsynchIO.cpp:462:21:
>  note: in expansion of macro ‘QPID_PROBE4’
>  QPID_PROBE4(asynchio_read_finished_maxtime, &h, 
> duration, total, readCalls);
>  ^
> /home/mcpierce/Programming/Qpid/qpid/cpp/src/qpid/sys/Probes.h:42:48: error: 
> impossible constraint in ‘asm’
>  #define QPID_PROBE5(probe, p1, p2, p3, p4, p5) DTRACE_PROBE5(qpid, probe, 
> p1, p2, p3, p4, p5)
> ^
> /home/mcpierce/Programming/Qpid/qpid/cpp/src/qpid/sys/posix/AsynchIO.cpp:471:17:
>  note: in expansion of macro ‘QPID_PROBE5’
>  QPID_PROBE5(asynchio_read_finished_error, &h, duration, 
> total, readCalls, errno);
>  ^
> /home/mcpierce/Programming/Qpid/qpid/cpp/src/qpid/sys/Probes.h:41:44: error: 
> impossible constraint in ‘asm’
>  #define QPID_PROBE4(probe, p1, p2, p3, p4) DTRACE_PROBE4(qpid, probe, p1, 
> p2, p3, p4)
> ^
> /home/mcpierce/Programming/Qpid/qpid/cpp/src/qpid/sys/posix/AsynchIO.cpp:497:17:
>  note: in expansion of macro ‘QPID_PROBE4’
>  QPID_PROBE4(asynchio_read_finished_nobuffers, &h, 
> Duration(readStartTime, AbsTime::now()), total, readCalls);
>  ^
> make[2]: *** [src/CMakeFiles/qpidcommon.dir/qpid/sys/posix/AsynchIO.o]
> Error 1
> make[2]: *** Waiting for unfinished jobs
> make[1]: *** [src/CMakeFiles/qpidcommon.dir/all] Error 2
> make: *** [all] Error 2
> 



-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (QPID-4642) Can't complete "make distcheck"

[Alan Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Conway resolved QPID-4642.
---

Resolution: Fixed

The build is failing because the SWIG version installed is too old:

configure: WARNING: SWIG version >= 1.3.32 is required.  You have 1.3.29.  You 
should look at http://www.swig.org

> Can't complete "make distcheck"
> ---
>
> Key: QPID-4642
> URL: https://issues.apache.org/jira/browse/QPID-4642
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Broker
>Affects Versions: 0.21
> Environment: Building on RHEL6, Server, x86_64 (automake).
>Reporter: Irina Boverman
>Assignee: Alan Conway
>Priority: Minor
>
> According to this: 
> http://www.gnu.org/software/automake/manual/automake.html#Checking-the-Distribution
> It should be possible to use defaults as in below.
> Using these steps:
> cd qpid/cpp
> ./bootstrap
> ./configure
> make distcheck
> --
> Ends up in error:
> --
> make[1]: Leaving directory 
> `/var/lib/jenkins/workspace/qpid-cpp-trunk-distcheck/label/master/qpid/cpp/docs/api'
>  (cd docs/man && make  top_distdir=../../qpidc-0.21 
> distdir=../../qpidc-0.21/docs/man \
>  am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir)
> make[1]: Entering directory 
> `/var/lib/jenkins/workspace/qpid-cpp-trunk-distcheck/label/master/qpid/cpp/docs/man'
> make[1]: *** No rule to make target `../../src/qpidd', needed by `qpidd.1'.  
> Stop.
> make[1]: Leaving directory 
> `/var/lib/jenkins/workspace/qpid-cpp-trunk-distcheck/label/master/qpid/cpp/docs/man'
> make: *** [distdir] Error 1

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Re: Various build issues with RC1 tarballs

[Chuck Rolke]

Windows builds qpid-cpp-0.22-rc1 fail with a CMake configure error:
  cmake_uninstall.cmake.in does not exist

Windows builds qpid-022.rc1 completes CMake and is compiling. (not done yet)

-Chuck

- Original Message -
> From: "Jimmy Jones" 
> To: dev@qpid.apache.org
> Sent: Sunday, April 7, 2013 1:32:34 PM
> Subject: Various build issues with RC1 tarballs
> 
> Hi,
> 
> I've been trying the 0.22 RC1 tarballs on a fresh RHEL6 VM and have had the
> following issues:
> 
> (QPID-4722) qpid-cpp-0.22-rc1 doesnt compile on RHEL6
> (QPID-4724) qpid-cpp-0.22-rc1 RHEL6 cmake issues
> (QPID-4719) Missing files from qpid 0.22 RC1 tarball
> 
> Has anyone else had the same issues?
> 
> Cheers,
> 
> Jimmy
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
> For additional commands, e-mail: dev-h...@qpid.apache.org
> 
> 

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (QPID-3675) New Feature Announce - Java QMF2 API Implementation.

[Fraser Adams (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Fraser Adams resolved QPID-3675.


Resolution: Fixed

Committed to repository

/tools/src/java

r1465662

> New Feature Announce - Java QMF2 API Implementation.
> 
>
> Key: QPID-3675
> URL: https://issues.apache.org/jira/browse/QPID-3675
> Project: Qpid
>  Issue Type: New Feature
>  Components: Qpid Managment Framework
>Affects Versions: 0.12
> Environment: Java QMF2
>Reporter: Fraser Adams
>Assignee: Ted Ross
>  Labels: features
> Attachments: Firefox Graphs.png, IE8 Add Queue.png, ipod 
> bindings.png, qmf2.tar.gz, qmf2.tar.gz, qmf2-v1.1.tar.gz, qmf2-v1.2.tar.gz, 
> qmf2-v1.3.tar.gz
>
>
> This is the first release of a QMF2 API Implementation for Java.
> Features:
> * Full Implementation of QMF2 Console, Agent and AgentExternal.
> * Supports QMF2 Query Subscriptions on Agent/AgentExternal implementations.
> * Emulates QMF2 Query Subscriptions on the Console side for the broker 
> ManagementAgent by
>   intercepting _data indications and filtering against QmfQuery. This is 
> necessary as the
>   ManagemetAgent doesn't yet support QMF2 style Query Subscriptions.
> * Console supports Agent discovery via findAgent() method, which can support 
> partial matches,
>   which is useful because the full Agent name has a UUID representing the 
> "instance" so it's hard
>   to know the full name.
> * QmfQuery supports regex matching.
> * Supports QMF2 WorkItem Event model and in addition supports an alternative 
> QmfEventListener 
>   Event model, which is rather more like the JMS MessageListener model.
> Example Tools Provided:
> * ConnectionAudit: Audits connections to one or more Qpid message brokers 
> against a whitelist.
> * ConnectionLogger: A QMF2 class used to provide information about 
> connections made to a broker.
> * QpidConfig: QpidConfig is a fairly "literal" Java port of the python 
> qpid-config tool. Uses pure 
>   QMF2 for adding/deleting queues, exchanges & bindings this provides useful 
> illustration of how 
>   to do these things using the ManagementAgent method calls.
> * QpidCtrl: A tool to allow QMF2 methods to be invoked from the command line.
> * QpidPrintEvents: Collect and print events from one or more Qpid message 
> brokers.
> * QpidQueueStats: Collect and print queue statistics. This is a rewrite of 
> the Python version and 
>   illustrates the use of QuerySubscriptions (via the Console side 
> emulation)to subscribe to 
>   objects on the ManagementAgent.
> * QueueFuse: QueueFuse provides protection to message producers from 
> consumers who can't consume 
>   messages fast enough. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-3675) New Feature Announce - Java QMF2 API Implementation.

[Fraser Adams (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625467#comment-13625467
 ] 

Fraser Adams commented on QPID-3675:


This work has now been added to the main Qpid code base in:
/tools/src/java


The Java Broker QmfManagementPlugin work described in release 1.3 above had to 
be rewritten following changes to the Java Broker Plugin API between Qpid 0.20 
and Qpid 0.22 the committed QmfManagementPlugin works with Qpid 0.22 upwards, 
if you want to use with Qpid 0.20 you would need to use the release 1.3 tarball.

> New Feature Announce - Java QMF2 API Implementation.
> 
>
> Key: QPID-3675
> URL: https://issues.apache.org/jira/browse/QPID-3675
> Project: Qpid
>  Issue Type: New Feature
>  Components: Qpid Managment Framework
>Affects Versions: 0.12
> Environment: Java QMF2
>Reporter: Fraser Adams
>Assignee: Ted Ross
>  Labels: features
> Attachments: Firefox Graphs.png, IE8 Add Queue.png, ipod 
> bindings.png, qmf2.tar.gz, qmf2.tar.gz, qmf2-v1.1.tar.gz, qmf2-v1.2.tar.gz, 
> qmf2-v1.3.tar.gz
>
>
> This is the first release of a QMF2 API Implementation for Java.
> Features:
> * Full Implementation of QMF2 Console, Agent and AgentExternal.
> * Supports QMF2 Query Subscriptions on Agent/AgentExternal implementations.
> * Emulates QMF2 Query Subscriptions on the Console side for the broker 
> ManagementAgent by
>   intercepting _data indications and filtering against QmfQuery. This is 
> necessary as the
>   ManagemetAgent doesn't yet support QMF2 style Query Subscriptions.
> * Console supports Agent discovery via findAgent() method, which can support 
> partial matches,
>   which is useful because the full Agent name has a UUID representing the 
> "instance" so it's hard
>   to know the full name.
> * QmfQuery supports regex matching.
> * Supports QMF2 WorkItem Event model and in addition supports an alternative 
> QmfEventListener 
>   Event model, which is rather more like the JMS MessageListener model.
> Example Tools Provided:
> * ConnectionAudit: Audits connections to one or more Qpid message brokers 
> against a whitelist.
> * ConnectionLogger: A QMF2 class used to provide information about 
> connections made to a broker.
> * QpidConfig: QpidConfig is a fairly "literal" Java port of the python 
> qpid-config tool. Uses pure 
>   QMF2 for adding/deleting queues, exchanges & bindings this provides useful 
> illustration of how 
>   to do these things using the ManagementAgent method calls.
> * QpidCtrl: A tool to allow QMF2 methods to be invoked from the command line.
> * QpidPrintEvents: Collect and print events from one or more Qpid message 
> brokers.
> * QpidQueueStats: Collect and print queue statistics. This is a rewrite of 
> the Python version and 
>   illustrates the use of QuerySubscriptions (via the Console side 
> emulation)to subscribe to 
>   objects on the ManagementAgent.
> * QueueFuse: QueueFuse provides protection to message producers from 
> consumers who can't consume 
>   messages fast enough. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Assigned] (QPID-4642) Can't complete "make distcheck"

[Alan Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Conway reassigned QPID-4642:
-

Assignee: Alan Conway

> Can't complete "make distcheck"
> ---
>
> Key: QPID-4642
> URL: https://issues.apache.org/jira/browse/QPID-4642
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Broker
>Affects Versions: 0.21
> Environment: Building on RHEL6, Server, x86_64 (automake).
>Reporter: Irina Boverman
>Assignee: Alan Conway
>Priority: Minor
>
> According to this: 
> http://www.gnu.org/software/automake/manual/automake.html#Checking-the-Distribution
> It should be possible to use defaults as in below.
> Using these steps:
> cd qpid/cpp
> ./bootstrap
> ./configure
> make distcheck
> --
> Ends up in error:
> --
> make[1]: Leaving directory 
> `/var/lib/jenkins/workspace/qpid-cpp-trunk-distcheck/label/master/qpid/cpp/docs/api'
>  (cd docs/man && make  top_distdir=../../qpidc-0.21 
> distdir=../../qpidc-0.21/docs/man \
>  am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir)
> make[1]: Entering directory 
> `/var/lib/jenkins/workspace/qpid-cpp-trunk-distcheck/label/master/qpid/cpp/docs/man'
> make[1]: *** No rule to make target `../../src/qpidd', needed by `qpidd.1'.  
> Stop.
> make[1]: Leaving directory 
> `/var/lib/jenkins/workspace/qpid-cpp-trunk-distcheck/label/master/qpid/cpp/docs/man'
> make: *** [distdir] Error 1

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPID-4727) C++ Broker ACL rules provide no way to match default exchange

[Chuck Rolke (JIRA)]

Chuck Rolke created QPID-4727:
-

 Summary: C++ Broker ACL rules provide no way to match default 
exchange
 Key: QPID-4727
 URL: https://issues.apache.org/jira/browse/QPID-4727
 Project: Qpid
  Issue Type: Bug
  Components: C++ Broker
Affects Versions: 0.20
Reporter: Chuck Rolke
Assignee: Chuck Rolke


ACL rules use 'name=value' formatting. In the case of ACL rule PUBLISH EXCHANGE 
the exchange name must be specified with a name= setting. However, in the case 
of the default exchange the exchange name is blank. There is no way to specify 
a blank exchange name and there is no acceptable workaround.

The proposal is to add keyword *amq.default* to the ACL syntax so that when a 
PUBLISH EXCHANGE rule exchange name is specified with this keyword then the 
run-time rule will actually match a blank exchange name.
{noformat}
 acl allow bob publish exchange name=amq.default routingkey=bobPrivate
 acl deny  all publish exchange name=amq.default routingkey=bobPrivate
{noformat}

Impact assessment:
||Design consideration||Proposed feature||
|Threading model|n/a|
|Memory management|n/a|
|Automated testing approach|easy to test|
|Impact on public API|Adds new keyword to ACL file syntax|
|- Interoperability with implementations in other languages|n/a|
|- Backwards compatibility|No. Old code will try to match literal 'amq.default' 
text|
|Performance implications|Per-message publish exchange lookup tests a bool in 
the rule before checking that the name in the lookup is blank|
|Security implications|New method already protected by ACL|
|Platform support|n/a|
|Logging|no change|
|Monitoring|no change|
|Management|no change|


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

GCC 4.8.0 build fails...

[Darryl L. Pierce]

In doing a test build of qpid-cpp on F19 with GCC 4.8.0 I'm still
getting build failures:

Building CXX object
src/CMakeFiles/qpidcommon.dir/qpid/sys/posix/BSDSocket.o
In file included from 
/home/mcpierce/Programming/Qpid/qpid/cpp/src/qpid/sys/Probes.h:27:0,
 from 
/home/mcpierce/Programming/Qpid/qpid/cpp/src/qpid/sys/posix/AsynchIO.cpp:26:
/home/mcpierce/Programming/Qpid/qpid/cpp/src/qpid/sys/posix/AsynchIO.cpp: In 
member function ‘void 
qpid::sys::posix::AsynchIO::readable(qpid::sys::DispatchHandle&)’:
/home/mcpierce/Programming/Qpid/qpid/cpp/src/qpid/sys/Probes.h:41:44: error: 
impossible constraint in ‘asm’
 #define QPID_PROBE4(probe, p1, p2, p3, p4) DTRACE_PROBE4(qpid, probe, p1, p2, 
p3, p4)
^
/home/mcpierce/Programming/Qpid/qpid/cpp/src/qpid/sys/posix/AsynchIO.cpp:456:21:
 note: in expansion of macro ‘QPID_PROBE4’
 QPID_PROBE4(asynchio_read_finished_done, &h, duration, 
total, readCalls);
 ^
/home/mcpierce/Programming/Qpid/qpid/cpp/src/qpid/sys/Probes.h:41:44: error: 
impossible constraint in ‘asm’
 #define QPID_PROBE4(probe, p1, p2, p3, p4) DTRACE_PROBE4(qpid, probe,
p1, p2, p3, p4)
^
/home/mcpierce/Programming/Qpid/qpid/cpp/src/qpid/sys/posix/AsynchIO.cpp:462:21:
 note: in expansion of macro ‘QPID_PROBE4’
 QPID_PROBE4(asynchio_read_finished_maxtime, &h, duration, 
total, readCalls);
 ^
/home/mcpierce/Programming/Qpid/qpid/cpp/src/qpid/sys/Probes.h:42:48: error: 
impossible constraint in ‘asm’
 #define QPID_PROBE5(probe, p1, p2, p3, p4, p5) DTRACE_PROBE5(qpid, probe, p1, 
p2, p3, p4, p5)
^
/home/mcpierce/Programming/Qpid/qpid/cpp/src/qpid/sys/posix/AsynchIO.cpp:471:17:
 note: in expansion of macro ‘QPID_PROBE5’
 QPID_PROBE5(asynchio_read_finished_error, &h, duration, total, 
readCalls, errno);
 ^
/home/mcpierce/Programming/Qpid/qpid/cpp/src/qpid/sys/Probes.h:41:44: error: 
impossible constraint in ‘asm’
 #define QPID_PROBE4(probe, p1, p2, p3, p4) DTRACE_PROBE4(qpid, probe, p1, p2, 
p3, p4)
^
/home/mcpierce/Programming/Qpid/qpid/cpp/src/qpid/sys/posix/AsynchIO.cpp:497:17:
 note: in expansion of macro ‘QPID_PROBE4’
 QPID_PROBE4(asynchio_read_finished_nobuffers, &h, 
Duration(readStartTime, AbsTime::now()), total, readCalls);
 ^
make[2]: *** [src/CMakeFiles/qpidcommon.dir/qpid/sys/posix/AsynchIO.o]
Error 1
make[2]: *** Waiting for unfinished jobs
make[1]: *** [src/CMakeFiles/qpidcommon.dir/all] Error 2
make: *** [all] Error 2

-- 
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/



pgpH8oX_hoigr.pgp
Description: PGP signature

rdma support in python

[euroford]

Hi all,

THere is a project Python-rmda, https://github.com/jgunthorpe/python-rdma,
is that possible qpid-python got rmda support with it? 

Bests,
eurofod



--
View this message in context: 
http://qpid.2158936.n2.nabble.com/rdma-support-in-python-tp7591211.html
Sent from the Apache Qpid developers mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

0.22 Inclusion Request - QPID-4698

[Darryl L. Pierce]

Fixes needed for the CMake build system when installing files.

Corrects the installation for several pieces, including Python site
packages, a couple of configuration files and a SysVInit script.

http://issues.apache.org/jira/browse/QPID-4698

-- 
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/



pgpf3uQbrRMYr.pgp
Description: PGP signature

[jira] [Commented] (QPID-4698) Fixes needed for the CMake build system when installing files.

[Darryl L. Pierce (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-4698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625387#comment-13625387
 ] 

Darryl L. Pierce commented on QPID-4698:


The check-in is here:
http://svn.apache.org/viewvc?view=revision&revision=1465643

> Fixes needed for the CMake build system when installing files.
> --
>
> Key: QPID-4698
> URL: https://issues.apache.org/jira/browse/QPID-4698
> Project: Qpid
>  Issue Type: Bug
>  Components: Build Tools
>Reporter: Darryl L. Pierce
>Assignee: Darryl L. Pierce
> Fix For: 0.23
>
>
> Some of the installed files are going into the wrong directories.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (QPID-4698) Fixes needed for the CMake build system when installing files.

[Darryl L. Pierce (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-4698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Darryl L. Pierce resolved QPID-4698.


   Resolution: Fixed
Fix Version/s: 0.23

> Fixes needed for the CMake build system when installing files.
> --
>
> Key: QPID-4698
> URL: https://issues.apache.org/jira/browse/QPID-4698
> Project: Qpid
>  Issue Type: Bug
>  Components: Build Tools
>Reporter: Darryl L. Pierce
>Assignee: Darryl L. Pierce
> Fix For: 0.23
>
>
> Some of the installed files are going into the wrong directories.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

0.22 inclusion requests

[Oleksandr Rudyy]

Hi Justin,

Could you please approve the inclusion of the following into 0.22:

JIRA: QPID-4705
Revision: http://svn.apache.org/r1465590
Description:
It fixes the potential security hole with an access to the web management
console and rest interfaces. Without the fix if ACL is not configured (by
default no ACL is configured) it is possible to access the web management
console anonymously and do any configuration changes including password
change,  configure authentication providers etc. The commit in revision
r1465590  stops this from happening by
adding functionality to check whether the request is authenticated or
authorised and send the redirect to the login page (for web management
console) or send the error status codes (401,403) for rest requests. The
changes are isolated to the http management plugin and do not affect the
broker core functionality.


JIRA: QPID-4725 
Revision: http://svn.apache.org/r1465457
Description: Enhances the web management console to display a principal
associated with a connection on connection and virtualhost tabs. The
changes are isolated to web console UI and of low risk.


JIRA: QPID-4726 
Revision: http://svn.apache.org/r1465459
Description: Improves SASL support for AMQP 1.0 client. The changes affect
only 1.0 AMQP functionality and of low risk.

Kind Regards,
Alex

[jira] [Commented] (QPID-4726) [Java Broker] AMQP 1.0 : Improve SASL support

[Alex Rudyy (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625360#comment-13625360
 ] 

Alex Rudyy commented on QPID-4726:
--

I reviewed the changes and would like to request the inclusion of them into 
0.22 branch

> [Java Broker] AMQP 1.0 : Improve SASL support
> -
>
> Key: QPID-4726
> URL: https://issues.apache.org/jira/browse/QPID-4726
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Rob Godfrey
>Assignee: Rob Godfrey
> Fix For: 0.23
>
>
> Improve the AMQP 1.0 SASL support in the Java broker to use the 
> authentication provider associated with the port on which the connection has 
> been made.  
> Set the user property of the Connection object when the connection has been 
> authenticated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-4725) [Java Broker] HTTP Managament Plugin GUI doesn't show user on connection

[Alex Rudyy (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625330#comment-13625330
 ] 

Alex Rudyy commented on QPID-4725:
--

I reviewed the changes and would like to request the inclusion of them into 
0.22 branch

> [Java Broker] HTTP Managament Plugin GUI doesn't show user on connection
> 
>
> Key: QPID-4725
> URL: https://issues.apache.org/jira/browse/QPID-4725
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Rob Godfrey
>Assignee: Rob Godfrey
>Priority: Minor
> Fix For: 0.23
>
>
> Both the Connection tab itself, and the table of connections on the 
> VirtualHost tab fail to display the authenticated principal associated with a 
> connection.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (QPID-4726) [Java Broker] AMQP 1.0 : Improve SASL support

[Rob Godfrey (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rob Godfrey resolved QPID-4726.
---

   Resolution: Fixed
Fix Version/s: 0.23

See: http://svn.apache.org/r1465459

> [Java Broker] AMQP 1.0 : Improve SASL support
> -
>
> Key: QPID-4726
> URL: https://issues.apache.org/jira/browse/QPID-4726
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Rob Godfrey
>Assignee: Rob Godfrey
> Fix For: 0.23
>
>
> Improve the AMQP 1.0 SASL support in the Java broker to use the 
> authentication provider associated with the port on which the connection has 
> been made.  
> Set the user property of the Connection object when the connection has been 
> authenticated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (QPID-4705) [Java Broker] anonymous users are able to view and update broker configuration via the web console by default

[Robbie Gemmell (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-4705.
--

Resolution: Fixed

> [Java Broker] anonymous users are able to view and update broker 
> configuration via the web console by default
> -
>
> Key: QPID-4705
> URL: https://issues.apache.org/jira/browse/QPID-4705
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.18, 0.20, 0.22
>Reporter: Alex Rudyy
>Assignee: Robbie Gemmell
>Priority: Blocker
> Fix For: 0.23
>
>
> In previous releases the default configuration allowed anonymous users to 
> view and perform a limited set of operations via the new web management 
> interface, with ability to restrict these via the ACLs. For the 0.22 release, 
> the broker-level configuration model has been replaced and is now entirely 
> configurable via the web management interface, exposing additional 
> configuration for viewing and/or manipulation that was previously either not 
> exposed via HTTP or only read-only.
> Now that functionality such as configuring the used authentication providers, 
> ports, SSL, etc can done via the web interface it should be authenticated by 
> default, with anonymous access only being provided where the user explicitly 
> assigns the anonymous authentication provider to the HTTP(S) port/ports in 
> use.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Comment Edited] (QPID-4705) [Java Broker] anonymous users are able to view and update broker configuration via the web console by default

[Robbie Gemmell (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625299#comment-13625299
 ] 

Robbie Gemmell edited comment on QPID-4705 at 4/8/13 11:35 AM:
---

Changes look good to me. Agreed that we should request these for inclusion in 
0.22.

  was (Author: gemmellr):
Changes look good to me. Aggreed that we should request these for inclusion 
in 0.22.
  
> [Java Broker] anonymous users are able to view and update broker 
> configuration via the web console by default
> -
>
> Key: QPID-4705
> URL: https://issues.apache.org/jira/browse/QPID-4705
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.18, 0.20, 0.22
>Reporter: Alex Rudyy
>Assignee: Robbie Gemmell
>Priority: Blocker
> Fix For: 0.23
>
>
> In previous releases the default configuration allowed anonymous users to 
> view and perform a limited set of operations via the new web management 
> interface, with ability to restrict these via the ACLs. For the 0.22 release, 
> the broker-level configuration model has been replaced and is now entirely 
> configurable via the web management interface, exposing additional 
> configuration for viewing and/or manipulation that was previously either not 
> exposed via HTTP or only read-only.
> Now that functionality such as configuring the used authentication providers, 
> ports, SSL, etc can done via the web interface it should be authenticated by 
> default, with anonymous access only being provided where the user explicitly 
> assigns the anonymous authentication provider to the HTTP(S) port/ports in 
> use.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-4705) [Java Broker] anonymous users are able to view and update broker configuration via the web console by default

[Robbie Gemmell (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625299#comment-13625299
 ] 

Robbie Gemmell commented on QPID-4705:
--

Changes look good to me. Aggreed that we should request these for inclusion in 
0.22.

> [Java Broker] anonymous users are able to view and update broker 
> configuration via the web console by default
> -
>
> Key: QPID-4705
> URL: https://issues.apache.org/jira/browse/QPID-4705
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.18, 0.20, 0.22
>Reporter: Alex Rudyy
>Assignee: Robbie Gemmell
>Priority: Blocker
> Fix For: 0.23
>
>
> In previous releases the default configuration allowed anonymous users to 
> view and perform a limited set of operations via the new web management 
> interface, with ability to restrict these via the ACLs. For the 0.22 release, 
> the broker-level configuration model has been replaced and is now entirely 
> configurable via the web management interface, exposing additional 
> configuration for viewing and/or manipulation that was previously either not 
> exposed via HTTP or only read-only.
> Now that functionality such as configuring the used authentication providers, 
> ports, SSL, etc can done via the web interface it should be authenticated by 
> default, with anonymous access only being provided where the user explicitly 
> assigns the anonymous authentication provider to the HTTP(S) port/ports in 
> use.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Assigned] (QPID-4705) [Java Broker] anonymous users are able to view and update broker configuration via the web console by default

[Alex Rudyy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy reassigned QPID-4705:


Assignee: Robbie Gemmell  (was: Alex Rudyy)

Robbie, 
Could you please review the changes made in a revision 
http://svn.apache.org/r1465590 ?

> [Java Broker] anonymous users are able to view and update broker 
> configuration via the web console by default
> -
>
> Key: QPID-4705
> URL: https://issues.apache.org/jira/browse/QPID-4705
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.18, 0.20, 0.22
>Reporter: Alex Rudyy
>Assignee: Robbie Gemmell
>Priority: Blocker
> Fix For: 0.23
>
>
> In previous releases the default configuration allowed anonymous users to 
> view and perform a limited set of operations via the new web management 
> interface, with ability to restrict these via the ACLs. For the 0.22 release, 
> the broker-level configuration model has been replaced and is now entirely 
> configurable via the web management interface, exposing additional 
> configuration for viewing and/or manipulation that was previously either not 
> exposed via HTTP or only read-only.
> Now that functionality such as configuring the used authentication providers, 
> ports, SSL, etc can done via the web interface it should be authenticated by 
> default, with anonymous access only being provided where the user explicitly 
> assigns the anonymous authentication provider to the HTTP(S) port/ports in 
> use.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPID-4705) [Java Broker] anonymous users are able to view and update broker configuration via the web console by default

[Alex Rudyy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-4705:
-

Status: Ready To Review  (was: In Progress)

> [Java Broker] anonymous users are able to view and update broker 
> configuration via the web console by default
> -
>
> Key: QPID-4705
> URL: https://issues.apache.org/jira/browse/QPID-4705
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.18, 0.20, 0.22
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Blocker
> Fix For: 0.23
>
>
> In previous releases the default configuration allowed anonymous users to 
> view and perform a limited set of operations via the new web management 
> interface, with ability to restrict these via the ACLs. For the 0.22 release, 
> the broker-level configuration model has been replaced and is now entirely 
> configurable via the web management interface, exposing additional 
> configuration for viewing and/or manipulation that was previously either not 
> exposed via HTTP or only read-only.
> Now that functionality such as configuring the used authentication providers, 
> ports, SSL, etc can done via the web interface it should be authenticated by 
> default, with anonymous access only being provided where the user explicitly 
> assigns the anonymous authentication provider to the HTTP(S) port/ports in 
> use.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org