[jira] Resolved: (QPID-2374) qpidd: --require-encryption with --auth no will reject SSL connections as being un-encrypted
[ https://issues.apache.org/jira/browse/QPID-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved QPID-2374. -- Resolution: Fixed --auth no and --require-encryption will now correctly identify TSL connections and accept them. qpidd: --require-encryption with --auth no will reject SSL connections as being un-encrypted - Key: QPID-2374 URL: https://issues.apache.org/jira/browse/QPID-2374 Project: Qpid Issue Type: Bug Components: C++ Broker Reporter: Ken Giusti Assignee: Ken Giusti Running qpidd with --auth no and --require-encryption will reject SSL-based encrypted connections. Running qpidd like so: $ ./qpidd --auth no --require-encryption --transport ssl --no-data-dir --no-module-dir --load-module ./.libs/ssl.so --ssl-cert-db /home/kgiusti/.test_ssl_cert_db/test_cert_db --ssl-cert-password-file /home/kgiusti/.test_ssl_cert_db/cert.password --ssl-cert-name localhost.localdomain 2010-01-28 10:11:35 notice SASL disabled: No Authentication Performed 2010-01-28 10:11:35 notice Listening on TCP port 5672 2010-01-28 10:11:35 notice Listening for SSL connections on TCP port 5671 5671 2010-01-28 10:11:35 notice Broker running And running perftest using SSL: $ export QPID_NO_MODULE_DIR=1 $ export QPID_LOAD_MODULE=./.libs/sslconnector.so $ export QPID_SSL_CERT_DB=/home/kgiusti/.test_ssl_cert_db/test_cert_db $ export QPID_SSL_CERT_PASSWORD_FILE=/home/kgiusti/.test_ssl_cert_db/cert.password $ ./tests/perftest --count 1 -P ssl -b localhost.localdomain --summary --port 5671 The connection is rejected, and the broker logs: 2010-01-28 10:13:18 error Rejected un-encrypted connection. I think the proper behavior would have the broker allow encrypted SSL connections, even if --auth no. -- 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-2376) C++ broker build broken at r
C++ broker build broken at r Key: QPID-2376 URL: https://issues.apache.org/jira/browse/QPID-2376 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.7 Environment: Linux (RHEL 5) Reporter: Steve Huston The overnight Linux trunk cmake build broke last night; errors are listed here: http://www.riverace.com/CDash-1.4.2/viewBuildError.php?buildid=398 From the looks of the error, I'm guessing that this change may be involved: SaslAuthenticator.cpp Revision: 904293 by kgiusti QPID-2374: Null authenticator now checks for SSL if --encryption-required specified -- 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: [jira] Updated: (QPID-2376) C++ broker build broken at 20:00 Thurs Jan 28, 2010
Thanks for checking into it Ken! Also, it's the Linux build that broke, not Windows. -Steve -Original Message- From: Ken Giusti [mailto:kgiu...@redhat.com] Sent: Friday, January 29, 2010 10:36 AM To: Steve Huston Cc: dev@qpid.apache.org Subject: Re: [jira] Updated: (QPID-2376) C++ broker build broken at 20:00 Thurs Jan 28, 2010 Sorry Steve, yes, this was my fault. I'll fix it immediately. Still need to get my Windows virtual machine setup building qpid -K - Steve Huston (JIRA) qpid-...@incubator.apache.org wrote: [ https://issues.apache.org/jira/browse/QPID-2376?page=com.atlassian.jir a.plugin.system.issuetabpanels:all-tabpanel ] Steve Huston updated QPID-2376: --- Summary: C++ broker build broken at 20:00 Thurs Jan 28, 2010 (was: C++ broker build broken at r) C++ broker build broken at 20:00 Thurs Jan 28, 2010 --- Key: QPID-2376 URL: https://issues.apache.org/jira/browse/QPID-2376 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.7 Environment: Linux (RHEL 5) Reporter: Steve Huston The overnight Linux trunk cmake build broke last night; errors are listed here: http://www.riverace.com/CDash-1.4.2/viewBuildError.php?buildid=398 From the looks of the error, I'm guessing that this change may be involved: SaslAuthenticator.cpp Revision: 904293 by kgiusti QPID-2374: Null authenticator now checks for SSL if --encryption-required specified -- 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 - 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 Fri, 2010-01-29 at 12:34 +, Marnie McCormack wrote: Andrew - did you run the rat tool on the rc ? What's that? A - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: [jira] Updated: (QPID-2376) C++ broker build broken at 20:00 Thurs Jan 28, 2010
Oh man - then I really don't have any excuse. :( I missed a conditional compile check. I just checked in a fix. Let me know if this doesn't fix it. http://svn.apache.org/viewcvs?view=revrev=904525 Thanks for finding that! -K - Steve Huston shus...@riverace.com wrote: Thanks for checking into it Ken! Also, it's the Linux build that broke, not Windows. -Steve -Original Message- From: Ken Giusti [mailto:kgiu...@redhat.com] Sent: Friday, January 29, 2010 10:36 AM To: Steve Huston Cc: dev@qpid.apache.org Subject: Re: [jira] Updated: (QPID-2376) C++ broker build broken at 20:00 Thurs Jan 28, 2010 Sorry Steve, yes, this was my fault. I'll fix it immediately. Still need to get my Windows virtual machine setup building qpid -K - Steve Huston (JIRA) qpid-...@incubator.apache.org wrote: [ https://issues.apache.org/jira/browse/QPID-2376?page=com.atlassian.jir a.plugin.system.issuetabpanels:all-tabpanel ] Steve Huston updated QPID-2376: --- Summary: C++ broker build broken at 20:00 Thurs Jan 28, 2010 (was: C++ broker build broken at r) C++ broker build broken at 20:00 Thurs Jan 28, 2010 --- Key: QPID-2376 URL: https://issues.apache.org/jira/browse/QPID-2376 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.7 Environment: Linux (RHEL 5) Reporter: Steve Huston The overnight Linux trunk cmake build broke last night; errors are listed here: http://www.riverace.com/CDash-1.4.2/viewBuildError.php?buildid=398 From the looks of the error, I'm guessing that this change may be involved: SaslAuthenticator.cpp Revision: 904293 by kgiusti QPID-2374: Null authenticator now checks for SSL if --encryption-required specified -- 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 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2377) ssl errors are not signalled correctly in nss based impl
ssl errors are not signalled correctly in nss based impl Key: QPID-2377 URL: https://issues.apache.org/jira/browse/QPID-2377 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Reporter: Gordon Sim this is due to making the handshake non-blocking: http://svn.apache.org/viewvc?view=revisionrevision=790291 -- 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]
http://incubator.apache.org/rat/ Can a previous rel manager tell Andrew some more (I can't rem that far back as M1 !) - the website is rubbish. M On Fri, Jan 29, 2010 at 3:51 PM, Andrew Stitcher astitc...@redhat.comwrote: On Fri, 2010-01-29 at 12:34 +, Marnie McCormack wrote: Andrew - did you run the rat tool on the rc ? What's that? A - 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 release notes should be generated out of JIRA for 0.6. items imho - certainly for the Java items. Highlights can of course be hand crafted if desired by anyone. Marnie On Fri, Jan 29, 2010 at 3:51 PM, Andrew Stitcher astitc...@redhat.comwrote: On Fri, 2010-01-29 at 11:31 +, Gordon Sim wrote: On 01/28/2010 04:42 PM, Andrew Stitcher wrote: I put up an RC4 on Tuesday, I just forgot to tell anyone about it! As usual you'll find it at: http://qpid.apache.org/dist/qpid-0.6rc4 The release notes appear unchanged and still refer to M4. I won't myself block release for that, but if have checked in corrections - so that the information is at least not embarrassingly stale even if it is not very informative - if there is a desire to fix that. As I said several times before, I do not have enough time to go through and do comprehensive release notes, as I've received exactly 3 lines of release notes I've not done anything yet. - they won't happen unless other people contribute. I can certainly remove erroneous references to M4 though. The WCF client zip doesn't contain any license info; I believe that is a requirement for any release artefact. On that topic are there any updates we need to make to any of the other licensing notices? I get cluster_test failures (on fedora 12) when running this: 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: 31726; uid: 500; exit value: 9 ClusterFailover.cpp(61): last checkpoint **2010-01-29 11:14:11 warning Connection closed unknown location(0): fatal error in testConnectionKnownHosts: child was killed; pid: 32483; uid: 500; exit value: 9 cluster_test.cpp(537): last checkpoint *unknown location(0): fatal error in testUpdateConsumers: memory access violation at address: 0x07d5ddbc: invalid permissions cluster_test.cpp(537): last checkpoint * *** 3 failures detected in test suite Master Test Suite FAIL: run_cluster_test However the same errors appear for rc3 as well, so its not a regression since then. This is an issue I fixed on trunk last week - I don't think it was reported in Jira. Its actually a problem with the tests code rather than the code itself. Fixed in r903008 Andrew - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Problems with certs
On 01/29/2010 01:21 PM, Steve Huston wrote: Just as a separate data point I have RHEL 5 w/ valid certs created per the instructions given. If I step through those instructions manually I also get valid certs and can successfully run perftest against the broker using ssl. Perhaps there is an issue with the script(?). - 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 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
Re: 0.6RC4 available [Was: 0.6 Release - Query]
On 01/29/2010 03:51 PM, Andrew Stitcher wrote: On Fri, 2010-01-29 at 11:31 +, Gordon Sim wrote: On 01/28/2010 04:42 PM, Andrew Stitcher wrote: I put up an RC4 on Tuesday, I just forgot to tell anyone about it! As usual you'll find it at: http://qpid.apache.org/dist/qpid-0.6rc4 The release notes appear unchanged and still refer to M4. I won't myself block release for that, but if have checked in corrections - so that the information is at least not embarrassingly stale even if it is not very informative - if there is a desire to fix that. As I said several times before, I do not have enough time to go through and do comprehensive release notes, as I've received exactly 3 lines of release notes I've not done anything yet. - they won't happen unless other people contribute. I can certainly remove erroneous references to M4 though. Understood and I'm not asking for any thing comprehensive. I have already checked in corrections to remove the M4 references. The WCF client zip doesn't contain any license info; I believe that is a requirement for any release artefact. On that topic are there any updates we need to make to any of the other licensing notices? I get cluster_test failures (on fedora 12) when running this: 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: 31726; uid: 500; exit value: 9 ClusterFailover.cpp(61): last checkpoint **2010-01-29 11:14:11 warning Connection closed unknown location(0): fatal error in testConnectionKnownHosts: child was killed; pid: 32483; uid: 500; exit value: 9 cluster_test.cpp(537): last checkpoint *unknown location(0): fatal error in testUpdateConsumers: memory access violation at address: 0x07d5ddbc: invalid permissions cluster_test.cpp(537): last checkpoint * *** 3 failures detected in test suite Master Test Suite FAIL: run_cluster_test However the same errors appear for rc3 as well, so its not a regression since then. This is an issue I fixed on trunk last week - I don't think it was reported in Jira. Its actually a problem with the tests code rather than the code itself. Fixed in r903008 Great, we can ignore that then. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Problems with certs
On Fri, 2010-01-29 at 16:24 +, Gordon Sim wrote: On 01/29/2010 01:21 PM, Steve Huston wrote: Just as a separate data point I have RHEL 5 w/ valid certs created per the instructions given. If I step through those instructions manually I also get valid certs and can successfully run perftest against the broker using ssl. Perhaps there is an issue with the script(?). Always possible, even likely. I started by stepping through that page by hand; I wrote the script because I kept failing at it and wanted to make sure I was doing stuff consistently. Are there any tools around for diagnosing what's different about this set of certs vs that other set of certs? - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Problems with certs
On 01/29/2010 04:46 PM, john dunning wrote: On Fri, 2010-01-29 at 16:24 +, Gordon Sim wrote: On 01/29/2010 01:21 PM, Steve Huston wrote: Just as a separate data point I have RHEL 5 w/ valid certs created per the instructions given. If I step through those instructions manually I also get valid certs and can successfully run perftest against the broker using ssl. Perhaps there is an issue with the script(?). Always possible, even likely. I started by stepping through that page by hand; I wrote the script because I kept failing at it and wanted to make sure I was doing stuff consistently. Are there any tools around for diagnosing what's different about this set of certs vs that other set of certs? certutil itself is the only one I know of - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Problems with certs
On Fri, 2010-01-29 at 16:51 +, Gordon Sim wrote: On 01/29/2010 04:46 PM, john dunning wrote: Are there any tools around for diagnosing what's different about this set of certs vs that other set of certs? certutil itself is the only one I know of Can you tar up your certs that you did by hand and fling them at me? Perhaps I can tell something by printing them with certutil and look for discrepancies between yours and mine. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2371) Missing includes for MSVC 2005 compiler
[ https://issues.apache.org/jira/browse/QPID-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Huston updated QPID-2371: --- Fix Version/s: (was: 0.6) 0.7 Assignee: Steve Huston I changed the fix version to 0.7. 0.6 is in the release process and can't be held back for this issue since this is not a regression from 0.5. 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
[jira] Created: (QPID-2378) WCF/C++ Client subtree lacks Apache licensing files
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 Priority: Blocker Fix For: 0.6 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 ] Cliff Jansen updated QPID-2378: --- Attachment: QPID-2378.patch LICENSE.txt and NOTICE.txt 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 Priority: Blocker Fix For: 0.6 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] Assigned: (QPID-2376) C++ broker build broken at 20:00 Thurs Jan 28, 2010
[ https://issues.apache.org/jira/browse/QPID-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti reassigned QPID-2376: Assignee: Ken Giusti C++ broker build broken at 20:00 Thurs Jan 28, 2010 --- Key: QPID-2376 URL: https://issues.apache.org/jira/browse/QPID-2376 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.7 Environment: Linux (RHEL 5) Reporter: Steve Huston Assignee: Ken Giusti The overnight Linux trunk cmake build broke last night; errors are listed here: http://www.riverace.com/CDash-1.4.2/viewBuildError.php?buildid=398 From the looks of the error, I'm guessing that this change may be involved: SaslAuthenticator.cpp Revision: 904293 by kgiusti QPID-2374: Null authenticator now checks for SSL if --encryption-required specified -- 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-2376) C++ broker build broken at 20:00 Thurs Jan 28, 2010
[ https://issues.apache.org/jira/browse/QPID-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved QPID-2376. -- Resolution: Fixed Resolved on trunk, http://svn.apache.org/viewcvs?view=revrev=904525 C++ broker build broken at 20:00 Thurs Jan 28, 2010 --- Key: QPID-2376 URL: https://issues.apache.org/jira/browse/QPID-2376 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.7 Environment: Linux (RHEL 5) Reporter: Steve Huston Assignee: Ken Giusti The overnight Linux trunk cmake build broke last night; errors are listed here: http://www.riverace.com/CDash-1.4.2/viewBuildError.php?buildid=398 From the looks of the error, I'm guessing that this change may be involved: SaslAuthenticator.cpp Revision: 904293 by kgiusti QPID-2374: Null authenticator now checks for SSL if --encryption-required specified -- 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: Problems with certs
On 01/29/2010 04:46 PM, john dunning wrote: On Fri, 2010-01-29 at 16:24 +, Gordon Sim wrote: On 01/29/2010 01:21 PM, Steve Huston wrote: Just as a separate data point I have RHEL 5 w/ valid certs created per the instructions given. If I step through those instructions manually I also get valid certs and can successfully run perftest against the broker using ssl. Perhaps there is an issue with the script(?). Always possible, even likely. I think I've found the issue. The script doesn't select 'Server Auth' and 'Client Auth' when issuing and signing the server/client certificates. E.g. it should be: x certutil -C -d $dir/CA_db -c $ca_pretty_name -a -i $dir/server_db/server.req -o $dir/server_db/server.crt -f $dir/cert.password -z $dir/random -2 -6 EOF 0 9 n n -1 EOF and: x certutil -C -d $dir/CA_db -c $ca_pretty_name -a -i $dir/client_db/client.req -o $dir/client_db/client.crt -f $dir/cert.password -z $dir/random -2 -6 EOF 1 9 n n -1 n EOF (Where 0 selects server auth and 1 selects client auth). With that change then verification of the generated certs works and (providing you have the right hostname for the cert and use that when connecting) I can get perftest to run over ssl using the certs generated by the script. - 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]
Please apply QPID-2378 to the 0.6 branch to pick up the WCF client specific release notes I'm sorry. I mean QPID-2313. Cliff -Original Message- From: Cliff Jansen (Interop Systems Inc) [mailto:v-clj...@microsoft.com] Sent: Friday, January 29, 2010 12:07 PM To: dev@qpid.apache.org; Andrew Stitcher Subject: RE: 0.6RC4 available [Was: 0.6 Release - Query] Hi Andrew, My deepest apologies for missing the Licensing files outage. I have attached patches to QPID-2378 to fix this. As I said several times before, I do not have enough time to go through and do comprehensive release notes, as I've received exactly 3 lines of release notes I've not done anything yet. Please apply QPID-2378 to the 0.6 branch to pick up the WCF client specific release notes which describe planned features, build instructions, transaction configuration settings, and known issues. Thanks. Cliff
[jira] Updated: (QPID-1440) [Java Client] - Tidy up tasks from QPID-1289
[ https://issues.apache.org/jira/browse/QPID-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-1440: - Affects Version/s: 0.5 Fix Version/s: 0.6 [Java Client] - Tidy up tasks from QPID-1289 Key: QPID-1440 URL: https://issues.apache.org/jira/browse/QPID-1440 Project: Qpid Issue Type: Sub-task Components: Java Client Affects Versions: M4, 0.5 Reporter: Rob Godfrey Assignee: Rob Godfrey Priority: Minor Fix For: 0.6 Review points from QPID-1289: AMQSession.java : _defaultPrefetchHighMark; _defaultPrefetchLowMark; should probably have the word default removed from their name AMQConnection.java: protected int _maxPrefetch; ... protected member varibales are (in general) evil... what is the justification for this over using getters/setters? ClientProperties.java: + public static final String MAX_PREFETCH_DEFAULT = 5000; What is the reason for making the already large (1000) default even larger? The JIRA text above says make it 500 XAConnectionImpl.java: + return _delegate.createXASession(_maxPrefetch, _maxPrefetch / 2); Why put this logic in the XAConnectionImpl? Surely we should have a method on the underlying connection which takes no arguments - and it can work out the default prefetch values? StreamMessageTest.java: - consumerSession.createConsumer(queue, AMQSession.DEFAULT_PREFETCH_LOW_MARK, - AMQSession.DEFAULT_PREFETCH_HIGH_MARK, false, false, (String) null, ft); + consumerSession.createConsumer(queue, Integer.parseInt(ClientProperties.MAX_PREFETCH_DEFAULT), Integer.parseInt(ClientProperties.MAX_PREFETCH_DEFAULT), false, false, (String) null, ft); This seems like a change in the test... what it really seems to suggest is that there should be a createConsumer method where you don't have to pass this in... since we clearly do not care about it in this instance, and we are having to repeat code that should be elsewhere (getting the defaults from client properties) ReturnUnroutableMandatoryMessageTest.java : same comment as for Stream message test -- 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: Problems with certs
On Fri, 2010-01-29 at 19:34 +, Gordon Sim wrote: On 01/29/2010 04:46 PM, john dunning wrote: On Fri, 2010-01-29 at 16:24 +, Gordon Sim wrote: On 01/29/2010 01:21 PM, Steve Huston wrote: Just as a separate data point I have RHEL 5 w/ valid certs created per the instructions given. If I step through those instructions manually I also get valid certs and can successfully run perftest against the broker using ssl. Perhaps there is an issue with the script(?). Always possible, even likely. I think I've found the issue. The script doesn't select 'Server Auth' and 'Client Auth' when issuing and signing the server/client certificates. E.g. it should be: Cool! Thank you! I'll try it when I get untangled from the bug I'm looking at now. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-2365) Reroute messages on a queue - remove messages from a queue and send them to an exchange
[ https://issues.apache.org/jira/browse/QPID-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-2365. Resolution: Fixed Reroute messages on a queue - remove messages from a queue and send them to an exchange --- Key: QPID-2365 URL: https://issues.apache.org/jira/browse/QPID-2365 Project: Qpid Issue Type: New Feature Components: C++ Broker Affects Versions: 0.7 Reporter: Ted Ross Assignee: Ted Ross Priority: Minor Fix For: 0.7 The Queue.Purge method simply discards messages (as it should) without sending them to an alternate exchange, even if one is configured for the queue. There are cases where it is desirable to take messages from a queue and re-route them through an exchange. In this case, a new method (Queue.Reroute) should be added. The proposed spec for this method follows: method name=reroute desc=Remove all or some messages on this queue and route them to an exchange arg name=request dir=I type=uint32 desc=0 for all messages or n0 for n messages/ arg name=useAltExchange dir=I type=bool desc=Iff true, use the queue's configured alternate exchange; iff false, use exchange named in the 'exchange' argument/ arg name=exchange dir=I type=sstr desc=Name of the exchange to route the messages through/ /method This method allows for messages to be sent to the alternate exchange (if configured) or to an exchange specified by the caller. -- 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
GSoC Projects Mentors ?
All, GSoC submissions start in March so we should begin to pull together the list of Qpid project outlines for prospective students. Can those willing/able to act as mentors this year please also reply on this thread ? Every project outline needs at least one mentor, preferably 1 + backup. I've tidied up the page from last year, and removed any items I know from the Java side wouldn't be easy for a GSoC-er to do. The page is here: http://cwiki.apache.org/confluence/display/qpid/GSoC Every outline needs details and mentor(s). I'll update the page details once we have an idea on the mentors available. Thanks Regards, Marnie
[jira] Assigned: (QPID-2369) TTR-Qpid-03-TX logs 'Got unexpected message with correlationId: xx'
[ https://issues.apache.org/jira/browse/QPID-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie reassigned QPID-2369: Assignee: Martin Ritchie TTR-Qpid-03-TX logs 'Got unexpected message with correlationId: xx' --- Key: QPID-2369 URL: https://issues.apache.org/jira/browse/QPID-2369 Project: Qpid Issue Type: Bug Components: Java Performance Tests, Java Tests Affects Versions: 0.5, 0.6 Reporter: Martin Ritchie Assignee: Martin Ritchie Priority: Minor When running through the perftest package of tests (Using perftests/bin/RunCore.sh) there was a warning logged: Dispatcher-Channel-1 2010-01-25 14:42:54,218 WARN [apache.qpid.requestreply.PingPongProducer] Got unexpected message with correlationId: 52 This came from the TTR-Qpid-03-TX test. The cause of this failure is that messages from a previous test cycle have been left behind and are unknown to the current cycle. This is logged as a warning and does not constitute a failure of the test. IIRC this check was added to ensure that data not generated by this test did not interfere with the current test run. However, this warning is not normally seen and has only started occuring consistently recently. Investigation into the exact cause and why it is only this test that shows the warnings would be helpful. -- 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: exceptions in the new apis
On 01/28/2010 07:20 PM, Rajith Attapattu wrote: For example the application may need to distinguish between the following scenarios as the behaviour could be different for each case. Connection closed with an error code - the behaviour would depend on the error code. Host unreachable - it may try the same broker after configurable interval in case it was due to a temporary network failure. Connection refused - then it may decide to try the next know broker. While network and broker failure are indeed different conditions - which I think is your key point - I'm not sure it would always be possible to accurately determine which one[1] it was and I'm still not entirely that anyone would want to treat those differently. [1] There is for example also the case (different from both of these) where the network connection is established (e.g. socket is accepted) but the broker or network fails before AMQP connection handshaking completes. - 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 01/28/2010 04:42 PM, Andrew Stitcher wrote: I put up an RC4 on Tuesday, I just forgot to tell anyone about it! As usual you'll find it at: http://qpid.apache.org/dist/qpid-0.6rc4 The release notes appear unchanged and still refer to M4. I won't myself block release for that, but if have checked in corrections - so that the information is at least not embarrassingly stale even if it is not very informative - if there is a desire to fix that. The WCF client zip doesn't contain any license info; I believe that is a requirement for any release artefact. On that topic are there any updates we need to make to any of the other licensing notices? I get cluster_test failures (on fedora 12) when running this: 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: 31726; uid: 500; exit value: 9 ClusterFailover.cpp(61): last checkpoint **2010-01-29 11:14:11 warning Connection closed unknown location(0): fatal error in testConnectionKnownHosts: child was killed; pid: 32483; uid: 500; exit value: 9 cluster_test.cpp(537): last checkpoint *unknown location(0): fatal error in testUpdateConsumers: memory access violation at address: 0x07d5ddbc: invalid permissions cluster_test.cpp(537): last checkpoint * *** 3 failures detected in test suite Master Test Suite FAIL: run_cluster_test However the same errors appear for rc3 as well, so its not a regression since then. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2369) TTR-Qpid-03-TX logs 'Got unexpected message with correlationId: xx'
[ https://issues.apache.org/jira/browse/QPID-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12806312#action_12806312 ] Martin Ritchie commented on QPID-2369: -- The recent change to use 500 as the max_prefetch default has caused the consume rate to drop sufficiently for this test to fail. Setting max_prefetch back to 5000 resolves this issue. TTR-Qpid-03-TX logs 'Got unexpected message with correlationId: xx' --- Key: QPID-2369 URL: https://issues.apache.org/jira/browse/QPID-2369 Project: Qpid Issue Type: Bug Components: Java Performance Tests, Java Tests Affects Versions: 0.5, 0.6 Reporter: Martin Ritchie Assignee: Martin Ritchie Priority: Minor When running through the perftest package of tests (Using perftests/bin/RunCore.sh) there was a warning logged: Dispatcher-Channel-1 2010-01-25 14:42:54,218 WARN [apache.qpid.requestreply.PingPongProducer] Got unexpected message with correlationId: 52 This came from the TTR-Qpid-03-TX test. The cause of this failure is that messages from a previous test cycle have been left behind and are unknown to the current cycle. This is logged as a warning and does not constitute a failure of the test. IIRC this check was added to ensure that data not generated by this test did not interfere with the current test run. However, this warning is not normally seen and has only started occuring consistently recently. Investigation into the exact cause and why it is only this test that shows the warnings would be helpful. -- 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-2369) TTR-Qpid-03-TX logs 'Got unexpected message with correlationId: xx'
[ https://issues.apache.org/jira/browse/QPID-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Ritchie updated QPID-2369: - Attachment: QPID-2369-Restore-5k-prefetch.out Add patch that ensures the perftests all run with a 5000 prefetch. Should we be doing this for all tests? Only TTR-Qpid3-Tx has failed as a result of the new lower, 500, prefetch. Should we have some way of setting System properties or additional values in the scripts.xml file? TTR-Qpid-03-TX logs 'Got unexpected message with correlationId: xx' --- Key: QPID-2369 URL: https://issues.apache.org/jira/browse/QPID-2369 Project: Qpid Issue Type: Bug Components: Java Performance Tests, Java Tests Affects Versions: 0.5, 0.6 Reporter: Martin Ritchie Assignee: Martin Ritchie Priority: Minor Attachments: QPID-2369-Restore-5k-prefetch.out When running through the perftest package of tests (Using perftests/bin/RunCore.sh) there was a warning logged: Dispatcher-Channel-1 2010-01-25 14:42:54,218 WARN [apache.qpid.requestreply.PingPongProducer] Got unexpected message with correlationId: 52 This came from the TTR-Qpid-03-TX test. The cause of this failure is that messages from a previous test cycle have been left behind and are unknown to the current cycle. This is logged as a warning and does not constitute a failure of the test. IIRC this check was added to ensure that data not generated by this test did not interfere with the current test run. However, this warning is not normally seen and has only started occuring consistently recently. Investigation into the exact cause and why it is only this test that shows the warnings would be helpful. -- 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-2375) --load-module msgstore.so without --store-dir causes explosion
[ https://issues.apache.org/jira/browse/QPID-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12806320#action_12806320 ] Kim van der Riet commented on QPID-2375: I have just tried this operation on trunk: $ ./qpidd --load-module /path/to/msgstore.so --load-module /path/to/cluster.so --cluster-name clusterX --port 0 --no-data-dir --auth no 2010-01-29 07:06:36 critical Unexpected error: msgstore: If --data-dir is blank or --no-data-dir is specified, --store-dir must be present. ... which is the response I expected. Can you provide more details on the versions of qpid/store? In particular, are the store and cluster libs matched to the version of qpid correctly? ie, are you sure that the cluster lib is the one you built and not one that was previously installed? I see from your command above that qpid was run from the src dir, and the store lib also has an absolute path to a build location, but not so with the cluster lib. qpid r.904000 store r.3814 --load-module msgstore.so without --store-dir causes explosion -- Key: QPID-2375 URL: https://issues.apache.org/jira/browse/QPID-2375 Project: Qpid Issue Type: Bug Components: C++ Broker Environment: Running from trunk, on F12 Reporter: john dunning Priority: Minor I was testing something else, tried to start a broker with a msgstore, and omitted the store-dir: [r...@jrd cpp]# src/.libs/qpidd -p5672 --auth no --load-module cluster.so --cluster-name=foo --load-module /home/jrd/work/messaging/sre/store/trunk/cpp/lib/.libs/msgstore.so --no-data-dir --log-enable trace 2010-01-28 16:42:04 trace SEND PackageInd package=org.apache.qpid.broker to=schema.package Segmentation fault (core dumped) [r...@jrd cpp]# With --store-dir it starts ok. I realize it might not be expected to work, but probably should die more gracefully. -- 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]
Andrew - did you run the rat tool on the rc ? Marnie On Fri, Jan 29, 2010 at 11:31 AM, Gordon Sim g...@redhat.com wrote: On 01/28/2010 04:42 PM, Andrew Stitcher wrote: I put up an RC4 on Tuesday, I just forgot to tell anyone about it! As usual you'll find it at: http://qpid.apache.org/dist/qpid-0.6rc4 The release notes appear unchanged and still refer to M4. I won't myself block release for that, but if have checked in corrections - so that the information is at least not embarrassingly stale even if it is not very informative - if there is a desire to fix that. The WCF client zip doesn't contain any license info; I believe that is a requirement for any release artefact. On that topic are there any updates we need to make to any of the other licensing notices? I get cluster_test failures (on fedora 12) when running this: 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: 31726; uid: 500; exit value: 9 ClusterFailover.cpp(61): last checkpoint **2010-01-29 11:14:11 warning Connection closed unknown location(0): fatal error in testConnectionKnownHosts: child was killed; pid: 32483; uid: 500; exit value: 9 cluster_test.cpp(537): last checkpoint *unknown location(0): fatal error in testUpdateConsumers: memory access violation at address: 0x07d5ddbc: invalid permissions cluster_test.cpp(537): last checkpoint * *** 3 failures detected in test suite Master Test Suite FAIL: run_cluster_test However the same errors appear for rc3 as well, so its not a regression since then. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Problems with certs
On 01/27/2010 06:31 PM, john dunning wrote: Hi all. While trying to test something else, I attempted to set up my qpidd with some certs, according to the instructions in http://www.mozilla.org/projects/security/pki/nss/ref/ssl/gtstd.html I'm losing big time; I can start qpidd ok, but when I try to connect to it, both client and server flame, with errors like this: 2010-01-27 12:49:23 error Error reading socket: Unknown error 18446744073709551615(-1) That error does seem to be a regression of some sort; on an earlier version I get the following logged on the broker: 2010-jan-29 07:21:49 error Could not accept socket: Failed: SSL peer cannot verify your certificate. [-12271] (qpid/sy/ssl/SslSocket.cpp:123) My initial guess would be that perhaps changes around the connection code have broken correct error handling in some way (or for some conditions). I've kicked it around with some folks around here, and the concensus is that either there's something non-obvious wrong with my certs, or a new bug has crept into the code. I believe the ssl tests do not include testing certs of the form produced by the above instructions. Does anybody have insight/experience running this way? I originally created the certs by hand, but ended up re-doing it enough times that it was worth it to write it down. Attached is the script I've been using generate the certs; it's essentially a transcription of the instructions in the above page. After running that script on rhel5 (nss-tools-3.12.3.99.3-1.el5_3.2) and then trying to verify the certs as per the page you link to above, I get: certutil: certificate is invalid: Certificate type not approved for application. Do you see the same? If so that suggests On f11 (nss-tools-3.12.4-3.fc11.i586) the script fails mid way through with an error: certutil -A -d ./server_db -n redhat.com -a -i ./server_db/server.crt -t ,, -f ./cert.password -z ./random certutil: could not obtain certificate from file: You are attempting to import a cert with the same issuer/serial as an existing cert, but that is not the same cert. Error 255 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
RE: Problems with certs
Just as a separate data point I have RHEL 5 w/ valid certs created per the instructions given. I'm losing big time; I can start qpidd ok, but when I try to connect to it, both client and server flame, with errors like this: 2010-01-27 12:49:23 error Error reading socket: Unknown error 18446744073709551615(-1) When doing some initial testing from Linux client to Windows broker, I get this same message (or something very close) on the Linux client. That error does seem to be a regression of some sort; on an earlier version I get the following logged on the broker: 2010-jan-29 07:21:49 error Could not accept socket: Failed: SSL peer cannot verify your certificate. [-12271] (qpid/sy/ssl/SslSocket.cpp:123) My initial guess would be that perhaps changes around the connection code have broken correct error handling in some way (or for some conditions). Right... Getting that latter message would have been very helpful :-) -Steve - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-2375) --load-module msgstore.so without --store-dir causes explosion
[ https://issues.apache.org/jira/browse/QPID-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] john dunning resolved QPID-2375. Resolution: Cannot Reproduce Apparently this was cruft in my environment. I updated to qpid svn 904375 and msgstore svn 3830, rebuilt everything, and it stopped croaking, now errors with exactly the right message. Never mind. --load-module msgstore.so without --store-dir causes explosion -- Key: QPID-2375 URL: https://issues.apache.org/jira/browse/QPID-2375 Project: Qpid Issue Type: Bug Components: C++ Broker Environment: Running from trunk, on F12 Reporter: john dunning Priority: Minor I was testing something else, tried to start a broker with a msgstore, and omitted the store-dir: [r...@jrd cpp]# src/.libs/qpidd -p5672 --auth no --load-module cluster.so --cluster-name=foo --load-module /home/jrd/work/messaging/sre/store/trunk/cpp/lib/.libs/msgstore.so --no-data-dir --log-enable trace 2010-01-28 16:42:04 trace SEND PackageInd package=org.apache.qpid.broker to=schema.package Segmentation fault (core dumped) [r...@jrd cpp]# With --store-dir it starts ok. I realize it might not be expected to work, but probably should die more gracefully. -- 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
