[jira] Resolved: (QPID-3142) enable brokers to use a pre-populated QPID-WORK directory during test run

[ https://issues.apache.org/jira/browse/QPID-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-3142. -- Resolution: Fixed Hi Robbie Looks good to me. No comments. regards Keith enable brokers to use a

[jira] Created: (QPID-3148) Seg fault caused by Buffer::putRawData(const string s)

Seg fault caused by Buffer::putRawData(const string s) --- Key: QPID-3148 URL: https://issues.apache.org/jira/browse/QPID-3148 Project: Qpid Issue Type: Improvement Environment:

[jira] Created: (QPID-3149) Set up Hudson Continuous Integration

Set up Hudson Continuous Integration Key: QPID-3149 URL: https://issues.apache.org/jira/browse/QPID-3149 Project: Qpid Issue Type: Task Components: Build Tools Affects Versions: 0.11

0-10 merge request: trivial fix to qpidd timer warnings

r684783 is a trivial fix for a bug that prints incorrect warnings for late-and-overran timer tasks. Its not important but its very low risk. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org

[jira] Updated: (QPID-2352) Add SASL encryption support for Java client

[ https://issues.apache.org/jira/browse/QPID-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu updated QPID-2352: --- Fix Version/s: (was: 0.9) Future Add SASL encryption support for Java

[jira] Updated: (QPID-2316) 0.6RC2 C++ Build fails if ruby-dev and swig installed

[ https://issues.apache.org/jira/browse/QPID-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated QPID-2316: --- Fix Version/s: (was: 0.9) 0.11 The proper resolution for this is to enforce that the

[jira] Updated: (QPID-3061) Discrepancies between CMake and Automake

[ https://issues.apache.org/jira/browse/QPID-3061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated QPID-3061: --- Fix Version/s: (was: 0.9) 0.11 I'm keeping this issue open because there are more

[jira] Resolved: (QPID-3144) qpidd --check does not work with info logging and --log-to-stdout=yes

[ https://issues.apache.org/jira/browse/QPID-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved QPID-3144. --- Resolution: Fixed qpidd --check does not work with info logging and --log-to-stdout=yes

[jira] Updated: (QPID-2228) C++ make dist builds the entire broker just to print out qpidd --help

[ https://issues.apache.org/jira/browse/QPID-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher updated QPID-2228: -- Component/s: C++ Broker Affects Version/s: 0.11 0.10 C++ make

[jira] Commented: (QPID-2560) WCF to WCF PubSub sample is mis-named or needs to be re-designed

[ https://issues.apache.org/jira/browse/QPID-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13008064#comment-13008064 ] Justin Ross commented on QPID-2560: --- Hi, Cliff. Any updates for this one? If it makes

[jira] Updated: (QPID-2951) QMF: C++ example agent needs to be properly integrated into the release distribution.

[ https://issues.apache.org/jira/browse/QPID-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti updated QPID-2951: - Affects Version/s: 0.10 Fix Version/s: 0.11 Assignee: Ken Giusti QMF: C++ example

[jira] Commented: (QPID-2656) Verify/correct error handling on 0-10 broker codepath

[ https://issues.apache.org/jira/browse/QPID-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13008080#comment-13008080 ] Justin Ross commented on QPID-2656: --- Hi, Andrew. Any updates here? Verify/correct

[jira] Assigned: (QPID-2968) Blocking on dead sockets

[ https://issues.apache.org/jira/browse/QPID-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming reassigned QPID-2968: - Assignee: Rafael H. Schloming Blocking on dead sockets

[jira] Assigned: (QPID-3116) rubygen with ruby 1.9

[ https://issues.apache.org/jira/browse/QPID-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway reassigned QPID-3116: - Assignee: Alan Conway rubygen with ruby 1.9 - Key:

[jira] Created: (QPID-3150) sasl_fed test fails to specify client's sasl mechanism

sasl_fed test fails to specify client's sasl mechanism -- Key: QPID-3150 URL: https://issues.apache.org/jira/browse/QPID-3150 Project: Qpid Issue Type: Bug Components: C++ Broker

[jira] Commented: (QPID-3116) rubygen with ruby 1.9

[ https://issues.apache.org/jira/browse/QPID-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13008102#comment-13008102 ] Alan Conway commented on QPID-3116: --- Comitted to trunk #1082670. rubygen with ruby 1.9

[jira] Updated: (QPID-3116) rubygen with ruby 1.9

[ https://issues.apache.org/jira/browse/QPID-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated QPID-3116: -- Fix Version/s: (was: 0.9) 0.10 rubygen with ruby 1.9 -

[jira] Resolved: (QPID-3127) Accept mode should be NONE for 0-10 NO_ACKNOWLEDGE subscriptions

[ https://issues.apache.org/jira/browse/QPID-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-3127. Resolution: Fixed Fix Version/s: (was: 0.11) There are tests that already cover

Broken C++ trunk: cluster_tests.ShortTests.test_sasl

This test is currently failing on trunk: cd src/; make check TESTS=run_cluster_tests CLUSTER_TESTS=*sasl According to git-bisect the culprit is: 1082478: added support for address assertion The failure looks like this: cluster_tests.ShortTests.test_sasl

Re: Broken C++ trunk: cluster_tests.ShortTests.test_sasl

Should be fixed now. --Rafael On 03/17/2011 04:28 PM, Alan Conway wrote: This test is currently failing on trunk: cd src/; make check TESTS=run_cluster_tests CLUSTER_TESTS=*sasl According to git-bisect the culprit is: 1082478: added support for address assertion The failure looks like this:

[jira] Created: (QPID-3151) Remove dotnet and ruby from the --all release artifacts

Remove dotnet and ruby from the --all release artifacts --- Key: QPID-3151 URL: https://issues.apache.org/jira/browse/QPID-3151 Project: Qpid Issue Type: Improvement Components:

[jira] Updated: (QPID-3151) Remove dotnet and ruby from the --all release artifacts

[ https://issues.apache.org/jira/browse/QPID-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-3151: -- Attachment: release.sh.patch Remove dotnet and ruby from the --all release artifacts

[jira] Resolved: (QPID-3011) NPE thrown when using a custom exchange in a replyTo address.

[ https://issues.apache.org/jira/browse/QPID-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-3011. Resolution: Fixed Fixed along with a test case. NPE thrown when using a custom exchange

[jira] Resolved: (QPID-2959) Java client null pointer exception thrown when there is no exchange set for ReplyTo

[ https://issues.apache.org/jira/browse/QPID-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-2959. Resolution: Fixed Fixed along with a test case. Java client null pointer exception thrown

0.10 release update - RC1 and status

Hi, everyone. Using revision 1082154 from Wednesday, I have generated our RC1 release artifacts: http://people.apache.org/~nsantos/qpid-0.10-rc1/ As Gordon suggested we do, with this release I've removed the orphaned dotnet and ruby tarballs from the artifacts. I've also verified that the

[jira] Resolved: (QPID-2930) JMS msg.getPropertyNames() method should not return x-amqp-0-10.routing-key

[ https://issues.apache.org/jira/browse/QPID-2930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajith Attapattu resolved QPID-2930. Resolution: Fixed Fix Version/s: (was: 0.9) 0.10 Fixed along

qmf-gen -2 bug?

Hi I have: cat schema-1.xml schema package=org.foobar class name=apple method name=rott desc=rott arg name=speed dir=I type=uint32/ arg name=review dir=O type=sstr/ /method /class /schema Then I run qmf-gen -2 schema-1.xml Traceback (most recent call last): File

[jira] Updated: (QPID-2560) WCF to WCF PubSub sample is mis-named or needs to be re-designed

[ https://issues.apache.org/jira/browse/QPID-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cliff Jansen updated QPID-2560: --- Fix Version/s: Future I'll see if I can get this done in 0.11 along with some doc and other sample

[jira] Created: (QPID-3152) non-clustered sasl_fed_ex_* tests load cluster.so

non-clustered sasl_fed_ex_* tests load cluster.so - Key: QPID-3152 URL: https://issues.apache.org/jira/browse/QPID-3152 Project: Qpid Issue Type: Bug Components: C++ Broker

[jira] Resolved: (QPID-3152) non-clustered sasl_fed_ex_* tests load cluster.so

[ https://issues.apache.org/jira/browse/QPID-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] michael j. goulish resolved QPID-3152. -- Resolution: Fixed Fix Version/s: 0.10 Assignee: michael j. goulish

[jira] Resolved: (QPID-3150) sasl_fed test fails to specify client's sasl mechanism

[ https://issues.apache.org/jira/browse/QPID-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] michael j. goulish resolved QPID-3150. -- Resolution: Fixed Fix Version/s: 0.10 fixed by 1082685. sasl_fed test fails to

[jira] Created: (QPID-3153) sasl_fed_ex_*_cluster tests should test for aisexec running

sasl_fed_ex_*_cluster tests should test for aisexec running --- Key: QPID-3153 URL: https://issues.apache.org/jira/browse/QPID-3153 Project: Qpid Issue Type: Bug Components:

[jira] Resolved: (QPID-3153) sasl_fed_ex_*_cluster tests should test for aisexec running

[ https://issues.apache.org/jira/browse/QPID-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] michael j. goulish resolved QPID-3153. -- Resolution: Fixed Fix Version/s: 0.11 fixed by rev 1082812.