[jira] Created: (QPID-2457) configure.ac doesn't check all required headers - breaks Debian derivatives.
configure.ac doesn't check all required headers - breaks Debian derivatives. Key: QPID-2457 URL: https://issues.apache.org/jira/browse/QPID-2457 Project: Qpid Issue Type: Bug Components: C++ Broker Environment: Ubuntu Hardy 8.04 Reporter: Neil Wilson Priority: Minor Debian splits out the libboost library into several separate packages. The configure.ac needs to check all the headers it uses in boost, not just an example. boost/program_options.hpp being the current case in point. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2458) nspr.h file assumed to be in nspr4 directory
nspr.h file assumed to be in nspr4 directory Key: QPID-2458 URL: https://issues.apache.org/jira/browse/QPID-2458 Project: Qpid Issue Type: Bug Components: C++ Broker Environment: Ubuntu - all versions Reporter: Neil Wilson qpid/sys/ssl/SslSocket.h includes nspr4/nspr.h. On Debian systems this header is at /usr/include/nspr/nspr.h. The configure system needs to detect the location of the header. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2457) configure.ac doesn't check all required headers - breaks Debian derivatives.
[ https://issues.apache.org/jira/browse/QPID-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Wilson updated QPID-2457: -- Description: Debian splits out the libboost library into several separate packages. The configure.ac needs to check more headers in boost to make sure that the Debian splits are catered for. (Note these may be Debian dependencies that aren't handled properly - however if configure handles it, it looks better than a make failure). Headers that currently fail are: boost/program_options.hpp boost/serialization/split_member.hpp was: Debian splits out the libboost library into several separate packages. The configure.ac needs to check all the headers it uses in boost, not just an example. boost/program_options.hpp being the current case in point. configure.ac doesn't check all required headers - breaks Debian derivatives. Key: QPID-2457 URL: https://issues.apache.org/jira/browse/QPID-2457 Project: Qpid Issue Type: Bug Components: C++ Broker Environment: Ubuntu Hardy 8.04 Reporter: Neil Wilson Priority: Minor Debian splits out the libboost library into several separate packages. The configure.ac needs to check more headers in boost to make sure that the Debian splits are catered for. (Note these may be Debian dependencies that aren't handled properly - however if configure handles it, it looks better than a make failure). Headers that currently fail are: boost/program_options.hpp boost/serialization/split_member.hpp -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2457) configure.ac doesn't check all required headers - breaks Debian derivatives.
[ https://issues.apache.org/jira/browse/QPID-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Wilson updated QPID-2457: -- Description: Debian splits out the libboost library into several separate packages. The configure.ac needs to check more headers in boost to make sure that the Debian splits are catered for. (Note these may be Debian dependencies that aren't handled properly - however if configure handles it, it looks better than a make failure). Headers that currently fail are: boost/program_options.hpp boost/serialization/split_member.hpp boost/filesystem/operations.hpp boost/filesystem/path.hpp was: Debian splits out the libboost library into several separate packages. The configure.ac needs to check more headers in boost to make sure that the Debian splits are catered for. (Note these may be Debian dependencies that aren't handled properly - however if configure handles it, it looks better than a make failure). Headers that currently fail are: boost/program_options.hpp boost/serialization/split_member.hpp configure.ac doesn't check all required headers - breaks Debian derivatives. Key: QPID-2457 URL: https://issues.apache.org/jira/browse/QPID-2457 Project: Qpid Issue Type: Bug Components: C++ Broker Environment: Ubuntu Hardy 8.04 Reporter: Neil Wilson Priority: Minor Debian splits out the libboost library into several separate packages. The configure.ac needs to check more headers in boost to make sure that the Debian splits are catered for. (Note these may be Debian dependencies that aren't handled properly - however if configure handles it, it looks better than a make failure). Headers that currently fail are: boost/program_options.hpp boost/serialization/split_member.hpp boost/filesystem/operations.hpp boost/filesystem/path.hpp -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2459) nss headers assumed to be in nss3 directory
nss headers assumed to be in nss3 directory --- Key: QPID-2459 URL: https://issues.apache.org/jira/browse/QPID-2459 Project: Qpid Issue Type: Bug Components: C++ Broker Environment: Ubuntu - all versions Reporter: Neil Wilson nss headers assumed to be in nss3 directory. On Debian derivatives they are in /usr/include/nss. Configure needs to check that and sort it out. See src/qpid/sys/ssl/check.cpp -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2459) nss headers assumed to be in nss3 directory
[ https://issues.apache.org/jira/browse/QPID-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Wilson updated QPID-2459: -- Description: nss headers assumed to be in nss3 directory. On Debian derivatives they are in /usr/include/nss. Configure needs to check that and sort it out. See src/qpid/sys/ssl/check.cpp src/qpid/sys/ssl/check.h was: nss headers assumed to be in nss3 directory. On Debian derivatives they are in /usr/include/nss. Configure needs to check that and sort it out. See src/qpid/sys/ssl/check.cpp nss headers assumed to be in nss3 directory --- Key: QPID-2459 URL: https://issues.apache.org/jira/browse/QPID-2459 Project: Qpid Issue Type: Bug Components: C++ Broker Environment: Ubuntu - all versions Reporter: Neil Wilson nss headers assumed to be in nss3 directory. On Debian derivatives they are in /usr/include/nss. Configure needs to check that and sort it out. See src/qpid/sys/ssl/check.cpp src/qpid/sys/ssl/check.h -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2459) nss headers assumed to be in nss3 directory
[ https://issues.apache.org/jira/browse/QPID-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Wilson updated QPID-2459: -- Description: nss headers assumed to be in nss3 directory. On Debian derivatives they are in /usr/include/nss. Configure needs to check that and sort it out. See qpid/sys/ssl/check.cpp qpid/sys/ssl/check.h qpid/sys/ssl/util.cpp qpid/sys/ssl/SslSocket.cpp was: nss headers assumed to be in nss3 directory. On Debian derivatives they are in /usr/include/nss. Configure needs to check that and sort it out. See src/qpid/sys/ssl/check.cpp src/qpid/sys/ssl/check.h nss headers assumed to be in nss3 directory --- Key: QPID-2459 URL: https://issues.apache.org/jira/browse/QPID-2459 Project: Qpid Issue Type: Bug Components: C++ Broker Environment: Ubuntu - all versions Reporter: Neil Wilson nss headers assumed to be in nss3 directory. On Debian derivatives they are in /usr/include/nss. Configure needs to check that and sort it out. See qpid/sys/ssl/check.cpp qpid/sys/ssl/check.h qpid/sys/ssl/util.cpp qpid/sys/ssl/SslSocket.cpp -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2457) configure.ac doesn't check all required headers - breaks Debian derivatives.
[ https://issues.apache.org/jira/browse/QPID-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Wilson updated QPID-2457: -- Description: Debian splits out the libboost library into several separate packages. The configure.ac needs to check more headers in boost to make sure that the Debian splits are catered for. (Note these may be Debian dependencies that aren't handled properly - however if configure handles it, it looks better than a make failure). Headers that currently fail are: boost/program_options.hpp boost/serialization/split_member.hpp boost/filesystem/operations.hpp boost/filesystem/path.hpp boost/test/unit_test.hpp was: Debian splits out the libboost library into several separate packages. The configure.ac needs to check more headers in boost to make sure that the Debian splits are catered for. (Note these may be Debian dependencies that aren't handled properly - however if configure handles it, it looks better than a make failure). Headers that currently fail are: boost/program_options.hpp boost/serialization/split_member.hpp boost/filesystem/operations.hpp boost/filesystem/path.hpp Environment: Ubuntu - all versions (was: Ubuntu Hardy 8.04) configure.ac doesn't check all required headers - breaks Debian derivatives. Key: QPID-2457 URL: https://issues.apache.org/jira/browse/QPID-2457 Project: Qpid Issue Type: Bug Components: C++ Broker Environment: Ubuntu - all versions Reporter: Neil Wilson Priority: Minor Debian splits out the libboost library into several separate packages. The configure.ac needs to check more headers in boost to make sure that the Debian splits are catered for. (Note these may be Debian dependencies that aren't handled properly - however if configure handles it, it looks better than a make failure). Headers that currently fail are: boost/program_options.hpp boost/serialization/split_member.hpp boost/filesystem/operations.hpp boost/filesystem/path.hpp boost/test/unit_test.hpp -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2457) configure.ac doesn't check all required headers - breaks Debian derivatives.
[ https://issues.apache.org/jira/browse/QPID-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Wilson updated QPID-2457: -- Description: Debian splits out the libboost library into several separate packages. The configure.ac needs to check more headers in boost to make sure that the Debian splits are catered for. (Note these may be Debian dependencies that aren't handled properly - however if configure handles it, it looks better than a make failure). Headers that currently fail are: boost/program_options.hpp boost/serialization/split_member.hpp boost/filesystem/operations.hpp boost/filesystem/path.hpp boost/test/unit_test.hpp boost/regex.hpp was: Debian splits out the libboost library into several separate packages. The configure.ac needs to check more headers in boost to make sure that the Debian splits are catered for. (Note these may be Debian dependencies that aren't handled properly - however if configure handles it, it looks better than a make failure). Headers that currently fail are: boost/program_options.hpp boost/serialization/split_member.hpp boost/filesystem/operations.hpp boost/filesystem/path.hpp boost/test/unit_test.hpp configure.ac doesn't check all required headers - breaks Debian derivatives. Key: QPID-2457 URL: https://issues.apache.org/jira/browse/QPID-2457 Project: Qpid Issue Type: Bug Components: C++ Broker Environment: Ubuntu - all versions Reporter: Neil Wilson Priority: Minor Debian splits out the libboost library into several separate packages. The configure.ac needs to check more headers in boost to make sure that the Debian splits are catered for. (Note these may be Debian dependencies that aren't handled properly - however if configure handles it, it looks better than a make failure). Headers that currently fail are: boost/program_options.hpp boost/serialization/split_member.hpp boost/filesystem/operations.hpp boost/filesystem/path.hpp boost/test/unit_test.hpp boost/regex.hpp -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2460) configure doesn't check for presence of libtool correctly
configure doesn't check for presence of libtool correctly - Key: QPID-2460 URL: https://issues.apache.org/jira/browse/QPID-2460 Project: Qpid Issue Type: Bug Components: C++ Broker Environment: Ubuntu - all versions Reporter: Neil Wilson If libtool is missing from the system, configure doesn't pick that up - breaking the 'make check' process. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2461) Bashisms in ssl_test script
Bashisms in ssl_test script --- Key: QPID-2461 URL: https://issues.apache.org/jira/browse/QPID-2461 Project: Qpid Issue Type: Bug Components: C++ Broker Environment: Ubuntu - all versions Reporter: Neil Wilson Priority: Minor There are bashisms in src/tests/ssl_test so it should request bash on the first line. #!/bin/bash -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: URL-friendly address syntax [ was Re: Client configuration Connection URL]
Alan Conway wrote:
On 03/15/2010 01:53 PM, Rajith Attapattu wrote:
On Mon, Mar 15, 2010 at 8:24 AM, Alan Conwayacon...@redhat.com wrote:
On 03/12/2010 10:40 AM, Rajith Attapattu wrote:
On Fri, Mar 12, 2010 at 8:59 AM, Alan Conwayacon...@redhat.com
wrote:
On 03/11/2010 06:41 PM, Rajith Attapattu wrote:
Hi All,
Currently quite a bit of options can be configured via the Java
Connection URL, which tends to make it ungainly and quite error
prone.
If we are to think in terms of a Connection String instead of a
Connection URL , then I believe we could come up with a more
simpler
solution.
Therefore I'd like to make the following proposals.
1) Introduce a simple scheme for a Connection String ( inspired by
the new addressing format)
2) Also allow the ability to specify the config using a property
file.
* I hate having to specify user/pass when the auth mech (ex kerberos)
is not even using it. Therefore it should be optional !
1. 0 Connection String
---
1.1 Examples
tcp://localhost
tcp://localhost:8672; {ssl: true, sasl-mech : EXTERNAL,
ssl-trust-store : ~/cert.jks ..}
tcp://host1.example.com; {user: bob, pass: nuts} ,
tcp://host2.example.com; {user: ding, pass: dong} ...
I think there is value in keeping to a URL-friendly
Could you please elaborate on this?
I mean avoiding characters that are not allowed in URLs, in particular
spaces which are troublesome in a variety of contexts. However I if the
spaces are optional (I think they are given that there are always other
separators involved ,:{} then that may not be an issue.
Alan I think we should treat the Broker portion of it as a URL and
the key : value pairs separately.
IMO opinion they are two distinct entities that should be treated
separately.
1. You need a URL parser to parse the broker part, migth as well use it
for the whole thing.
2. You're going to want to pass these strings around by various means
outside of qpid (filesystem, program arguments, web pages, other XML
docs...) URL strings are well known and easy to pass around. Strings
with custom syntax and embedded spaces will pose a variety of problems -
you'll end up having to use some form of quoting, URL syntax provides
this for you.
I'll go one step further and suggest that we should use the standard
query-string syntax for name/value pairs:
tcp://localhost:8672/?ssl=truesasl-mech=EXTERNALssl-trust-store=~/cert.jks
...
Every URL parser out there already knows how to parse this.
I'll go another step further and propose that we modify the new address
string format to be URL friendly.
I see 2 issues: spaces and ';'
I think spaces is a non issue as you can just leave them out - am I
correct on that?
The issue with ';' is that URLs use it as a separator (alternative to
'') in the query string. I suggest we simply drop it. Then we can
easily embed addresses in URLS, e.g.
tcp://localhost:8672/?ssl=true;sasl-mech=EXTERNAL;address=myqueue{create:always,node-properties:{durable:true}}
...
I don't think we can really remove the ';'. The name/subject part of the
address can include fairly complex patterns that include curly braces,
so we really need something to separate the options from the address,
and ';' is pretty much the only reasonable option for this given the
syntax for what goes on either side.
The address syntax was specifically chosen because the URL syntax is
insufficiently powerful to be able to reasonably express everything that
needs to be able to go into an address, things like nested maps/lists,
embedded selector strings, etc. The address syntax is pretty much a pure
subset of python dictionary syntax, so it's always going to be more
expressive than what will be able to naturally fit in a URL.
Personally I think if we nest it's more natural to do it the other way
around. Nest the more limited syntax inside the more powerful one. This
is trivial: {url: foo://bar.baz.qux}. You're always going to have
problems if you try to nest the other way around.
--Rafael
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Why do we create the cpp/src/tests/python dir?
Alan Conway wrote: The C++ builds install python files in src/tests/python. This is kind of a pain for at least 2 reasons: - src/tests/python can go stale - not sure how but it just happened to me. - debugging python code, error messages take you to the src/tests/python copy rather than the real source file. - python gets re-installed every time you build. Whats the reason for doing this? Can we get the same effect some other way that doesn't involve duplicating all the .py files? The root cause for this is that the python client needs to support python 2.3, and to do this it needs to do some preprocessing on the files before you can run them (assuming you're on a system with python 2.3). So it's not actually copying the files it's actually compiling them, and the reason this is done under the cpp build root is simply to not pollute the source tree. As for why they get re-installed every time and how they can go stale, I'm not sure about that. I believe andrew was the one who modified the cpp build to do this. I'm guessing it could be done in a smarter way that wouldn't rebuild and wouldn't allow things to go stale. --Rafael - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2459) nss headers assumed to be in nss3 directory
[ https://issues.apache.org/jira/browse/QPID-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Wilson updated QPID-2459: -- Affects Version/s: 0.5 nss headers assumed to be in nss3 directory --- Key: QPID-2459 URL: https://issues.apache.org/jira/browse/QPID-2459 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.5 Environment: Ubuntu - all versions Reporter: Neil Wilson nss headers assumed to be in nss3 directory. On Debian derivatives they are in /usr/include/nss. Configure needs to check that and sort it out. See qpid/sys/ssl/check.cpp qpid/sys/ssl/check.h qpid/sys/ssl/util.cpp qpid/sys/ssl/SslSocket.cpp -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2461) Bashisms in ssl_test script
[ https://issues.apache.org/jira/browse/QPID-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Wilson updated QPID-2461: -- Affects Version/s: 0.5 Bashisms in ssl_test script --- Key: QPID-2461 URL: https://issues.apache.org/jira/browse/QPID-2461 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.5 Environment: Ubuntu - all versions Reporter: Neil Wilson Priority: Minor There are bashisms in src/tests/ssl_test so it should request bash on the first line. #!/bin/bash -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2457) configure.ac doesn't check all required headers - breaks Debian derivatives.
[ https://issues.apache.org/jira/browse/QPID-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Wilson updated QPID-2457: -- Affects Version/s: 0.5 configure.ac doesn't check all required headers - breaks Debian derivatives. Key: QPID-2457 URL: https://issues.apache.org/jira/browse/QPID-2457 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.5 Environment: Ubuntu - all versions Reporter: Neil Wilson Priority: Minor Debian splits out the libboost library into several separate packages. The configure.ac needs to check more headers in boost to make sure that the Debian splits are catered for. (Note these may be Debian dependencies that aren't handled properly - however if configure handles it, it looks better than a make failure). Headers that currently fail are: boost/program_options.hpp boost/serialization/split_member.hpp boost/filesystem/operations.hpp boost/filesystem/path.hpp boost/test/unit_test.hpp boost/regex.hpp -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2458) nspr.h file assumed to be in nspr4 directory
[ https://issues.apache.org/jira/browse/QPID-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Wilson updated QPID-2458: -- Affects Version/s: 0.5 nspr.h file assumed to be in nspr4 directory Key: QPID-2458 URL: https://issues.apache.org/jira/browse/QPID-2458 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.5 Environment: Ubuntu - all versions Reporter: Neil Wilson qpid/sys/ssl/SslSocket.h includes nspr4/nspr.h. On Debian systems this header is at /usr/include/nspr/nspr.h. The configure system needs to detect the location of the header. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2460) configure doesn't check for presence of libtool correctly
[ https://issues.apache.org/jira/browse/QPID-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Wilson updated QPID-2460: -- Affects Version/s: 0.5 configure doesn't check for presence of libtool correctly - Key: QPID-2460 URL: https://issues.apache.org/jira/browse/QPID-2460 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.5 Environment: Ubuntu - all versions Reporter: Neil Wilson If libtool is missing from the system, configure doesn't pick that up - breaking the 'make check' process. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Client configuration Connection URL
I think the first step we need to take before actually thinking about
the syntax is to put together a matrix with all the connection
parameters for all the clients.
Historically we've picked a common syntax (URL) but not really bothered
to ensure that we use the syntax the same way. This is in part because
the different clients support different options or different ways of
semantically expressing the same option, so I think the first step is to
actually align the semantics of the different client connection options
so that there is actually some benefit to using the same syntax.
Also, I think once we do that it will be easier to see what the
requirements for the syntax are and whether URL or something more
expressive is a better fit.
I'm actually futzing with a few of the connection options for the python
client now, but when I finish with that I'll post a complete list for
the python client.
--Rafael
Rajith Attapattu wrote:
Hi All,
Currently quite a bit of options can be configured via the Java
Connection URL, which tends to make it ungainly and quite error prone.
If we are to think in terms of a Connection String instead of a
Connection URL , then I believe we could come up with a more simpler
solution.
Therefore I'd like to make the following proposals.
1) Introduce a simple scheme for a Connection String ( inspired by
the new addressing format)
2) Also allow the ability to specify the config using a property file.
* I hate having to specify user/pass when the auth mech (ex kerberos)
is not even using it. Therefore it should be optional !
1. 0 Connection String
---
1.1 Examples
tcp://localhost
tcp://localhost:8672; {ssl: true, sasl-mech : EXTERNAL,
ssl-trust-store : ~/cert.jks ..}
tcp://host1.example.com; {user: bob, pass: nuts} ,
tcp://host2.example.com; {user: ding, pass: dong} ...
1.2 Syntax
broker [ ; options ] [ , broker [ ; options ]] *
Where broker is::
protocol:// [ host [ : port ] ](protocol = {tcp|vm|rdma}
Where options is::
{ key : value, ... }
And values may be:
- numbers
- single, double, or non quoted strings
- maps (dictionaries)
- lists
2.0 Config file
-
Example
JNDI prop file
connection.my-connection = tcp://localhost; {id : 1}
connection.my-con = tcp://host1.example.com; {id: 2} ,
tcp://host2.example.com; {id: 2}, tcp://host3.example.com; {id: 3}
=Connection.properties=
con id : 1 {
ssl: true
sasl-mech : EXTERNAL
ssl-trust-store : ~/cert.jks
ssl-key-store : ~/keys.jks
ssl-verify-hostname : true
}
con id : 1 {
sasl-mech : GSSAPI
sasl-hostname : host1.example.com
sasl-protocol : qpidd
sasl-encryption : true
tcp-nodelay : true
}
con id : 3 {
user : ding
pass : dong
tcp-nodelay : true
}
==
Connection.properties can be loaded from the classpath or specified as
an option in the connection string.
(You could also trivially have a connection property file per connection).
Comments and suggestions are most welcomed !
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: cluster test error?
On 03/18/2010 02:27 PM, Gordon Sim wrote: Anyone else seen the error below intermittently? Looks like a crashed process perhaps(?) but I didn't see a core file. A perftest client of broker named cluster1-2 got disconnected which could mean the broker crashed. Do you still have the cluster1-2.log? cluster_tests.LongTests.test_failover .. pass cluster_tests.LongTests.test_management fail Error during test: Traceback (most recent call last): File /home/gordon/projects/qpid-svn-trunk/cpp/build/src/tests/python/commands/qpid-python-test, line 311, in run phase() File /home/gordon/projects/qpid-svn-trunk/cpp/src/tests/cluster_tests.py, line 271, in test_management c.stop() File /home/gordon/projects/qpid-svn-trunk/cpp/src/tests/cluster_tests.py, line 220, in stop StoppableThread.stop(self) File /home/gordon/projects/qpid-svn-trunk/cpp/build/src/tests/python/qpid/brokertest.py, line 481, in stop if self.error: raise self.error RethrownException: Error in ClientLoop.run Traceback (most recent call last): File /home/gordon/projects/qpid-svn-trunk/cpp/src/tests/cluster_tests.py, line 200, in run client of %s exit code %s%(self.broker.name, exit)) File /home/gordon/projects/qpid-svn-trunk/cpp/build/src/tests/python/qpid/brokertest.py, line 177, in unexpected raise BadProcessStatus(%s %s%s % (self.pname, msg, err)) BadProcessStatus: perftest-16459 client of cluster1-2 exit code 256: 2010-03-18 12:20:19 warning Connection closed cluster_tests.ShortTests.test_config_change_seq pass cluster_tests.ShortTests.test_message_replication .. pass cluster_tests.ShortTests.test_store_direct_update_match pass Totals: 15 tests, 4 passed, 0 skipped, 10 ignored, 1 failed FAIL: run_cluster_tests - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: cluster test error?
On 03/19/2010 01:24 PM, Alan Conway wrote: On 03/18/2010 02:27 PM, Gordon Sim wrote: Anyone else seen the error below intermittently? Looks like a crashed process perhaps(?) but I didn't see a core file. A perftest client of broker named cluster1-2 got disconnected which could mean the broker crashed. Do you still have the cluster1-2.log? Not from a failed case, but I'll check those next time I see it. Thanks! - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Client configuration Connection URL
On Fri, Mar 19, 2010 at 8:23 AM, Rafael Schloming rafa...@redhat.com wrote:
I think the first step we need to take before actually thinking about the
syntax is to put together a matrix with all the connection parameters for
all the clients.
Historically we've picked a common syntax (URL) but not really bothered to
ensure that we use the syntax the same way. This is in part because the
different clients support different options or different ways of
semantically expressing the same option, so I think the first step is to
actually align the semantics of the different client connection options so
that there is actually some benefit to using the same syntax.
Also, I think once we do that it will be easier to see what the requirements
for the syntax are and whether URL or something more expressive is a better
fit.
I'm actually futzing with a few of the connection options for the python
client now, but when I finish with that I'll post a complete list for the
python client.
+1
I think it's a very sensible step to first figure out the requirements
for each client.
I will create a wiki page and add the Java client stuff.
Regards,
Rajith
--Rafael
Rajith Attapattu wrote:
Hi All,
Currently quite a bit of options can be configured via the Java
Connection URL, which tends to make it ungainly and quite error prone.
If we are to think in terms of a Connection String instead of a
Connection URL , then I believe we could come up with a more simpler
solution.
Therefore I'd like to make the following proposals.
1) Introduce a simple scheme for a Connection String ( inspired by
the new addressing format)
2) Also allow the ability to specify the config using a property file.
* I hate having to specify user/pass when the auth mech (ex kerberos)
is not even using it. Therefore it should be optional !
1. 0 Connection String
---
1.1 Examples
tcp://localhost
tcp://localhost:8672; {ssl: true, sasl-mech : EXTERNAL,
ssl-trust-store : ~/cert.jks ..}
tcp://host1.example.com; {user: bob, pass: nuts} ,
tcp://host2.example.com; {user: ding, pass: dong} ...
1.2 Syntax
broker [ ; options ] [ , broker [ ; options ]] *
Where broker is::
protocol:// [ host [ : port ] ] (protocol = {tcp|vm|rdma}
Where options is::
{ key : value, ... }
And values may be:
- numbers
- single, double, or non quoted strings
- maps (dictionaries)
- lists
2.0 Config file
-
Example
JNDI prop file
connection.my-connection = tcp://localhost; {id : 1}
connection.my-con = tcp://host1.example.com; {id: 2} ,
tcp://host2.example.com; {id: 2}, tcp://host3.example.com; {id: 3}
=Connection.properties=
con id : 1 {
ssl: true
sasl-mech : EXTERNAL
ssl-trust-store : ~/cert.jks
ssl-key-store : ~/keys.jks
ssl-verify-hostname : true
}
con id : 1 {
sasl-mech : GSSAPI
sasl-hostname : host1.example.com
sasl-protocol : qpidd
sasl-encryption : true
tcp-nodelay : true
}
con id : 3 {
user : ding
pass : dong
tcp-nodelay : true
}
==
Connection.properties can be loaded from the classpath or specified as
an option in the connection string.
(You could also trivially have a connection property file per connection).
Comments and suggestions are most welcomed !
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Why do we create the cpp/src/tests/python dir?
On 03/19/2010 07:59 AM, Rafael Schloming wrote: Alan Conway wrote: The C++ builds install python files in src/tests/python. This is kind of a pain for at least 2 reasons: - src/tests/python can go stale - not sure how but it just happened to me. - debugging python code, error messages take you to the src/tests/python copy rather than the real source file. - python gets re-installed every time you build. Whats the reason for doing this? Can we get the same effect some other way that doesn't involve duplicating all the .py files? The root cause for this is that the python client needs to support python 2.3, and to do this it needs to do some preprocessing on the files before you can run them (assuming you're on a system with python 2.3). So it's not actually copying the files it's actually compiling them, and the reason this is done under the cpp build root is simply to not pollute the source tree. As for why they get re-installed every time and how they can go stale, I'm not sure about that. I believe andrew was the one who modified the cpp build to do this. I'm guessing it could be done in a smarter way that wouldn't rebuild and wouldn't allow things to go stale. I think this is a good case study to think about how we do dependencies between sub-projects in qpid. The C++ build currently has dependencies on (at least) - python - tools - extras And it picks them up via a variety of routes. In an svn checkout it has a bunch of coded-in assumptions about looking for things in ../python, it's got hackery to run the python install process mentioned above and it's all quite nasty. In a distribution tree it picks up qpid-tool and the like from PATH if they're installed, quietly skips the python tests if it can't find the ../python tree, randomly fails if there happens to be a ../python directory that's not what the build expected etc. I think the clean way out is to make the python project a dependency of the C++ project just like it depends on boost or other tools. I.e. to run the tests you must *install* the python project, and the tests pick up components via standard PATH and PYTHONPATH env vars. A developer would set their install --prefix to their own directory rather than the system one and install the dependencies there. A user building from a distro could do this or install in standard system places as they wish. To keep things simple for developers we would have a script that install all the C++ deps for you in an SVN checkout. This idea is in the half-baked stage so please point to holes suggest improvements. There are a couple drawbacks I can think of: - extra step for developers to build, although could consider this part of installing pre-reqs so not really a new step. - risk of picking up stuff installed in standard places by accident, getting wrong version. Don't know how to avoid this. - not sure how this plays in the windows world. Thoughts? Alan. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: cluster test error?
On 03/19/2010 09:33 AM, Gordon Sim wrote: On 03/19/2010 01:24 PM, Alan Conway wrote: On 03/18/2010 02:27 PM, Gordon Sim wrote: Anyone else seen the error below intermittently? Looks like a crashed process perhaps(?) but I didn't see a core file. A perftest client of broker named cluster1-2 got disconnected which could mean the broker crashed. Do you still have the cluster1-2.log? Not from a failed case, but I'll check those next time I see it. Thanks! I have just seen something like this in a manual test running perftest and mgmt tools on a 4 node cluster. One of the perftests was disconnected but the broker is fine, still responding. Not sure why the disconnection or how reproducible this is. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: URL-friendly address syntax [ was Re: Client configuration Connection URL]
On 03/19/2010 07:42 AM, Rafael Schloming wrote:
Alan Conway wrote:
On 03/15/2010 01:53 PM, Rajith Attapattu wrote:
On Mon, Mar 15, 2010 at 8:24 AM, Alan Conwayacon...@redhat.com wrote:
On 03/12/2010 10:40 AM, Rajith Attapattu wrote:
On Fri, Mar 12, 2010 at 8:59 AM, Alan Conwayacon...@redhat.com
wrote:
On 03/11/2010 06:41 PM, Rajith Attapattu wrote:
Hi All,
Currently quite a bit of options can be configured via the Java
Connection URL, which tends to make it ungainly and quite error
prone.
If we are to think in terms of a Connection String instead of a
Connection URL , then I believe we could come up with a more
simpler
solution.
Therefore I'd like to make the following proposals.
1) Introduce a simple scheme for a Connection String ( inspired by
the new addressing format)
2) Also allow the ability to specify the config using a property
file.
* I hate having to specify user/pass when the auth mech (ex
kerberos)
is not even using it. Therefore it should be optional !
1. 0 Connection String
---
1.1 Examples
tcp://localhost
tcp://localhost:8672; {ssl: true, sasl-mech : EXTERNAL,
ssl-trust-store : ~/cert.jks ..}
tcp://host1.example.com; {user: bob, pass: nuts} ,
tcp://host2.example.com; {user: ding, pass: dong} ...
I think there is value in keeping to a URL-friendly
Could you please elaborate on this?
I mean avoiding characters that are not allowed in URLs, in particular
spaces which are troublesome in a variety of contexts. However I if the
spaces are optional (I think they are given that there are always other
separators involved ,:{} then that may not be an issue.
Alan I think we should treat the Broker portion of it as a URL and
the key : value pairs separately.
IMO opinion they are two distinct entities that should be treated
separately.
1. You need a URL parser to parse the broker part, migth as well use
it for the whole thing.
2. You're going to want to pass these strings around by various means
outside of qpid (filesystem, program arguments, web pages, other XML
docs...) URL strings are well known and easy to pass around. Strings
with custom syntax and embedded spaces will pose a variety of problems
- you'll end up having to use some form of quoting, URL syntax
provides this for you.
I'll go one step further and suggest that we should use the standard
query-string syntax for name/value pairs:
tcp://localhost:8672/?ssl=truesasl-mech=EXTERNALssl-trust-store=~/cert.jks
...
Every URL parser out there already knows how to parse this.
I'll go another step further and propose that we modify the new
address string format to be URL friendly.
I see 2 issues: spaces and ';'
I think spaces is a non issue as you can just leave them out - am I
correct on that?
The issue with ';' is that URLs use it as a separator (alternative to
'') in the query string. I suggest we simply drop it. Then we can
easily embed addresses in URLS, e.g.
tcp://localhost:8672/?ssl=true;sasl-mech=EXTERNAL;address=myqueue{create:always,node-properties:{durable:true}}
...
I don't think we can really remove the ';'. The name/subject part of the
address can include fairly complex patterns that include curly braces,
so we really need something to separate the options from the address,
and ';' is pretty much the only reasonable option for this given the
syntax for what goes on either side.
The address syntax was specifically chosen because the URL syntax is
insufficiently powerful to be able to reasonably express everything that
needs to be able to go into an address, things like nested maps/lists,
embedded selector strings, etc. The address syntax is pretty much a pure
subset of python dictionary syntax, so it's always going to be more
expressive than what will be able to naturally fit in a URL.
Personally I think if we nest it's more natural to do it the other way
around. Nest the more limited syntax inside the more powerful one. This
is trivial: {url: foo://bar.baz.qux}. You're always going to have
problems if you try to nest the other way around.
You can nest any string in a URL by using the standard URL quoting. It's nicer
though, if you don't have to quote.
URLs are a widely accepted format for addressing and part of the AMQP 0-10
standard for addressing brokers, so I think it would be valuable to make it
easy for these strings to be included in URLs. I don't think there's a big
change needed, or that python dictionary syntax is something that we need to
stick to for a multi-language system like qpid.
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-2459) nss headers assumed to be in nss3 directory
[ https://issues.apache.org/jira/browse/QPID-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Wilson resolved QPID-2459. --- Resolution: Fixed Fix Version/s: 0.6 nss headers assumed to be in nss3 directory --- Key: QPID-2459 URL: https://issues.apache.org/jira/browse/QPID-2459 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.5 Environment: Ubuntu - all versions Reporter: Neil Wilson Fix For: 0.6 nss headers assumed to be in nss3 directory. On Debian derivatives they are in /usr/include/nss. Configure needs to check that and sort it out. See qpid/sys/ssl/check.cpp qpid/sys/ssl/check.h qpid/sys/ssl/util.cpp qpid/sys/ssl/SslSocket.cpp -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-2458) nspr.h file assumed to be in nspr4 directory
[ https://issues.apache.org/jira/browse/QPID-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Wilson resolved QPID-2458. --- Resolution: Fixed Fix Version/s: 0.6 nspr.h file assumed to be in nspr4 directory Key: QPID-2458 URL: https://issues.apache.org/jira/browse/QPID-2458 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.5 Environment: Ubuntu - all versions Reporter: Neil Wilson Fix For: 0.6 qpid/sys/ssl/SslSocket.h includes nspr4/nspr.h. On Debian systems this header is at /usr/include/nspr/nspr.h. The configure system needs to detect the location of the header. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Closed: (QPID-2404) The following files does not have the ASL license header
[ https://issues.apache.org/jira/browse/QPID-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu closed QPID-2404. -- Resolution: Fixed 0.6 has been released, hence closing the JIRA The following files does not have the ASL license header Key: QPID-2404 URL: https://issues.apache.org/jira/browse/QPID-2404 Project: Qpid Issue Type: Improvement Components: Licensing Reporter: Rajith Attapattu Assignee: Rajith Attapattu Priority: Blocker Fix For: 0.6 Attachments: rat_feb_11_2005_06_branch ./cpp/examples/README.verify ./cpp/src/qpid/framing/Blob.h ./cpp/src/qpid/framing/BodyHolder.cpp ./cpp/src/qpid/framing/BodyHolder.h ./cpp/src/tests/Blob.cpp ./cpp/src/tests/cluster_python_tests ./cpp/src/tests/cluster_test_scripts/cluster_check ./cpp/src/tests/cluster_test_scripts/cluster_start ./cpp/src/tests/cluster_test_scripts/cluster_stop ./cpp/src/tests/cluster_test_scripts/config_example.sh ./cpp/src/tests/cluster_test_scripts/perftest ./java/broker/scripts/resetAlerting.sh ./java/broker/src/main/java/org/apache/qpid/server/protocol/AMQProtocolEngineFactory.java ./java/broker/src/main/java/org/apache/qpid/server/queue/SubFlushRunner.java ./java/broker/src/main/java/org/apache/qpid/server/security/access/AuthorizationManager.java ./java/broker/src/main/java/org/apache/qpid/server/txn/LocalTransaction.java ./java/client/src/test/java/org/apache/qpid/client/message/AbstractJMSMessageTest.java ./java/client/test/bin/IBM-README.txt ./java/common/src/main/java/org/apache/qpid/thread/DefaultThreadFactory.java ./java/common/src/main/java/org/apache/qpid/thread/RealtimeThreadFactory.java ./java/common/src/main/java/org/apache/qpid/thread/ThreadFactory.java ./java/common/src/main/java/org/apache/qpid/thread/Threading.java ./java/common/src/test/java/org/apache/qpid/codec/AMQDecoderTest.java ./java/common/src/test/java/org/apache/qpid/codec/MockAMQVersionAwareProtocolSession.java ./java/common/src/test/java/org/apache/qpid/thread/ThreadFactoryTest.java ./java/integrationtests/docs/RunningSustainedTests.txt ./java/management/agent/src/main/java/org/apache/qpid/agent/EventSeverity.java ./java/management/client/web.xml ./java/management/client/console/brokers_management.jsp ./java/management/client/console/console.jsp ./java/management/client/console/error_page.jsp ./java/management/client/console/jmx_perspective.jsp ./java/management/client/console/logging_configuration.jsp ./java/management/client/console/resources_management.jsp ./java/management/client/console/tbd.jsp ./java/management/client/console/wsdm_operations_perspective.jsp ./java/management/client/console/wsdm_properties_perspective.jsp ./java/management/client/console/wsdm_rmd_perspective.jsp ./java/management/client/console/wsdm_wsdl_perspective.jsp ./java/management/client/console/fragments/header.jsp ./java/management/client/console/fragments/menu.jsp ./java/management/client/console/images/style.css ./java/management/client/etc/jetty.xml ./java/management/client/etc/log4j.xml ./java/management/client/src/main/java/muse.xml ./java/management/client/src/main/java/org/apache/qpid/management/domain/model/QpidEntity.java ./java/management/client/src/main/java/org/apache/qpid/management/wsdm/muse/engine/WSDMAdapterEnvironment.java ./java/management/client/src/main/java/org/apache/qpid/management/wsdm/muse/engine/WSDMAdapterIsolationLayer.java ./java/management/client/src/main/java/router-entries/adapter/resource-instance-1.xml ./java/management/client/src/main/java/router-entries/consumer/resource-instance-1.xml ./java/management/client/src/main/java/wsdl/QManAdapter.rmd ./java/management/client/src/main/java/wsdl/QManAdapter.wsdl ./java/management/client/src/main/java/wsdl/QManWsResource.rmd ./java/management/client/src/main/java/wsdl/QManWsResource.wsdl ./java/management/client/src/main/java/wsdl/SOAP-Envelope-1_2.xsd ./java/management/client/src/main/java/wsdl/WS-Addressing-2005_08.xsd ./java/management/client/src/main/java/wsdl/WS-MetadataExchange-2004_09.xsd ./java/management/client/src/main/java/wsdl/WS-ServiceGroup-1_2.wsdl ./java/management/client/src/main/java/wsdl/WS-ServiceGroupEntry-1_2.wsdl ./java/management/client/src/main/java/wsdl/WSDM-MUWS-Part1-1_1.xsd ./java/management/client/src/main/java/wsdl/WSDM-MUWS-Part2-1_1.xsd ./java/management/client/src/main/java/wsdl/WsResource.rmd ./java/management/client/src/main/java/wsdl/WsResourceFactory.wsdl ./java/management/client/src/main/java/wsdl/XML-Namespace-1998.xsd ./java/management/client/src/test/java/log4j.xml ./java/management/client/src/test/java/org/apache/qpid/management/wsdm/web.xml ./java/management/console/src/main/java/org/apache/qpid/console/XMLUtil.java
Re: URL-friendly address syntax [ was Re: Client configuration Connection URL]
On Fri, Mar 19, 2010 at 11:08 AM, Gordon Sim g...@redhat.com wrote: On 03/19/2010 02:57 PM, Alan Conway wrote: URLs are a widely accepted format for addressing and part of the AMQP 0-10 standard for addressing brokers, so I think it would be valuable to make it easy for these strings to be included in URLs. Does the currently defined URL scheme for AMQP 0-10 support options? It is certainly a different form from the example URls given in this thread and currently is only supported in c++. I don't know if it does as it was designed for a specific purpose. IIRC correctly the AMQP 0-10 format was introduced to provide the list of brokers through the failover exchange. All most all the options are client side configuration and don't need to be shipped around. We could use existing URL parsers if we somehow shoehorn the connection string into a URL format. But I'd argue the issues surrounding the current Java URL connection format far outweighed those benefits. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/ - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2457) configure.ac doesn't check all required headers - breaks Debian derivatives.
[ https://issues.apache.org/jira/browse/QPID-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Wilson updated QPID-2457: -- Environment: Ubuntu 8.04 - hardy (was: Ubuntu - all versions) configure.ac doesn't check all required headers - breaks Debian derivatives. Key: QPID-2457 URL: https://issues.apache.org/jira/browse/QPID-2457 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.5 Environment: Ubuntu 8.04 - hardy Reporter: Neil Wilson Priority: Minor Debian splits out the libboost library into several separate packages. The configure.ac needs to check more headers in boost to make sure that the Debian splits are catered for. (Note these may be Debian dependencies that aren't handled properly - however if configure handles it, it looks better than a make failure). Headers that currently fail are: boost/program_options.hpp boost/serialization/split_member.hpp boost/filesystem/operations.hpp boost/filesystem/path.hpp boost/test/unit_test.hpp boost/regex.hpp -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Why do we create the cpp/src/tests/python dir?
On Fri, 2010-03-19 at 07:59 -0400, Rafael Schloming wrote: As for why they get re-installed every time and how they can go stale, I'm not sure about that. I believe andrew was the one who modified the cpp build to do this. I plead not guilty m'lud. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2462) Ignored return value in qrsh_server.cpp
Ignored return value in qrsh_server.cpp --- Key: QPID-2462 URL: https://issues.apache.org/jira/browse/QPID-2462 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Environment: Ubuntu - Lucid gcc -v Using built-in specs. Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.4.3-3ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --enable-multiarch --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4 --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-plugin --enable-objc-gc --disable-werror --with-arch-32=i486 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.4.3 (Ubuntu 4.4.3-3ubuntu3) Reporter: Neil Wilson cc1plus: warnings being treated as errors qrsh_server.cpp: In member function 'void qpid::tests::QrshServer::getNames()': qrsh_server.cpp:489: error: ignoring return value of 'int fscanf(FILE*, const char*, ...)', declared with attribute warn_unused_result qrsh_server.cpp: In member function 'void qpid::tests::QrshServer::execute(const qpid::client::Message)': qrsh_server.cpp:590: error: ignoring return value of 'int system(const char*)', declared with attribute warn_unused_result -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2462) Ignored return value in various files
[ https://issues.apache.org/jira/browse/QPID-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Wilson updated QPID-2462: -- Summary: Ignored return value in various files (was: Ignored return value in qrsh_server.cpp) Ignored return value in various files - Key: QPID-2462 URL: https://issues.apache.org/jira/browse/QPID-2462 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Environment: Ubuntu - Lucid gcc -v Using built-in specs. Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.4.3-3ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --enable-multiarch --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4 --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-plugin --enable-objc-gc --disable-werror --with-arch-32=i486 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.4.3 (Ubuntu 4.4.3-3ubuntu3) Reporter: Neil Wilson cc1plus: warnings being treated as errors qrsh_server.cpp: In member function 'void qpid::tests::QrshServer::getNames()': qrsh_server.cpp:489: error: ignoring return value of 'int fscanf(FILE*, const char*, ...)', declared with attribute warn_unused_result qrsh_server.cpp: In member function 'void qpid::tests::QrshServer::execute(const qpid::client::Message)': qrsh_server.cpp:590: error: ignoring return value of 'int system(const char*)', declared with attribute warn_unused_result -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2461) Bashisms in ssl_test script
[ https://issues.apache.org/jira/browse/QPID-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Wilson updated QPID-2461: -- Affects Version/s: (was: 0.5) 0.6 Bashisms in ssl_test script --- Key: QPID-2461 URL: https://issues.apache.org/jira/browse/QPID-2461 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Environment: Ubuntu - all versions Reporter: Neil Wilson Priority: Minor There are bashisms in src/tests/ssl_test so it should request bash on the first line. #!/bin/bash -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2461) Bashisms in ssl_test script
[ https://issues.apache.org/jira/browse/QPID-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Wilson updated QPID-2461: -- Description: There are bashisms in src/tests/ssl_test and src/tests/run_test. It should request bash on the first line. #!/bin/bash was: There are bashisms in src/tests/ssl_test so it should request bash on the first line. #!/bin/bash Bashisms in ssl_test script --- Key: QPID-2461 URL: https://issues.apache.org/jira/browse/QPID-2461 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Environment: Ubuntu - all versions Reporter: Neil Wilson Priority: Minor There are bashisms in src/tests/ssl_test and src/tests/run_test. It should request bash on the first line. #!/bin/bash -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2461) Bashisms in test scripts
[ https://issues.apache.org/jira/browse/QPID-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Wilson updated QPID-2461: -- Description: There are bashisms in the test scripts. They should request bash on the first line (#!/bin/bash) Affects all shell scripts in src/tests/ was: There are bashisms in src/tests/ssl_test and src/tests/run_test. It should request bash on the first line. #!/bin/bash Summary: Bashisms in test scripts (was: Bashisms in ssl_test script) Bashisms in test scripts Key: QPID-2461 URL: https://issues.apache.org/jira/browse/QPID-2461 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Environment: Ubuntu - all versions Reporter: Neil Wilson Priority: Minor There are bashisms in the test scripts. They should request bash on the first line (#!/bin/bash) Affects all shell scripts in src/tests/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2462) Ignored return value in various files
[ https://issues.apache.org/jira/browse/QPID-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Wilson updated QPID-2462: -- Attachment: unused_result_patches Patch for unused results. Ignored return value in various files - Key: QPID-2462 URL: https://issues.apache.org/jira/browse/QPID-2462 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Environment: Ubuntu - Lucid gcc -v Using built-in specs. Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.4.3-3ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --enable-multiarch --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4 --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-plugin --enable-objc-gc --disable-werror --with-arch-32=i486 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.4.3 (Ubuntu 4.4.3-3ubuntu3) Reporter: Neil Wilson Attachments: unused_result_patches cc1plus: warnings being treated as errors qrsh_server.cpp: In member function 'void qpid::tests::QrshServer::getNames()': qrsh_server.cpp:489: error: ignoring return value of 'int fscanf(FILE*, const char*, ...)', declared with attribute warn_unused_result qrsh_server.cpp: In member function 'void qpid::tests::QrshServer::execute(const qpid::client::Message)': qrsh_server.cpp:590: error: ignoring return value of 'int system(const char*)', declared with attribute warn_unused_result -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2461) Bashisms in test scripts
[ https://issues.apache.org/jira/browse/QPID-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Wilson updated QPID-2461: -- Attachment: ssl_test_uses_bash Fixes bashisms Bashisms in test scripts Key: QPID-2461 URL: https://issues.apache.org/jira/browse/QPID-2461 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Environment: Ubuntu - all versions Reporter: Neil Wilson Priority: Minor Attachments: ssl_test_uses_bash There are bashisms in the test scripts. They should request bash on the first line (#!/bin/bash) Affects all shell scripts in src/tests/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-2460) configure doesn't check for presence of libtool correctly
[ https://issues.apache.org/jira/browse/QPID-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Wilson resolved QPID-2460. --- Resolution: Fixed Fix Version/s: 0.6 configure doesn't check for presence of libtool correctly - Key: QPID-2460 URL: https://issues.apache.org/jira/browse/QPID-2460 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.5 Environment: Ubuntu - all versions Reporter: Neil Wilson Fix For: 0.6 If libtool is missing from the system, configure doesn't pick that up - breaking the 'make check' process. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2460) configure doesn't check for presence of libtool correctly
[ https://issues.apache.org/jira/browse/QPID-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12847435#action_12847435 ] Jan Sarenik commented on QPID-2460: --- Neil, is something resolved on the qpid side or you just found problem in your local environment? In case of the latter, the bug should not be put into Resolved state, but rather Closed with appropriate resolution string (maybe Not a problem, but I don't know what happend now). By the way I appreciate very much the peer-review you are doing in Debian perspective. configure doesn't check for presence of libtool correctly - Key: QPID-2460 URL: https://issues.apache.org/jira/browse/QPID-2460 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.5 Environment: Ubuntu - all versions Reporter: Neil Wilson Fix For: 0.6 If libtool is missing from the system, configure doesn't pick that up - breaking the 'make check' process. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2360) declaring virtualhost level firewall configuration in virtualhosts.xml leads to NPE on startup
[ https://issues.apache.org/jira/browse/QPID-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12847436#action_12847436 ] Robbie Gemmell commented on QPID-2360: -- The trunk patch does not compile because it also contains various other (unfinished?) changes to classes unrelated to the update of the server/virtualhost configuration and their tests, eg: reorganised imports, addition of generic types, spacing, annotations etc. MockAMQQueue changes also add a tab character that should be removed. It would be best to split these types of change and any others which aren't related to the configuration updates out into a new JIRA and patch, as it will make both a lot easier to digest. The changes to ServeConfiguration itself in order to address the issues raised look good, however there are some points to address with the changes: ServerConfigurationTest: L904 is now a function definition that does nothing other than call itself, and so gets stuck in an infinite recursion when used by the Firewall related test methods, leading to a StackOverFlowException when they are run. ServerConfiguration: L165 The exception should be updated to say Only one external virtualhosts configuration *file* allowed, *multiple filenames found* to avoid users thinking they have too many virtualhosts should the exception ever be thrown, rather than that they have just specified multiple strings that we then assume to be file locations. ServerConfiguration: L192 This comment has been made invalid by the patch changes and should be removed: // Add the keys of the virtual host to the main config I think that the broker/etc/log4j.xml configuration should not be modified to suppress warnings regarding optional config files not being present, with the associated logging level left as-is. Primarily only the tests use the ConfigurationFactory abilities and then the optional ability on top of that, so this will rarely if ever be logged in actual use, but it should be output when it is. broker/etc/transient_config.xml and broker/etc/persistent_config.xml should just be removed (they are not really used at all, at worst some tests use them and if so they should just be updated to use overrides where required.) rather than updating them and adding new individualised virtualhosts files for each and causing more clutter in the repository and Apache release bundles. Related to the above, the new virtualhost files referenced in the patch changes are not actually included in the patch and so are missing. Similarly for the main new broker/etc/virtualhosts.xml file and various new virtualhosts files for the Systests module. declaring virtualhost level firewall configuration in virtualhosts.xml leads to NPE on startup -- Key: QPID-2360 URL: https://issues.apache.org/jira/browse/QPID-2360 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.6 Reporter: Robbie Gemmell Fix For: 0.7 Attachments: qpid-2360-broker-etc.patch, qpid-2360-broker-src.patch, qpid-2360-systests-etc.patch, qpid-2360-systests-src.patch, qpid-2360-trunk-all.patch Declaring virtualhost level firewall configuration in virtualhosts.xml leads to NPE on startup. After moving the same configuration into config.xml the broker then loads ok and the configuration works as expected. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Assigned: (QPID-2360) declaring virtualhost level firewall configuration in virtualhosts.xml leads to NPE on startup
[ https://issues.apache.org/jira/browse/QPID-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-2360: Assignee: Robbie Gemmell declaring virtualhost level firewall configuration in virtualhosts.xml leads to NPE on startup -- Key: QPID-2360 URL: https://issues.apache.org/jira/browse/QPID-2360 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.6 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.7 Attachments: qpid-2360-broker-etc.patch, qpid-2360-broker-src.patch, qpid-2360-systests-etc.patch, qpid-2360-systests-src.patch, qpid-2360-trunk-all.patch Declaring virtualhost level firewall configuration in virtualhosts.xml leads to NPE on startup. After moving the same configuration into config.xml the broker then loads ok and the configuration works as expected. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Assigned: (QPID-2361) exchange configuration attributes are ignored when configuration is placed in virtualhosts.xml
[ https://issues.apache.org/jira/browse/QPID-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-2361: Assignee: Robbie Gemmell exchange configuration attributes are ignored when configuration is placed in virtualhosts.xml -- Key: QPID-2361 URL: https://issues.apache.org/jira/browse/QPID-2361 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.5, 0.6 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.7 When configuring exchanges in virtualhosts.xml, only the name is picked up. The type element is ignored and the default direct is used. Similarly, the durable element is ignored and the default false is used. As such it is impossible to define anything other than a transient direct exchange within virtualhosts.xml. When configured within the main config.xml file, the configuration is picked up and used as expected. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2458) nspr.h file assumed to be in nspr4 directory
[ https://issues.apache.org/jira/browse/QPID-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12847441#action_12847441 ] Jan Sarenik commented on QPID-2458: --- What happened to this bug? Was the code changed? I have experienced similar problem on other non-RedHat distribution. nspr.h file assumed to be in nspr4 directory Key: QPID-2458 URL: https://issues.apache.org/jira/browse/QPID-2458 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.5 Environment: Ubuntu - all versions Reporter: Neil Wilson Fix For: 0.6 qpid/sys/ssl/SslSocket.h includes nspr4/nspr.h. On Debian systems this header is at /usr/include/nspr/nspr.h. The configure system needs to detect the location of the header. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2460) configure doesn't check for presence of libtool correctly
[ https://issues.apache.org/jira/browse/QPID-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12847450#action_12847450 ] Neil Wilson commented on QPID-2460: --- 0.5 was a nightmare on Ubuntu and I gave up with it. So many errors. Hardy was too old for it and Lucid too new. 0.6 is much better. configure doesn't check for presence of libtool correctly - Key: QPID-2460 URL: https://issues.apache.org/jira/browse/QPID-2460 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.5 Environment: Ubuntu - all versions Reporter: Neil Wilson Fix For: 0.6 If libtool is missing from the system, configure doesn't pick that up - breaking the 'make check' process. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Closed: (QPID-2460) configure doesn't check for presence of libtool correctly
[ https://issues.apache.org/jira/browse/QPID-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Wilson closed QPID-2460. - Unable to verify error. Probably due to conflicts with libraries installed on Ubuntu. configure doesn't check for presence of libtool correctly - Key: QPID-2460 URL: https://issues.apache.org/jira/browse/QPID-2460 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.5 Environment: Ubuntu - all versions Reporter: Neil Wilson Fix For: 0.6 If libtool is missing from the system, configure doesn't pick that up - breaking the 'make check' process. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2457) configure.ac doesn't check all required headers - breaks Debian derivatives.
[ https://issues.apache.org/jira/browse/QPID-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Wilson updated QPID-2457: -- Affects Version/s: (was: 0.5) 0.6 Affects 0.6 in the same way on Ubuntu Hardy. configure.ac doesn't check all required headers - breaks Debian derivatives. Key: QPID-2457 URL: https://issues.apache.org/jira/browse/QPID-2457 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Environment: Ubuntu 8.04 - hardy Reporter: Neil Wilson Priority: Minor Debian splits out the libboost library into several separate packages. The configure.ac needs to check more headers in boost to make sure that the Debian splits are catered for. (Note these may be Debian dependencies that aren't handled properly - however if configure handles it, it looks better than a make failure). Headers that currently fail are: boost/program_options.hpp boost/serialization/split_member.hpp boost/filesystem/operations.hpp boost/filesystem/path.hpp boost/test/unit_test.hpp boost/regex.hpp -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2457) configure.ac doesn't check all required headers - breaks Debian derivatives.
[ https://issues.apache.org/jira/browse/QPID-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12847457#action_12847457 ] Carl Trieloff commented on QPID-2457: - Once you have a set of pacthes for trunk to make it go, send a mail to dev@qpid.apache.org with a list of JIRA and notes so that one of us work them into the tree for you. Carl configure.ac doesn't check all required headers - breaks Debian derivatives. Key: QPID-2457 URL: https://issues.apache.org/jira/browse/QPID-2457 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Environment: Ubuntu 8.04 - hardy Reporter: Neil Wilson Priority: Minor Debian splits out the libboost library into several separate packages. The configure.ac needs to check more headers in boost to make sure that the Debian splits are catered for. (Note these may be Debian dependencies that aren't handled properly - however if configure handles it, it looks better than a make failure). Headers that currently fail are: boost/program_options.hpp boost/serialization/split_member.hpp boost/filesystem/operations.hpp boost/filesystem/path.hpp boost/test/unit_test.hpp boost/regex.hpp -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Why do we create the cpp/src/tests/python dir?
Gordon Sim wrote: On 03/19/2010 02:23 PM, Alan Conway wrote: I think the clean way out is to make the python project a dependency of the C++ project just like it depends on boost or other tools. I.e. to run the tests you must *install* the python project, and the tests pick up components via standard PATH and PYTHONPATH env vars. Assuming I understand this correctly, we would have to reinstall every time we needed to pick up any change in the python client or tools. Unlike with boost or other tools, that's likely to occur quite frequently. I'm not arguing against your suggestion however, just making an observation on the impact as I see it. There is also a dependency on tests, which would probably be more problematic since it's not uncommon to fix/add something to the broker and also change these tests in a single commit. --Rafael - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
