[jira] [Commented] (QPID-3364) Segmentation fault when unloading shared libraries linked with libqpidmessaging
[
https://issues.apache.org/jira/browse/QPID-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248143#comment-13248143
]
Paul Colby commented on QPID-3364:
--
A not-so-quick heuristically driven binary search has narrowed the fix down to
revision 1297185.
That revision only changed two files - FieldTable.h and FieldTable.cpp. I
suspect that the actual fix has to do with the use of the private
FieldTable::values member variable (the now-removed "// ### Hack Alert" comment
adds to that suspicion).
Anyway, it's _probably_ safe to say that this issue has been fixed by
r1297185... at least as far as the one test case above is concerned.
> Segmentation fault when unloading shared libraries linked with
> libqpidmessaging
> ---
>
> Key: QPID-3364
> URL: https://issues.apache.org/jira/browse/QPID-3364
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
>Affects Versions: 0.8, 0.10, 0.11, 0.14
> Environment: Linux version 2.6.32-5-686 (Debian 2.6.32-34squeeze1)
> (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed May 18
> 07:08:50 UTC 2011
> Linux version 2.6.32-5-amd64 (Debian 2.6.32-34squeeze1) (da...@debian.org)
> (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed May 18 23:13:22 UTC 2011
>Reporter: Paul Colby
>Priority: Minor
> Attachments: Makefile, loadee.cpp, loader.cpp
>
>
> Disclaimer: I'm not a dlopen/dlclose expert... I'm perfectly happy to be told
> that I don't know what I'm doing! ;)
> h3. Basic Description
> If I create a shared object (that may or may not implement anything) that
> links with libqpidmessaging (ie g++ ... -lqpidmessaging), and then create an
> application that dlopen's that library, then dlclose's that library, then
> that application will cause a seg-fault, which appears to be in the
> libqpidmessaging library itself.
> To demonstrate, I have a loadee.cpp file that contains just the following
> unimportant code:
> {code:title=loadee.cpp|borderStyle=solid}
> void foo() { }
> {code}
> Then I build a loadee.so shared object like:
> {noformat}
> g++ -g -shared -lqpidmessaging -o loadee.so loadee.cpp
> {noformat}
> Next I have:
> {code:title=loader.cpp|borderStyle=solid}
> #include
> #include
> #include
> int main(int c, char *argv[]) {
> void *handle = dlopen("./loadee.so", RTLD_LAZY); // segfaults in dlclose
> below.
> //void *handle = dlopen("./loadee.so", RTLD_NOW); // no segfault.
> if (!handle) {
> fprintf(stderr, "%s\n", dlerror());
> exit(EXIT_FAILURE);
> }
> dlclose(handle);
> return EXIT_SUCCESS;
> }
> {code}
> Finally I build the loader program like:
> {noformat}
> g++ -g -rdynamic -o loader loader.cpp -ldl
> {noformat}
> Now, if I run the resulting loader program, then the program seg-faults in
> libqpidmessaging. However, there is no such seg-fault (for me at least), if
> I *either* remove the -lqpidmessaging flag from the first g++ command, *or*
> change the flopen flags from RTLD_NOW to RTLD_LAZY (as indicated in the code
> comments above).
> h3. Tested Versions
> I've tried this against the 0.8 and 0.10 tags, as well as trunk at r1148263,
> with both Autotools and CMake.
> h3. GDB
> Unfortunately, gdb is not giving me much... very strange.
> {noformat}
> paul@debian:~/src/simple$ gdb ./loader
> GNU gdb (GDB) 7.0.1-debian
> Copyright (C) 2009 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i486-linux-gnu".
> For bug reporting instructions, please see:
>
[jira] [Commented] (QPID-3759) Heartbeat timeout in Windows does not lead to timely reconnect
[ https://issues.apache.org/jira/browse/QPID-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13247776#comment-13247776 ] Steve Huston commented on QPID-3759: With the closesocket instead of CancelIoEx, the nightly quick qpid-perftest crashes trying to close the socket after its impl has been freed. Test case: - Start broker - qpid-perftest --summary --count 100 > Heartbeat timeout in Windows does not lead to timely reconnect > -- > > Key: QPID-3759 > URL: https://issues.apache.org/jira/browse/QPID-3759 > Project: Qpid > Issue Type: Bug > Components: C++ Client >Affects Versions: 0.14 > Environment: Windows C++ messaging >Reporter: Chuck Rolke >Assignee: Cliff Jansen > Fix For: 0.17 > > Attachments: main.cpp > > > Reported by Wolf Wolfswinkel on Qpid users > http://qpid.2158936.n2.nabble.com/Heartbeats-in-C-broker-on-Windows-td7118702.html > 22-Dec-2011 > The simplest test case is in attached main.cpp. Establish a good network > connection to the broker and then start the program. It creates a connection, > sends two messages, and then pauses for 15 seconds. During the pause > disconnect the network connection to the broker for at least two heartbeat > timeouts (12 seconds). > After the heartbeat timeout the timer task fires and a debug trace shows: > Traffic timeout, TCPConnector::abort, TCPConnector::eof, TCPConnector::close > But the connection is not actually closed until something happens on the > network to wake up the thread waiting in Poller::run(). > The timer event appears unable to interrupt the IO thread waiting for the > completion port. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Consider QPID-3938 for 0.16
+1 Ship it - Original Message - > From: "Ted Ross" > To: dev@qpid.apache.org, "Justin Ross" > Sent: Thursday, April 5, 2012 2:34:16 PM > Subject: Consider QPID-3938 for 0.16 > > https://issues.apache.org/jira/browse/QPID-3938 > > qmf-tool fails to create connection against updated Python wrapper > > > - > To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org > For additional commands, e-mail: dev-h...@qpid.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Consider QPID-3937 for 0.16
+1 Ship it - Original Message - > From: "Ted Ross" > To: dev@qpid.apache.org, "Justin Ross" > Sent: Thursday, April 5, 2012 2:28:47 PM > Subject: Consider QPID-3937 for 0.16 > > https://issues.apache.org/jira/browse/QPID-3937 > > Wrapped Python uses syntax that is incompatible with older Python > interpreters > > -Ted > > > - > To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org > For additional commands, e-mail: dev-h...@qpid.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Consider QPID-3901 for 0.16
https://issues.apache.org/jira/browse/QPID-3901 0.16 Release issues for Windows This patch didn't make it onto the branch. - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-3369) Loss of cluster elder can result in loss of whole cluster
[ https://issues.apache.org/jira/browse/QPID-3369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13247514#comment-13247514 ] Justin Ross commented on QPID-3369: --- Alan and Jason, what's the status here? I think Jason is saying that the defect is still there. > Loss of cluster elder can result in loss of whole cluster > - > > Key: QPID-3369 > URL: https://issues.apache.org/jira/browse/QPID-3369 > Project: Qpid > Issue Type: Bug > Components: C++ Clustering >Affects Versions: 0.7 >Reporter: Jason Dillaman >Assignee: Alan Conway > Fix For: Future > > Attachments: QPID-3369.patch > > > If the cluster elder is lost, it is possible that the remaining nodes of the > cluster will fail with the following errors: > Error delivering frames: Cluster timer wakeup non-existent task > ManagementAgent::periodicProcessing (qpid/cluster/ClusterTimer.cpp:93) > -- or -- > Error delivering frames: Cluster timer drop non-existent task > ManagementAgent::periodicProcessing (qpid/cluster/ClusterTimer.cpp:109) > When a member is promoted to be the elder, the ClusterTimer::becomeElder() > method will add all the current cluster tasks to the Timer. However, there is > a potential race condition where CPG can deliver the timer wakeup from the > original elder. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Consider QPID-3938 for 0.16
https://issues.apache.org/jira/browse/QPID-3938 qmf-tool fails to create connection against updated Python wrapper - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-3938) qmf-tool fails to create connection against updated Python wrapper
qmf-tool fails to create connection against updated Python wrapper -- Key: QPID-3938 URL: https://issues.apache.org/jira/browse/QPID-3938 Project: Qpid Issue Type: Bug Components: Tools Affects Versions: 0.16 Reporter: Ted Ross Assignee: Ted Ross Priority: Trivial Fix For: 0.16 The changes made to the wrapped Python client (to make it drop-in compatible with the pure Python client) caused an API change that broke qmf-tool. A trivial change is needed to fix it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Consider QPID-3937 for 0.16
https://issues.apache.org/jira/browse/QPID-3937 Wrapped Python uses syntax that is incompatible with older Python interpreters -Ted - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-3937) Wrapped Python uses syntax that is incompatible with older Python interpreters
Wrapped Python uses syntax that is incompatible with older Python interpreters -- Key: QPID-3937 URL: https://issues.apache.org/jira/browse/QPID-3937 Project: Qpid Issue Type: Bug Components: Python Client Affects Versions: 0.16 Reporter: Ted Ross Assignee: Ted Ross Priority: Minor Fix For: 0.16 The following construct is used in the Python qpid wrapper: args = [url] if url else [] This is incompatible with the version of Python distributed with RHEL5 and should be converted to a more backward compatible structure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3923) Update BDB+Derby message stores to use new configuration storage model, representing ConfiguredObjects in a more generic fashion through storage attributes as JSON
[ https://issues.apache.org/jira/browse/QPID-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-3923: - Attachment: (was: 0002-QPID-3923-WIP-Add-functionality-to-store-configured-.patch) > Update BDB+Derby message stores to use new configuration storage model, > representing ConfiguredObjects in a more generic fashion through storage > attributes as JSON > --- > > Key: QPID-3923 > URL: https://issues.apache.org/jira/browse/QPID-3923 > Project: Qpid > Issue Type: Improvement > Components: Java Broker, Java Broker BDB Store >Affects Versions: 0.17 >Reporter: Alex Rudyy > Fix For: 0.17 > > Attachments: > 0001-QPID-3923-Store-queue-exchange-and-binding-as-config.patch > > > Update BDB+Derby message stores to use new configuration storage model, > representing ConfiguredObjects in a more generic fashion through storage > attributes as JSON rather than specific table columns as at present. This > will be done while maintaining the existing store interface for now and using > a new layer shared between BDB+Derby to convert existing objects into the > JSON format stored by the new store schema, allowing later change of the > store interface whilst using the same on-disk format. The message content and > metadata references to queues should be changed to use ids rather than names > when being stored (allowing queues to be renamed in future). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3923) Update BDB+Derby message stores to use new configuration storage model, representing ConfiguredObjects in a more generic fashion through storage attributes as JSON
[ https://issues.apache.org/jira/browse/QPID-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-3923: - Attachment: 0001-QPID-3923-Store-queue-exchange-and-binding-as-config.patch > Update BDB+Derby message stores to use new configuration storage model, > representing ConfiguredObjects in a more generic fashion through storage > attributes as JSON > --- > > Key: QPID-3923 > URL: https://issues.apache.org/jira/browse/QPID-3923 > Project: Qpid > Issue Type: Improvement > Components: Java Broker, Java Broker BDB Store >Affects Versions: 0.17 >Reporter: Alex Rudyy > Fix For: 0.17 > > Attachments: > 0001-QPID-3923-Store-queue-exchange-and-binding-as-config.patch > > > Update BDB+Derby message stores to use new configuration storage model, > representing ConfiguredObjects in a more generic fashion through storage > attributes as JSON rather than specific table columns as at present. This > will be done while maintaining the existing store interface for now and using > a new layer shared between BDB+Derby to convert existing objects into the > JSON format stored by the new store schema, allowing later change of the > store interface whilst using the same on-disk format. The message content and > metadata references to queues should be changed to use ids rather than names > when being stored (allowing queues to be renamed in future). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3923) Update BDB+Derby message stores to use new configuration storage model, representing ConfiguredObjects in a more generic fashion through storage attributes as JSON
[ https://issues.apache.org/jira/browse/QPID-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-3923: - Attachment: (was: 0001-QPID-3923-Add-jackson-library-and-configured-object-.patch) > Update BDB+Derby message stores to use new configuration storage model, > representing ConfiguredObjects in a more generic fashion through storage > attributes as JSON > --- > > Key: QPID-3923 > URL: https://issues.apache.org/jira/browse/QPID-3923 > Project: Qpid > Issue Type: Improvement > Components: Java Broker, Java Broker BDB Store >Affects Versions: 0.17 >Reporter: Alex Rudyy > Fix For: 0.17 > > Attachments: > 0001-QPID-3923-Store-queue-exchange-and-binding-as-config.patch > > > Update BDB+Derby message stores to use new configuration storage model, > representing ConfiguredObjects in a more generic fashion through storage > attributes as JSON rather than specific table columns as at present. This > will be done while maintaining the existing store interface for now and using > a new layer shared between BDB+Derby to convert existing objects into the > JSON format stored by the new store schema, allowing later change of the > store interface whilst using the same on-disk format. The message content and > metadata references to queues should be changed to use ids rather than names > when being stored (allowing queues to be renamed in future). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-3936) Add new framework for running distributed tests, eg for performance testing
[ https://issues.apache.org/jira/browse/QPID-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-3936: Assignee: Philip Harvey (was: Robbie Gemmell) Initial patch applied. Marking as 'In Progress' since there is work yet to be done, assigning back to Phil. > Add new framework for running distributed tests, eg for performance testing > --- > > Key: QPID-3936 > URL: https://issues.apache.org/jira/browse/QPID-3936 > Project: Qpid > Issue Type: New Feature > Components: Java Tests >Reporter: Philip Harvey >Assignee: Philip Harvey > Fix For: 0.17 > > Attachments: > 0001-QPID-3936-initial-checkin-of-new-testing-framework-i.patch > > > We would like a framework that makes it easy to run configuration-driven > distributed Qpid tests. > The framework should read a configuration file that specifies a number of > queues, producers, and consumers. It should then run the test, collecting > statistics along the way. > This is being initially implemented in Java, but is ultimately intended to be > language-neutral. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3936) Add new framework for running distributed tests, eg for performance testing
[ https://issues.apache.org/jira/browse/QPID-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-3936: - Status: Open (was: Ready To Review) > Add new framework for running distributed tests, eg for performance testing > --- > > Key: QPID-3936 > URL: https://issues.apache.org/jira/browse/QPID-3936 > Project: Qpid > Issue Type: New Feature > Components: Java Tests >Reporter: Philip Harvey >Assignee: Robbie Gemmell > Fix For: 0.17 > > Attachments: > 0001-QPID-3936-initial-checkin-of-new-testing-framework-i.patch > > > We would like a framework that makes it easy to run configuration-driven > distributed Qpid tests. > The framework should read a configuration file that specifies a number of > queues, producers, and consumers. It should then run the test, collecting > statistics along the way. > This is being initially implemented in Java, but is ultimately intended to be > language-neutral. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-3936) Add new framework for running distributed tests, eg for performance testing
[ https://issues.apache.org/jira/browse/QPID-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-3936: Assignee: Robbie Gemmell (was: Alex Rudyy) I am happy with the patch. Robbie, Could you please commit it? > Add new framework for running distributed tests, eg for performance testing > --- > > Key: QPID-3936 > URL: https://issues.apache.org/jira/browse/QPID-3936 > Project: Qpid > Issue Type: New Feature > Components: Java Tests >Reporter: Philip Harvey >Assignee: Robbie Gemmell > Fix For: 0.17 > > Attachments: > 0001-QPID-3936-initial-checkin-of-new-testing-framework-i.patch > > > We would like a framework that makes it easy to run configuration-driven > distributed Qpid tests. > The framework should read a configuration file that specifies a number of > queues, producers, and consumers. It should then run the test, collecting > statistics along the way. > This is being initially implemented in Java, but is ultimately intended to be > language-neutral. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3936) Add new framework for running distributed tests, eg for performance testing
[ https://issues.apache.org/jira/browse/QPID-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-3936: - Status: Ready To Review (was: In Progress) > Add new framework for running distributed tests, eg for performance testing > --- > > Key: QPID-3936 > URL: https://issues.apache.org/jira/browse/QPID-3936 > Project: Qpid > Issue Type: New Feature > Components: Java Tests >Reporter: Philip Harvey >Assignee: Alex Rudyy > Fix For: 0.17 > > Attachments: > 0001-QPID-3936-initial-checkin-of-new-testing-framework-i.patch > > > We would like a framework that makes it easy to run configuration-driven > distributed Qpid tests. > The framework should read a configuration file that specifies a number of > queues, producers, and consumers. It should then run the test, collecting > statistics along the way. > This is being initially implemented in Java, but is ultimately intended to be > language-neutral. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-3936) Add new framework for running distributed tests, eg for performance testing
[ https://issues.apache.org/jira/browse/QPID-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean reassigned QPID-3936: Assignee: Alex Rudyy (was: Andrew MacBean) Alex, I have attached our patch, could you please check it and then assign to Robbie if you're happy? > Add new framework for running distributed tests, eg for performance testing > --- > > Key: QPID-3936 > URL: https://issues.apache.org/jira/browse/QPID-3936 > Project: Qpid > Issue Type: New Feature > Components: Java Tests >Reporter: Philip Harvey >Assignee: Alex Rudyy > Fix For: 0.17 > > Attachments: > 0001-QPID-3936-initial-checkin-of-new-testing-framework-i.patch > > > We would like a framework that makes it easy to run configuration-driven > distributed Qpid tests. > The framework should read a configuration file that specifies a number of > queues, producers, and consumers. It should then run the test, collecting > statistics along the way. > This is being initially implemented in Java, but is ultimately intended to be > language-neutral. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-3936) Add new framework for running distributed tests, eg for performance testing
[ https://issues.apache.org/jira/browse/QPID-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-3936: - Attachment: 0001-QPID-3936-initial-checkin-of-new-testing-framework-i.patch > Add new framework for running distributed tests, eg for performance testing > --- > > Key: QPID-3936 > URL: https://issues.apache.org/jira/browse/QPID-3936 > Project: Qpid > Issue Type: New Feature > Components: Java Tests >Reporter: Philip Harvey >Assignee: Andrew MacBean > Fix For: 0.17 > > Attachments: > 0001-QPID-3936-initial-checkin-of-new-testing-framework-i.patch > > > We would like a framework that makes it easy to run configuration-driven > distributed Qpid tests. > The framework should read a configuration file that specifies a number of > queues, producers, and consumers. It should then run the test, collecting > statistics along the way. > This is being initially implemented in Java, but is ultimately intended to be > language-neutral. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Integrating destination patch into the code base
Once we get agreement on the destination work, the next step is to integrate it into the code base. I see the following options. Please feel free to provide your feedback on the options provide or even suggest new options. I'm quite happy to work with any option the majority feels the best. 1. Integrate into both 0-8 and 0-10 code paths. 2. Integrate into 0-10 only. - This would be tricky as there is a fair bit of common code that uses destination stuff. 3. Have a new implementation of Session, Producer, Consumer etc for 0-10 that exclusively uses the new destination impl. We could then use AMQConnectionDelegate_0_10 as a point to plug in this new structure when 0-10 is used. (Note: I'm not advocating a rewrite, rather to reuse as much code as possible, and by moving necessary pieces from common code into the specific implementation we could do #2 without being encumbered by common code). The flip side is code duplication. Regards, Rajith
[jira] [Assigned] (QPID-3936) Add new framework for running distributed tests, eg for performance testing
[ https://issues.apache.org/jira/browse/QPID-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Harvey reassigned QPID-3936: --- Assignee: Andrew MacBean Andrew - please submit the patch > Add new framework for running distributed tests, eg for performance testing > --- > > Key: QPID-3936 > URL: https://issues.apache.org/jira/browse/QPID-3936 > Project: Qpid > Issue Type: New Feature > Components: Java Tests >Reporter: Philip Harvey >Assignee: Andrew MacBean > Fix For: 0.17 > > > We would like a framework that makes it easy to run configuration-driven > distributed Qpid tests. > The framework should read a configuration file that specifies a number of > queues, producers, and consumers. It should then run the test, collecting > statistics along the way. > This is being initially implemented in Java, but is ultimately intended to be > language-neutral. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-3936) Add new framework for running distributed tests, eg for performance testing
Add new framework for running distributed tests, eg for performance testing --- Key: QPID-3936 URL: https://issues.apache.org/jira/browse/QPID-3936 Project: Qpid Issue Type: New Feature Components: Java Tests Reporter: Philip Harvey Fix For: 0.17 We would like a framework that makes it easy to run configuration-driven distributed Qpid tests. The framework should read a configuration file that specifies a number of queues, producers, and consumers. It should then run the test, collecting statistics along the way. This is being initially implemented in Java, but is ultimately intended to be language-neutral. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-3401) Refactor address resolution code
[ https://issues.apache.org/jira/browse/QPID-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13247270#comment-13247270 ] jirapos...@reviews.apache.org commented on QPID-3401: - --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/4658/ --- Review request for qpid, Gordon Sim, Robbie Gemmell, Weston Price, Rafael Schloming, and Rob Godfrey. Summary --- The following patch is based on the various discussions we've had on the dev list about restructing our destination implementation. As the first phase this patch only includes the new class heirachy. For the second phase we will tackle the integration into the code base. A summary of the desgin is as follows, 1. Once initialized with the destination string, the destination objects are immutable. 2. There are 2 concrete implementations in the form of QpidTopic and QpidQueue. 3. Destinations will be desginated as "Queues" and "Topics" by the users in the jndi file. This prevents us from having to automagically decide the type. 4. Both BURL and Address strings are parsed and adapted into a common data structure. Internally the code will work with this data structure. 5. The Destination impl does not depend on any other classes, thus allowing it be used with the current code or the new client. (There are 2 oe 3 white space errors that I can't seem to get rid of. It seems they are comming from the diff process). This addresses bug QPID-3401. https://issues.apache.org/jira/browse/QPID-3401 Diffs - http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/client/src/main/java/org/apache/qpid/jms/DestinationStringParser.java PRE-CREATION http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/client/src/main/java/org/apache/qpid/jms/QpidDestination.java PRE-CREATION http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/client/src/main/java/org/apache/qpid/jms/QpidQueue.java PRE-CREATION http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/client/src/main/java/org/apache/qpid/jms/QpidTemporaryQueue.java PRE-CREATION http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/client/src/main/java/org/apache/qpid/jms/QpidTemporaryTopic.java PRE-CREATION http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/client/src/main/java/org/apache/qpid/jms/QpidTopic.java PRE-CREATION http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/client/src/main/java/org/apache/qpid/jms/TemporaryDestinationProvider.java PRE-CREATION http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/common/src/main/java/org/apache/qpid/messaging/Address.java 1309769 http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/common/src/main/java/org/apache/qpid/messaging/address/AddressException.java PRE-CREATION http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/common/src/main/java/org/apache/qpid/messaging/address/Link.java PRE-CREATION http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/common/src/main/java/org/apache/qpid/messaging/address/Node.java PRE-CREATION http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/common/src/main/java/org/apache/qpid/messaging/util/AddressHelper.java PRE-CREATION Diff: https://reviews.apache.org/r/4658/diff Testing --- Thanks, rajith > Refactor address resolution code > > > Key: QPID-3401 > URL: https://issues.apache.org/jira/browse/QPID-3401 > Project: Qpid > Issue Type: Improvement > Components: Java Client >Reporter: Rajith Attapattu >Assignee: Rajith Attapattu > Labels: addressing > Fix For: Future > > Attachments: QPID-3401-systests.patch, QPID-3401.patch, > class_diagram.png, model2.gif > > > After some thought it seems that the following JIRA's would benefit from some > reworking of the address resolution code as the original design had a few > flaws based on incorrect understanding of the address syntax. > QPID-3265 > QPID-3317 > QPID-3271 > The redesign would be minimal and not very disruptive. The goal is to fix > certain design flaws in the current code, rather than a complete redesign. I > am planning to reuse as much code as possible to ensure we don't throw away > tested code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.or
Review Request: Destination refactoring
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/4658/ --- Review request for qpid, Gordon Sim, Robbie Gemmell, Weston Price, Rafael Schloming, and Rob Godfrey. Summary --- The following patch is based on the various discussions we've had on the dev list about restructing our destination implementation. As the first phase this patch only includes the new class heirachy. For the second phase we will tackle the integration into the code base. A summary of the desgin is as follows, 1. Once initialized with the destination string, the destination objects are immutable. 2. There are 2 concrete implementations in the form of QpidTopic and QpidQueue. 3. Destinations will be desginated as "Queues" and "Topics" by the users in the jndi file. This prevents us from having to automagically decide the type. 4. Both BURL and Address strings are parsed and adapted into a common data structure. Internally the code will work with this data structure. 5. The Destination impl does not depend on any other classes, thus allowing it be used with the current code or the new client. (There are 2 oe 3 white space errors that I can't seem to get rid of. It seems they are comming from the diff process). This addresses bug QPID-3401. https://issues.apache.org/jira/browse/QPID-3401 Diffs - http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/client/src/main/java/org/apache/qpid/jms/DestinationStringParser.java PRE-CREATION http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/client/src/main/java/org/apache/qpid/jms/QpidDestination.java PRE-CREATION http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/client/src/main/java/org/apache/qpid/jms/QpidQueue.java PRE-CREATION http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/client/src/main/java/org/apache/qpid/jms/QpidTemporaryQueue.java PRE-CREATION http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/client/src/main/java/org/apache/qpid/jms/QpidTemporaryTopic.java PRE-CREATION http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/client/src/main/java/org/apache/qpid/jms/QpidTopic.java PRE-CREATION http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/client/src/main/java/org/apache/qpid/jms/TemporaryDestinationProvider.java PRE-CREATION http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/common/src/main/java/org/apache/qpid/messaging/Address.java 1309769 http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/common/src/main/java/org/apache/qpid/messaging/address/AddressException.java PRE-CREATION http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/common/src/main/java/org/apache/qpid/messaging/address/Link.java PRE-CREATION http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/common/src/main/java/org/apache/qpid/messaging/address/Node.java PRE-CREATION http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/common/src/main/java/org/apache/qpid/messaging/util/AddressHelper.java PRE-CREATION Diff: https://reviews.apache.org/r/4658/diff Testing --- Thanks, rajith
[jira] [Commented] (QPID-3767) Federation link index becomes invalid on failover against a cluster.
[ https://issues.apache.org/jira/browse/QPID-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13247263#comment-13247263 ] jirapos...@reviews.apache.org commented on QPID-3767: - --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/4659/ --- Review request for qpid, Alan Conway, Gordon Sim, Ted Ross, and Rob Godfrey. Summary --- This set of changes modifies the Broker's Link and Bridge objects by changing the way they are indexed. This change is visible to users as it modifies the existing management model for this objects. The current implementation uses the remote broker's Host and Port value to identify the Link, and also as part of the index for identifiying the Bridge. The problem with this approach is that it does not support failover well, where the remote Host and Port values are likely to change. This patch modifies the Link and Bridge object to now be indexed by a unique name (expressed as a string). It removes the host & port indexing from the QMF model. With this patch, host and port are allowed to change over time without invalidating the Link or Bridge. I've also added a reference to the connection that the Link is using - this useful information was missing from the existing model. This patch also introduces the ability to create Links and Bridges via the QMF Broker object's "create" and "delete" method. This feature is yet to be used by qpid-route, however, and the old methods to create Links and Bridges using host and ports are preserved for backward compatibility. We can remove this if desired in a later release. Things this patch does not do, and I'll like to track as separate feature requests if possible: o) Modify the qpid-route tool to allow the ability to name links and bridges if desired - and allowe more control over the management of Links & Bridges - details TBD. o) Java broker support of Link and Bridge naming, and the ability to manage Links/Bridges via the broker's create/delete methods. Alan - my changes to the HA code are at best a guess, can you take a look? Rob - ditto my changes to the Java broker. thanks This addresses bug qpid-3767. https://issues.apache.org/jira/browse/qpid-3767 Diffs - /trunk/qpid/cpp/src/qpid/broker/LinkRegistry.cpp 1306454 /trunk/qpid/cpp/src/qpid/broker/LinkRegistry.h 1306454 /trunk/qpid/cpp/src/qpid/broker/Link.cpp 1306454 /trunk/qpid/cpp/src/qpid/broker/Link.h 1306454 /trunk/qpid/cpp/src/qpid/broker/Broker.cpp 1306454 /trunk/qpid/cpp/src/qpid/broker/Bridge.h 1306454 /trunk/qpid/cpp/src/qpid/broker/Bridge.cpp 1306454 /trunk/qpid/cpp/src/qpid/broker/NameGenerator.h 1306454 /trunk/qpid/cpp/src/qpid/broker/RecoveryManagerImpl.cpp 1306454 /trunk/qpid/cpp/src/qpid/cluster/Connection.cpp 1306454 /trunk/qpid/cpp/src/qpid/ha/Backup.cpp 1306454 /trunk/qpid/cpp/src/qpid/ha/BrokerReplicator.cpp 1306454 /trunk/qpid/cpp/src/qpid/ha/HaBroker.cpp 1306454 /trunk/qpid/cpp/src/qpid/ha/QueueReplicator.h 1306454 /trunk/qpid/cpp/src/qpid/ha/QueueReplicator.cpp 1306454 /trunk/qpid/cpp/src/tests/federation.py 1306454 /trunk/qpid/java/broker/src/main/java/org/apache/qpid/qmf/QMFService.java 1306454 /trunk/qpid/java/broker/src/main/java/org/apache/qpid/server/configuration/LinkConfigType.java 1306454 /trunk/qpid/specs/management-schema.xml 1306454 /trunk/qpid/tools/src/py/qpid-tool 1306454 Diff: https://reviews.apache.org/r/4659/diff Testing --- make check, ant build/test windows build via Hudson Thanks, Kenneth > Federation link index becomes invalid on failover against a cluster. > > > Key: QPID-3767 > URL: https://issues.apache.org/jira/browse/QPID-3767 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: 0.14 >Reporter: Ken Giusti >Assignee: Ken Giusti > Fix For: 0.15 > > > The Link management object that represents a connection between two federated > brokers is indexed (identified) by the remote broker's host and port. If the > remote broker is part of a cluster, and a failover event occurs, the > host:port used by the Link object's index may no longer exist. This prevents > the route from being deleted. > For example, create a cluster of two brokers using addresses 127.0.0.1: > and 127.0.0.1:. Start a third broker, say 127.0.0.1:. Create a > queue route from 127.0.0.1: to an exchange on 127.0.0.1:. Kill the > broker 127.0.0.1:. This results in a Link object that is connected to > 127.0.0.1:, but reports 127.0.0.1: as it's host.
Review Request: QPID-3767: identify Link and Bridge objects by an assigned name, rather than by the remote Host and Port.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/4659/ --- Review request for qpid, Alan Conway, Gordon Sim, Ted Ross, and Rob Godfrey. Summary --- This set of changes modifies the Broker's Link and Bridge objects by changing the way they are indexed. This change is visible to users as it modifies the existing management model for this objects. The current implementation uses the remote broker's Host and Port value to identify the Link, and also as part of the index for identifiying the Bridge. The problem with this approach is that it does not support failover well, where the remote Host and Port values are likely to change. This patch modifies the Link and Bridge object to now be indexed by a unique name (expressed as a string). It removes the host & port indexing from the QMF model. With this patch, host and port are allowed to change over time without invalidating the Link or Bridge. I've also added a reference to the connection that the Link is using - this useful information was missing from the existing model. This patch also introduces the ability to create Links and Bridges via the QMF Broker object's "create" and "delete" method. This feature is yet to be used by qpid-route, however, and the old methods to create Links and Bridges using host and ports are preserved for backward compatibility. We can remove this if desired in a later release. Things this patch does not do, and I'll like to track as separate feature requests if possible: o) Modify the qpid-route tool to allow the ability to name links and bridges if desired - and allowe more control over the management of Links & Bridges - details TBD. o) Java broker support of Link and Bridge naming, and the ability to manage Links/Bridges via the broker's create/delete methods. Alan - my changes to the HA code are at best a guess, can you take a look? Rob - ditto my changes to the Java broker. thanks This addresses bug qpid-3767. https://issues.apache.org/jira/browse/qpid-3767 Diffs - /trunk/qpid/cpp/src/qpid/broker/LinkRegistry.cpp 1306454 /trunk/qpid/cpp/src/qpid/broker/LinkRegistry.h 1306454 /trunk/qpid/cpp/src/qpid/broker/Link.cpp 1306454 /trunk/qpid/cpp/src/qpid/broker/Link.h 1306454 /trunk/qpid/cpp/src/qpid/broker/Broker.cpp 1306454 /trunk/qpid/cpp/src/qpid/broker/Bridge.h 1306454 /trunk/qpid/cpp/src/qpid/broker/Bridge.cpp 1306454 /trunk/qpid/cpp/src/qpid/broker/NameGenerator.h 1306454 /trunk/qpid/cpp/src/qpid/broker/RecoveryManagerImpl.cpp 1306454 /trunk/qpid/cpp/src/qpid/cluster/Connection.cpp 1306454 /trunk/qpid/cpp/src/qpid/ha/Backup.cpp 1306454 /trunk/qpid/cpp/src/qpid/ha/BrokerReplicator.cpp 1306454 /trunk/qpid/cpp/src/qpid/ha/HaBroker.cpp 1306454 /trunk/qpid/cpp/src/qpid/ha/QueueReplicator.h 1306454 /trunk/qpid/cpp/src/qpid/ha/QueueReplicator.cpp 1306454 /trunk/qpid/cpp/src/tests/federation.py 1306454 /trunk/qpid/java/broker/src/main/java/org/apache/qpid/qmf/QMFService.java 1306454 /trunk/qpid/java/broker/src/main/java/org/apache/qpid/server/configuration/LinkConfigType.java 1306454 /trunk/qpid/specs/management-schema.xml 1306454 /trunk/qpid/tools/src/py/qpid-tool 1306454 Diff: https://reviews.apache.org/r/4659/diff Testing --- make check, ant build/test windows build via Hudson Thanks, Kenneth
[jira] [Created] (QPID-3935) ManagedQueueMBeanTest.testMoveMessagesBetweenQueuesWithActiveConsumerOnSourceQueue fails sporadically on slow CI
ManagedQueueMBeanTest.testMoveMessagesBetweenQueuesWithActiveConsumerOnSourceQueue
fails sporadically on slow CI
Key: QPID-3935
URL: https://issues.apache.org/jira/browse/QPID-3935
Project: Qpid
Issue Type: Bug
Components: Java Tests
Affects Versions: 0.16
Environment: A non-Apache Jenkins instance running on a slow server.
Reporter: Philip Harvey
Priority: Minor
We last saw this test failure a while ago, and believed it had been fixed by
commit http://svn.apache.org/viewvc?view=rev&rev=1295574 in [QPID-3867].
However, this test failed again using profile java-mms-spawn.0-9-1 against SVN
revision 1309050. It then passed on several subsequent builds.
{noformat}
junit.framework.AssertionFailedError: Unexpected number of messages after move
expected:<50> but was:<51>
at
org.apache.qpid.management.jmx.ManagedQueueMBeanTest.testMoveMessagesBetweenQueuesWithActiveConsumerOnSourceQueue(ManagedQueueMBeanTest.java:241)
at
org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:138)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-3934) QpidBrokerTestCase.getConnection sometimes fails on a slow CI server
QpidBrokerTestCase.getConnection sometimes fails on a slow CI server
Key: QPID-3934
URL: https://issues.apache.org/jira/browse/QPID-3934
Project: Qpid
Issue Type: Bug
Components: Java Tests
Affects Versions: 0.16
Environment: A Jenkins instance (not the Apache one), running on a
slow server.
Reporter: Philip Harvey
Priority: Minor
In the last few builds, two have failed because
QpidBrokerTestCase.getConnection throws this exception, in each time in a
different test:
{noformat}
javax.jms.JMSException: Error creating connection: connect() aborted
at
org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:153)
at
org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:128)
at
org.apache.qpid.test.utils.QpidBrokerTestCase.getConnection(QpidBrokerTestCase.java:1006)
at
org.apache.qpid.test.utils.QpidBrokerTestCase.getConnection(QpidBrokerTestCase.java:980)
at
org.apache.qpid.client.AsynchMessageListenerTest.setUp(AsynchMessageListenerTest.java:59)
at
org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:138)
Caused by: org.apache.qpid.AMQConnectionFailureException: connect() aborted
[error code 200: reply success]
at org.apache.qpid.client.AMQConnection.(AMQConnection.java:438)
at
org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:149)
Caused by: org.apache.qpid.AMQException: Cannot connect to broker: connect()
aborted [error code 200: reply success]
at
org.apache.qpid.client.AMQConnectionDelegate_0_10.makeBrokerConnection(AMQConnectionDelegate_0_10.java:238)
at
org.apache.qpid.client.AMQConnection.makeBrokerConnection(AMQConnection.java:582)
at org.apache.qpid.client.AMQConnection.(AMQConnection.java:361)
Caused by: org.apache.qpid.transport.ConnectionException: connect() aborted
at org.apache.qpid.transport.Connection.connect(Connection.java:274)
at
org.apache.qpid.client.AMQConnectionDelegate_0_10.makeBrokerConnection(AMQConnectionDelegate_0_10.java:219)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
