[jira] Created: (QPID-2529) Update the Felix OSGI framework to a recent release
Update the Felix OSGI framework to a recent release --- Key: QPID-2529 URL: https://issues.apache.org/jira/browse/QPID-2529 Project: Qpid Issue Type: Improvement Components: Java Broker Affects Versions: 0.6 Reporter: Sorin Suciu Priority: Minor Fix For: 0.7 The felix framework currently used in qpid is version 1.0.0, an update to a later version would provide new features as well as bugfixes. -- 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-2530) Refactor the broker-plugins directory setup to allow adding new modules
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 Fix For: 0.7 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 -- 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-2531) Improve the qpid broker build system to automatically build OSGI modules on broker-plugins directory
Improve the qpid broker build system to automatically build OSGI modules on broker-plugins directory Key: QPID-2531 URL: https://issues.apache.org/jira/browse/QPID-2531 Project: Qpid Issue Type: Improvement Reporter: Sorin Suciu The qpid broker ant build system could be improved to automatically build the OSGI modules in the broker-plugins directory given we might have multiple modules. For this, we could modify the current build.xml file from broker-plugins to delegate the tasks to each individual module via a subant task. Each module would have its own build.xml file (which would be pretty much generic). So the task of adding a new OSGI module would involve: - creating a new directory (eg myplugin) having a generic build.xml and the code in src subdir - adding the new directory to the subant task so it will be build - updating the build.deps file -- 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-2498) Upgrade Mina to 1.1.7
[ https://issues.apache.org/jira/browse/QPID-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12859710#action_12859710 ] Martin Ritchie commented on QPID-2498: -- Hi Emmanuel, Thanks for the patches I'll take a look at these over the next few days. Cheers Martin Upgrade Mina to 1.1.7 - Key: QPID-2498 URL: https://issues.apache.org/jira/browse/QPID-2498 Project: Qpid Issue Type: Improvement Components: Java Broker, Java Client Affects Versions: 0.6 Reporter: Emmanuel Bourg Assignee: Martin Ritchie Fix For: 0.7 Attachments: mina-poms.patch, mina.patch, mina2.patch Upgrading Mina to 1.1.7 would allow the removal of backport-util-concurrent.jar from the dependencies. -- 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-2498) Upgrade Mina to 1.1.7
[ https://issues.apache.org/jira/browse/QPID-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie reassigned QPID-2498: Assignee: Martin Ritchie Upgrade Mina to 1.1.7 - Key: QPID-2498 URL: https://issues.apache.org/jira/browse/QPID-2498 Project: Qpid Issue Type: Improvement Components: Java Broker, Java Client Affects Versions: 0.6 Reporter: Emmanuel Bourg Assignee: Martin Ritchie Fix For: 0.7 Attachments: mina-poms.patch, mina.patch, mina2.patch Upgrading Mina to 1.1.7 would allow the removal of backport-util-concurrent.jar from the dependencies. -- 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: Unresolved issues but marked 0.6
Hi Rajith, Everything sitting at RtR for 0.6 on the Java side did make it into the release. Thing thats holding up the resolution is the outstanding reviews, which will take longer than a moment - but should be done. I'll try to get to them as soon as I can/close out anything not requiring review. As ever happy for others to contribute on the reviews too. Marnie On Tue, Apr 20, 2010 at 7:51 PM, Rajith Attapattu rajit...@gmail.comwrote: Hi All, Could we please take a moment to resolve any JIRA's with ready to review status that actually made it into the 0.6 release? If a fix actually made it into a release, then it's not correct to just bump the version to the next release. Therefore at the end of the week, what ever that is renaming will be pushed into no version as suggested by Martin. Please shout if anybody disagrees. Regards, Rajith On Wed, Mar 31, 2010 at 8:20 PM, Aidan Skinner aidan.skin...@gmail.com wrote: On Tue, Mar 30, 2010 at 4:28 PM, Marnie McCormack marnie.mccorm...@googlemail.com wrote: That's corect - they will have done. I've been reviewing them when time permits, but happy for other devs to review too to aid progress. Hoping we'll have more time for review in the 0.8 cycle. This is essentially inevitable with CTR. Somehow there's never enough time to get around to all the reviews, but I've never seen a patch not go in due to lack of review time with RTC. - Aidan -- Apache Qpid - AMQP, JMS, other messaging love http://qpid.apache.org A witty saying proves nothing - Voltaire - 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/
Re: [Java] Broker Roadmap/0-10 Java Client Query
Thanks Gordon. Rob has suggested we put client side detection in i.e. interrogate whether the broker support server side selectors so that the Java broker's sss could be used. Any objections to this approach ? Thanks, Marnie On Tue, Apr 20, 2010 at 6:10 PM, Gordon Sim g...@redhat.com wrote: On 04/20/2010 05:03 PM, Marnie McCormack wrote: Can the devs on this list please chip in with the key items outstanding on the Java Client side for 0-10 i.e. - are there features on the 0-8/0-9 codepaths that have not been completed on the 0-10 client path ? Server-side selectors is the obvious item. That is not yet supported by the c++ broker so the 0-10 client implements it (or attempts to!) client side. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: [Java] Broker Roadmap/0-10 Java Client Query
On 04/22/2010 10:04 AM, Marnie McCormack wrote: Thanks Gordon. Rob has suggested we put client side detection in i.e. interrogate whether the broker support server side selectors so that the Java broker's sss could be used. Any objections to this approach ? No, sounds very sensible. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2532) stale lock file
stale lock file --- Key: QPID-2532 URL: https://issues.apache.org/jira/browse/QPID-2532 Project: Qpid Issue Type: Test Components: C++ Broker Affects Versions: 0.7 Environment: Fedora Rawhide Reporter: Jan Sarenik Fix For: 0.7 This happents quite regularly in last week but still pretty randomly (sometimes whole make checks works well on the same revision on which it did not a while ago). I do `rm -rf ~/.qpidd; qpid clean -xfd' before every compilation. And still cluster_read_credit test fails because of following error: (relevant part of `make check' output follows) 2010-04-22 11:54:31 warning Connection closed 2010-04-22 11:54:31 warning Connect failed: Connection refused 2010-04-22 11:54:31 warning Connection closed Failed: Cannot establish a connection 2010-04-22 11:54:31 critical Unexpected error: Removing stale lock file /home/jsarenik/.qpidd/qpidd.41519.pid Errors stopping brokers on ports: 41519 FAIL: cluster_read_credit -- 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-2532) stale lock file
[ https://issues.apache.org/jira/browse/QPID-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12859768#action_12859768 ] Jan Sarenik commented on QPID-2532: --- If it is caused by the previous test, the previous is PASS: run_cluster_test stale lock file --- Key: QPID-2532 URL: https://issues.apache.org/jira/browse/QPID-2532 Project: Qpid Issue Type: Test Components: C++ Broker Affects Versions: 0.7 Environment: Fedora Rawhide Reporter: Jan Sarenik Fix For: 0.7 This happents quite regularly in last week but still pretty randomly (sometimes whole make checks works well on the same revision on which it did not a while ago). I do `rm -rf ~/.qpidd; qpid clean -xfd' before every compilation. And still cluster_read_credit test fails because of following error: (relevant part of `make check' output follows) 2010-04-22 11:54:31 warning Connection closed 2010-04-22 11:54:31 warning Connect failed: Connection refused 2010-04-22 11:54:31 warning Connection closed Failed: Cannot establish a connection 2010-04-22 11:54:31 critical Unexpected error: Removing stale lock file /home/jsarenik/.qpidd/qpidd.41519.pid Errors stopping brokers on ports: 41519 FAIL: cluster_read_credit -- 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
Nightly builds and Maven artifacts
Hi, I've setup an Hudson job to make nightly builds of the Java client and broker. It also generates the Maven artifacts of the client, including the source bundle for a nice integration in your favorite IDE. The nightly builds are available here: http://people.apache.org/~ebourg/qpid/ And the Maven repository is there (it contains only the qpid-common and qpid-client snapshots at this time): http://people.apache.org/~ebourg/qpid/maven/ Emmanuel Bourg - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[0-10] Forcibly closing a client session
Hi, Before I crack open the spec doc. just wanted to check here to see what the C++ broker does when it wants to close a client session. I'm looking at this for adding slow consumer disconnection (QPID-1447) but it will also be pertinent for any situation where the broker wants to disconnect a client session. I am currently creating an ExecutionException method with the required error code and description and sending that back to the client. It appears to be doing the right thing. Is this what the C++ broker does when an ACL violation occurs? Cheers Martin -- Martin Ritchie - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Contributer Patches - Committers Requested
Hi All, I think there may be a few JIRAs out there with patches looking for a committer to pick up. We've got quite a few contributers who are new/just getting established just now so I'd like to propose we volunteer to pair up with the new submitters to pick up patches. Perhaps the ad hoc system is working just now, but I'm not sure how else we avoid items dropping into gaps ? Be good to have thoughts on this subject. I've spotted a few patches (below) in need of a committer, just from recent activity on JIRA and I think Emmanuel might have a couple of older ones about too. (There's a couple I wasn't sure if the patch had been applied/issue resolved or not.) Contributers - please shout if I've missed anything else you're waiting for us to pick up ? Thank you. *Key* *Summary* *Assignee* *Reporter* QPID-2498 http://issues.apache.org/jira/browse/QPID-2498 Upgrade Mina to 1.1.7 Martin Ritchie Emmanuel Bourg QPID-2531 http://issues.apache.org/jira/browse/QPID-2531 Improve the qpid broker build system to automatically build OSGI modules on broker-plugins directory Unassigned Sorin Suciu QPID-2530 http://issues.apache.org/jira/browse/QPID-2530 Refactor the broker-plugins directory setup to allow adding new modules Unassigned Sorin Suciu QPID-2529 http://issues.apache.org/jira/browse/QPID-2529 Update the Felix OSGI framework to a recent release Unassigned Sorin Suciu QPID-2528 http://issues.apache.org/jira/browse/QPID-2528 qpid-config's add exchange option --durable doesn't work Unassigned Tim Powers QPID-1811 http://issues.apache.org/jira/browse/QPID-1811 Unable to compile qpid on FreeBSD ? Andrew Stitcher Attila Nagy QPID-2526 http://issues.apache.org/jira/browse/QPID-2526 Ant build fails if the path contains a space character Unassigned Emmanuel Bourg QPID-2513 http://issues.apache.org/jira/browse/QPID-2513 Expose the ServerConfiguration as an OSGI service for use in plugins Unassigned Sorin Suciu QPID-2519 http://issues.apache.org/jira/browse/QPID-2519 Allow Windows Broker to run as a Service Unassigned Kerry Bonin QPID-2520 http://issues.apache.org/jira/browse/QPID-2520 Broken POM generation on Windows Unassigned Emmanuel Bourg QPID-2516 http://issues.apache.org/jira/browse/QPID-2516 New sample to show how to specify WCF bindings in config files Unassigned Cliff Jansen QPID-2501 http://issues.apache.org/jira/browse/QPID-2501 WCF Binding Configuration parameters Unassigned Cliff Jansen QPID-2500 http://issues.apache.org/jira/browse/QPID-2500 Transport security for the WCF channel Unassigned Cliff Jansen QPID-2502 http://issues.apache.org/jira/browse/QPID-2502 securityTracker open() call is made on exchangeTracker instance instead Unassigned Sorin Suciu Regards, Marnie
Re: Contributer Patches - Committers Requested
On 22 April 2010 12:05, Marnie McCormack marnie.mccorm...@googlemail.com wrote: Hi All, I think there may be a few JIRAs out there with patches looking for a committer to pick up. We've got quite a few contributers who are new/just getting established just now so I'd like to propose we volunteer to pair up with the new submitters to pick up patches. Perhaps the ad hoc system is working just now, but I'm not sure how else we avoid items dropping into gaps ? Be good to have thoughts on this subject. I've spotted a few patches (below) in need of a committer, just from recent activity on JIRA and I think Emmanuel might have a couple of older ones about too. (There's a couple I wasn't sure if the patch had been applied/issue resolved or not.) Contributers - please shout if I've missed anything else you're waiting for us to pick up ? Thank you. *Key* *Summary* *Assignee* *Reporter* QPID-2498 http://issues.apache.org/jira/browse/QPID-2498 Upgrade Mina to 1.1.7 Martin Ritchie Emmanuel Bourg QPID-2531 http://issues.apache.org/jira/browse/QPID-2531 Improve the qpid broker build system to automatically build OSGI modules on broker-plugins directory Unassigned Sorin Suciu QPID-2530 http://issues.apache.org/jira/browse/QPID-2530 Refactor the broker-plugins directory setup to allow adding new modules Unassigned Sorin Suciu QPID-2529 http://issues.apache.org/jira/browse/QPID-2529 Update the Felix OSGI framework to a recent release Unassigned Sorin Suciu QPID-2528 http://issues.apache.org/jira/browse/QPID-2528 qpid-config's add exchange option --durable doesn't work Unassigned Tim Powers QPID-1811 http://issues.apache.org/jira/browse/QPID-1811 Unable to compile qpid on FreeBSD ? Andrew Stitcher Attila Nagy QPID-2526 http://issues.apache.org/jira/browse/QPID-2526 Ant build fails if the path contains a space character Unassigned Emmanuel Bourg QPID-2513 http://issues.apache.org/jira/browse/QPID-2513 Expose the ServerConfiguration as an OSGI service for use in plugins Unassigned Sorin Suciu QPID-2519 http://issues.apache.org/jira/browse/QPID-2519 Allow Windows Broker to run as a Service Unassigned Kerry Bonin QPID-2520 http://issues.apache.org/jira/browse/QPID-2520 Broken POM generation on Windows Unassigned Emmanuel Bourg QPID-2516 http://issues.apache.org/jira/browse/QPID-2516 New sample to show how to specify WCF bindings in config files Unassigned Cliff Jansen QPID-2501 http://issues.apache.org/jira/browse/QPID-2501 WCF Binding Configuration parameters Unassigned Cliff Jansen QPID-2500 http://issues.apache.org/jira/browse/QPID-2500 Transport security for the WCF channel Unassigned Cliff Jansen QPID-2502 http://issues.apache.org/jira/browse/QPID-2502 securityTracker open() call is made on exchangeTracker instance instead Unassigned Sorin Suciu Regards, Marnie I'll take a look at the following: QPID-2498 QPID-2502 QPID-2513 QPID-2529 QPID-2530 QPID-2531 I'll assign them over to me now. Martin -- Martin Ritchie - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Assigned: (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 ] Martin Ritchie reassigned QPID-2530: Assignee: Martin Ritchie 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 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 -- 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-2513) Expose the ServerConfiguration as an OSGI service for use in plugins
[ https://issues.apache.org/jira/browse/QPID-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie reassigned QPID-2513: Assignee: Martin Ritchie Expose the ServerConfiguration as an OSGI service for use in plugins Key: QPID-2513 URL: https://issues.apache.org/jira/browse/QPID-2513 Project: Qpid Issue Type: Improvement Affects Versions: 0.5, 0.6, 0.7 Reporter: Sorin Suciu Assignee: Martin Ritchie Fix For: 0.7 Attachments: qpid-2513.patch The ServerConfiguration could be used by OSGI plugins to query configuration parameters. For this, a service has to be registered with the current OSGI framework (currently Apache Felix). -- 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-2531) Improve the qpid broker build system to automatically build OSGI modules on broker-plugins directory
[ https://issues.apache.org/jira/browse/QPID-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie reassigned QPID-2531: Assignee: Martin Ritchie Improve the qpid broker build system to automatically build OSGI modules on broker-plugins directory Key: QPID-2531 URL: https://issues.apache.org/jira/browse/QPID-2531 Project: Qpid Issue Type: Improvement Reporter: Sorin Suciu Assignee: Martin Ritchie The qpid broker ant build system could be improved to automatically build the OSGI modules in the broker-plugins directory given we might have multiple modules. For this, we could modify the current build.xml file from broker-plugins to delegate the tasks to each individual module via a subant task. Each module would have its own build.xml file (which would be pretty much generic). So the task of adding a new OSGI module would involve: - creating a new directory (eg myplugin) having a generic build.xml and the code in src subdir - adding the new directory to the subant task so it will be build - updating the build.deps file -- 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-2502) securityTracker open() call is made on exchangeTracker instance instead
[ https://issues.apache.org/jira/browse/QPID-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie reassigned QPID-2502: Assignee: Martin Ritchie securityTracker open() call is made on exchangeTracker instance instead - Key: QPID-2502 URL: https://issues.apache.org/jira/browse/QPID-2502 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.5 Reporter: Sorin Suciu Assignee: Martin Ritchie Priority: Minor Fix For: 0.7 Attachments: qpid-2502.patch In this snippet: _exchangeTracker = new ServiceTracker(_activator.getContext(), ExchangeType.class.getName(), null); _exchangeTracker.open(); _securityTracker = new ServiceTracker(_activator.getContext(), ACLPlugin.class.getName(), null); _exchangeTracker.open(); the open method is called on _exchangeTracker instead of _securityTracker. This leads to a NPE if plugin-directory is used in the config file. -- 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: certificate authentication
Hi Li, I know qpid c++ broker supports certificate authentication, I would like to know whether the c++ broker verifies the client certificate against CRL (certificate revoked list). Thanks. If the broker is started with the ssl plugin and the option: --ssl-require-client-authentication is specified when the broker is started, then yes. -Steve - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1916) Maven releases for the client and management jars
[ https://issues.apache.org/jira/browse/QPID-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg updated QPID-1916: - Attachment: maven.patch I attached an alternative patch to generate the Maven artifacts: - like Bryan's patch it's based on the Maven Ant tasks, it installs the artifacts in the local repository and copy them in the release directory of the module. - the name of the artifacts has been changed from module to qpid-module. That's necessary to get the name of the jar right in the repository (qpid-client-version.jar instead of client-version.jar) - a source bundle is generated, when imported into an IDE it provides a convenient contextual help (quick javadoc lookup, parameters names) - the release.sh script has been modified to pickup the maven artifacts and sign them automatically. After uploading the files to people.apache.org the following document explains how to deploy them into the Apache repository : http://commons.apache.org/releases/release.html#a3_Deploy_Maven_Artifacts Snapshot artifacts based on this patch are available here: http://people.apache.org/~ebourg/qpid/maven/ Maven releases for the client and management jars - Key: QPID-1916 URL: https://issues.apache.org/jira/browse/QPID-1916 Project: Qpid Issue Type: New Feature Components: Ant Build System, Build Tools, Java Client, Java Common, Java Tools, Maven build system, Qpid Managment Framework Reporter: Bryan Kearney Attachments: maven.patch, mavenize3.patch The attached patch files adds the maven ant tasks to the build system. It allows, on a per-module basis, to support creating a pom file and exporting the jars to a maven repository. This is not a very DRY solution, as it requires copying the dependency information from the build.deps file. I have only added the pom files for the client bits, since i believe these are the most likely to be required by folks using QMF. -- 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-2528) qpid-config's add exchange option --durable doesn't work
[ https://issues.apache.org/jira/browse/QPID-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12859800#action_12859800 ] Tim Powers commented on QPID-2528: -- Something occurred to me Instead of using the patch one can do this in qpid-config instead: True = 1 That would also solve the problem. qpid-config's add exchange option --durable doesn't work -- Key: QPID-2528 URL: https://issues.apache.org/jira/browse/QPID-2528 Project: Qpid Issue Type: Bug Components: python tools Affects Versions: 0.7 Reporter: Tim Powers Attachments: qpid-config-durable.patch qpid-config (svn 929716) doesn't set _durable properly when adding a new exchange or queue when specifying --durable. The problem appears to be that the Python boolean True is being used to set _durable. Changing this to 1 solves the problem. There are other items (_passive, _clusterDurable) which do the same and may have the same problem. Note: This is a regression. -- 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-2528) qpid-config's add exchange option --durable doesn't work
[ https://issues.apache.org/jira/browse/QPID-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned QPID-2528: -- Assignee: Ted Ross qpid-config's add exchange option --durable doesn't work -- Key: QPID-2528 URL: https://issues.apache.org/jira/browse/QPID-2528 Project: Qpid Issue Type: Bug Components: python tools Affects Versions: 0.7 Reporter: Tim Powers Assignee: Ted Ross Attachments: qpid-config-durable.patch qpid-config (svn 929716) doesn't set _durable properly when adding a new exchange or queue when specifying --durable. The problem appears to be that the Python boolean True is being used to set _durable. Changing this to 1 solves the problem. There are other items (_passive, _clusterDurable) which do the same and may have the same problem. Note: This is a regression. -- 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: Contributer Patches - Committers Requested
I have taken care of QPID-2508 and QPID-2522 from Emmanuel. I left the MINA patch to Martin as he is more familiar with that side. Rajith On Thu, Apr 22, 2010 at 7:05 AM, Marnie McCormack marnie.mccorm...@googlemail.com wrote: Hi All, I think there may be a few JIRAs out there with patches looking for a committer to pick up. We've got quite a few contributers who are new/just getting established just now so I'd like to propose we volunteer to pair up with the new submitters to pick up patches. Perhaps the ad hoc system is working just now, but I'm not sure how else we avoid items dropping into gaps ? Be good to have thoughts on this subject. I've spotted a few patches (below) in need of a committer, just from recent activity on JIRA and I think Emmanuel might have a couple of older ones about too. (There's a couple I wasn't sure if the patch had been applied/issue resolved or not.) Contributers - please shout if I've missed anything else you're waiting for us to pick up ? Thank you. *Key* *Summary* *Assignee* *Reporter* QPID-2498 http://issues.apache.org/jira/browse/QPID-2498 Upgrade Mina to 1.1.7 Martin Ritchie Emmanuel Bourg QPID-2531 http://issues.apache.org/jira/browse/QPID-2531 Improve the qpid broker build system to automatically build OSGI modules on broker-plugins directory Unassigned Sorin Suciu QPID-2530 http://issues.apache.org/jira/browse/QPID-2530 Refactor the broker-plugins directory setup to allow adding new modules Unassigned Sorin Suciu QPID-2529 http://issues.apache.org/jira/browse/QPID-2529 Update the Felix OSGI framework to a recent release Unassigned Sorin Suciu QPID-2528 http://issues.apache.org/jira/browse/QPID-2528 qpid-config's add exchange option --durable doesn't work Unassigned Tim Powers QPID-1811 http://issues.apache.org/jira/browse/QPID-1811 Unable to compile qpid on FreeBSD ? Andrew Stitcher Attila Nagy QPID-2526 http://issues.apache.org/jira/browse/QPID-2526 Ant build fails if the path contains a space character Unassigned Emmanuel Bourg QPID-2513 http://issues.apache.org/jira/browse/QPID-2513 Expose the ServerConfiguration as an OSGI service for use in plugins Unassigned Sorin Suciu QPID-2519 http://issues.apache.org/jira/browse/QPID-2519 Allow Windows Broker to run as a Service Unassigned Kerry Bonin QPID-2520 http://issues.apache.org/jira/browse/QPID-2520 Broken POM generation on Windows Unassigned Emmanuel Bourg QPID-2516 http://issues.apache.org/jira/browse/QPID-2516 New sample to show how to specify WCF bindings in config files Unassigned Cliff Jansen QPID-2501 http://issues.apache.org/jira/browse/QPID-2501 WCF Binding Configuration parameters Unassigned Cliff Jansen QPID-2500 http://issues.apache.org/jira/browse/QPID-2500 Transport security for the WCF channel Unassigned Cliff Jansen QPID-2502 http://issues.apache.org/jira/browse/QPID-2502 securityTracker open() call is made on exchangeTracker instance instead Unassigned Sorin Suciu Regards, Marnie -- 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: Contributer Patches - Committers Requested
Rajith Attapattu a écrit : I have taken care of QPID-2508 and QPID-2522 from Emmanuel. I left the MINA patch to Martin as he is more familiar with that side. Thanks all for taking care of the patches. There is also an involved patch waiting for a thorough review in QPID-2433. https://issues.apache.org/jira/browse/QPID-2433 Emmanuel Bourg - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Assigned: (QPID-1811) Unable to compile qpid on FreeBSD
[ https://issues.apache.org/jira/browse/QPID-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned QPID-1811: - Assignee: Andrew Stitcher Unable to compile qpid on FreeBSD - Key: QPID-1811 URL: https://issues.apache.org/jira/browse/QPID-1811 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Environment: FreeBSD 8-CURRENT on amd64 (64 bit) $ g++ -v Using built-in specs. Target: amd64-undermydesk-freebsd Configured with: FreeBSD/amd64 system compiler Thread model: posix gcc version 4.2.1 20070719 [FreeBSD] $ python -V Python 2.6.1 $ pkg_info | grep boost boost-python-1.37.0 Free peer-reviewed portable C++ source libraries svn trunk version, checked out now (r765092) ./configure CPPFLAGS=-I/usr/local/include -L/usr/local/lib LDFLAGS=-L/usr/local/lib --with-poller=poll Reporter: Attila Nagy Assignee: Andrew Stitcher Priority: Critical Attachments: freebsd.patch, qpidfbsdcompile.diff, sasl.diff I'm trying to build qpid c++ broker on FreeBSD. Problems found during the build process: -8- g++ -DHAVE_CONFIG_H -I. -Igen -I./gen -I/usr/local/include -Werror -pedantic -Wall -Wextra -Wno-shadow -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long -Wvolatile-register-var -Winvalid-pch -Wno-system-headers -Woverloaded-virtual -g -O2 -MT qpid/sys/posix/Thread.lo -MD -MP -MF qpid/sys/posix/.deps/Thread.Tpo -c qpid/sys/posix/Thread.cpp -fPIC -DPIC -o qpid/sys/posix/.libs/Thread.o qpid/sys/posix/Thread.cpp: In member function 'long unsigned int qpid::sys::Thread::id()': qpid/sys/posix/Thread.cpp:64: error: invalid conversion from 'pthread*' to 'long unsigned int' I don't know whether it helps during the run, but allows to compile: return (unsigned long)impl-thread; -8- g++ -DHAVE_CONFIG_H -I. -Igen -I./gen -I/usr/local/include -Werror -pedantic -Wall -Wextra -Wno-shadow -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long -Wvolatile-register-var -Winvalid-pch -Wno-system-headers -Woverloaded-virtual -g -O2 -MT qpid/sys/posix/SystemInfo.lo -MD -MP -MF qpid/sys/posix/.deps/SystemInfo.Tpo -c qpid/sys/posix/SystemInfo.cpp -fPIC -DPIC -o qpid/sys/posix/.libs/SystemInfo.o In file included from qpid/sys/posix/SystemInfo.cpp:25: /usr/include/net/if.h:293: error: field 'ifru_addr' has incomplete type /usr/include/net/if.h:294: error: field 'ifru_dstaddr' has incomplete type /usr/include/net/if.h:295: error: field 'ifru_broadaddr' has incomplete type /usr/include/net/if.h:327: error: field 'ifra_addr' has incomplete type /usr/include/net/if.h:328: error: field 'ifra_broadaddr' has incomplete type /usr/include/net/if.h:329: error: field 'ifra_mask' has incomplete type /usr/include/net/if.h:427: error: field 'addr' has incomplete type /usr/include/net/if.h:428: error: field 'dstaddr' has incomplete type qpid/sys/posix/SystemInfo.cpp: In function 'void qpid::sys::SystemInfo::getLocalIpAddresses(uint16_t, std::vectorqpid::Address, std::allocatorqpid::Address )': qpid/sys/posix/SystemInfo.cpp:63: error: 'PF_INET' was not declared in this scope qpid/sys/posix/SystemInfo.cpp:63: error: 'SOCK_STREAM' was not declared in this scope qpid/sys/posix/SystemInfo.cpp:63: error: 'socket' was not declared in this scope qpid/sys/posix/SystemInfo.cpp:66: error: 'struct ifreq' has no member named 'ifr_ifindex' qpid/sys/posix/SystemInfo.cpp:67: error: 'SIOCGIFNAME' was not declared in this scope qpid/sys/posix/SystemInfo.cpp:72: error: 'union ifreq::anonymous' has no member named 'ifru_addr' qpid/sys/posix/SystemInfo.cpp:73: error: invalid use of incomplete type 'struct qpid::sys::sockaddr_in' qpid/sys/posix/SystemInfo.cpp:72: error: forward declaration of 'struct qpid::sys::sockaddr_in' The incomplete type error can be fixed by including sys/socket.h before net/if.h. The 'struct ifreq' has no member named 'ifr_ifindex' can be fixed by: #ifdef __FreeBSD__ ifr.ifr_index = i; #else ifr.ifr_ifindex = i; #endif The 'SIOCGIFNAME' was not declared in this scope is hopefully solved by: #ifdef SIOCGIFNAME if (::ioctl (s, SIOCGIFNAME, ifr) 0) #else if (!if_indextoname(ifr.ifr_index, ifr.ifr_name)) #endif break; The forward declaration of 'struct qpid::sys::sockaddr_in' can be solved by including net/pfvar.h after if.h -8-
[jira] Commented: (QPID-2528) qpid-config's add exchange option --durable doesn't work
[ https://issues.apache.org/jira/browse/QPID-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12859835#action_12859835 ] Tim Powers commented on QPID-2528: -- PEBKAC Please close this bug. qpid-config's add exchange option --durable doesn't work -- Key: QPID-2528 URL: https://issues.apache.org/jira/browse/QPID-2528 Project: Qpid Issue Type: Bug Components: python tools Affects Versions: 0.7 Reporter: Tim Powers Assignee: Ted Ross Attachments: qpid-config-durable.patch qpid-config (svn 929716) doesn't set _durable properly when adding a new exchange or queue when specifying --durable. The problem appears to be that the Python boolean True is being used to set _durable. Changing this to 1 solves the problem. There are other items (_passive, _clusterDurable) which do the same and may have the same problem. Note: This is a regression. -- 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-2531) Improve the qpid broker build system to automatically build OSGI modules on broker-plugins directory
[ https://issues.apache.org/jira/browse/QPID-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sorin Suciu updated QPID-2531: -- Attachment: qpid-2531.patch Improve the qpid broker build system to automatically build OSGI modules on broker-plugins directory Key: QPID-2531 URL: https://issues.apache.org/jira/browse/QPID-2531 Project: Qpid Issue Type: Improvement Reporter: Sorin Suciu Assignee: Martin Ritchie Attachments: qpid-2531.patch The qpid broker ant build system could be improved to automatically build the OSGI modules in the broker-plugins directory given we might have multiple modules. For this, we could modify the current build.xml file from broker-plugins to delegate the tasks to each individual module via a subant task. Each module would have its own build.xml file (which would be pretty much generic). So the task of adding a new OSGI module would involve: - creating a new directory (eg myplugin) having a generic build.xml and the code in src subdir - adding the new directory to the subant task so it will be build - updating the build.deps file -- 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-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 ] Sorin Suciu updated QPID-2530: -- Attachment: build.xml 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 -- 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-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 ] Sorin Suciu updated QPID-2530: -- Attachment: extras.tgz 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 -- 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-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 ] Sorin Suciu updated QPID-2530: -- Description: 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-2531 to update the build.deps and main build.xml - apply QPID-2513 was: 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 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-2531 to update the build.deps and main build.xml - apply QPID-2513 -- 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-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 ] Sorin Suciu updated QPID-2530: -- Description: 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 was: 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-2531 to update the build.deps and main build.xml - apply QPID-2513 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] Created: (QPID-2533) Modify config.xml to have ${QPID_HOME}/lib/plugins as the standar OSGI plugin directory
Modify config.xml to have ${QPID_HOME}/lib/plugins as the standar OSGI plugin
directory
---
Key: QPID-2533
URL: https://issues.apache.org/jira/browse/QPID-2533
Project: Qpid
Issue Type: Improvement
Components: Java Broker
Affects Versions: 0.7
Reporter: Sorin Suciu
Priority: Minor
Fix For: 0.7
As currently the OSGI plugins are built on lib/plugins, it would be natural to
configure in config.xml to use ${QPID_HOME}/lib/plugins as the plugin
directory. Any plugin in that directory would be loaded at startup.
--
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-2523) When reloading a large acl file while acl lookup is in progress, the broker core dumps
[
https://issues.apache.org/jira/browse/QPID-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-2523:
---
Attachment: QPID-2523.patch
valgrind-output
After some investigation (see the valgrind output) it seems the issue was
related to,
line 70 81 in Acl.cpp, (rev 936028)
boost::shared_ptrAclData dataLocal = data; //rcu copy
and line 136 in Acl.cpp, (rev 936028)
data = d;
Consulting the boost documentation, it seems this is not thread safe. (See
example #3)
http://www.boost.org/doc/libs/1_42_0/libs/smart_ptr/shared_ptr.htm#ThreadSafety
The fix was to add a lock around the assignments to ensure they are atomic.
When reloading a large acl file while acl lookup is in progress, the broker
core dumps
--
Key: QPID-2523
URL: https://issues.apache.org/jira/browse/QPID-2523
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: M4, 0.5, 0.6
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: 0.7
Attachments: QPID-2523-reproducer.tar.gz, QPID-2523.patch,
valgrind-output
Description of problem:
When reloading a large acl file , the broker core dumps.
This surfaced while running the attached reproducer.
How reproducible:
Always - reproducer attached.
Steps to Reproduce:
1. Start the broker with the acl module and and --acl-file /tmp/policy.acl
2. The initial acl file should contain only acl allow all all
3. run the message_sender.py (This program will keep on publishing to
amq.direct)
4. run acl_reloader.py with --mode allow | deny a few times
Actual results:
The broker core dumps.
Expected results:
The broker should continue to work after reloading the acl file properly.
Additional info:
Following is the backtrace from the code dump.
1.
(gdb) bt
2.
#0 0x00cbe422 in __kernel_vsyscall ()
3.
#1 0x00183781 in raise () from /lib/libc.so.6
4.
#2 0x0018504a in abort () from /lib/libc.so.6
5.
#3 0x001c1619 in __libc_message () from /lib/libc.so.6
6.
#4 0x001c7a71 in malloc_printerr () from /lib/libc.so.6
7.
#5 0x001ca363 in munmap_chunk () from /lib/libc.so.6
8.
#6 0x040a1681 in operator delete(void*) () from /usr/lib/libstdc++.so.6
9.
#7 0x0035243e in qpid::acl::AclData::clear (this=0x8221328) at
qpid/acl/AclData.cpp:40
10.
#8 0x003524ad in qpid::acl::AclData::~AclData (this=0x8221328,
__in_chrg=value optimized out) at qpid/acl/AclData.cpp:259
11.
#9 0x003515a8 in checked_deleteqpid::acl::AclData (x=value optimized
out) at /usr/include/boost/checked_delete.hpp:34
12.
#10 boost::detail::sp_counted_impl_pqpid::acl::AclData::dispose
(x=value optimized out) at /usr/include/boost/detail/sp_counted_impl.hpp:78
13.
#11 0x0034e50b in boost::detail::sp_counted_base::release (this=value
optimized out) at /usr/include/boost/detail/sp_counted_base_gcc_x86.hpp:145
14.
#12 ~shared_count (this=value optimized out) at
/usr/include/boost/detail/shared_count.hpp:216
15.
#13 ~shared_ptr (this=value optimized out) at
/usr/include/boost/shared_ptr.hpp:165
16.
#14 qpid::acl::Acl::authorise (this=value optimized out) at
qpid/acl/Acl.cpp:86
17.
#15 0x00add720 in qpid::broker::SemanticState::route (this=0x82218a0,
msg={p_ = 0xb5644868}, strate...@0xb61fe178)
18.
at qpid/broker/SemanticState.cpp:447
19.
#16 0x00ade215 in qpid::broker::SemanticState::handle (this=0x82218a0,
msg={p_ = 0xb5644868}) at qpid/broker/SemanticState.cpp:415
20.
--
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-2533) Modify config.xml to have ${QPID_HOME}/lib/plugins as the standard OSGI plugin directory
[
https://issues.apache.org/jira/browse/QPID-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu updated QPID-2533:
--
Patch attached.
Modify config.xml to have ${QPID_HOME}/lib/plugins as the standard OSGI
plugin directory
Key: QPID-2533
URL: https://issues.apache.org/jira/browse/QPID-2533
Project: Qpid
Issue Type: Improvement
Components: Java Broker
Affects Versions: 0.7
Reporter: Sorin Suciu
Priority: Minor
Fix For: 0.7
Attachments: qpid-2533.patch
As currently the OSGI plugins are built on lib/plugins, it would be natural
to configure in config.xml to use ${QPID_HOME}/lib/plugins as the plugin
directory. Any plugin in that directory would be loaded at startup.
--
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-2528) qpid-config's add exchange option --durable doesn't work
[ https://issues.apache.org/jira/browse/QPID-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim closed QPID-2528. Resolution: Not A Problem qpid-config's add exchange option --durable doesn't work -- Key: QPID-2528 URL: https://issues.apache.org/jira/browse/QPID-2528 Project: Qpid Issue Type: Bug Components: python tools Affects Versions: 0.7 Reporter: Tim Powers Assignee: Ted Ross Attachments: qpid-config-durable.patch qpid-config (svn 929716) doesn't set _durable properly when adding a new exchange or queue when specifying --durable. The problem appears to be that the Python boolean True is being used to set _durable. Changing this to 1 solves the problem. There are other items (_passive, _clusterDurable) which do the same and may have the same problem. Note: This is a regression. -- 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-2533) Modify config.xml to have ${QPID_HOME}/lib/plugins as the standard OSGI plugin directory
[
https://issues.apache.org/jira/browse/QPID-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu updated QPID-2533:
--
Attachment: qpid-2533.patch
Modify config.xml to have ${QPID_HOME}/lib/plugins as the standard OSGI
plugin directory
Key: QPID-2533
URL: https://issues.apache.org/jira/browse/QPID-2533
Project: Qpid
Issue Type: Improvement
Components: Java Broker
Affects Versions: 0.7
Reporter: Sorin Suciu
Priority: Minor
Fix For: 0.7
Attachments: qpid-2533.patch
As currently the OSGI plugins are built on lib/plugins, it would be natural
to configure in config.xml to use ${QPID_HOME}/lib/plugins as the plugin
directory. Any plugin in that directory would be loaded at startup.
--
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: Help requested w/ federation - what am I doing wrong?
OK, thanks for the pointer to that issue, I remember reading it a
while ago, didn't realize it was still open (I love JIRA, but issue
search isn't very effective, at least for me - I often don't find
highly relevant open issues...) Can you think of any other open
issues that might bite me in this area? In the mean time, I guess I'm
blocked by 2199, if that is the case I'll go fix it...
Kerry
On Wed, Apr 21, 2010 at 4:33 PM, Steve Huston shus...@riverace.com wrote:
Hi Kerry,
--
Steve Huston, Riverace Corporation
Total Lifecycle Support for Your Networked Applications
http://www.riverace.com
-Original Message-
From: Kerry Bonin [mailto:kerrybo...@gmail.com]
Sent: Wednesday, April 21, 2010 4:05 PM
To: qpid-dev
Subject: Help requested w/ federation - what am I doing wrong?
This is on XP SP2, using recent build (r921371 + my QPID-2519
patch applied but not being used.)
I think I'm doing this correctly, but I never see anything
from the receiver on the second broker. As I understand it,
shouldn't clients be able to subscribe to topics and see
published messages no matter which broker they are connected to?
You're not doing anything wrong that I can see, but Windows has a known
problem in this area: https://issues.apache.org/jira/browse/QPID-2199
Nobody has had time to address it yet, so I don't know if this is a big
or small problem. I suspect it's not terribly big.
Let me know if you need some help navigating this.
Best regards,
-Steve
My end goal here is to add some fault tolerance to a Windows
AMQP QPID system, where clients can switch to another broker
if their current broker dies. Since someone chose a Linux
only solution for clustering, I think my simplest option is
to leverage Federation, with something like
ResilientConnection to manage a list of brokers, and fail
client connections over to other brokers on connection
failure. This is from my federation test case, and I'm
probably setting something up incorrectly...
Greatly appreciate the help!
Kerry Bonin
I bring up two brokers:
start 5680 /Dd:\dev\qpid-r921371\cpp\build\src\debug
qpidd.exe --data-dir=.\qpidd.data.5680 --auth=no --port=5680
--load-module=qmfconsoled.dll
start 5681 /Dd:\dev\qpid-r921371\cpp\build\src\debug
qpidd.exe --data-dir=.\qpidd.data.5681 --auth=no --port=5681
--load-module=qmfconsoled.dll
Create exchanges
python D:\dev\qpid-r921371\tools\src\py\qpid-config -a
localhost:5680 add exchange topic fed.topic
python D:\dev\qpid-r921371\tools\src\py\qpid-config -a
localhost:5681 add exchange topic fed.topic
Create routes
python D:\dev\qpid-r921371\tools\src\py\qpid-route dynamic
add localhost:5680 localhost:5681 fed.topic
python D:\dev\qpid-r921371\tools\src\py\qpid-route dynamic
add localhost:5681 localhost:5680 fed.topic
This appears to work correctly :
D:\dev\qpid\binpython d:\dev\qpid-r921371\tools\src\py\qpid-route
route map localhost:5680
Finding Linked Brokers:
localhost:5680... Ok
localhost:5681... Ok
Dynamic Routes:
Exchange fed.topic:
localhost:5681 = localhost:5680
Static Routes:
none found
Now trimmed from my C++ testbed...
// Setup URLs and Addresses
std::string urlA = amqp:tcp:127.0.0.1:5680;
std::string urlB = amqp:tcp:127.0.0.1:5681;
std::string queue = fed.topic;
Address addressTx( queue );
Address addressRx( queue );
int64_t timeout = 1000;
// Setup transmitter on 5680
Connection connectionTxA;
connectionTxA.open( urlA );
Session sessionTxA = connectionTxA.newSession();
Sender senderTxA = sessionTxA.createSender( addressTx );
// Setup listeners on 5680 and 5681
Connection connectionRxA;
connectionRxA.open( urlA );
Session sessionRxA = connectionRxA.newSession();
Receiver receiverRxA = sessionRxA.createReceiver( addressRx );
Connection connectionRxB;
connectionRxB.open( urlB );
Session sessionRxB = connectionRxB.newSession();
Receiver receiverRxB = sessionRxB.createReceiver( addressRx );
// Transmit to 5680
Message messageOut;
MapContent contentOut( messageOut );
contentOut[id] = 1234;
contentOut[name] = Request;
contentOut.encode();
senderTxA.send( messageOut );
// Local listener sees the message
Message messageRxA;
if( receiverRxA.fetch( messageRxA, qpid::sys::Duration(
timeout ) ) ) {
MapView contentRxA( messageRxA );
std::cout local received: contentRxA std::endl;
sessionRxA.acknowledge();
}
else
std::cout local timeout std::endl;
// Remote never does...
Message messageRxB;
if( receiverRxB.fetch( messageRxB, qpid::sys::Duration(
timeout ) ) ) {
MapView contentRxB( messageRxB );
std::cout remote received: contentRxB std::endl;
sessionRxB.acknowledge();
}
else
std::cout remote timeout std::endl;
-
Apache Qpid - AMQP Messaging Implementation
Project:
[jira] Created: (QPID-2534) Add org.apache.qpid.protocol and org.apache.junit.extensions.util to the packages exported by the PluginManager
Add org.apache.qpid.protocol and org.apache.junit.extensions.util to the packages exported by the PluginManager - Key: QPID-2534 URL: https://issues.apache.org/jira/browse/QPID-2534 Project: Qpid Issue Type: Improvement Components: Java Broker Affects Versions: 0.7 Reporter: Sorin Suciu Priority: Minor Fix For: 0.7 org.apache.qpid.protocol and org.apache.junit.extensions.util are needed by the extras plugin so it should be exported by the PluginManager. -- 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: Help requested w/ federation - what am I doing wrong?
Hi Kerry,
OK, thanks for the pointer to that issue, I remember reading
it a while ago, didn't realize it was still open (I love
JIRA, but issue search isn't very effective, at least for me
- I often don't find highly relevant open issues...)
It's a bit odd because search by default brings in every Apache project
- narrowing it to just Qpid and just Unresolved issues makes it better.
Can you
think of any other open issues that might bite me in this
area? In the mean time, I guess I'm blocked by 2199, if that
is the case I'll go fix it...
Great! I'll be happy to review patches attached to the JIRA. FYI, the
federation_tests currently hang, which is probably the issue you're
encountering. It's easy to just run that test with:
ctest -V -R federation_tests
-Steve
On Wed, Apr 21, 2010 at 4:33 PM, Steve Huston
shus...@riverace.com wrote:
Hi Kerry,
--
Steve Huston, Riverace Corporation
Total Lifecycle Support for Your Networked Applications
http://www.riverace.com
-Original Message-
From: Kerry Bonin [mailto:kerrybo...@gmail.com]
Sent: Wednesday, April 21, 2010 4:05 PM
To: qpid-dev
Subject: Help requested w/ federation - what am I doing wrong?
This is on XP SP2, using recent build (r921371 + my
QPID-2519 patch
applied but not being used.)
I think I'm doing this correctly, but I never see anything
from the
receiver on the second broker. As I understand it,
shouldn't clients
be able to subscribe to topics and see published messages
no matter
which broker they are connected to?
You're not doing anything wrong that I can see, but Windows has a
known problem in this area:
https://issues.apache.org/jira/browse/QPID-2199
Nobody has had time to address it yet, so I don't know if this is a
big or small problem. I suspect it's not terribly big.
Let me know if you need some help navigating this.
Best regards,
-Steve
My end goal here is to add some fault tolerance to a Windows AMQP
QPID system, where clients can switch to another broker if their
current broker dies. Since someone chose a Linux only
solution for
clustering, I think my simplest option is to leverage Federation,
with something like ResilientConnection to manage a list
of brokers,
and fail client connections over to other brokers on connection
failure. This is from my federation test case, and I'm
probably setting something up incorrectly...
Greatly appreciate the help!
Kerry Bonin
I bring up two brokers:
start 5680 /Dd:\dev\qpid-r921371\cpp\build\src\debug
qpidd.exe --data-dir=.\qpidd.data.5680 --auth=no --port=5680
--load-module=qmfconsoled.dll
start 5681 /Dd:\dev\qpid-r921371\cpp\build\src\debug
qpidd.exe --data-dir=.\qpidd.data.5681 --auth=no --port=5681
--load-module=qmfconsoled.dll
Create exchanges
python D:\dev\qpid-r921371\tools\src\py\qpid-config -a
localhost:5680 add exchange topic fed.topic
python D:\dev\qpid-r921371\tools\src\py\qpid-config -a
localhost:5681 add exchange topic fed.topic
Create routes
python D:\dev\qpid-r921371\tools\src\py\qpid-route dynamic add
localhost:5680 localhost:5681 fed.topic
python D:\dev\qpid-r921371\tools\src\py\qpid-route dynamic add
localhost:5681 localhost:5680 fed.topic
This appears to work correctly :
D:\dev\qpid\binpython
d:\dev\qpid-r921371\tools\src\py\qpid-route
route map localhost:5680
Finding Linked Brokers:
localhost:5680... Ok
localhost:5681... Ok
Dynamic Routes:
Exchange fed.topic:
localhost:5681 = localhost:5680
Static Routes:
none found
Now trimmed from my C++ testbed...
// Setup URLs and Addresses
std::string urlA = amqp:tcp:127.0.0.1:5680;
std::string urlB = amqp:tcp:127.0.0.1:5681;
std::string queue = fed.topic;
Address addressTx( queue );
Address addressRx( queue );
int64_t timeout = 1000;
// Setup transmitter on 5680
Connection connectionTxA;
connectionTxA.open( urlA );
Session sessionTxA = connectionTxA.newSession();
Sender senderTxA = sessionTxA.createSender( addressTx );
// Setup listeners on 5680 and 5681
Connection connectionRxA;
connectionRxA.open( urlA );
Session sessionRxA = connectionRxA.newSession();
Receiver receiverRxA = sessionRxA.createReceiver( addressRx );
Connection connectionRxB;
connectionRxB.open( urlB );
Session sessionRxB = connectionRxB.newSession();
Receiver receiverRxB = sessionRxB.createReceiver( addressRx );
// Transmit to 5680
Message messageOut;
MapContent contentOut( messageOut );
contentOut[id] = 1234;
contentOut[name] = Request;
contentOut.encode();
senderTxA.send( messageOut );
// Local listener sees the message
Message messageRxA;
if( receiverRxA.fetch( messageRxA, qpid::sys::Duration(
timeout ) ) )
{
MapView contentRxA( messageRxA );
std::cout local received: contentRxA
Re: Contributer Patches - Committers Requested
I'd also suggest the patch I made w/ QPID-1904 - The C++ AbsTime Duration values are not set to a consistent epoch, which causes problems when you try using QMF timestamps across Linux and Windows, and even on Windows when you try and talk between Python and C++ clients. I submitted a patch which forces the epoch to that specified in AMQP, instead of inheriting it from the platform, which seems quite wrong for a network protocol across platforms with differing native epochs. The epoch is calculated once, and the conversion was already relative to a base, so there should be no performance hit. On Thu, Apr 22, 2010 at 8:27 AM, Emmanuel Bourg ebo...@apache.org wrote: Rajith Attapattu a écrit : I have taken care of QPID-2508 and QPID-2522 from Emmanuel. I left the MINA patch to Martin as he is more familiar with that side. Thanks all for taking care of the patches. There is also an involved patch waiting for a thorough review in QPID-2433. https://issues.apache.org/jira/browse/QPID-2433 Emmanuel Bourg - 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: c++: performance of new vs. old API
Alan Conway wrote: I'm happy to report that after appropriate tuning of the tests, the new API seems to perform as well as the old for basic thruput/latency tests. Detailed results attached. The main change since my previous mail on the subject was to disable setting sequence number and timestamp properties and compare results with a reliable receiver - all fair changes since they are equivalent to what perftest does. There is one mystery with the new api: an unreliable sender is _slower_ than reliable sender. As far as I can see by inspection and profiling, an unreliable sender does strictly less work than reliable one so this puzzles me. If anyone has a theory I'd love to hear it! Have you isolated that it is actually the sender that is slower, or is it that overall throughput is slower when unreliably sending? If it is the latter it doesn't seem entirely implausible since overall throughput is generally gated by consumption, which means a more efficient producer (i.e. the unreliable one) might actually result in slower overall throughput because it simply ends up filling the queue more quickly. --Rafael - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Assigned: (QPID-1904) Timestamps are incorrect
[ https://issues.apache.org/jira/browse/QPID-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned QPID-1904: - Assignee: Andrew Stitcher Timestamps are incorrect Key: QPID-1904 URL: https://issues.apache.org/jira/browse/QPID-1904 Project: Qpid Issue Type: Bug Components: Qpid Managment Framework Affects Versions: 0.5 Environment: Windows XP Reproduced both with the python API and the .Net API Reporter: Julien Lavigne du Cadet Assignee: Andrew Stitcher Attachments: qpid-1904.patch, qpid-dates.png The timestamps for configuration and instrumentation messages are incorrect both with the python and the .Net api. According to the documentation All timestamps are uint64 values representing nanoseconds since the epoch (January 1, 1970). However, the dates resulting can be several years in the past or in the future. To reproduce with the python api : - in disp.py, line 178 add the following line : print gmtime (nsec / 10) - start qpid-tool and list the queues = the full dates will be displayed -- 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-1904) Timestamps are incorrect
[ https://issues.apache.org/jira/browse/QPID-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved QPID-1904. --- Fix Version/s: 0.7 Resolution: Fixed Timestamps are incorrect Key: QPID-1904 URL: https://issues.apache.org/jira/browse/QPID-1904 Project: Qpid Issue Type: Bug Components: Qpid Managment Framework Affects Versions: 0.5 Environment: Windows XP Reproduced both with the python API and the .Net API Reporter: Julien Lavigne du Cadet Assignee: Andrew Stitcher Fix For: 0.7 Attachments: qpid-1904.patch, qpid-dates.png The timestamps for configuration and instrumentation messages are incorrect both with the python and the .Net api. According to the documentation All timestamps are uint64 values representing nanoseconds since the epoch (January 1, 1970). However, the dates resulting can be several years in the past or in the future. To reproduce with the python api : - in disp.py, line 178 add the following line : print gmtime (nsec / 10) - start qpid-tool and list the queues = the full dates will be displayed -- 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-2259) Add static build support in cmake for Windows
[ https://issues.apache.org/jira/browse/QPID-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved QPID-2259. --- Resolution: Won't Fix I don't think there is a strong justification for static libraries, and the project that needed them in this case has since fixed it's underlying build problems and doesn't any longer. Add static build support in cmake for Windows - Key: QPID-2259 URL: https://issues.apache.org/jira/browse/QPID-2259 Project: Qpid Issue Type: Improvement Components: Build Tools Environment: Windows XP SP3, VC++ 9.0 Reporter: Pete MacKinnon Assignee: Andrew Stitcher Attachments: 0001-Added-cmake-static-build-support-for-Windows.patch Some projects (e.g., Condor) that depend on qpid specifically for QMF integration require static builds of qpid cpp on Windows. Propose a new var (QPID_WINDOWS_STATIC) that when set makes available static release and debug configuration targets for VC++. -- 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-1494) Core on perf exit
[ https://issues.apache.org/jira/browse/QPID-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved QPID-1494. --- Resolution: Fixed I think this bug was fixed long ago. Core on perf exit - Key: QPID-1494 URL: https://issues.apache.org/jira/browse/QPID-1494 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: M4 Reporter: Carl Trieloff Assignee: Andrew Stitcher Perftest core on exit. Stack trace indicates issue that needs to be resolved prior to release -- 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
