[jira] Created: (QPID-2551) python client cannot create a receiver to the xml exchange
python client cannot create a receiver to the xml exchange
--
Key: QPID-2551
URL: https://issues.apache.org/jira/browse/QPID-2551
Project: Qpid
Issue Type: Bug
Components: Python Client
Affects Versions: 0.7
Reporter: Gordon Sim
Assignee: Rafael H. Schloming
Fix For: 0.7
E.g. drain -f xml; {link:{x-bindings: [{exchange:
xml,key:content_feed,arguments:{xquery:\declare variable \$control external;
./message/id mod 2 = 1 or \$control = 'end'\}}]}}
this fails as there is an extra bind request created with no arguments, which
the XML exchange rejects as invalid.
broker log:
2010-04-27 09:59:54 trace RECV [127.0.0.1:48880]: Frame[BEbe; channel=0;
{QueueDeclareBody: queue=6a6be132-7e41-4506-a651-d7dd27055a28:0.0; exclusive=1;
auto-delete=1; }]
2010-04-27 09:59:54 info Queue 6a6be132-7e41-4506-a651-d7dd27055a28:0.0:
Policy created: type=reject; maxCount=0; maxSize=104857600
2010-04-27 09:59:54 trace RECV [127.0.0.1:48880]: Frame[BEbe; channel=0;
{ExchangeBindBody: queue=6a6be132-7e41-4506-a651-d7dd27055a28:0.0;
exchange=xml; }] == this is the problem
2010-04-27 09:59:54 error Execution exception: internal-error: Could not parse
xquery: (../../src/qpid/xml/XmlExchange.cpp:118)
2010-04-27 09:59:54 trace RECV [127.0.0.1:48880]: Frame[BEbe; channel=0;
{ExchangeBindBody: queue=message_queue; exchange=xml; binding-key=content_feed;
arguments={xquery:V2:78:str16(declare variable $control external; ./message/id
mod 2 = 1 or $control = 'end')}; }]
2010-04-27 09:59:54 trace RECV [127.0.0.1:48880]: Frame[BEbe; channel=0;
{MessageSubscribeBody: queue=6a6be132-7e41-4506-a651-d7dd27055a28:0.0;
destination=0; acquire-mode=0; }]
--
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-2538) Add XML configuration syntax for ACLs in Java broker
[
https://issues.apache.org/jira/browse/QPID-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12861322#action_12861322
]
Andrew Kennedy commented on QPID-2538:
--
this is an example of a mapping between xml and c++ acl syntax.
== virtualhosts.xml ==
virtualhosts
virtualhost
localhost
security
!-- access control list (plain text AND xml) configuration --
access
plugin
org.apache.qpid.server.security.access.plugin.AccessControl
/plugin
config
!-- plain text --
plain file=${conf}/access-control /
!-- external xml c.f. firewall --
xml file=${conf}/access.xml /
!-- internal xml (alternative) --
rules
!-- acl entries ... --
/rules
/config
/accses
/security
/localhost
/virtualhost
/virtualhosts
==
== access.xml ==
rules
!-- allow adk access to this virtual host --
acl permission=ALLOW identity=adk operation=ACCESS
object=VIRTUALHOST /
!-- allow creating temporary queues and queues with names matching adk.*
--
acl permission=ALLOW-LOG identity=adk operation=BIND
object=EXCHANGE
properties
property key=routingKey value=adk.* /
property key=name value=amq.direct /
/properties
/acl
acl permission=ALLOW-LOG identity=adk operation=BIND
object=EXCHANGE
properties
property key=routingKey value=tmp.* /
property key=name value=amq.direct /
/properties
/acl
acl permission=ALLOW identity=adk operation=CREATE object=QUEUE
properties
property key=name value=adk.* /
property key=owner value=adk /
/properties
/acl
acl permission=ALLOW identity=adk operation=CREATE object=QUEUE
properties
property key=temporary value=true /
property key=owner value=adk /
/properties
/acl
!-- allow publish and consume of messages on the queues --
acl permission=ALLOW identity=adk operation=CONSUME object=QUEUE
properties
property key=name value=adk.* /
/properties
/acl
acl permission=ALLOW identity=adk operation=PUBLISH object=QUEUE
properties
property key=name value=adk.* /
/properties
/acl
!-- default deny --
aclpermission=DENY identity=ANY
operation=ALL object=ALL /
/rules
==
== access-control ==
# allow adk access to this virtual host
ALLOW a...@iterator ACCESS VIRTUALHOST
# allow creating temporary queues and queues with names matching adk.*
ALLOW-LOG adk BIND EXCHANGE routingKey=adk.* name=amq.direct
ALLOW-LOG adk BIND EXCHANGE routingKey=tmp.* name=amq.direct
ALLOW adk CREATE QUEUE name=adk.* owner=adk
ALLOW adk CREATE QUEUE temporary=true owner=adk
# allow publish and consume of messages on the queues
ALLOW adk CONSUME QUEUE name=adk.*
ALLOW adk PUBLISH QUEUE name=adk.*
# default deny
DENY ANY ALL ALL
==
Add XML configuration syntax for ACLs in Java broker
Key: QPID-2538
URL: https://issues.apache.org/jira/browse/QPID-2538
Project: Qpid
Issue Type: Sub-task
Components: Java Broker
Reporter: Andrew Kennedy
Fix For: 0.7
--
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: JavaBroker v2 ACLs (QPID-2476)
On 23 April 2010 16:24, Rajith Attapattu rajit...@gmail.com wrote: Andrew, Sorry about the late reply. I've been a bit swamped the past 2 weeks. On Fri, Apr 16, 2010 at 5:29 AM, Andrew Kennedy andrewinternatio...@gmail.com wrote: at the moment i am going to simply port the C++ file format to Java, and access it from the existing XML configuration via a link to a separate file, but i think the ACLs should also be expressible as a pure XML configuration, to be documented later. I think for all intents and purposes we should only have a single file format. I think we debated this point and agreed on the current file format. It's not just the c++ file format, but the acl file format for Qpid as well. Also I'd question the value of having an XML based format. Is there a specific reason for this? as for an xml file format for ACLs, i assumed that this wasreallyjust a standard requirement for enterprise Java products in this space, and is expected. also, if we create an XSD schema then it makes it easy for administrators to create ACLs using a validating XML editor. the XML configuration used for the rest of the java broker would make it easy to include this extra ACL data in the main config file or in the virtualhosts file, as needed. as it stands, the internal representation of ACLs can be mapped to from any format, and it is also possible to save a modified or edited ACL configuration as whatever format is convenient. it would be fairly trivial to implement this in a straightforward mapping of the plain text file (see access.xml file contents below) acl permission=ALLOW-LOG identity=adk operation=BIND object=EXCHANGE properties property key=routingKey value=adk.* / property key=name value=amq.direct / /properties /acl is the XML equivalent opf the following: ALLOW-LOG adk BIND EXCHANGE routingKey=adk.* name=amq.direct adk. -- -- andrew d kennedy ? edinburgh : +44 7941 197 134 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2541) Separate Group an ACL configuration and make group sources pluggable
[
https://issues.apache.org/jira/browse/QPID-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12861328#action_12861328
]
Andrew Kennedy commented on QPID-2541:
--
a suggested api for the plugin is shown below (although only the first method
is needed) followed by an example of how various group plugins would be
configured in the main java broker XML configuration file. see the
authentication mechanisms in the Java broker for an example of how this could
be implemented.
== groups plugin api ==
/** Check if a user is in a group? */
boolean checkMembership(String userName, String groupName);
/** Get the users that are members of a group. */
ListString getMembership(String groupName);
/** Get the groups that a user is a member of. */
ListString getGroups(String userName);
==
== config.xml ==
broker
security
!-- group file configuration --
groups
plugin
org.apache.qpid.server.security.groups.plugin.UnixFile
/plugin
file${QPID_HOME}/etc/group/file
/groups
!-- widows active directory configuration --
groups
plugin
org.apache.qpid.server.security.groups.plugin.ActiveDirectory
/plugin
root
server name=192.168.0.1
config name=key value=data /
config name=key value=data /
config name=key value=data /
/server
/root
/groups
!-- LDAP / JNDI servers --
groups
plugin
org.apache.qpid.server.security.groups.plugin.LDAPServer
org.apache.qpid.server.security.groups.plugin.JNDIServer
/plugin
server username=user password=pass ip=192.168.0.2 /
/groups
/security
/broker
==
Separate Group an ACL configuration and make group sources pluggable
Key: QPID-2541
URL: https://issues.apache.org/jira/browse/QPID-2541
Project: Qpid
Issue Type: Sub-task
Components: Java Broker
Reporter: Andrew Kennedy
Fix For: 0.7
--
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: JavaBroker v2 ACLs (QPID-2476)
On 23 April 2010 16:01, Marnie McCormack marnie.mccorm...@googlemail.com wrote: On Fri, Apr 16, 2010 at 10:29 AM, Andrew Kennedy andrewinternatio...@gmail.com wrote: hi. perhaps also splitting group configuration and ACL configuration into separate files, since these are obviously quite different things, and it is foreseeable that groups would be desirable to load via an external authentication or directory service. I think splitting out groups and ACL from the one file would be a good thing, I don't see why we'd maintain them in the same place. I don't know how the groups are used (aside from ACLs) in the C++ broker though ? Groups would often be anticipated to come from another source, ideally, to negate the need to maintain multiple user credentials. the changes i am suggesting for the acl file format are fairly minor, to be honest, and i will expand on this in a later message. i also agree with all the points made on-list about group definitions. there are several mechanisms available for accessing group and role informastion, such as the basic unix /etc file format, microsoft active directory or plain LDAP or JNDI. Also, proprietary SSO systems, or mechanisms like siteminder or perhaps links to a kerberos authentication system could be used. this would function with a pluggable group access module, similar to the ACL and authentication modules. the plugin would need to allow verification of an authenticated principal's membership in a group. this could be achieved at initial authentication, however for long-lived connections this might cause problems if group memberships are changed to add permissions mwhile the broker is running. the plugin could integrate with an authenticationm mechanism and share code and configuration, simply offering an extra interface via a new group access API. in fact, the authentication code provides a good model for implementation of different group access mechanisms. the api for the plugin must, at minimum support a method that checks if a given user is a member of a particular group name: boolean checkMembership(String userName, String groupName); examples of plugin classes would be: org.apache.qpid.server.security.groups.plugin.UnixFile org.apache.qpid.server.security.groups.plugin.ActiveDirectory org.apache.qpid.server.security.groups.plugin.LDAPServer org.apache.qpid.server.security.groups.plugin.JNDIServer cheers, adk. -- -- andrew d kennedy ? edinburgh : +44 7941 197 134 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2552) broker memory leaks
broker memory leaks --- Key: QPID-2552 URL: https://issues.apache.org/jira/browse/QPID-2552 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.7 Environment: Fedora Rawhide x86_64 glibc-2.11.90-20.x86_64 valgrind-3.5.0-16.fc14.x86_64 gcc-c++-4.4.3-18.fc14.x86_64 boost-devel-1.41.0-8.fc14.x86_64 Reporter: Jan Sarenik Priority: Critical Fix For: 0.7 There was a recent patch to Glibc which added another sanity check for fastbins (I personally do not understand the whole fastbin concept yet and when the error first occured, I was mislead by myself and thought it has something to do with prelink, but now I have clean system without prelink with all the binaries exactly the same as they come in packages). See http://repo.or.cz/w/glibc.git/commit/90a3055e8bdd9308eceeadc0b37278f324ec6b5d The problem here is, that qpidd is very easily (though randomly) caught by this check. This often happens during 'make check' and it successfully renders any of the tests as false-positive. I was discussing this issue with Jakub Jelinek (Glibc hacker) as I was not sure if the problem resides on our side or not and he suggested to use Valgrind or ElectricFence. So I installed Valgrind and I am kindly asking you, the developers to fix the memory leaks in Qpid. Have a look at the attached log of 'make check' on r938298 of qpid trunk (with little clean-up patches also included in attachment). The problem should arise in any of the modern GNU/Linux distributions. Even the beta RHEL6 contains new Glibc with mentioned patch so I am setting critical priority for this. I did not try to compile the whole thing against older (stable?) boost version, but can do that easily if it helps in extracting the root cause of the problem. No idea how suspicious boost can be in this case. Get back to me if there is anything else I can help with or more info to add. -- 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-2552) broker memory leaks
[ https://issues.apache.org/jira/browse/QPID-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Sarenik updated QPID-2552: -- Attachment: qpid-cpp-r938298-makecheck.log The log of 'make check' run on r938298 svn trunk (only the little patch applied, see other attachment) broker memory leaks --- Key: QPID-2552 URL: https://issues.apache.org/jira/browse/QPID-2552 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.7 Environment: Fedora Rawhide x86_64 glibc-2.11.90-20.x86_64 valgrind-3.5.0-16.fc14.x86_64 gcc-c++-4.4.3-18.fc14.x86_64 boost-devel-1.41.0-8.fc14.x86_64 Reporter: Jan Sarenik Priority: Critical Fix For: 0.7 Attachments: qpid-cpp-r938298-makecheck.log There was a recent patch to Glibc which added another sanity check for fastbins (I personally do not understand the whole fastbin concept yet and when the error first occured, I was mislead by myself and thought it has something to do with prelink, but now I have clean system without prelink with all the binaries exactly the same as they come in packages). See http://repo.or.cz/w/glibc.git/commit/90a3055e8bdd9308eceeadc0b37278f324ec6b5d The problem here is, that qpidd is very easily (though randomly) caught by this check. This often happens during 'make check' and it successfully renders any of the tests as false-positive. I was discussing this issue with Jakub Jelinek (Glibc hacker) as I was not sure if the problem resides on our side or not and he suggested to use Valgrind or ElectricFence. So I installed Valgrind and I am kindly asking you, the developers to fix the memory leaks in Qpid. Have a look at the attached log of 'make check' on r938298 of qpid trunk (with little clean-up patches also included in attachment). The problem should arise in any of the modern GNU/Linux distributions. Even the beta RHEL6 contains new Glibc with mentioned patch so I am setting critical priority for this. I did not try to compile the whole thing against older (stable?) boost version, but can do that easily if it helps in extracting the root cause of the problem. No idea how suspicious boost can be in this case. Get back to me if there is anything else I can help with or more info to add. -- 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-2552) broker memory leaks
[ https://issues.apache.org/jira/browse/QPID-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12861334#action_12861334 ] Jan Sarenik commented on QPID-2552: --- In the log file look for lines simillar to following one: *** glibc detected *** /home/jsarenik/pub/git/qpid/cpp/src/.libs/lt-qpidd: invalid fastbin entry (free): 0x01bdde80 *** broker memory leaks --- Key: QPID-2552 URL: https://issues.apache.org/jira/browse/QPID-2552 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.7 Environment: Fedora Rawhide x86_64 glibc-2.11.90-20.x86_64 valgrind-3.5.0-16.fc14.x86_64 gcc-c++-4.4.3-18.fc14.x86_64 boost-devel-1.41.0-8.fc14.x86_64 Reporter: Jan Sarenik Priority: Critical Fix For: 0.7 Attachments: qpid-cpp-r938298-makecheck.log, qpid-r938298.diff There was a recent patch to Glibc which added another sanity check for fastbins (I personally do not understand the whole fastbin concept yet and when the error first occured, I was mislead by myself and thought it has something to do with prelink, but now I have clean system without prelink with all the binaries exactly the same as they come in packages). See http://repo.or.cz/w/glibc.git/commit/90a3055e8bdd9308eceeadc0b37278f324ec6b5d The problem here is, that qpidd is very easily (though randomly) caught by this check. This often happens during 'make check' and it successfully renders any of the tests as false-positive. I was discussing this issue with Jakub Jelinek (Glibc hacker) as I was not sure if the problem resides on our side or not and he suggested to use Valgrind or ElectricFence. So I installed Valgrind and I am kindly asking you, the developers to fix the memory leaks in Qpid. Have a look at the attached log of 'make check' on r938298 of qpid trunk (with little clean-up patches also included in attachment). The problem should arise in any of the modern GNU/Linux distributions. Even the beta RHEL6 contains new Glibc with mentioned patch so I am setting critical priority for this. I did not try to compile the whole thing against older (stable?) boost version, but can do that easily if it helps in extracting the root cause of the problem. No idea how suspicious boost can be in this case. Get back to me if there is anything else I can help with or more info to add. -- 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-2553) CMakeLists wrong file name
CMakeLists wrong file name --- Key: QPID-2553 URL: https://issues.apache.org/jira/browse/QPID-2553 Project: Qpid Issue Type: Bug Components: Documentation Affects Versions: 0.7 Reporter: Bruno Matos In cpp/docs/api/CMakeLists.txt: 29 the file name is typed incorrectly. -- 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-2553) CMakeLists wrong file name
[ https://issues.apache.org/jira/browse/QPID-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Matos updated QPID-2553: -- Attachment: developer-docs.diff Possible patch CMakeLists wrong file name --- Key: QPID-2553 URL: https://issues.apache.org/jira/browse/QPID-2553 Project: Qpid Issue Type: Bug Components: Documentation Affects Versions: 0.7 Reporter: Bruno Matos Attachments: developer-docs.diff Original Estimate: 0.02h Remaining Estimate: 0.02h In cpp/docs/api/CMakeLists.txt: 29 the file name is typed incorrectly. -- 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-2552) broker memory leaks
[ https://issues.apache.org/jira/browse/QPID-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reassigned QPID-2552: Assignee: Gordon Sim broker memory leaks --- Key: QPID-2552 URL: https://issues.apache.org/jira/browse/QPID-2552 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.7 Environment: Fedora Rawhide x86_64 glibc-2.11.90-20.x86_64 valgrind-3.5.0-16.fc14.x86_64 gcc-c++-4.4.3-18.fc14.x86_64 boost-devel-1.41.0-8.fc14.x86_64 Reporter: Jan Sarenik Assignee: Gordon Sim Priority: Critical Fix For: 0.7 Attachments: qpid-cpp-r938298-makecheck.log, qpid-r938298.diff There was a recent patch to Glibc which added another sanity check for fastbins (I personally do not understand the whole fastbin concept yet and when the error first occured, I was mislead by myself and thought it has something to do with prelink, but now I have clean system without prelink with all the binaries exactly the same as they come in packages). See http://repo.or.cz/w/glibc.git/commit/90a3055e8bdd9308eceeadc0b37278f324ec6b5d The problem here is, that qpidd is very easily (though randomly) caught by this check. This often happens during 'make check' and it successfully renders any of the tests as false-positive. I was discussing this issue with Jakub Jelinek (Glibc hacker) as I was not sure if the problem resides on our side or not and he suggested to use Valgrind or ElectricFence. So I installed Valgrind and I am kindly asking you, the developers to fix the memory leaks in Qpid. Have a look at the attached log of 'make check' on r938298 of qpid trunk (with little clean-up patches also included in attachment). The problem should arise in any of the modern GNU/Linux distributions. Even the beta RHEL6 contains new Glibc with mentioned patch so I am setting critical priority for this. I did not try to compile the whole thing against older (stable?) boost version, but can do that easily if it helps in extracting the root cause of the problem. No idea how suspicious boost can be in this case. Get back to me if there is anything else I can help with or more info to add. -- 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
Building qpidc on CentOS 5.3 (CGV 5.3)
Hi Qpid developers, rpmbuild --bb qpidc.spec fails to build due to: Failed: Unknown NSS error code. [-5961] (qpid/sys/ssl/SslSocket.cpp:154) FAIL: ssl_test PASS: start_broker PASS: client_test 2227.82 595.493 2323.26 2.26881 PASS: quick_perftest PASS: quick_topictest Skipping header test as python libs not found PASS: run_header_test All expected messages were retrieved. PASS: quick_txtest WARNING: No python tests. /usr/src/redhat/BUILD/qpidc-0.5.752581/src/tests/../../../python not found. PASS: python_tests PASS: stop_broker PASS: run_federation_tests PASS: run_acl_tests PASS: run_cli_tests Skipping replication test, plugins not built or python utils not located PASS: replication_test What is reason? What am I lacking? Python 2.4.3 is installed. So is python libs afaics. Thanks! Regards, ToreL snip g++ -pedantic -Wall -Wextra -Wno-shadow -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long -Wvolatile-register-var -Winvalid-pch -Wno-system-headers -Woverloaded-virtual -DBOOST_TEST_DYN_LINK -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -DNDEBUG -O3 -o .libs/DispatcherTest DispatcherTest.o -L/usr/lib/openais -L/usr/lib64/openais -L/usr/lib/corosync -L/usr/lib64/corosync /usr/src/redhat/BUILD/qpidc-0.5.752581/src/tests/../.libs/libqpidcommon.so -lboost_program_options -lboost_filesystem -luuid -ldl -lrt -lsasl2 creating DispatcherTest make[3]: Leaving directory `/usr/src/redhat/BUILD/qpidc-0.5.752581/src/tests' make check-TESTS make[3]: Entering directory `/usr/src/redhat/BUILD/qpidc-0.5.752581/src/tests' Running 211 test cases... 0% 10 20 30 40 50 60 70 80 90 100% ||||||||||| *** *** No errors detected PASS: unit_test === WARNING: NOT RUNNING AIS TESTS == Tests that depend on the openais library (used for clustering) will not be run because: You are not a member of the ais group. The aisexec or corosync daemon is not running as root == PASS: ais_check rm: cannot remove `cluster.ports': No such file or directory PASS: federated_cluster_test PASS: clustered_replication_test Generating key. This may take a few moments... Running SSL test on port 12979 Failed: Unknown NSS error code. [-5961] (qpid/sys/ssl/SslSocket.cpp:154) FAIL: ssl_test PASS: start_broker PASS: client_test 2227.82 595.493 2323.26 2.26881 PASS: quick_perftest PASS: quick_topictest Skipping header test as python libs not found PASS: run_header_test All expected messages were retrieved. PASS: quick_txtest WARNING: No python tests. /usr/src/redhat/BUILD/qpidc-0.5.752581/src/tests/../../../python not found. PASS: python_tests PASS: stop_broker PASS: run_federation_tests PASS: run_acl_tests PASS: run_cli_tests Skipping replication test, plugins not built or python utils not located PASS: replication_test 1 of 17 tests failed Please report to dev@qpid.apache.org make[3]: *** [check-TESTS] Error 1 make[3]: Leaving directory `/usr/src/redhat/BUILD/qpidc-0.5.752581/src/tests' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/usr/src/redhat/BUILD/qpidc-0.5.752581/src/tests' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/usr/src/redhat/BUILD/qpidc-0.5.752581/src' make: *** [check-recursive] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.96942 (%check) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.96942 (%check) Mvh / Best Regards, -- MSc Tore H. Larsen Sr. Systems Engineer, TSG Instrumentation CGGVeritas MAPL TSG tel: +47 56 11 48 36 mob:+47 918 33 670 fax: +47 56 11 48 01 www.cggveritas.com mailto:tore.hoivaag.lar...@cggveritas.com CGGVeritas Services Norway AS Carl Konows gate 34 N-5162 Laksevåg - Bergen Norway - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Building qpidc on CentOS 5.3 (CGV 5.3)
On 04/27/2010 11:44 AM, Larsen, Tore Høivaag wrote: Hi Qpid developers, rpmbuild --bb qpidc.spec fails to build due to: Failed: Unknown NSS error code. [-5961] (qpid/sys/ssl/SslSocket.cpp:154) FAIL: ssl_test Not sure why the ssl test would fail. Previously I've seen that where the cert is stale (not relevant here as they have just been generated) or where the hostname is not valid (that is now changed to use 127.0.0.1). Try ping $(hostname) PASS: start_broker PASS: client_test 2227.82 595.493 2323.26 2.26881 PASS: quick_perftest PASS: quick_topictest Skipping header test as python libs not found PASS: run_header_test All expected messages were retrieved. PASS: quick_txtest WARNING: No python tests. /usr/src/redhat/BUILD/qpidc-0.5.752581/src/tests/../../../python not found. This is because the test scripts expect the qpid python libs and tests to be in a specific location relative to the source which they aren't in this case. This is nothing to worry about though. PASS: python_tests PASS: stop_broker PASS: run_federation_tests PASS: run_acl_tests PASS: run_cli_tests Skipping replication test, plugins not built or python utils not located PASS: replication_test What is reason? What am I lacking? Python 2.4.3 is installed. So is python libs afaics. Thanks! Regards, ToreL snip g++ -pedantic -Wall -Wextra -Wno-shadow -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long -Wvolatile-register-var -Winvalid-pch -Wno-system-headers -Woverloaded-virtual -DBOOST_TEST_DYN_LINK -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -DNDEBUG -O3 -o .libs/DispatcherTest DispatcherTest.o -L/usr/lib/openais -L/usr/lib64/openais -L/usr/lib/corosync -L/usr/lib64/corosync /usr/src/redhat/BUILD/qpidc-0.5.752581/src/tests/../.libs/libqpidcommon.so -lboost_program_options -lboost_filesystem -luuid -ldl -lrt -lsasl2 creating DispatcherTest make[3]: Leaving directory `/usr/src/redhat/BUILD/qpidc-0.5.752581/src/tests' make check-TESTS make[3]: Entering directory `/usr/src/redhat/BUILD/qpidc-0.5.752581/src/tests' Running 211 test cases... 0% 10 20 30 40 50 60 70 80 90 100% ||||||||||| *** *** No errors detected PASS: unit_test === WARNING: NOT RUNNING AIS TESTS == Tests that depend on the openais library (used for clustering) will not be run because: You are not a member of the ais group. The aisexec or corosync daemon is not running as root == PASS: ais_check rm: cannot remove `cluster.ports': No such file or directory PASS: federated_cluster_test PASS: clustered_replication_test Generating key. This may take a few moments... Running SSL test on port 12979 Failed: Unknown NSS error code. [-5961] (qpid/sys/ssl/SslSocket.cpp:154) FAIL: ssl_test PASS: start_broker PASS: client_test 2227.82 595.493 2323.26 2.26881 PASS: quick_perftest PASS: quick_topictest Skipping header test as python libs not found PASS: run_header_test All expected messages were retrieved. PASS: quick_txtest WARNING: No python tests. /usr/src/redhat/BUILD/qpidc-0.5.752581/src/tests/../../../python not found. PASS: python_tests PASS: stop_broker PASS: run_federation_tests PASS: run_acl_tests PASS: run_cli_tests Skipping replication test, plugins not built or python utils not located PASS: replication_test 1 of 17 tests failed Please report to dev@qpid.apache.org make[3]: *** [check-TESTS] Error 1 make[3]: Leaving directory `/usr/src/redhat/BUILD/qpidc-0.5.752581/src/tests' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/usr/src/redhat/BUILD/qpidc-0.5.752581/src/tests' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/usr/src/redhat/BUILD/qpidc-0.5.752581/src' make: *** [check-recursive] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.96942 (%check) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.96942 (%check) Mvh / Best Regards, -- MSc Tore H. Larsen Sr. Systems Engineer, TSG Instrumentation CGGVeritas MAPL TSG tel: +47 56 11 48 36 mob:+47 918 33 670 fax: +47 56 11 48 01 www.cggveritas.com mailto:tore.hoivaag.lar...@cggveritas.com CGGVeritas Services Norway AS Carl Konows gate 34 N-5162 Laksevåg - Bergen Norway - 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
[jira] Assigned: (QPID-2553) CMakeLists wrong file name
[ https://issues.apache.org/jira/browse/QPID-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Huston reassigned QPID-2553: -- Assignee: Steve Huston CMakeLists wrong file name --- Key: QPID-2553 URL: https://issues.apache.org/jira/browse/QPID-2553 Project: Qpid Issue Type: Bug Components: Documentation Affects Versions: 0.7 Reporter: Bruno Matos Assignee: Steve Huston Attachments: developer-docs.diff Original Estimate: 0.02h Remaining Estimate: 0.02h In cpp/docs/api/CMakeLists.txt: 29 the file name is typed incorrectly. -- 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-2553) CMakeLists wrong file name
[ https://issues.apache.org/jira/browse/QPID-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Huston resolved QPID-2553. Fix Version/s: 0.7 Resolution: Fixed Applied patch on trunk r938415. Thanks! CMakeLists wrong file name --- Key: QPID-2553 URL: https://issues.apache.org/jira/browse/QPID-2553 Project: Qpid Issue Type: Bug Components: Documentation Affects Versions: 0.7 Reporter: Bruno Matos Assignee: Steve Huston Fix For: 0.7 Attachments: developer-docs.diff Original Estimate: 0.02h Remaining Estimate: 0.02h In cpp/docs/api/CMakeLists.txt: 29 the file name is typed incorrectly. -- 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: JavaBroker v2 ACLs (QPID-2476)
On 04/27/2010 10:22 AM, Andrew Kennedy wrote: as for an xml file format for ACLs, i assumed that this wasreallyjust a standard requirement for enterprise Java products in this space, and is expected. also, if we create an XSD schema then it makes it easy for administrators to create ACLs using a validating XML editor. On the topic of xml formats for ACLs, is anyone familiar with XACML? I was asked recently whether this had ever been considered as a format for Qpid, and hadn't heard of it before. Wondered if anyone else had any thoughts on it? - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: JavaBroker v2 ACLs (QPID-2476)
I've heard of a few projects using the Oracle Ent Services version of XACML, and of some that have failed to build their own engine using XACML, some using other vendor incarnations. Some projects chose Drools, though I couldn't spot whether that was with XACML or instead of from the docs. Marnie On Tue, Apr 27, 2010 at 1:29 PM, Gordon Sim g...@redhat.com wrote: On 04/27/2010 10:22 AM, Andrew Kennedy wrote: as for an xml file format for ACLs, i assumed that this wasreallyjust a standard requirement for enterprise Java products in this space, and is expected. also, if we create an XSD schema then it makes it easy for administrators to create ACLs using a validating XML editor. On the topic of xml formats for ACLs, is anyone familiar with XACML? I was asked recently whether this had ever been considered as a format for Qpid, and hadn't heard of it before. Wondered if anyone else had any thoughts on it? - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Proposed directory structure for web site
I think we're converging on using svnpubsub to maintain documentation. We need to determine our directory structure. Any of these structures make sense to me. In all cases, qpid.apache.org includes Rajith's index.html and associated .css, etc., as well as the DocBook generated files. It would contain links to the download directory and the Wiki, but not include them. Here are some possible directory structures: 1. Make the web site a subdirectory of doc doc/src -- XML source files doc/build -- the build directory doc/qpid.apache.org -- the Apache web site, starting with index.html, and including all documentation. 2. Make the web site a parallel directory to doc qpd/cpp qpid/doc qpid/qpid.apache.org I suppose it would also be logically possible to have the web site be on a separate svn branch, or even in a separate svn repository. I'm inclined to go with #2. Does anyone else have strong feelings on this? Jonathan - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: JavaBroker v2 ACLs (QPID-2476)
Andrew, since you have already opened several JIRA's focused on specific areas, lets continue the discussion there. On Tue, Apr 27, 2010 at 5:39 AM, Andrew Kennedy andrewinternatio...@gmail.com wrote: On 23 April 2010 16:01, Marnie McCormack marnie.mccorm...@googlemail.com wrote: On Fri, Apr 16, 2010 at 10:29 AM, Andrew Kennedy andrewinternatio...@gmail.com wrote: hi. perhaps also splitting group configuration and ACL configuration into separate files, since these are obviously quite different things, and it is foreseeable that groups would be desirable to load via an external authentication or directory service. I think splitting out groups and ACL from the one file would be a good thing, I don't see why we'd maintain them in the same place. I don't know how the groups are used (aside from ACLs) in the C++ broker though ? Groups would often be anticipated to come from another source, ideally, to negate the need to maintain multiple user credentials. the changes i am suggesting for the acl file format are fairly minor, to be honest, and i will expand on this in a later message. i also agree with all the points made on-list about group definitions. there are several mechanisms available for accessing group and role informastion, such as the basic unix /etc file format, microsoft active directory or plain LDAP or JNDI. Also, proprietary SSO systems, or mechanisms like siteminder or perhaps links to a kerberos authentication system could be used. this would function with a pluggable group access module, similar to the ACL and authentication modules. the plugin would need to allow verification of an authenticated principal's membership in a group. this could be achieved at initial authentication, however for long-lived connections this might cause problems if group memberships are changed to add permissions mwhile the broker is running. the plugin could integrate with an authenticationm mechanism and share code and configuration, simply offering an extra interface via a new group access API. in fact, the authentication code provides a good model for implementation of different group access mechanisms. the api for the plugin must, at minimum support a method that checks if a given user is a member of a particular group name: boolean checkMembership(String userName, String groupName); examples of plugin classes would be: org.apache.qpid.server.security.groups.plugin.UnixFile org.apache.qpid.server.security.groups.plugin.ActiveDirectory org.apache.qpid.server.security.groups.plugin.LDAPServer org.apache.qpid.server.security.groups.plugin.JNDIServer cheers, adk. -- -- andrew d kennedy ? edinburgh : +44 7941 197 134 - 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] Commented: (QPID-2538) Add XML configuration syntax for ACLs in Java broker
[ https://issues.apache.org/jira/browse/QPID-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12861395#action_12861395 ] Rajith Attapattu commented on QPID-2538: Andrew, If you think we'd make administrators life easy by having an XML incarnation of the ACL format then I am fine with it, all though I am not convinced. Also I am not really convinced that you need XML based config to make it look enterpricy either :) To me the current file format is very simple, compact and less error prone than an equivalent in XML. However I'm not going to stand in your way of supporting an XML version if you think the following is reasonable. 1. The current ACL file format is not C++ specific. We should have that as the Qpid ACL file format and supported by both brokers. 2. The XML based version is an alternative file format. Add XML configuration syntax for ACLs in Java broker Key: QPID-2538 URL: https://issues.apache.org/jira/browse/QPID-2538 Project: Qpid Issue Type: Sub-task Components: Java Broker Reporter: Andrew Kennedy Fix For: 0.7 -- 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-2541) Separate Group an ACL configuration and make group sources pluggable
[ https://issues.apache.org/jira/browse/QPID-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12861400#action_12861400 ] Rajith Attapattu commented on QPID-2541: Excellent ! I agree that both brokers needs to have the groups mechanism pluggable. However we also need to think about how these groups will correspond to the users handled via the authentication mechanism. Here are some questions. 1. If we use LDAP, unix file or active directory, is that only used to manage the groups? will they be also used with authentication via the SASL EXTERNAL mechanism? 2. If we are not going to use the above mechanisms for authentication, then how do propose to tie in them? (I'd question the value of using them for just managing groups, but perhaps I may have missed something) The authentication and authorization mechanisms work hand in hand and any grouping has to be thought in the context of both. Separate Group an ACL configuration and make group sources pluggable Key: QPID-2541 URL: https://issues.apache.org/jira/browse/QPID-2541 Project: Qpid Issue Type: Sub-task Components: Java Broker Reporter: Andrew Kennedy Fix For: 0.7 -- 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-2554) FE: have Session or Agent getObjects return a list of QMF objects based only on a _package name
FE: have Session or Agent getObjects return a list of QMF objects based only on a _package name --- Key: QPID-2554 URL: https://issues.apache.org/jira/browse/QPID-2554 Project: Qpid Issue Type: Improvement Components: Qpid Managment Framework Environment: All, Python Reporter: Pete MacKinnon Priority: Minor It would be nice if we could get a list of QMF objects without having to specify a _class for a _package. The _package alone should return a list of matching objects. This would make certain query applications easier and more intuitive. -- 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-2555) Qpid Info OSGI plugin
Qpid Info OSGI plugin - Key: QPID-2555 URL: https://issues.apache.org/jira/browse/QPID-2555 Project: Qpid Issue Type: New Feature Components: Java Broker Affects Versions: 0.7 Reporter: Sorin Suciu Priority: Minor Fix For: 0.7 This OSGI plugin is implementing an info service that would post broker information to a central location. It will activate on broker start and will http post the following information: QPID_HOME (eg /home/sorin/qpid-broker) QPID_WORK (eg /home/sorin) hostname (eg sorins-pc) ip (eg 192.168.1.24) java.class.path ( java.class.version (eg java.vm.name (eg os.arch (eg amd64) os.name (eg Linux) os.version (eg 2.6.18-128.7.1.el5) port (eg [5672]) sun.arch.data.model (eg 64) time (eg 2010-04-27 14:37:59.894+0100) user.dir (eg /home/sorin) user.name (eg sorin) user.timezone (eg Europe/London) This info is useful for large qpid deployments for automated monitoring purposes. -- 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
info OSGI plugin
Hi, In order to easily manage/monitor large qpid deployments, having an OSGI plugin that sends some basic information to a central location could be valuable from a support perspective. With this in mind, I have written a plugin to do this. The plugin will activate upon broker start only and post only if $QPID_WORK/etc/qpidinfo.properties does exist and contains a URL property pointing to a relevant URL that can accept and process the body of the http request. Raised JIRA QPID-2555 to cover the work. I would appreciate any feedback or suggestion on this... Thank you, -- Sorin
Re: Proposed directory structure for web site
On 04/27/2010 09:18 AM, Jonathan Robie wrote: 2. Make the web site a parallel directory to doc qpd/cpp qpid/doc qpid/qpid.apache.org This is what I'll do if nobody complains ;- Jonathan - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Proposed directory structure for web site
Jonathan Robie wrote: I think we're converging on using svnpubsub to maintain documentation. We need to determine our directory structure. Any of these structures make sense to me. In all cases, qpid.apache.org includes Rajith's index.html and associated .css, etc., as well as the DocBook generated files. It would contain links to the download directory and the Wiki, but not include them. Here are some possible directory structures: 1. Make the web site a subdirectory of doc doc/src -- XML source files doc/build -- the build directory doc/qpid.apache.org -- the Apache web site, starting with index.html, and including all documentation. 2. Make the web site a parallel directory to doc qpd/cpp qpid/doc qpid/qpid.apache.org I suppose it would also be logically possible to have the web site be on a separate svn branch, or even in a separate svn repository. I'm inclined to go with #2. Does anyone else have strong feelings on this? I think the web site really needs to be a distinct repo from the one we use for code for a few reasons. First, it is very confusing and generally considered horribly bad practice to mix source code and generated artifacts in the same repo. This confuses build systems to no end since most build systems are predicated upon the concept that they are the only thing that ever modifies the output files. However if the output files are in svn, then an svn update can cause an older file to appear newer than the input resulting in very confusing and broken behavior where the build system doesn't actually build everything that needs to be built. In this circumstance this could very easily lead to a broken and partially updated web site, especially when developers follow the best practice of doing an svn update prior to building in order to ensure they are working from fresh sources. Secondly, I don't want to be exposed to getting multi-megabyte diffs everytime someone updates the web site. Thirdly, the doc source should be part of the source release (i.e. an svn export), however the generated web site should *not*. And finally, I think that if we're using svnpubsub for the web site, we may well want to have other portions of the site in svn, not just the docs, so the web site repo should be organized to reflect this. --Rafael - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Proposed directory structure for web site
On Tue, 2010-04-27 at 10:47 -0400, Rafael Schloming wrote: Jonathan Robie wrote: I think we're converging on using svnpubsub to maintain documentation. We need to determine our directory structure. Any of these structures make sense to me. In all cases, qpid.apache.org includes Rajith's index.html and associated .css, etc., as well as the DocBook generated files. It would contain links to the download directory and the Wiki, but not include them. Here are some possible directory structures: 1. Make the web site a subdirectory of doc doc/src -- XML source files doc/build -- the build directory doc/qpid.apache.org -- the Apache web site, starting with index.html, and including all documentation. 2. Make the web site a parallel directory to doc qpd/cpp qpid/doc qpid/qpid.apache.org I suppose it would also be logically possible to have the web site be on a separate svn branch, or even in a separate svn repository. I'm inclined to go with #2. Does anyone else have strong feelings on this? I think the web site really needs to be a distinct repo from the one we use for code for a few reasons. First, it is very confusing and generally considered horribly bad practice to mix source code and generated artifacts in the same repo. This confuses build systems to no end since most build systems are predicated upon the concept that they are the only thing that ever modifies the output files. However if the output files are in svn, then an svn update can cause an older file to appear newer than the input resulting in very confusing and broken behavior where the build system doesn't actually build everything that needs to be built. In this circumstance this could very easily lead to a broken and partially updated web site, especially when developers follow the best practice of doing an svn update prior to building in order to ensure they are working from fresh sources. Secondly, I don't want to be exposed to getting multi-megabyte diffs everytime someone updates the web site. Thirdly, the doc source should be part of the source release (i.e. an svn export), however the generated web site should *not*. And finally, I think that if we're using svnpubsub for the web site, we may well want to have other portions of the site in svn, not just the docs, so the web site repo should be organized to reflect this. +1 - I agree on all counts. This might actually be a place where the stupid arrangement of our repo to have a superfluous qpid directory might help: Currently the repo structure is actually: qpid + trunk +qpid + branches +branchname + qpid So we could use the existing structure and put the checked in docs in parallel like: qpid/trunk/qpid.apache.org But actually I'd prefer a simpler solution - why not just make it completely separate viz: http://svn.apache.org/repos/asf/qpid/qpid.apache.org Either of these places will avoid the usual dev check out from picking up the checked in web source. If infrastructure are happy to give us a completely separate repo then this might be better as it would be easier to give it its own access control. Andrew - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
acl_test failing on Linux - anyoen seeing this in the automake build?
Hi folks, The acl_test has been failing on Linux in the cmake build for a couple of days now... Anyone seeing this on the autoconf build? http://www.riverace.com/CDash-1.4.2/viewTest.php?onlyfailedbuildid=586 It appears that maybe the broker is crashing on the first test execution. -Steve - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2556) QMF: signed integer in map and list types incorrectly converted to unsigned 64
QMF: signed integer in map and list types incorrectly converted to unsigned 64
--
Key: QPID-2556
URL: https://issues.apache.org/jira/browse/QPID-2556
Project: Qpid
Issue Type: Bug
Components: Qpid Managment Framework
Environment: Ruby QMF Console (wrapper)
Reporter: Ken Giusti
Priority: Minor
A management object that contains a list or a map which contains a signed
integer incorrectly converts the integer to unsigned.
Example: {'a' = -1} is received at the Ruby console as {'a' = 4294967295};
['a', -1] is received as ['a', 4294967295]
--
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-2555) Qpid Info OSGI plugin
[ https://issues.apache.org/jira/browse/QPID-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sorin Suciu updated QPID-2555: -- Attachment: info.tgz Qpid Info OSGI plugin - Key: QPID-2555 URL: https://issues.apache.org/jira/browse/QPID-2555 Project: Qpid Issue Type: New Feature Components: Java Broker Affects Versions: 0.7 Reporter: Sorin Suciu Priority: Minor Fix For: 0.7 Attachments: info.tgz This OSGI plugin is implementing an info service that would post broker information to a central location. It will activate on broker start and will http post the following information: QPID_HOME (eg /home/sorin/qpid-broker) QPID_WORK (eg /home/sorin) hostname (eg sorins-pc) ip (eg 192.168.1.24) java.class.path ( java.class.version (eg java.vm.name (eg os.arch (eg amd64) os.name (eg Linux) os.version (eg 2.6.18-128.7.1.el5) port (eg [5672]) sun.arch.data.model (eg 64) time (eg 2010-04-27 14:37:59.894+0100) user.dir (eg /home/sorin) user.name (eg sorin) user.timezone (eg Europe/London) This info is useful for large qpid deployments for automated monitoring purposes. -- 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: acl_test failing on Linux - anyoen seeing this in the automake build?
Steve, is that a RHEL 5 machine? A change I made in rev 937119 is causing the broker to core dump on RHEL5 while it works fine on Fedora 11, 12 I haven't been able to identify the issue. Therefore I rollbacked the change in rev 938298. So it should be fine now. Rajith On Tue, Apr 27, 2010 at 11:14 AM, Steve Huston shus...@riverace.com wrote: Hi folks, The acl_test has been failing on Linux in the cmake build for a couple of days now... Anyone seeing this on the autoconf build? http://www.riverace.com/CDash-1.4.2/viewTest.php?onlyfailedbuildid=586 It appears that maybe the broker is crashing on the first test execution. -Steve - 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: acl_test failing on Linux - anyoen seeing this in the automake build?
Hi Rajith, Steve, is that a RHEL 5 machine? Yes, it is RHEL 5. A change I made in rev 937119 is causing the broker to core dump on RHEL5 while it works fine on Fedora 11, 12 I haven't been able to identify the issue. Therefore I rollbacked the change in rev 938298. So it should be fine now. Ok, thanks. -Steve On Tue, Apr 27, 2010 at 11:14 AM, Steve Huston shus...@riverace.com wrote: Hi folks, The acl_test has been failing on Linux in the cmake build for a couple of days now... Anyone seeing this on the autoconf build? http://www.riverace.com/CDash-1.4.2/viewTest.php?onlyfailedbuildid=58 6 It appears that maybe the broker is crashing on the first test execution. -Steve - 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 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: acl_test failing on Linux - anyoen seeing this in the automake build?
Hi Steve! On Tue, Apr 27, 2010 at 11:14:44AM -0400, Steve Huston wrote: The acl_test has been failing on Linux in the cmake build for a couple of days now... Anyone seeing this on the autoconf build? No. I just run 'make check' which includes acl_test on today's revision 938298 and it worked well. And I compile it with autotools. Best regards, Ján -- Red Hat Czech, MRG Quality Engineering - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: acl_test failing on Linux - anyoen seeing this in the automake build?
On Tue, Apr 27, 2010 at 05:56:06PM +0200, Ján Sáreník wrote: No. I just run 'make check' which includes acl_test on today's revision 938298 and it worked well. And I compile it with autotools. But after reading Rajith's message - yes, I am on Fedora Rawhide :-) -- Red Hat Czech, MRG Quality Engineering - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Closed: (QPID-2530) Refactor the broker-plugins directory setup to allow adding new modules
[ https://issues.apache.org/jira/browse/QPID-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell closed QPID-2530. Assignee: Martin Ritchie (was: Robbie Gemmell) Resolution: Fixed Changes look good. Refactor the broker-plugins directory setup to allow adding new modules Key: QPID-2530 URL: https://issues.apache.org/jira/browse/QPID-2530 Project: Qpid Issue Type: Improvement Reporter: Sorin Suciu Assignee: Martin Ritchie Fix For: 0.7 Attachments: build.xml, extras.tgz The broker-plugins is currently having only one module (DiagnosticExchange and TestExchange). We should have a directory for each module building as a separate jar. This would allow adding a new module to be just a matter of creating a new directory and adding it to the build system, We should move the content of the src directory to its own plugin directory and adjust the build system accordingly. Suggested layout: broker-plugins --- build.xml --- extras (OSGI-Plugin) --- my_plugin1 (OSGI-Plugin) --- my_plugin2 (OSGI-Plugin) etc Please perform the following: on java/broker-plugins folder: - delete the src folder and untar the tarball attached - remove the build.xml and add the attached build.xml - apply QPID-2502 to fix the PluginManager.java issue with security tracker - apply QPID-2513 - apply QPID-2531 to update the build.deps and main build.xml -- 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-2501) WCF Binding Configuration parameters
[ https://issues.apache.org/jira/browse/QPID-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Huston resolved QPID-2501. Resolution: Fixed Applied patch on trunk r938691. WCF Binding Configuration parameters Key: QPID-2501 URL: https://issues.apache.org/jira/browse/QPID-2501 Project: Qpid Issue Type: Improvement Components: WCF/C++ Client Affects Versions: 0.7 Environment: Windows Reporter: Cliff Jansen Assignee: Steve Huston Fix For: 0.7 Attachments: QPID-2501.patch Original Estimate: 48h Remaining Estimate: 48h The existing configuration capabilities of the WCF channel should be fleshed out to handle transport level security. -- 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-2516) New sample to show how to specify WCF bindings in config files
[ https://issues.apache.org/jira/browse/QPID-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Huston resolved QPID-2516. Resolution: Fixed Applied patch on trunk r938694 New sample to show how to specify WCF bindings in config files -- Key: QPID-2516 URL: https://issues.apache.org/jira/browse/QPID-2516 Project: Qpid Issue Type: Improvement Components: WCF/C++ Client Affects Versions: 0.7 Environment: Windows Reporter: Cliff Jansen Assignee: Steve Huston Fix For: 0.7 Attachments: QPID-2516.patch Original Estimate: 2h Remaining Estimate: 2h -- 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-2359) Need functional tests for the transactional AMQP WCF channel
[ https://issues.apache.org/jira/browse/QPID-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Huston updated QPID-2359: --- Fix Version/s: 0.7 Need functional tests for the transactional AMQP WCF channel Key: QPID-2359 URL: https://issues.apache.org/jira/browse/QPID-2359 Project: Qpid Issue Type: Test Components: WCF/C++ Client Affects Versions: 0.6 Reporter: Devang Gandhi Assignee: Steve Huston Fix For: 0.7 Attachments: QPID-2359.patch -- 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
