Re: moving stuff out of the python dir
On Tue, Feb 2, 2010 at 4:23 PM, Rafael Schloming wrote: > Some of you may recall that I ranted a bit just prior to the freeze for the > 0.6 release about how lots of non-client related stuff has been accumulating > in the python directory as of late. It was a bit too late to do anything > about it at the time, but as the freeze is over now, I'd like to start > cleaning things up a bit. > > For that reason I intend to make the following moves over the next few days. > Please shout if this will disrupt you or if you disagree with any of the > locations I've picked. Instead of the following qmf/ ---> qpid/extras/qmf qmf2/ ---> qpid/extras/qmf How about, qmf/ ---> qpid/management/qmf qmf2/ ---> qpid/management/qmf Ideally I'd like to see the following top level directories management brokers clients tools extras docs tests sandbox Getting there might be a challenge, but we will eventually get there if we do it step by step. > These are the files currently under qpid/python: > > Makefile > LICENSE.txt > NOTICE.txt > README.txt > RELEASE_NOTES > todo.txt > commands/ ---> qpid/tools > doc/ > examples/ > mllib/ ---> qpid/extras/mllib > models/ ---> qpid/sandbox/models > preppy > qmf/ ---> qpid/extras/qmf > qmf2/ ---> qpid/extras/qmf > qpid/ > qpid-python-test > qpid_config.py > setup.py > tests/ > tests_0-10/ ---> qpid/tests/amqp_0-10 > tests_0-8/ ---> qpid/tests/amqp_0-8 > tests_0-9/ ---> qpid/tests/amqp_0-9 > > --Rafael > > > - > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > > -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/ - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2371) Missing includes for MSVC 2005 compiler
[ https://issues.apache.org/jira/browse/QPID-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828785#action_12828785 ] Marcel Roelofs commented on QPID-2371: -- It's not really pervasive, it's needed to get mssql_store and qpidxarm compiled properly. The first component has its own cmakefile where you could add the extra define, but the latter is generated via the cmakefile to which I suggested the change (for that particular reason). Your change works fine as well, it's just my non-fluency in cmake that made me come up with my less sophisticated solution. With the exception of the ResilientConnection.cpp compilation (that was subject of QPID-1982), it seems we're there now to get everything to compile and link properly using VC8. In case you're interested, in ResilientConnection.cpp the problem was the write function not being declared anywhere. If that's relevant information for QPID-1982, I would add it as a comment there, and close this jira. > Missing includes for MSVC 2005 compiler > --- > > Key: QPID-2371 > URL: https://issues.apache.org/jira/browse/QPID-2371 > Project: Qpid > Issue Type: Improvement > Components: C++ Broker >Affects Versions: 0.6 > Environment: MSVC 2005 >Reporter: Marcel Roelofs >Assignee: Steve Huston >Priority: Minor > Fix For: 0.7 > > Attachments: msvc2005.patch > > > When compiling the 0.6 release candidate using MSVC 2005 I found some missing > header file includes that prevented qpid to compile out of the box. I'll add > a patch later. > Also I had to add "/D _WIN32_WINNT=0x0501" to the compiler flags during cmake > makefile generation to prevent compile errors in various components, but I've > no idea how to add this to the cmake configuration. -- 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: moving stuff out of the python dir
Rafael Schloming wrote: Some of you may recall that I ranted a bit just prior to the freeze for the 0.6 release about how lots of non-client related stuff has been accumulating in the python directory as of late. It was a bit too late to do anything about it at the time, but as the freeze is over now, I'd like to start cleaning things up a bit. For that reason I intend to make the following moves over the next few days. Please shout if this will disrupt you or if you disagree with any of the locations I've picked. These are the files currently under qpid/python: Makefile LICENSE.txt NOTICE.txt README.txt RELEASE_NOTES todo.txt commands/ ---> qpid/tools doc/ examples/ mllib/---> qpid/extras/mllib models/ ---> qpid/sandbox/models preppy qmf/ ---> qpid/extras/qmf qmf2/ ---> qpid/extras/qmf qpid/ qpid-python-test qpid_config.py setup.py tests/ tests_0-10/ ---> qpid/tests/amqp_0-10 tests_0-8/---> qpid/tests/amqp_0-8 tests_0-9/---> qpid/tests/amqp_0-9 On second thought, I think perhaps moving the tests as below may be better. This will result in a python package structure that puts them in the qpid namespace which will allow them to be installed, as well as replacing "-" with "_" which will allow normal imports: tests_0-10/ ---> qpid/tests/amqp/qpid/broker_0_10 tests_0-8/---> qpid/tests/amqp/qpid/broker_0_8 tests_0-9/---> qpid/tests/amqp/qpid/broker_0_9 --Rafael - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
moving stuff out of the python dir
Some of you may recall that I ranted a bit just prior to the freeze for the 0.6 release about how lots of non-client related stuff has been accumulating in the python directory as of late. It was a bit too late to do anything about it at the time, but as the freeze is over now, I'd like to start cleaning things up a bit. For that reason I intend to make the following moves over the next few days. Please shout if this will disrupt you or if you disagree with any of the locations I've picked. These are the files currently under qpid/python: Makefile LICENSE.txt NOTICE.txt README.txt RELEASE_NOTES todo.txt commands/ ---> qpid/tools doc/ examples/ mllib/---> qpid/extras/mllib models/ ---> qpid/sandbox/models preppy qmf/ ---> qpid/extras/qmf qmf2/ ---> qpid/extras/qmf qpid/ qpid-python-test qpid_config.py setup.py tests/ tests_0-10/ ---> qpid/tests/amqp_0-10 tests_0-8/---> qpid/tests/amqp_0-8 tests_0-9/---> qpid/tests/amqp_0-9 --Rafael - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
RE: Fifth (and I hope final) Release Candidate for 0.6 qpid release
The fixes you made on my behalf look good. Thanks very much. Cliff -Original Message- From: Andrew Stitcher [mailto:astitc...@redhat.com] Sent: Tuesday, February 02, 2010 9:26 AM To: Qpid Dev List Subject: Fifth (and I hope final) Release Candidate for 0.6 qpid release I've now uploaded another release candidate for 0.6. As usual you'll find it in: http://qpid.apache.org/dist/qpid-0.6rc5 The list of issues fixed since we branched the release from trunk is: (that branch point was rc3) == qpid-0.6rc5 == QPID-2378: Necessary License files for the WCF release artifact (from Cliff Jansen) QPID-2313: Update to WCF Release notes (from Cliff Jansen) Revised release notes for 0.6 == qpid-0.6rc4 == QPID-2137 : Commit patch to address StringIndexOutOfBounds during status logging. Merge of trunk r898821. QPID-2320: merged fix from trunk to 0.6 release branch. == qpid-0.6rc3 == I think this release should fix all the problems that have been reported up to this point for the 0.6 release. Please download something and give it a smoke test. As you can see ther have only been documentation changes since rc4. So if you built and tested something successfully under rc4 then there is every reason to think it will still work. I'll leave this a day, then I will call for a release vote on this version packaged up as 0.6 if there are no reported problems. Andrew - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
RE: 0.6RC4 available [Was: 0.6 Release - Query]
You can get a Rat binary (2.2MB) at: http://www.apache.org/dyn/closer.cgi/incubator/rat/binaries/apache-rat-incubating-0.6-bin.tar.gz Don't believe you'll need it now but for reference, Maven binary (2.7MB) available at: http://www.apache.org/dyn/closer.cgi/maven/binaries/apache-maven-2.2.1-bin.tar.gz Robbie > -Original Message- > From: Andrew Stitcher [mailto:astitc...@redhat.com] > Sent: 02 February 2010 17:29 > I've looked at rat and I'm put off to see that it needs maven to build > (huge download under Fedora) and as you say the documentaion seems to > be > pants. > - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2359) Need functional tests for the transactional AMQP WCF channel
[ https://issues.apache.org/jira/browse/QPID-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devang Gandhi updated QPID-2359: Attachment: QPID-2359.patch Attached diff file that has the tests. > Need functional tests for the transactional AMQP WCF channel > > > Key: QPID-2359 > URL: https://issues.apache.org/jira/browse/QPID-2359 > Project: Qpid > Issue Type: Test > Components: WCF/C++ Client >Affects Versions: 0.6 >Reporter: Devang Gandhi > Attachments: QPID-2359.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-2313) Release notes for the WCF/C++ client
[ https://issues.apache.org/jira/browse/QPID-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved QPID-2313. --- Resolution: Fixed Documentation applied to 0.6 branch and trunk > Release notes for the WCF/C++ client > - > > Key: QPID-2313 > URL: https://issues.apache.org/jira/browse/QPID-2313 > Project: Qpid > Issue Type: Improvement > Components: WCF/C++ Client >Affects Versions: 0.6 > Environment: Windows >Reporter: Cliff Jansen >Assignee: Andrew Stitcher > Fix For: 0.6, 0.7 > > Attachments: QPID-2313.patch > > > Updated release notes are required for the 0.6 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
[jira] Updated: (QPID-2313) Release notes for the WCF/C++ client
[ https://issues.apache.org/jira/browse/QPID-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated QPID-2313: -- Fix Version/s: 0.7 > Release notes for the WCF/C++ client > - > > Key: QPID-2313 > URL: https://issues.apache.org/jira/browse/QPID-2313 > Project: Qpid > Issue Type: Improvement > Components: WCF/C++ Client >Affects Versions: 0.6 > Environment: Windows >Reporter: Cliff Jansen >Assignee: Andrew Stitcher > Fix For: 0.6, 0.7 > > Attachments: QPID-2313.patch > > > Updated release notes are required for the 0.6 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
[jira] Resolved: (QPID-2378) WCF/C++ Client subtree lacks Apache licensing files
[ https://issues.apache.org/jira/browse/QPID-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved QPID-2378. --- Resolution: Fixed Applied to 0.6 and trunk > WCF/C++ Client subtree lacks Apache licensing files > --- > > Key: QPID-2378 > URL: https://issues.apache.org/jira/browse/QPID-2378 > Project: Qpid > Issue Type: Bug > Components: WCF/C++ Client >Affects Versions: 0.6 > Environment: Windows >Reporter: Cliff Jansen >Assignee: Andrew Stitcher >Priority: Blocker > Fix For: 0.6, 0.7 > > Attachments: QPID-2378.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > Licence and Notice files are missing. Requirements described at > http://www.apache.org/dev/apply-license.html -- 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-2378) WCF/C++ Client subtree lacks Apache licensing files
[ https://issues.apache.org/jira/browse/QPID-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated QPID-2378: -- Fix Version/s: 0.7 Assignee: Andrew Stitcher > WCF/C++ Client subtree lacks Apache licensing files > --- > > Key: QPID-2378 > URL: https://issues.apache.org/jira/browse/QPID-2378 > Project: Qpid > Issue Type: Bug > Components: WCF/C++ Client >Affects Versions: 0.6 > Environment: Windows >Reporter: Cliff Jansen >Assignee: Andrew Stitcher >Priority: Blocker > Fix For: 0.6, 0.7 > > Attachments: QPID-2378.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > Licence and Notice files are missing. Requirements described at > http://www.apache.org/dev/apply-license.html -- 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: 0.6RC4 available [Was: 0.6 Release - Query]
On Tue, 2010-02-02 at 13:00 +, Marnie McCormack wrote: > The docs are a bit ropey but I'm *fairly* sure it checks licenses. Anyone > confirm ? I've looked at rat and I'm put off to see that it needs maven to build (huge download under Fedora) and as you say the documentaion seems to be pants. If someone else would like to run rat against the 0.6rc5 packages I'd be very happy to let them. Andrew > > Marnie > > On Fri, Jan 29, 2010 at 4:34 PM, Andrew Stitcher wrote: > > > On Fri, 2010-01-29 at 16:22 +, Marnie McCormack wrote: > > > http://incubator.apache.org/rat/ > > > > Ah, thanks for that. Looks like it's in java though which might add some > > time to me getting it working. > > > > Andrew > > > > > > > > - > > 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
Fifth (and I hope final) Release Candidate for 0.6 qpid release
I've now uploaded another release candidate for 0.6. As usual you'll find it in: http://qpid.apache.org/dist/qpid-0.6rc5 The list of issues fixed since we branched the release from trunk is: (that branch point was rc3) == qpid-0.6rc5 == QPID-2378: Necessary License files for the WCF release artifact (from Cliff Jansen) QPID-2313: Update to WCF Release notes (from Cliff Jansen) Revised release notes for 0.6 == qpid-0.6rc4 == QPID-2137 : Commit patch to address StringIndexOutOfBounds during status logging. Merge of trunk r898821. QPID-2320: merged fix from trunk to 0.6 release branch. == qpid-0.6rc3 == I think this release should fix all the problems that have been reported up to this point for the 0.6 release. Please download something and give it a smoke test. As you can see ther have only been documentation changes since rc4. So if you built and tested something successfully under rc4 then there is every reason to think it will still work. I'll leave this a day, then I will call for a release vote on this version packaged up as 0.6 if there are no reported problems. Andrew - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-2384) Cluster recovers duplicate messages when using async store and --no-data-dir and --store-dir together
[ https://issues.apache.org/jira/browse/QPID-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPID-2384. Resolution: Fixed This is a logic flaw in the cluster store status. When --no-data-dir is specified, the logic which discards the store for the second and subsequent nodes fails to run. In addition, the cluster has nowhere to write its store status information which is normally written into the data directory. Considering that the store-dir used by the async store is unique to that store and is not available on stores generally, it makes sense therefore to make the use of --data-dir mandatory when the cluster is loaded together with any non-null store. This fix now will stop the broker with an error message if --no-data-dir is used in the presence of any non-null store. Fixed in r.905680 > Cluster recovers duplicate messages when using async store and --no-data-dir > and --store-dir together > - > > Key: QPID-2384 > URL: https://issues.apache.org/jira/browse/QPID-2384 > Project: Qpid > Issue Type: Bug > Components: C++ Clustering >Reporter: Kim van der Riet >Assignee: Kim van der Riet > > (copied from https://bugzilla.redhat.com/show_bug.cgi?id=560102) > When using a persistent store in cluster mode, if you say --no-data-dir, the > wrong thing happens at init time, and the broker comes up in a confused state. > Version-Release number of selected component (if applicable): trunk > How reproducible: Always > Steps to Reproduce: > 1. Start two brokers with a stores, specify --store-dir, and --no-data-dir > 2. Create some objects > 3. Bounce and restart a broker > Actual results: Broker recovers objects from the store, when it shouldn't > Expected results: Should get statea from the peer. -- 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-2384) Cluster recovers duplicate messages when using async store and --no-data-dir and --store-dir together
[ https://issues.apache.org/jira/browse/QPID-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet reassigned QPID-2384: -- Assignee: Kim van der Riet > Cluster recovers duplicate messages when using async store and --no-data-dir > and --store-dir together > - > > Key: QPID-2384 > URL: https://issues.apache.org/jira/browse/QPID-2384 > Project: Qpid > Issue Type: Bug > Components: C++ Clustering >Reporter: Kim van der Riet >Assignee: Kim van der Riet > > (copied from https://bugzilla.redhat.com/show_bug.cgi?id=560102) > When using a persistent store in cluster mode, if you say --no-data-dir, the > wrong thing happens at init time, and the broker comes up in a confused state. > Version-Release number of selected component (if applicable): trunk > How reproducible: Always > Steps to Reproduce: > 1. Start two brokers with a stores, specify --store-dir, and --no-data-dir > 2. Create some objects > 3. Bounce and restart a broker > Actual results: Broker recovers objects from the store, when it shouldn't > Expected results: Should get statea from the peer. -- 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-2384) Cluster recovers duplicate messages when using async store and --no-data-dir and --store-dir together
Cluster recovers duplicate messages when using async store and --no-data-dir and --store-dir together - Key: QPID-2384 URL: https://issues.apache.org/jira/browse/QPID-2384 Project: Qpid Issue Type: Bug Components: C++ Clustering Reporter: Kim van der Riet (copied from https://bugzilla.redhat.com/show_bug.cgi?id=560102) When using a persistent store in cluster mode, if you say --no-data-dir, the wrong thing happens at init time, and the broker comes up in a confused state. Version-Release number of selected component (if applicable): trunk How reproducible: Always Steps to Reproduce: 1. Start two brokers with a stores, specify --store-dir, and --no-data-dir 2. Create some objects 3. Bounce and restart a broker Actual results: Broker recovers objects from the store, when it shouldn't Expected results: Should get statea from the peer. -- 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-2155) QpidRollingFileAppender has no tests and does not appear to work.
[ https://issues.apache.org/jira/browse/QPID-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828641#action_12828641 ] Rob Godfrey commented on QPID-2155: --- Robbie is correct a test of the form (new (...) == null) must always return false, or throw an exception (if the constructor throws an Exception) > QpidRollingFileAppender has no tests and does not appear to work. > - > > Key: QPID-2155 > URL: https://issues.apache.org/jira/browse/QPID-2155 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.5 >Reporter: Martin Ritchie >Assignee: Martin Ritchie > Fix For: 0.6 > > > When investigating QPID-2085 the following issues were found: > The QpidRollingFileAppender does not appear to behave as expected from the > configuration. > Have noticed the following: > - qpid.log being archived shortly after creation, resulting in no log file > for the broker. (When using StaticName) > - Log files being archived before 10MB setting, using default configuration. > - Log files index not being used as described in the comments. file .0 is > always the current head of the log rather than 'n' as described. -- 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-2155) QpidRollingFileAppender has no tests and does not appear to work.
[
https://issues.apache.org/jira/browse/QPID-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828638#action_12828638
]
Robbie Gemmell commented on QPID-2155:
--
It isnt clear what the following is supposed to accomplish atQCRA line 920. The
commit (891331) message references adding NPE checks, but the testFileName
String is constructed immediately above this and wont be null, and the JavaDoc
for File doesnt list anything about nulls other than it will NPE if the given
string is null.
// Bail out early if there is a problem with the file
if (new File(testFileName) == null
|| new File(testFileName + COMPRESS_EXTENSION) == null)
{
return index;
}
> QpidRollingFileAppender has no tests and does not appear to work.
> -
>
> Key: QPID-2155
> URL: https://issues.apache.org/jira/browse/QPID-2155
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: 0.5
>Reporter: Martin Ritchie
>Assignee: Martin Ritchie
> Fix For: 0.6
>
>
> When investigating QPID-2085 the following issues were found:
> The QpidRollingFileAppender does not appear to behave as expected from the
> configuration.
> Have noticed the following:
> - qpid.log being archived shortly after creation, resulting in no log file
> for the broker. (When using StaticName)
> - Log files being archived before 10MB setting, using default configuration.
> - Log files index not being used as described in the comments. file .0 is
> always the current head of the log rather than 'n' as described.
--
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: qpidc and FreeBSD
Hi Andrey, > I have done a little patch. Should I register in JIRA to send > it or may I send it to somebody of developers? Please register in JIRA, submit the report and attach your patch to the jira. Be sure to check off the license-to-apache box when you attach the patch. Thanks! -Steve > 2009/12/11 Alan Conway > > > On 12/10/2009 10:43 AM, Andrew Stitcher wrote: > > > >> On Thu, 2009-12-10 at 10:30 -0500, Rajith Attapattu wrote: > >> > >>> Hello Andrey > >>> > >>> No it's not off topic. > >>> Currently there is no effort on this. > >>> Are you interested in having a crack at this? > >>> There have been successful ports to windows and solaris. > >>> > >> > >> Currently the Solaris port does not build - and there isn't enough > >> time to get it working for the 0.6 release. > >> > >> Some of the problem here is due to the use of the SunPro > C++ compiler > >> which has yet different quirks from the gcc and Visual Studio > >> compilers which currently can build qpid. > >> > >> > >> > >>> Please feel to join the dev list and ask questions. > >>> I am sure you will receive enough guidance on what to do. > >>> > >>> Regards, > >>> > >>> Rajith Attapattu > >>> Red Hat > >>> http://rajith.2rlabs.com/ > >>> > >>> On Thu, Dec 10, 2009 at 10:11 AM, Andrey Kotrekhov > >>> wrote: > >>> > Hello. > Are there any plans to port qpidc to FreeBSD or other BSD* ? > > >>> > >> It would be great to port to a bsd. As long as you can use > gcc4 then > >> the only significant area involved in the port is the Poller class > >> which is currently Linux specific (implemented in > >> cpp/src/qpid/sys/epoll/EpollPoller.cpp). > >> > >> The most general way to do this would be to port to use > poll(). The > >> advantage here would be that this would be very portable to posix > >> systems. But this wouldn't have great performance. On FreeBSD > >> creating a kqueues based port would probably be the way to go. > >> > >> Andrew > >> > >> > >> > > There's already a JIRA for a freeBSD port: > > https://issues.apache.org/jira/browse/QPID-1811. You can > use that to > > recordideas and attach patches when it gets to that. > > > > > > > - > > Apache Qpid - AMQP Messaging Implementation > > Project: http://qpid.apache.org > > Use/Interact: mailto:dev-subscr...@qpid.apache.org > > > > > > > -- > Andrey Kotrekhov > - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: qpidc and FreeBSD
Please create a JIRA and attach to it. Also please make sure to check the box "Grant license to ASF for inclusion in ASF works (as per the Apache License §5) " There is also the following JIRA. https://issues.apache.org/jira/browse/QPID-1811 Rajith On Tue, Feb 2, 2010 at 9:34 AM, Andrey Kotrekhov wrote: > I have done a little patch. Should I register in JIRA to send it or may I > send it to somebody of developers? > > > > > > 2009/12/11 Alan Conway > >> On 12/10/2009 10:43 AM, Andrew Stitcher wrote: >> >>> On Thu, 2009-12-10 at 10:30 -0500, Rajith Attapattu wrote: >>> Hello Andrey No it's not off topic. Currently there is no effort on this. Are you interested in having a crack at this? There have been successful ports to windows and solaris. >>> >>> Currently the Solaris port does not build - and there isn't enough time >>> to get it working for the 0.6 release. >>> >>> Some of the problem here is due to the use of the SunPro C++ compiler >>> which has yet different quirks from the gcc and Visual Studio compilers >>> which currently can build qpid. >>> >>> >>> Please feel to join the dev list and ask questions. I am sure you will receive enough guidance on what to do. Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/ On Thu, Dec 10, 2009 at 10:11 AM, Andrey Kotrekhov wrote: > Hello. > Are there any plans to port qpidc to FreeBSD or other BSD* ? > >>> It would be great to port to a bsd. As long as you can use gcc4 then the >>> only significant area involved in the port is the Poller class which is >>> currently Linux specific (implemented in >>> cpp/src/qpid/sys/epoll/EpollPoller.cpp). >>> >>> The most general way to do this would be to port to use poll(). The >>> advantage here would be that this would be very portable to posix >>> systems. But this wouldn't have great performance. On FreeBSD creating a >>> kqueues based port would probably be the way to go. >>> >>> Andrew >>> >>> >>> >> There's already a JIRA for a freeBSD port: >> https://issues.apache.org/jira/browse/QPID-1811. You can use that to >> recordideas and attach patches when it gets to that. >> >> >> - >> Apache Qpid - AMQP Messaging Implementation >> Project: http://qpid.apache.org >> Use/Interact: mailto:dev-subscr...@qpid.apache.org >> >> > > > -- > Andrey Kotrekhov > -- 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
WsDmAdapterTest failure
Hi, The WsDmAdapterTest is failing, and I see the following exception in the logs. Is there anybody actively maintaining this code? If so I will create a JIRA and attach the complete log to the ticket. If not I will disable the test. 07:36:08,826 ERROR [QManAdapterCapability] : Unable to build WS artifacts. org.apache.qpid.management.wsdm.capabilities.ArtifactsNotAvailableException: java.lang.ClassCastException: org.apache.xml.dtm.ref.DTMManagerDefault cannot be cast to org.apache.xml.dtm.DTMManager at org.apache.qpid.management.wsdm.capabilities.WsArtifactsFactory.getArtifactsFor(WsArtifactsFactory.java:116) at org.apache.qpid.management.wsdm.capabilities.QManAdapterCapability$3.handleNotification(QManAdapterCapability.java:171) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor$ListenerWrapper.handleNotification(DefaultMBeanServerInterceptor.java:1732) at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:257) at javax.management.NotificationBroadcasterSupport$SendNotifJob.run(NotificationBroadcasterSupport.java:322) at javax.management.NotificationBroadcasterSupport$1.execute(NotificationBroadcasterSupport.java:307) at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:229) at org.apache.qpid.management.wsdm.QEmu.sendNotification(QEmu.java:88) at org.apache.qpid.management.wsdm.QEmu.createQueue(QEmu.java:74) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27) at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208) at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120) at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) at org.apache.qpid.management.wsdm.BaseWsDmAdapterTestCase.setUp(BaseWsDmAdapterTestCase.java:71) at junit.framework.TestCase.runBare(TestCase.java:128) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:297) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeInVM(JUnitTask.java:1072) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:682) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeOrQueue(JUnitTask.java:1434) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:633) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382) at org.apache.tools.ant.taskdefs.SubAnt.execute(SubAnt.java:277) at org.apache.tools.ant.taskdefs.SubAnt.execute(SubAnt.java:201) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:64) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
Re: qpidc and FreeBSD
I have done a little patch. Should I register in JIRA to send it or may I send it to somebody of developers? 2009/12/11 Alan Conway > On 12/10/2009 10:43 AM, Andrew Stitcher wrote: > >> On Thu, 2009-12-10 at 10:30 -0500, Rajith Attapattu wrote: >> >>> Hello Andrey >>> >>> No it's not off topic. >>> Currently there is no effort on this. >>> Are you interested in having a crack at this? >>> There have been successful ports to windows and solaris. >>> >> >> Currently the Solaris port does not build - and there isn't enough time >> to get it working for the 0.6 release. >> >> Some of the problem here is due to the use of the SunPro C++ compiler >> which has yet different quirks from the gcc and Visual Studio compilers >> which currently can build qpid. >> >> >> >>> Please feel to join the dev list and ask questions. >>> I am sure you will receive enough guidance on what to do. >>> >>> Regards, >>> >>> Rajith Attapattu >>> Red Hat >>> http://rajith.2rlabs.com/ >>> >>> On Thu, Dec 10, 2009 at 10:11 AM, Andrey Kotrekhov >>> wrote: >>> Hello. Are there any plans to port qpidc to FreeBSD or other BSD* ? >>> >> It would be great to port to a bsd. As long as you can use gcc4 then the >> only significant area involved in the port is the Poller class which is >> currently Linux specific (implemented in >> cpp/src/qpid/sys/epoll/EpollPoller.cpp). >> >> The most general way to do this would be to port to use poll(). The >> advantage here would be that this would be very portable to posix >> systems. But this wouldn't have great performance. On FreeBSD creating a >> kqueues based port would probably be the way to go. >> >> Andrew >> >> >> > There's already a JIRA for a freeBSD port: > https://issues.apache.org/jira/browse/QPID-1811. You can use that to > recordideas and attach patches when it gets to that. > > > - > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > > -- Andrey Kotrekhov
[jira] Created: (QPID-2383) Clustered broker crashes with sesame and qpid-queue-stat
Clustered broker crashes with sesame and qpid-queue-stat Key: QPID-2383 URL: https://issues.apache.org/jira/browse/QPID-2383 Project: Qpid Issue Type: Bug Components: C++ Clustering Affects Versions: 0.6 Reporter: Alan Conway Assignee: Alan Conway See https://bugzilla.redhat.com/show_bug.cgi?id=560692 -- 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-2364) Management updates in timer create inconsistencies in a cluster.
[ https://issues.apache.org/jira/browse/QPID-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved QPID-2364. --- Resolution: Fixed > Management updates in timer create inconsistencies in a cluster. > > > Key: QPID-2364 > URL: https://issues.apache.org/jira/browse/QPID-2364 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: 0.6 >Reporter: Alan Conway >Assignee: Alan Conway > Attachments: periodic-timer.patch > > > Management updates are triggered by a timer. They are not predictable for the > cluster and so can cause cluster shut-downs and inconsistent message delivery. > We have a hack in place that suppresses exceptions when the session receives > completions for transfers not yet sent (which is the usual manifestation of > the > unpredictability). I.e. we have in essence disabled consistency checking for > management sessions. This solved immediate problems but would quickly stop > working if sessions/connections could be used for management and other things > (as will be more likely with QMFv2 where using management becomes quite > straightforward). > In a cluster, management updates need to be synchronized by executing them in > the cluster dispatch thread rather than a timer thread. -- 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: 0.6RC4 available [Was: 0.6 Release - Query]
The docs are a bit ropey but I'm *fairly* sure it checks licenses. Anyone confirm ? Marnie On Fri, Jan 29, 2010 at 4:34 PM, Andrew Stitcher wrote: > On Fri, 2010-01-29 at 16:22 +, Marnie McCormack wrote: > > http://incubator.apache.org/rat/ > > Ah, thanks for that. Looks like it's in java though which might add some > time to me getting it working. > > Andrew > > > > - > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > >
[jira] Reopened: (QPID-2059) SubscriptionLoggingTest fails intermittently
[ https://issues.apache.org/jira/browse/QPID-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie reopened QPID-2059: -- Assignee: Martin Ritchie (was: Aidan Skinner) The testSubscriptionCreateDurable is still failing expecting 1 result but getting 0 > SubscriptionLoggingTest fails intermittently > > > Key: QPID-2059 > URL: https://issues.apache.org/jira/browse/QPID-2059 > Project: Qpid > Issue Type: Bug > Components: Java Tests >Affects Versions: 0.6 >Reporter: Aidan Skinner >Assignee: Martin Ritchie > Fix For: 0.6 > > > SubscriptionLoggingTest sometimes fails with: > junit.framework.AssertionFailedError: Result set not expected size: > expected:<3> but was:<1> > at > org.apache.qpid.server.logging.SubscriptionLoggingTest.testSubscriptionSuspend(SubscriptionLoggingTest.java:363) > > at > org.apache.qpid.test.utils.QpidTestCase.runBare(QpidTestCase.java:224) > at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:270) -- 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-2370) TTR-Qpid-07-NA failed due to channel error 504 during tear down
[ https://issues.apache.org/jira/browse/QPID-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie reassigned QPID-2370: Assignee: Robbie Gemmell (was: Martin Ritchie) Hi Robbie can you review these changes please. I commited the Broker and the client change (withStateCheck). Cheers. > TTR-Qpid-07-NA failed due to channel error 504 during tear down > --- > > Key: QPID-2370 > URL: https://issues.apache.org/jira/browse/QPID-2370 > Project: Qpid > Issue Type: Bug > Components: Java Performance Tests >Affects Versions: 0.6 >Reporter: Martin Ritchie >Assignee: Robbie Gemmell > Attachments: QPID-2370-Improve-BrokerDebug.patch, > QPID-2370.CheckClosedBeforeFlow.patch, > QPID-2370.CheckClosedBeforeFlowWithStateCheck.patch > > > During a full 'RunCore.sh' performance test run TTR-Qpid-07-NA hung holding > the test run up. This appeared to be as a result of a Channel Error that was > thrown during. > Thread-4 2010-01-26 03:29:48,722 ERROR [apache.qpid.client.AMQConnection] > error: > org.apache.qpid.AMQConnectionClosedException: Error: channel is closed [error > code 504: channel error] [error code 504: channel error] > This may have occured during test tear down as the following was logged by > the same thread just after the stack trace. > Thread-4 2010-01-26 03:29:48,725 WARN [apache.qpid.ping.PingTestPerf] There > was an exception during per thread tear down. -- 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-2370) TTR-Qpid-07-NA failed due to channel error 504 during tear down
[ https://issues.apache.org/jira/browse/QPID-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie updated QPID-2370: - Status: Ready To Review (was: In Progress) > TTR-Qpid-07-NA failed due to channel error 504 during tear down > --- > > Key: QPID-2370 > URL: https://issues.apache.org/jira/browse/QPID-2370 > Project: Qpid > Issue Type: Bug > Components: Java Performance Tests >Affects Versions: 0.6 >Reporter: Martin Ritchie >Assignee: Martin Ritchie > Attachments: QPID-2370-Improve-BrokerDebug.patch, > QPID-2370.CheckClosedBeforeFlow.patch, > QPID-2370.CheckClosedBeforeFlowWithStateCheck.patch > > > During a full 'RunCore.sh' performance test run TTR-Qpid-07-NA hung holding > the test run up. This appeared to be as a result of a Channel Error that was > thrown during. > Thread-4 2010-01-26 03:29:48,722 ERROR [apache.qpid.client.AMQConnection] > error: > org.apache.qpid.AMQConnectionClosedException: Error: channel is closed [error > code 504: channel error] [error code 504: channel error] > This may have occured during test tear down as the following was logged by > the same thread just after the stack trace. > Thread-4 2010-01-26 03:29:48,725 WARN [apache.qpid.ping.PingTestPerf] There > was an exception during per thread tear down. -- 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-1535) Test Failure : FailoverMethodTest
[ https://issues.apache.org/jira/browse/QPID-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828575#action_12828575 ] Martin Ritchie commented on QPID-1535: -- This issue has been addressed but the newer testNoFailover test is failing: Testcase: testNoFailover took 2.035 sec FAILED Notification of the connection failure took was : 100 >:(1003) junit.framework.AssertionFailedError: Notification of the connection failure took was : 100 >:(1003) at org.apache.qpid.server.failover.FailoverMethodTest.testNoFailover(FailoverMethodTest.java:228) > Test Failure : FailoverMethodTest > -- > > Key: QPID-1535 > URL: https://issues.apache.org/jira/browse/QPID-1535 > Project: Qpid > Issue Type: Bug > Components: Java Tests >Affects Versions: M4 >Reporter: Martin Ritchie >Priority: Minor > Attachments: > TEST-org.apache.qpid.server.failover.FailoverMethodTest.txt > > > This test failed on the local CC box because failover took to long. > Run output is attached. > testFailoverSingleDelay > org.apache.qpid.server.failover.FailoverMethodTest > at > org.apache.qpid.server.failover.FailoverMethodTest.testFailoverSingleDelay(FailoverMethodTest.java:139) -- 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
