Re: Final 0.6 release candidate and vote
Ahoj! On Wed, Mar 10, 2010 at 01:56:16PM -0500, Andrew Stitcher wrote: I've put up qpid-0.6rc7 for testing, you'll find it in the usual place: http://qpid.apache.org/dist/qpid-0.6rc7/ Is it noted somewhere, which revision of store should be used with this release of qpid? If it's not, please do so as I believe many users will appreciate that. I would suggest placing that info into the store section at http://qpidcomponents.org/download.html I do not think I have voting right (yet), but I am watching the evolution of qpid-0.6 since the first candidates and I am very thankful for such a team of developers who do things precisely. Good job. Best regards, Jasan -- Red Hat Czech, MRG Quality Assurance Associate - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Final 0.6 release candidate and vote
Hi again! On Thu, Mar 11, 2010 at 09:08:29AM +0100, Ján Sáreník wrote: I do not think I have voting right (yet), but I am watching the evolution of qpid-0.6 since the first candidates and I am very thankful for such a team of developers who do things precisely. Ehm, excuse me, I really did not give it a try though I was watching the discussion regarding the previous candidates. In the attached log there are two things I would like to point out: 1. Released tarball should contain developer-generated configure script and not require the user to have all the autotools stuff. 2. The error on cluster tests - I did not investigate much, but what I know is that the environment I am compiling in is able to cleanly compile, check and install current trunk (including the cluster module). What I have here: fedora-release-12-2.noarch corosynclib-devel-1.2.0-1.fc12.x86_64 including the needed records in /etc/corosync/uidgid.d That's my few cents. Sorry to be that late as I do not want to delay the release any more. Best regards, Jasan -- Red Hat Czech, MRG Quality Assurance Associate - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Final 0.6 release candidate and vote
And the attachment... + cd /home/jsarenik/qpid-0.6rc7 + cd cpp + ./bootstrap + CXXFLAGS=' -DNDEBUG -O3' + ./configure --disable-static --with-cpg --without-help2man [... SNIP ...] + make -j 5 [... SNIP ...] + make check [... SNIP ...] 0% 10 20 30 40 50 60 70 80 90 100% ||||||||||| Running 263 test cases... *** *** No errors detected PASS: unit_test 0% 10 20 30 40 50 60 70 80 90 100% ||||||||||| Running 48 test cases... *unknown location(0): fatal error in testReconnectSameSessionName: child was killed; pid: 29529; uid: 500; exit value: 9 ClusterFailover.cpp(61): last checkpoint *unknown location(0): fatal error in testCoincidentErrors: child was killed; pid: 29577; uid: 500; exit value: 11 ClusterFailover.cpp(61): last checkpoint *unknown location(0): fatal error in testConnectionKnownHosts: child was killed; pid: 30289; uid: 500; exit value: 9 cluster_test.cpp(537): last checkpoint *unknown location(0): fatal error in testUpdateConsumers: child was killed; pid: 30341; uid: 500; exit value: 9 cluster_test.cpp(588): last checkpoint *** *** 4 failures detected in test suite Master Test Suite FAIL: run_cluster_test [... SNIP ...] 1 of 20 tests failed Please report to dev@qpid.apache.org make[3]: *** [check-TESTS] Error 1 make[3]: Leaving directory `/home/jsarenik/qpid-0.6rc7/cpp/src/tests' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/home/jsarenik/qpid-0.6rc7/cpp/src/tests' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/home/jsarenik/qpid-0.6rc7/cpp/src' make: *** [check-recursive] Error 1 + exit 1 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Final 0.6 release candidate and vote
On Thu, Mar 11, 2010 at 09:54:29AM +0100, Ján Sáreník wrote: 2. The error on cluster tests - I did not investigate much, but what I know is that the environment I am compiling in is able to cleanly compile, check and install current trunk (including the cluster module). And if I compile without CPG, I am getting a 'make check' error which is fixed in trunk, see https://issues.apache.org/jira/browse/QPID-2441 Jasan + cd /home/jsarenik/qpid-0.6rc7 + cd cpp + CXXFLAGS=' -DNDEBUG -O3' + ./configure --disable-static --without-cpg --without-help2man ...SNIP... + make -j 5 ...SNIP... + make check ...SNIP... make[2]: Entering directory `/home/jsarenik/qpid-0.6rc7/cpp/examples' make check-local make[3]: Entering directory `/home/jsarenik/qpid-0.6rc7/cpp/examples' ./verify_all /home/jsarenik/qpid-0.6rc7/cpp/.. /home/jsarenik/qpid-0.6rc7/cpp --no-module-dir --data-dir \\ --auth no --load-module ../src/.libs/xml.so == /home/jsarenik/qpid-0.6rc7/cpp/../cpp/examples/pub-sub/verify_python_cpp *** verify_python_cpp.out Thu Mar 11 10:19:56 2010 --- /home/jsarenik/qpid-0.6rc7/cpp/examples/pub-sub/verify_python_cpp.in Thu Mar 11 10:01:22 2010 *** *** 5,14 Declaring queue: usa Declaring queue: weather Listening for messages ... - Message: That's all, folks! from europe - Message: That's all, folks! from news - Message: That's all, folks! from usa - Message: That's all, folks! from weather Message: europe.news 0 from europe Message: europe.news 0 from news Message: europe.news 1 from europe --- 5,10 *** *** 29,34 --- 25,34 Message: europe.weather 3 from weather Message: europe.weather 4 from europe Message: europe.weather 4 from weather + Message: That's all, folks! from europe + Message: That's all, folks! from news + Message: That's all, folks! from usa + Message: That's all, folks! from weather Message: usa.news 0 from news Message: usa.news 0 from usa Message: usa.news 1 from news FAIL ...SNIP... == /home/jsarenik/qpid-0.6rc7/cpp/../python/examples/pubsub/verify *** verify.out Thu Mar 11 10:20:28 2010 --- /home/jsarenik/qpid-0.6rc7/python/examples/pubsub/verify.in Thu Mar 11 10:01:22 2010 *** *** 1,18 topic_publisher.py.out topic_subscriber.py.out | remove_uuid | sort - Messages on 'europe' queue: - Messages on 'news' queue: - Messages on 'usa' queue: - Messages on 'weather' queue: - Queues created - please start the topic producer - Subscribing local queue 'local_europe' to europe-' - Subscribing local queue 'local_news' to news-' - Subscribing local queue 'local_usa' to usa-' - Subscribing local queue 'local_weather' to weather-' - That's all, folks! - That's all, folks! - That's all, folks! - That's all, folks! europe.news 0 europe.news 0 europe.news 1 --- 1,5 *** *** 33,38 --- 20,38 europe.weather 3 europe.weather 4 europe.weather 4 + Messages on 'europe' queue: + Messages on 'news' queue: + Messages on 'usa' queue: + Messages on 'weather' queue: + Queues created - please start the topic producer + Subscribing local queue 'local_europe' to europe-' + Subscribing local queue 'local_news' to news-' + Subscribing local queue 'local_usa' to usa-' + Subscribing local queue 'local_weather' to weather-' + That's all, folks! + That's all, folks! + That's all, folks! + That's all, folks! usa.news 0 usa.news 0 usa.news 1 FAIL ...SNIP... make[3]: *** [check-local] Error 1 make[3]: Leaving directory `/home/jsarenik/qpid-0.6rc7/cpp/examples' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/home/jsarenik/qpid-0.6rc7/cpp/examples' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/home/jsarenik/qpid-0.6rc7/cpp/examples' make: *** [check-recursive] Error 1 + exit 1 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Final 0.6 release candidate and vote
On Thu, Mar 11, 2010 at 09:54:29AM +0100, Ján Sáreník wrote: 1. Released tarball should contain developer-generated configure script and not require the user to have all the autotools stuff. This is contained in qpid-cpp-0.6rc7.tar.gz though. Ján. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Final 0.6 release candidate and vote
+1 for release, based on previous testing. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2328) Querying for 500 objects causes C++ based ruby console to hang
[ https://issues.apache.org/jira/browse/QPID-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12844073#action_12844073 ] Jan Sarenik commented on QPID-2328: --- See https://bugzilla.redhat.com/show_bug.cgi?id=564419 Querying for 500 objects causes C++ based ruby console to hang -- Key: QPID-2328 URL: https://issues.apache.org/jira/browse/QPID-2328 Project: Qpid Issue Type: Bug Components: Qpid Managment Framework Environment: Version: qmf-0.5.829175-3 Reporter: Ian Main Assignee: Ted Ross Fix For: 0.7 Attachments: qmf_race_fixes.patch, qmf_race_fixes_try_2.patch Using the test framework at http://github.com/movitto/qmf/ we were able to cause the console to hang and require a SIGKILL to stop it by querying for 450 or so objects. To reproduce: in project_stress/stress_agent/src run: ./stress_agent -n 500 And in project_stress/ruby/bin run: ./console.rb -t testobject -s If you try rerunning the agent with fewer objects you will see what normal output looks like. -- 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: Final 0.6 release candidate and vote
On 03/11/2010 03:54 AM, Ján Sáreník wrote: Hi again! On Thu, Mar 11, 2010 at 09:08:29AM +0100, Ján Sáreník wrote: I do not think I have voting right (yet), but I am watching the evolution of qpid-0.6 since the first candidates and I am very thankful for such a team of developers who do things precisely. Ehm, excuse me, I really did not give it a try though I was watching the discussion regarding the previous candidates. In the attached log there are two things I would like to point out: 1. Released tarball should contain developer-generated configure script and not require the user to have all the autotools stuff. That's in the C++ distribution: qpid-cpp-0.6rc7.tar.gz 2. The error on cluster tests - I did not investigate much, but what I know is that the environment I am compiling in is able to cleanly compile, check and install current trunk (including the cluster module). I did verify the cluster tests with 0.6, I'll double check... - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Qpid Wiki in DocBook
Here's a PDF built from the Qpid Wiki, converted to DocBook: http://people.apache.org/~jonathan/qpid-book.pdf I'm posting this now as a sign of life, to give a feel for where this is headed, and to get feedback on the organization. There are some things that still need cleaning up: - some links don't resolve properly - some formatting issues - some pages have been updated since I converted them But some of this should simply be replaced with new content - I have some existing content that we can contribute, and I'd like to start creating new content here, instead of or in addition to the Wiki. I'd also like to get some other people working on this with me. I'd particularly like to get someone to be in charge of the section on the Java Broker. Who wants to get involved in this? Jonathan - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Qpid Wiki in DocBook
On 03/11/2010 09:31 AM, Jonathan Robie wrote: Here's a PDF built from the Qpid Wiki, converted to DocBook: http://people.apache.org/~jonathan/qpid-book.pdf I'm posting this now as a sign of life, to give a feel for where this is headed, and to get feedback on the organization. There are some things that still need cleaning up: - some links don't resolve properly - some formatting issues - some pages have been updated since I converted them But some of this should simply be replaced with new content - I have some existing content that we can contribute, and I'd like to start creating new content here, instead of or in addition to the Wiki. I'd also like to get some other people working on this with me. I'd particularly like to get someone to be in charge of the section on the Java Broker. Who wants to get involved in this? This is a great start, we really need proper versioned documentation. The content definitely needs work to get it up to date and accurate, and we should strip out remarks such as in version 0.4 since this doc should refers to the version it's in SVN with. It may also need some re-org but that will probably come about as we rework the content. I suggest that this book be strictly user documentation and we strip out any design stuff that may have been imported from the wiki. We need design docs also but they're separate. I'm currently thinking that design docs belong closer to the source, e.g. in doxygen for C++. I'll give the clustering content the once-over, may take me a week or two though. Anyone know any good open-source docbook WYSIWYG editing tools? Editing the raw XML is a little unappealing :) - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Final 0.6 release candidate and vote
On 03/11/2010 03:54 AM, Ján Sáreník wrote: Hi again! On Thu, Mar 11, 2010 at 09:08:29AM +0100, Ján Sáreník wrote: I do not think I have voting right (yet), but I am watching the evolution of qpid-0.6 since the first candidates and I am very thankful for such a team of developers who do things precisely. Ehm, excuse me, I really did not give it a try though I was watching the discussion regarding the previous candidates. In the attached log there are two things I would like to point out: 1. Released tarball should contain developer-generated configure script and not require the user to have all the autotools stuff. 2. The error on cluster tests - I did not investigate much, but what I know is that the environment I am compiling in is able to cleanly compile, check and install current trunk (including the cluster module). What I have here: fedora-release-12-2.noarch corosynclib-devel-1.2.0-1.fc12.x86_64 including the needed records in /etc/corosync/uidgid.d I can build run those tests on rhel5 and fedora12. I just did configure --with-cpg. Not sure what is going on for your build. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Qpid Wiki in DocBook
On 2010/03/11, at 14:31, Jonathan Robie wrote: Here's a PDF built from the Qpid Wiki, converted to DocBook: http://people.apache.org/~jonathan/qpid-book.pdf Excellent work!!! I'm posting this now as a sign of life, to give a feel for where this is headed, and to get feedback on the organization. There are some things that still need cleaning up: - some links don't resolve properly - some formatting issues - some pages have been updated since I converted them But some of this should simply be replaced with new content - I have some existing content that we can contribute, and I'd like to start creating new content here, instead of or in addition to the Wiki. I'd also like to get some other people working on this with me. I'd particularly like to get someone to be in charge of the section on the Java Broker. Who wants to get involved in this? I would like, but I don't know enough. Jonathan - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org -- Bruno Matos bruno.ma...@paradigmaxis.pt smime.p7s Description: S/MIME cryptographic signature
Re: Final 0.6 release candidate and vote
On 03/11/2010 04:27 AM, Ján Sáreník wrote: On Thu, Mar 11, 2010 at 09:54:29AM +0100, Ján Sáreník wrote: 2. The error on cluster tests - I did not investigate much, but what I know is that the environment I am compiling in is able to cleanly compile, check and install current trunk (including the cluster module). And if I compile without CPG, I am getting a 'make check' error which is fixed in trunk, see https://issues.apache.org/jira/browse/QPID-2441 Annoying but minor, I say ship it! - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Qpid Wiki in DocBook
On 03/11/2010 02:47 PM, Alan Conway wrote: On 03/11/2010 09:31 AM, Jonathan Robie wrote: Here's a PDF built from the Qpid Wiki, converted to DocBook: http://people.apache.org/~jonathan/qpid-book.pdf I'm posting this now as a sign of life, to give a feel for where this is headed, and to get feedback on the organization. There are some things that still need cleaning up: - some links don't resolve properly - some formatting issues - some pages have been updated since I converted them But some of this should simply be replaced with new content - I have some existing content that we can contribute, and I'd like to start creating new content here, instead of or in addition to the Wiki. I'd also like to get some other people working on this with me. I'd particularly like to get someone to be in charge of the section on the Java Broker. Who wants to get involved in this? This is a great start, we really need proper versioned documentation. Indeed, thanks! Can you put in a readme with some basic instructions/process for building pdf or html for those not yet conversant with docbook? The content definitely needs work to get it up to date and accurate, and we should strip out remarks such as in version 0.4 since this doc should refers to the version it's in SVN with. It may also need some re-org but that will probably come about as we rework the content. I suggest that this book be strictly user documentation and we strip out any design stuff that may have been imported from the wiki. We need design docs also but they're separate. I'm currently thinking that design docs belong closer to the source, e.g. in doxygen for C++. I'll give the clustering content the once-over, may take me a week or two though. Anyone know any good open-source docbook WYSIWYG editing tools? Editing the raw XML is a little unappealing :) - 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: Qpid Wiki in DocBook
On 03/11/2010 09:47 AM, Alan Conway wrote: This is a great start, we really need proper versioned documentation. The content definitely needs work to get it up to date and accurate, and we should strip out remarks such as in version 0.4 since this doc should refers to the version it's in SVN with. It may also need some re-org but that will probably come about as we rework the content. I agree. And yes, it's a start. I think the next step is probably to decide whether the rough organization is good, and identify portions that need to be replaced, portions that should be kept but improved, etc. To me, polishing the presentation of the existing material as is may not be worth the effort. I suggest that this book be strictly user documentation and we strip out any design stuff that may have been imported from the wiki. We need design docs also but they're separate. I'm currently thinking that design docs belong closer to the source, e.g. in doxygen for C++. I agree. And I tried to keep design docs mostly out of this. I'll give the clustering content the once-over, may take me a week or two though. I think we can probably contribute better material on Clustering, Federation, Persistence, Security, etc. based on other materials that we have at Red Hat. I also think we can write high level API tutorials in DocBook, perhaps using some of the material in the Red Hat tutorials. Anyone know any good open-source docbook WYSIWYG editing tools? Editing the raw XML is a little unappealing :) For the Emacs crowd, I like nxml-mode, especially if you learn how to use tag completion, outlining, etc. (See http://www.dpawson.co.uk/relaxng/nxml/info.html). For vi folks, here's something I've seen but never tried: http://www.linuxjournal.com/article/7737. On Windows, I like Stylus Studio (http://www.stylusstudio.com/). On Linux, I like Oxygen (http://www.oxygenxml.com/). Both are commercial products. Here's a page on authoring tools for DocBook: http://wiki.docbook.org/topic/DocBookAuthoringTools Jonathan - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Qpid Wiki in DocBook
First up good job jonathan ! I think we can start from here and improve it gradually. As Alan said we should strip out any design docs etc.. I will also have a look and try organize the java client side as much as I can. Joanthan would you like to send an email outlining how the docs are currently organized and how we may want the end product to look? Perhaps then people can keep that in mind when they do the updates or new addition of content. On Thu, Mar 11, 2010 at 9:47 AM, Alan Conway acon...@redhat.com wrote: On 03/11/2010 09:31 AM, Jonathan Robie wrote: Here's a PDF built from the Qpid Wiki, converted to DocBook: http://people.apache.org/~jonathan/qpid-book.pdf I'm posting this now as a sign of life, to give a feel for where this is headed, and to get feedback on the organization. There are some things that still need cleaning up: - some links don't resolve properly - some formatting issues - some pages have been updated since I converted them But some of this should simply be replaced with new content - I have some existing content that we can contribute, and I'd like to start creating new content here, instead of or in addition to the Wiki. I'd also like to get some other people working on this with me. I'd particularly like to get someone to be in charge of the section on the Java Broker. Who wants to get involved in this? This is a great start, we really need proper versioned documentation. The content definitely needs work to get it up to date and accurate, and we should strip out remarks such as in version 0.4 since this doc should refers to the version it's in SVN with. It may also need some re-org but that will probably come about as we rework the content. I suggest that this book be strictly user documentation and we strip out any design stuff that may have been imported from the wiki. We need design docs also but they're separate. I'm currently thinking that design docs belong closer to the source, e.g. in doxygen for C++. I'll give the clustering content the once-over, may take me a week or two though. Anyone know any good open-source docbook WYSIWYG editing tools? Editing the raw XML is a little unappealing :) - 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: Qpid Wiki in DocBook
On 03/11/2010 10:07 AM, Gordon Sim wrote: Indeed, thanks! Can you put in a readme with some basic instructions/process for building pdf or html for those not yet conversant with docbook? Absolutely - and I'll also put some info on editing tools into the README. I want to check in a build system, I'll put instructions into the README when I do that. I think an ant-based system is probably best at least until there are no dangling references. I like Publican, it's easy to use and gives great output, but it's unforgiving. Jonathan - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
RE: Qpid Wiki in DocBook
Hi Jonathan, Great stuff! I'll try to put together some WCF/C++ client related material over the weekend. Cheers. Cliff -Original Message- From: Jonathan Robie [mailto:jonathan.ro...@redhat.com] Sent: Thursday, March 11, 2010 6:32 AM To: dev@qpid.apache.org Subject: Qpid Wiki in DocBook Here's a PDF built from the Qpid Wiki, converted to DocBook: http://people.apache.org/~jonathan/qpid-book.pdf I'm posting this now as a sign of life, to give a feel for where this is headed, and to get feedback on the organization. There are some things that still need cleaning up: - some links don't resolve properly - some formatting issues - some pages have been updated since I converted them But some of this should simply be replaced with new content - I have some existing content that we can contribute, and I'd like to start creating new content here, instead of or in addition to the Wiki. I'd also like to get some other people working on this with me. I'd particularly like to get someone to be in charge of the section on the Java Broker. Who wants to get involved in this? Jonathan - 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: Qpid Wiki in DocBook
On 03/11/2010 12:08 PM, Cliff Jansen (Interop Systems Inc) wrote: I'll try to put together some WCF/C++ client related material over the weekend. Excellent! The sources are in qpid/doc/book/src. I'll have a README later today. Jonathan - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-2382) implement utility for receiving member updates from failover exchange
[ https://issues.apache.org/jira/browse/QPID-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-2382. -- Resolution: Fixed Fixed in revision 921971 implement utility for receiving member updates from failover exchange - Key: QPID-2382 URL: https://issues.apache.org/jira/browse/QPID-2382 Project: Qpid Issue Type: Improvement Components: C++ Client, Python Client Reporter: Gordon Sim Assignee: Gordon Sim -- 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: Qpid Wiki in DocBook
On 03/11/2010 10:20 AM, Jonathan Robie wrote: On 03/11/2010 10:07 AM, Gordon Sim wrote: Indeed, thanks! Can you put in a readme with some basic instructions/process for building pdf or html for those not yet conversant with docbook? Absolutely - and I'll also put some info on editing tools into the README. I want to check in a build system, I'll put instructions into the README when I do that. I think an ant-based system is probably best at least until there are no dangling references. I'd suggest a Makefile as make as it has fewer dependencies than ant. I'm guessing it will be pretty simple in any case. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Qpid Wiki in DocBook
Alan Conway wrote: On 03/11/2010 10:20 AM, Jonathan Robie wrote: On 03/11/2010 10:07 AM, Gordon Sim wrote: Indeed, thanks! Can you put in a readme with some basic instructions/process for building pdf or html for those not yet conversant with docbook? Absolutely - and I'll also put some info on editing tools into the README. I want to check in a build system, I'll put instructions into the README when I do that. I think an ant-based system is probably best at least until there are no dangling references. I'd suggest a Makefile as make as it has fewer dependencies than ant. I'm guessing it will be pretty simple in any case. If you want to be able to build the docs on windows, then ant is probably easier than a Makefile. On unix both make and ant are readily available in just about any distro, along with all their dependencies, so it shouldn't really matter much from that perspective. --Rafael - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Client configuration Connection URL
Hi All,
Currently quite a bit of options can be configured via the Java
Connection URL, which tends to make it ungainly and quite error prone.
If we are to think in terms of a Connection String instead of a
Connection URL , then I believe we could come up with a more simpler
solution.
Therefore I'd like to make the following proposals.
1) Introduce a simple scheme for a Connection String ( inspired by
the new addressing format)
2) Also allow the ability to specify the config using a property file.
* I hate having to specify user/pass when the auth mech (ex kerberos)
is not even using it. Therefore it should be optional !
1. 0 Connection String
---
1.1 Examples
tcp://localhost
tcp://localhost:8672; {ssl: true, sasl-mech : EXTERNAL,
ssl-trust-store : ~/cert.jks ..}
tcp://host1.example.com; {user: bob, pass: nuts} ,
tcp://host2.example.com; {user: ding, pass: dong} ...
1.2 Syntax
broker [ ; options ] [ , broker [ ; options ]] *
Where broker is::
protocol:// [ host [ : port ] ](protocol = {tcp|vm|rdma}
Where options is::
{ key : value, ... }
And values may be:
- numbers
- single, double, or non quoted strings
- maps (dictionaries)
- lists
2.0 Config file
-
Example
JNDI prop file
connection.my-connection = tcp://localhost; {id : 1}
connection.my-con = tcp://host1.example.com; {id: 2} ,
tcp://host2.example.com; {id: 2}, tcp://host3.example.com; {id: 3}
=Connection.properties=
con id : 1 {
ssl: true
sasl-mech : EXTERNAL
ssl-trust-store : ~/cert.jks
ssl-key-store : ~/keys.jks
ssl-verify-hostname : true
}
con id : 1 {
sasl-mech : GSSAPI
sasl-hostname : host1.example.com
sasl-protocol : qpidd
sasl-encryption : true
tcp-nodelay : true
}
con id : 3 {
user : ding
pass : dong
tcp-nodelay : true
}
==
Connection.properties can be loaded from the classpath or specified as
an option in the connection string.
(You could also trivially have a connection property file per connection).
Comments and suggestions are most welcomed !
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
