[jira] [Created] (QPID-4761) [Java Broker] Upgrade jetty to recent 7.x version (7.6.10.v20130312)
Alex Rudyy created QPID-4761: Summary: [Java Broker] Upgrade jetty to recent 7.x version (7.6.10.v20130312) Key: QPID-4761 URL: https://issues.apache.org/jira/browse/QPID-4761 Project: Qpid Issue Type: Improvement Components: Java Broker Affects Versions: 0.22 Reporter: Alex Rudyy Assignee: Alex Rudyy Fix For: 0.23 The Qpid broker depends on jetty of version 7.6.3.v20120416. There were several bug fixing releases of jetty. We need to upgrade it to the recent 7.x version which is 7.6.10.v20130312. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-4761) [Java Broker] Upgrade jetty to recent 7.x version (7.6.10.v20130312)
[ https://issues.apache.org/jira/browse/QPID-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-4761: - Status: Ready To Review (was: In Progress) [Java Broker] Upgrade jetty to recent 7.x version (7.6.10.v20130312) Key: QPID-4761 URL: https://issues.apache.org/jira/browse/QPID-4761 Project: Qpid Issue Type: Improvement Components: Java Broker Affects Versions: 0.22 Reporter: Alex Rudyy Assignee: Alex Rudyy Fix For: 0.23 The Qpid broker depends on jetty of version 7.6.3.v20120416. There were several bug fixing releases of jetty. We need to upgrade it to the recent 7.x version which is 7.6.10.v20130312. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-4761) [Java Broker] Upgrade jetty to recent 7.x version (7.6.10.v20130312)
[ https://issues.apache.org/jira/browse/QPID-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-4761: Assignee: Robbie Gemmell (was: Alex Rudyy) The jetty was upgraded in the revision http://svn.apache.org/r1470439 . Robbie, could you please review? [Java Broker] Upgrade jetty to recent 7.x version (7.6.10.v20130312) Key: QPID-4761 URL: https://issues.apache.org/jira/browse/QPID-4761 Project: Qpid Issue Type: Improvement Components: Java Broker Affects Versions: 0.22 Reporter: Alex Rudyy Assignee: Robbie Gemmell Fix For: 0.23 The Qpid broker depends on jetty of version 7.6.3.v20120416. There were several bug fixing releases of jetty. We need to upgrade it to the recent 7.x version which is 7.6.10.v20130312. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-4762) [Java Broker] Upgrade dojo to the version 1.8.3
Alex Rudyy created QPID-4762: Summary: [Java Broker] Upgrade dojo to the version 1.8.3 Key: QPID-4762 URL: https://issues.apache.org/jira/browse/QPID-4762 Project: Qpid Issue Type: Improvement Components: Java Broker Affects Versions: 0.22 Reporter: Alex Rudyy Assignee: Alex Rudyy Fix For: 0.23 Upgrade dojo toolkit to the latest stable version 1.8.3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-4763) [Java Broker] Create generic JDBC store
Rob Godfrey created QPID-4763: - Summary: [Java Broker] Create generic JDBC store Key: QPID-4763 URL: https://issues.apache.org/jira/browse/QPID-4763 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Rob Godfrey Assignee: Rob Godfrey Priority: Minor Fix For: 0.23 The Java Broker currently has code to allow for using Derby as an in-process store. It is relatively trivial to modify this code to allow for the use of any JDBC compliant database as an external store provider (though performance is unlikely to be impressive). The advantage of using an external JDBC store is the ability for third party libraries to easily inspect the store, and for storage to be provided by existing infrastructure. Some tweaking of the store is necessary for those parts which create the tables since SQL92 datatypes are not universally implemented. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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] [Resolved] (QPID-4763) [Java Broker] Create generic JDBC store
[ https://issues.apache.org/jira/browse/QPID-4763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved QPID-4763. --- Resolution: Fixed Checked in as http://svn.apache.org/r1470454 [Java Broker] Create generic JDBC store - Key: QPID-4763 URL: https://issues.apache.org/jira/browse/QPID-4763 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Rob Godfrey Assignee: Rob Godfrey Priority: Minor Fix For: 0.23 The Java Broker currently has code to allow for using Derby as an in-process store. It is relatively trivial to modify this code to allow for the use of any JDBC compliant database as an external store provider (though performance is unlikely to be impressive). The advantage of using an external JDBC store is the ability for third party libraries to easily inspect the store, and for storage to be provided by existing infrastructure. Some tweaking of the store is necessary for those parts which create the tables since SQL92 datatypes are not universally implemented. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-4751) Hello example still use the 'test' virtualhost, which no longer exists in the initial Java broker config
[ https://issues.apache.org/jira/browse/QPID-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4751: - Summary: Hello example still use the 'test' virtualhost, which no longer exists in the initial Java broker config (was: Connection URLs in existing examples still use the 'test' virtualhost, which no longer exists in the initial Java broker config) Hello example still use the 'test' virtualhost, which no longer exists in the initial Java broker config Key: QPID-4751 URL: https://issues.apache.org/jira/browse/QPID-4751 Project: Qpid Issue Type: Bug Affects Versions: 0.21 Reporter: Robbie Gemmell Fix For: 0.22 Connection URLs in existing examples still use the 'test' virtualhost, which no longer exists in the initial Java broker config, which removed the thre previous 'localhost' 'development' and 'test' virtualhosts and instead has only a single 'default' virtualhsot. As a result, the examples will fail to run unless the user adds a 'test' virtualhost or changes the connection URL themselves. The example configurations should be updated to remove the virtualhost from the URL entirely, which will make the client connect to the brokers current default virtualhost regardless what it is actually called, meaning the examples will work against newer and older releases shipping config as well as after the user reconfigures the broker. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-4751) Hello example still use the 'test' virtualhost, which no longer exists in the initial Java broker config
[ https://issues.apache.org/jira/browse/QPID-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13637968#comment-13637968 ] Robbie Gemmell commented on QPID-4751: -- Narrowed scope to the Hello example, any others can occur via their own JIRA. Change committed in http://svn.apache.org/r1470474 Hello example still use the 'test' virtualhost, which no longer exists in the initial Java broker config Key: QPID-4751 URL: https://issues.apache.org/jira/browse/QPID-4751 Project: Qpid Issue Type: Bug Affects Versions: 0.21 Reporter: Robbie Gemmell Fix For: 0.22 Connection URLs in existing examples still use the 'test' virtualhost, which no longer exists in the initial Java broker config, which removed the thre previous 'localhost' 'development' and 'test' virtualhosts and instead has only a single 'default' virtualhsot. As a result, the examples will fail to run unless the user adds a 'test' virtualhost or changes the connection URL themselves. The example configurations should be updated to remove the virtualhost from the URL entirely, which will make the client connect to the brokers current default virtualhost regardless what it is actually called, meaning the examples will work against newer and older releases shipping config as well as after the user reconfigures the broker. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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] [Resolved] (QPID-4751) Hello example still use the 'test' virtualhost, which no longer exists in the initial Java broker config
[ https://issues.apache.org/jira/browse/QPID-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4751. -- Resolution: Fixed Fix Version/s: (was: 0.22) 0.23 Assignee: Robbie Gemmell Hello example still use the 'test' virtualhost, which no longer exists in the initial Java broker config Key: QPID-4751 URL: https://issues.apache.org/jira/browse/QPID-4751 Project: Qpid Issue Type: Bug Affects Versions: 0.21 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.23 Connection URLs in existing examples still use the 'test' virtualhost, which no longer exists in the initial Java broker config, which removed the thre previous 'localhost' 'development' and 'test' virtualhosts and instead has only a single 'default' virtualhsot. As a result, the examples will fail to run unless the user adds a 'test' virtualhost or changes the connection URL themselves. The example configurations should be updated to remove the virtualhost from the URL entirely, which will make the client connect to the brokers current default virtualhost regardless what it is actually called, meaning the examples will work against newer and older releases shipping config as well as after the user reconfigures the broker. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-4685) [Java Broker] update documentation to reflect changes to configuration etc
[ https://issues.apache.org/jira/browse/QPID-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13637969#comment-13637969 ] Robbie Gemmell commented on QPID-4685: -- Change to command line options documetned via: http://svn.apache.org/r1470475 [Java Broker] update documentation to reflect changes to configuration etc -- Key: QPID-4685 URL: https://issues.apache.org/jira/browse/QPID-4685 Project: Qpid Issue Type: Bug Components: Documentation, Java Broker Affects Versions: 0.21 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Priority: Blocker Fix For: 0.22 update documentation to reflect changes to configuration etc E.g: - Remove all trace of config.xml - Update command line option documentation to reflect additions/removal in this area. - New ACL option in QPID-4678 - Outline when it is still necessary to use an XML configuration file for a virtualhost and how to do so. Etc -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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] [Comment Edited] (QPID-4685) [Java Broker] update documentation to reflect changes to configuration etc
[ https://issues.apache.org/jira/browse/QPID-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13637969#comment-13637969 ] Robbie Gemmell edited comment on QPID-4685 at 4/22/13 12:39 PM: Change to command line options documented on trunk via: http://svn.apache.org/r1470475 was (Author: gemmellr): Change to command line options documetned via: http://svn.apache.org/r1470475 [Java Broker] update documentation to reflect changes to configuration etc -- Key: QPID-4685 URL: https://issues.apache.org/jira/browse/QPID-4685 Project: Qpid Issue Type: Bug Components: Documentation, Java Broker Affects Versions: 0.21 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Priority: Blocker Fix For: 0.22 update documentation to reflect changes to configuration etc E.g: - Remove all trace of config.xml - Update command line option documentation to reflect additions/removal in this area. - New ACL option in QPID-4678 - Outline when it is still necessary to use an XML configuration file for a virtualhost and how to do so. Etc -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-4762) [Java Broker] Upgrade dojo to the version 1.8.3
[ https://issues.apache.org/jira/browse/QPID-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13637970#comment-13637970 ] Robbie Gemmell commented on QPID-4762: -- Alex made change via: http://svn.apache.org/r1470463 [Java Broker] Upgrade dojo to the version 1.8.3 --- Key: QPID-4762 URL: https://issues.apache.org/jira/browse/QPID-4762 Project: Qpid Issue Type: Improvement Components: Java Broker Affects Versions: 0.22 Reporter: Alex Rudyy Assignee: Alex Rudyy Fix For: 0.23 Upgrade dojo toolkit to the latest stable version 1.8.3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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] [Resolved] (QPID-4762) [Java Broker] Upgrade dojo to the version 1.8.3
[ https://issues.apache.org/jira/browse/QPID-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4762. -- Resolution: Fixed Looks good, resolving. [Java Broker] Upgrade dojo to the version 1.8.3 --- Key: QPID-4762 URL: https://issues.apache.org/jira/browse/QPID-4762 Project: Qpid Issue Type: Improvement Components: Java Broker Affects Versions: 0.22 Reporter: Alex Rudyy Assignee: Alex Rudyy Fix For: 0.23 Upgrade dojo toolkit to the latest stable version 1.8.3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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] [Resolved] (QPID-4761) [Java Broker] Upgrade jetty to recent 7.x version (7.6.10.v20130312)
[ https://issues.apache.org/jira/browse/QPID-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4761. -- Resolution: Fixed Looks good, resolving. [Java Broker] Upgrade jetty to recent 7.x version (7.6.10.v20130312) Key: QPID-4761 URL: https://issues.apache.org/jira/browse/QPID-4761 Project: Qpid Issue Type: Improvement Components: Java Broker Affects Versions: 0.22 Reporter: Alex Rudyy Assignee: Robbie Gemmell Fix For: 0.23 The Qpid broker depends on jetty of version 7.6.3.v20120416. There were several bug fixing releases of jetty. We need to upgrade it to the recent 7.x version which is 7.6.10.v20130312. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-4761) [Java Broker] Upgrade jetty to 7.6.10.v20130312
[ https://issues.apache.org/jira/browse/QPID-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4761: - Summary: [Java Broker] Upgrade jetty to 7.6.10.v20130312 (was: [Java Broker] Upgrade jetty to recent 7.x version (7.6.10.v20130312)) [Java Broker] Upgrade jetty to 7.6.10.v20130312 --- Key: QPID-4761 URL: https://issues.apache.org/jira/browse/QPID-4761 Project: Qpid Issue Type: Improvement Components: Java Broker Affects Versions: 0.22 Reporter: Alex Rudyy Assignee: Robbie Gemmell Fix For: 0.23 The Qpid broker depends on jetty of version 7.6.3.v20120416. There were several bug fixing releases of jetty. We need to upgrade it to the recent 7.x version which is 7.6.10.v20130312. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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] [Resolved] (QPID-4701) Exception types lost in qpidmessaging when compiling with cmake and gcc 4.1.2 (e.g. RHEL5)
[ https://issues.apache.org/jira/browse/QPID-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-4701. -- Resolution: Fixed Fix Version/s: 0.23 Exception types lost in qpidmessaging when compiling with cmake and gcc 4.1.2 (e.g. RHEL5) --- Key: QPID-4701 URL: https://issues.apache.org/jira/browse/QPID-4701 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.20, 0.22 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.23 Exceptions are thrown simply as std::exception rather than the specific types defined. This appears to be a result of the visibility flag support in the version of gcc (cmake turns that on, autotools does not). (See also QPID-4484) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-4764) Locking may lead to deadlock for concurrent receiver
Gordon Sim created QPID-4764: Summary: Locking may lead to deadlock for concurrent receiver Key: QPID-4764 URL: https://issues.apache.org/jira/browse/QPID-4764 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.22 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.23 The lock ordering leaves open the possibility of a deadlock if one thread is fetching on a receiver, another is accepting messages received by it and a third is closing the receiver. Thread 1 holds SessionImpl's lock and is blocked on IncomingMessage's lock. Thread 2 holds IncomingMessage's lock and is blocked on ReceiverImpl's lock. Thread 3 holds the ReceiverImpl's lock and is blocked on SessionImpl's lock. I have been unable to reproduce this myself, but an actual incidence has been reported: https://bugzilla.redhat.com/show_bug.cgi?id=703891 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-4761) [Java Broker] Upgrade jetty to 7.6.10.v20130312
[ https://issues.apache.org/jira/browse/QPID-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13638074#comment-13638074 ] Robbie Gemmell commented on QPID-4761: -- Alex merged the above changes to the 0.22 branch via: http://svn.apache.org/r1470486 [Java Broker] Upgrade jetty to 7.6.10.v20130312 --- Key: QPID-4761 URL: https://issues.apache.org/jira/browse/QPID-4761 Project: Qpid Issue Type: Improvement Components: Java Broker Affects Versions: 0.22 Reporter: Alex Rudyy Assignee: Robbie Gemmell Fix For: 0.23 The Qpid broker depends on jetty of version 7.6.3.v20120416. There were several bug fixing releases of jetty. We need to upgrade it to the recent 7.x version which is 7.6.10.v20130312. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-4761) [Java Broker] Upgrade jetty to 7.6.10.v20130312
[ https://issues.apache.org/jira/browse/QPID-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4761: - Fix Version/s: (was: 0.23) 0.22 [Java Broker] Upgrade jetty to 7.6.10.v20130312 --- Key: QPID-4761 URL: https://issues.apache.org/jira/browse/QPID-4761 Project: Qpid Issue Type: Improvement Components: Java Broker Affects Versions: 0.22 Reporter: Alex Rudyy Assignee: Robbie Gemmell Fix For: 0.22 The Qpid broker depends on jetty of version 7.6.3.v20120416. There were several bug fixing releases of jetty. We need to upgrade it to the recent 7.x version which is 7.6.10.v20130312. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-4762) [Java Broker] Upgrade dojo to the version 1.8.3
[ https://issues.apache.org/jira/browse/QPID-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4762: - Fix Version/s: (was: 0.23) 0.22 [Java Broker] Upgrade dojo to the version 1.8.3 --- Key: QPID-4762 URL: https://issues.apache.org/jira/browse/QPID-4762 Project: Qpid Issue Type: Improvement Components: Java Broker Affects Versions: 0.22 Reporter: Alex Rudyy Assignee: Alex Rudyy Fix For: 0.22 Upgrade dojo toolkit to the latest stable version 1.8.3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-4762) [Java Broker] Upgrade dojo to the version 1.8.3
[ https://issues.apache.org/jira/browse/QPID-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13638076#comment-13638076 ] Robbie Gemmell commented on QPID-4762: -- Alex merged the above change to the 0.22 branch via: http://svn.apache.org/r1470488 [Java Broker] Upgrade dojo to the version 1.8.3 --- Key: QPID-4762 URL: https://issues.apache.org/jira/browse/QPID-4762 Project: Qpid Issue Type: Improvement Components: Java Broker Affects Versions: 0.22 Reporter: Alex Rudyy Assignee: Alex Rudyy Fix For: 0.23 Upgrade dojo toolkit to the latest stable version 1.8.3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-4685) [Java Broker] update documentation to reflect changes to configuration etc
[ https://issues.apache.org/jira/browse/QPID-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13638080#comment-13638080 ] Robbie Gemmell commented on QPID-4685: -- Alex merged the above change to the 0.22 branch via: http://svn.apache.org/r1470499 [Java Broker] update documentation to reflect changes to configuration etc -- Key: QPID-4685 URL: https://issues.apache.org/jira/browse/QPID-4685 Project: Qpid Issue Type: Bug Components: Documentation, Java Broker Affects Versions: 0.21 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Priority: Blocker Fix For: 0.22 update documentation to reflect changes to configuration etc E.g: - Remove all trace of config.xml - Update command line option documentation to reflect additions/removal in this area. - New ACL option in QPID-4678 - Outline when it is still necessary to use an XML configuration file for a virtualhost and how to do so. Etc -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-4751) Hello example still use the 'test' virtualhost, which no longer exists in the initial Java broker config
[ https://issues.apache.org/jira/browse/QPID-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13638079#comment-13638079 ] Robbie Gemmell commented on QPID-4751: -- Alex merged the above change to the 0.22 branch via: http://svn.apache.org/r1470490 Hello example still use the 'test' virtualhost, which no longer exists in the initial Java broker config Key: QPID-4751 URL: https://issues.apache.org/jira/browse/QPID-4751 Project: Qpid Issue Type: Bug Affects Versions: 0.21 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.23 Connection URLs in existing examples still use the 'test' virtualhost, which no longer exists in the initial Java broker config, which removed the thre previous 'localhost' 'development' and 'test' virtualhosts and instead has only a single 'default' virtualhsot. As a result, the examples will fail to run unless the user adds a 'test' virtualhost or changes the connection URL themselves. The example configurations should be updated to remove the virtualhost from the URL entirely, which will make the client connect to the brokers current default virtualhost regardless what it is actually called, meaning the examples will work against newer and older releases shipping config as well as after the user reconfigures the broker. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-4751) Hello example still use the 'test' virtualhost, which no longer exists in the initial Java broker config
[ https://issues.apache.org/jira/browse/QPID-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4751: - Fix Version/s: (was: 0.23) 0.22 Hello example still use the 'test' virtualhost, which no longer exists in the initial Java broker config Key: QPID-4751 URL: https://issues.apache.org/jira/browse/QPID-4751 Project: Qpid Issue Type: Bug Affects Versions: 0.21 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.22 Connection URLs in existing examples still use the 'test' virtualhost, which no longer exists in the initial Java broker config, which removed the thre previous 'localhost' 'development' and 'test' virtualhosts and instead has only a single 'default' virtualhsot. As a result, the examples will fail to run unless the user adds a 'test' virtualhost or changes the connection URL themselves. The example configurations should be updated to remove the virtualhost from the URL entirely, which will make the client connect to the brokers current default virtualhost regardless what it is actually called, meaning the examples will work against newer and older releases shipping config as well as after the user reconfigures the broker. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-4763) [Java Broker] Create generic JDBC store
[ https://issues.apache.org/jira/browse/QPID-4763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13638081#comment-13638081 ] Robbie Gemmell commented on QPID-4763: -- Alex merged the above change to the 0.22 branch via: http://svn.apache.org/r1470549 [Java Broker] Create generic JDBC store - Key: QPID-4763 URL: https://issues.apache.org/jira/browse/QPID-4763 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Rob Godfrey Assignee: Rob Godfrey Priority: Minor Fix For: 0.23 The Java Broker currently has code to allow for using Derby as an in-process store. It is relatively trivial to modify this code to allow for the use of any JDBC compliant database as an external store provider (though performance is unlikely to be impressive). The advantage of using an external JDBC store is the ability for third party libraries to easily inspect the store, and for storage to be provided by existing infrastructure. Some tweaking of the store is necessary for those parts which create the tables since SQL92 datatypes are not universally implemented. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-4763) [Java Broker] Create generic JDBC store
[ https://issues.apache.org/jira/browse/QPID-4763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4763: - Fix Version/s: (was: 0.23) 0.22 [Java Broker] Create generic JDBC store - Key: QPID-4763 URL: https://issues.apache.org/jira/browse/QPID-4763 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Rob Godfrey Assignee: Rob Godfrey Priority: Minor Fix For: 0.22 The Java Broker currently has code to allow for using Derby as an in-process store. It is relatively trivial to modify this code to allow for the use of any JDBC compliant database as an external store provider (though performance is unlikely to be impressive). The advantage of using an external JDBC store is the ability for third party libraries to easily inspect the store, and for storage to be provided by existing infrastructure. Some tweaking of the store is necessary for those parts which create the tables since SQL92 datatypes are not universally implemented. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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
Review Request: receiver/session locking changes
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/10704/ --- Review request for qpid and Alan Conway. Description --- The changes involve: (1) removing the unnecessary lock from ReceiverImpl::getName() since the destination member variable is const (2) removing the lock from the two forms of SessionImpl:acknowledgeImpl() since the transactional member is const and IncomingMessages::accept() does its own locking (3) releasing the lock while calling back from ReceiverImpl to SessionImpl in ReceiverImpl::close() These help break the possible deadlock. This addresses bug QPID-4764. https://issues.apache.org/jira/browse/QPID-4764 Diffs - /trunk/qpid/cpp/src/qpid/client/amqp0_10/ReceiverImpl.cpp 1470466 /trunk/qpid/cpp/src/qpid/client/amqp0_10/SessionImpl.cpp 1470466 Diff: https://reviews.apache.org/r/10704/diff/ Testing --- make check passes (I couldn't reproduce the deadlock). Thanks, Gordon Sim
[jira] [Commented] (QPID-4764) Locking may lead to deadlock for concurrent receiver
[ https://issues.apache.org/jira/browse/QPID-4764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13638121#comment-13638121 ] Gordon Sim commented on QPID-4764: -- Fix available for review: https://reviews.apache.org/r/10704/ Locking may lead to deadlock for concurrent receiver Key: QPID-4764 URL: https://issues.apache.org/jira/browse/QPID-4764 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.22 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.23 The lock ordering leaves open the possibility of a deadlock if one thread is fetching on a receiver, another is accepting messages received by it and a third is closing the receiver. Thread 1 holds SessionImpl's lock and is blocked on IncomingMessage's lock. Thread 2 holds IncomingMessage's lock and is blocked on ReceiverImpl's lock. Thread 3 holds the ReceiverImpl's lock and is blocked on SessionImpl's lock. I have been unable to reproduce this myself, but an actual incidence has been reported: https://bugzilla.redhat.com/show_bug.cgi?id=703891 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-4765) Incorrect parameter validation for legacystore wcache-page-size and jfile-size-pgs
[ https://issues.apache.org/jira/browse/QPID-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13638350#comment-13638350 ] Kim van der Riet commented on QPID-4765: Fixed r.1470667 Thanks to Siddhesh Poyarekar for the patch. Incorrect parameter validation for legacystore wcache-page-size and jfile-size-pgs -- Key: QPID-4765 URL: https://issues.apache.org/jira/browse/QPID-4765 Project: Qpid Issue Type: Bug Components: C++ Broker Reporter: Kim van der Riet Assignee: Kim van der Riet Priority: Minor The store module incorrectly changes the size of the page cache to 64kB when the file size parameter is equal to 1 (--jfile-size-pgs=1) for any valid page cache size. This should only happen when the page cache size is set to 128kB. The legacystore file size is specified in terms of the read cache size (which is fixed to 64kB). Hence a jfile-size-pgs set to 1 creates 64kB files, the smallest allowed. However, the write page cache, set by the wcache-page-size parameter, cannot be larger than the physical file size, as libaio uses DMA to write each page, and this cannot be split between files. This can occur for only one legal setting of wcache-page-size, ie 128kB. In this case only, a check must be made to see if the file size parameter jfile-size-pgs==1. If so, then the write cache size exceeds the physical file size, and must be reduced to be the same as the physical file size, ie 64kB. The logic incorrectly makes this change for all legal write page cache size values, not just the maximum of 128kB where this change is required. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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
[Java Build failure] SessionCreateTest is hanging
Hi Folks, org.apache.qpid.client.SessionCreateTest hangs when I run its under the cpp profile. It works well under the java broker profile. It seems the last successful run on Jenkins was 2 days ago https://builds.apache.org/job/Qpid-Java-Cpp-Test/ Anybody else seeing this ? Regards, Rajith
[jira] [Created] (QPID-4766) [AMQP 1.0] provide a way of specifying an xquery for receivers from an xml exchange
Gordon Sim created QPID-4766: Summary: [AMQP 1.0] provide a way of specifying an xquery for receivers from an xml exchange Key: QPID-4766 URL: https://issues.apache.org/jira/browse/QPID-4766 Project: Qpid Issue Type: Bug Components: C++ Broker, C++ Client Affects Versions: 0.22 Reporter: Gordon Sim Assignee: Gordon Sim -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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] [Resolved] (QPID-4702) cmake build of ssl support does not work on certain platforms
[ https://issues.apache.org/jira/browse/QPID-4702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-4702. -- Resolution: Fixed Fix Version/s: 0.23 Patch from review board applied on trunk http://svn.apache.org/viewvc?view=revisionrevision=r1470693 A better solution may be found in future, but this should address it for now. cmake build of ssl support does not work on certain platforms - Key: QPID-4702 URL: https://issues.apache.org/jira/browse/QPID-4702 Project: Qpid Issue Type: Bug Components: C++ Broker, C++ Client Affects Versions: 0.20, 0.22 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.23 This is a result of the order of libraries and object files passed to the linker. The libraries must follow the .o files that require them or they will be ignored (assumed not needed). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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: Review Request: QPID-4760: Associate Java Broker QueueAdapter and SessionAdapter via ConsumerAdapter
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/10686/#review19545 --- Sorry for the delayed response, you picked possibly the second time this year both Rob and I were otherwise occupied over the weekend and beyond :) Looking this over it seems like it would work, but I can't say I am a big fan of inspecting potentially every connection during every consumer creation and removal. An alternative might be: the SessionModel interface has a method to get the associated ConnectionModel, with which you could directly query for the associated Connection[Adapter] from the Virtualhost since it already maintains that mapping. http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/broker/src/main/java/org/apache/qpid/server/model/adapter/QueueAdapter.java https://reviews.apache.org/r/10686/#comment40348 Marking for reference http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/broker/src/main/java/org/apache/qpid/server/model/adapter/QueueAdapter.java https://reviews.apache.org/r/10686/#comment40349 Marking for reference - Robbie Gemmell On April 20, 2013, 6:59 p.m., Fraser Adams wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/10686/ --- (Updated April 20, 2013, 6:59 p.m.) Review request for qpid, Gordon Sim, Robbie Gemmell, and Rob Godfrey. Description --- In the management model it should be possible to navigate from a Connection through its associated Sessions to Queues via Subscriptions/Consumers. Basically Subscription is an association class linking Session and Queue. In the Java Broker Management Model there was code missing that should allow the SessionAdapter to getSubscriptions(). This patch provides code to do the necessary object registrations to allow the Subscriptions in SessionAdapter to be correctly maintained thus allowing navigation from Connection to Queue and vice versa. Diffs - http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/broker/src/main/java/org/apache/qpid/server/model/adapter/ConnectionAdapter.java 1469902 http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/broker/src/main/java/org/apache/qpid/server/model/adapter/ConsumerAdapter.java 1469902 http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/broker/src/main/java/org/apache/qpid/server/model/adapter/QueueAdapter.java 1469902 http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/broker/src/main/java/org/apache/qpid/server/model/adapter/SessionAdapter.java 1469902 http://svn.apache.org/repos/asf/qpid/trunk/qpid/java/broker/src/main/java/org/apache/qpid/server/model/adapter/VirtualHostAdapter.java 1469902 http://svn.apache.org/repos/asf/qpid/trunk/qpid/tools/src/java/src/qpid-broker-plugins-management-qmf2/java/org/apache/qpid/server/qmf2/QmfManagementAgent.java 1469902 Diff: https://reviews.apache.org/r/10686/diff/ Testing --- I've tested in the QmfManagementPlugin. Plugin loaded and the QMF Gui was able to navigate starting from a Connection through Subscribed Sessions to Queue. Also Started with Queue and navigated through Subscriptions to show Session info and navigate to Connection. Thanks, Fraser Adams
Re: [Java Build failure] SessionCreateTest is hanging
The last run being 2 days ago is just reflective of the few properly functioning Jenkins nodes currently being overloaded with jobs. It has passed on the several previous CPP profile runs on Jenkins, e.g: https://builds.apache.org/job/Qpid-Java-Cpp-Test/1341/testReport/org.apache.qpid.client/SessionCreateTest/ There are some cases it was rather slow though, but that could just be from running on one of the poorly Jenkins nodes: https://builds.apache.org/job/Qpid-Java-Cpp-Test/1338/testReport/org.apache.qpid.client/SessionCreateTest/ This JIRA was raised some time ago due to the test being really slow, though it was only noticed on the SSL profile: https://issues.apache.org/jira/browse/QPID-3431 Are you sure it has actually hung? Do you have any local changes, and does it work without them? The test doesn't look to have failed in any of the build results on record for the last 2 weeks, and the last change to the client was 3 weeks ago: http://svn.apache.org/r1463158 It isn't actually running at all on the Java broker profiles: java/test-profiles/JavaExcludes:org.apache.qpid.client.SessionCreateTest#* Robbie On 22 April 2013 20:30, Rajith Attapattu rajit...@gmail.com wrote: Hi Folks, org.apache.qpid.client.SessionCreateTest hangs when I run its under the cpp profile. It works well under the java broker profile. It seems the last successful run on Jenkins was 2 days ago https://builds.apache.org/job/Qpid-Java-Cpp-Test/ Anybody else seeing this ? Regards, Rajith
Re: [Java Build failure] SessionCreateTest is hanging
There are no local changes. I initially came across this when testing out a patch on a branch. After that, I moved back to trunk, made sure I have the latest and no local changes. From the stack trace below it appears to be hung on a timed wait. But why it doesn't time out beats me. It certainly looks strange, hence the reason why I wanted to reach out and see if others are also noticing this. This can be reproduced (on my machine every time I run the build). main prio=10 tid=0x7f3d1c011000 nid=0xd54 in Object.wait() [0x7f3d21c85000] [junit]java.lang.Thread.State: TIMED_WAITING (on object monitor) [junit] at java.lang.Object.wait(Native Method) [junit] at org.apache.qpid.transport.util.Waiter.await(Waiter.java:54) [junit] at org.apache.qpid.transport.Session.awaitClose(Session.java:1067) [junit] at org.apache.qpid.transport.Session.close(Session.java:1056) Does this test pass on your env? The fact that it pass with the java profile and fails consistently with the cpp profile is interesting. I will try this out on a different env tomorrow and see what happens. Meanwhile I hope we get a jenkins run going or someone else had run it on their local machine. Rajith On Mon, Apr 22, 2013 at 5:42 PM, Robbie Gemmell robbie.gemm...@gmail.comwrote: The last run being 2 days ago is just reflective of the few properly functioning Jenkins nodes currently being overloaded with jobs. It has passed on the several previous CPP profile runs on Jenkins, e.g: https://builds.apache.org/job/Qpid-Java-Cpp-Test/1341/testReport/org.apache.qpid.client/SessionCreateTest/ There are some cases it was rather slow though, but that could just be from running on one of the poorly Jenkins nodes: https://builds.apache.org/job/Qpid-Java-Cpp-Test/1338/testReport/org.apache.qpid.client/SessionCreateTest/ This JIRA was raised some time ago due to the test being really slow, though it was only noticed on the SSL profile: https://issues.apache.org/jira/browse/QPID-3431 Are you sure it has actually hung? Do you have any local changes, and does it work without them? The test doesn't look to have failed in any of the build results on record for the last 2 weeks, and the last change to the client was 3 weeks ago: http://svn.apache.org/r1463158 It isn't actually running at all on the Java broker profiles: java/test-profiles/JavaExcludes:org.apache.qpid.client.SessionCreateTest#* Robbie On 22 April 2013 20:30, Rajith Attapattu rajit...@gmail.com wrote: Hi Folks, org.apache.qpid.client.SessionCreateTest hangs when I run its under the cpp profile. It works well under the java broker profile. It seems the last successful run on Jenkins was 2 days ago https://builds.apache.org/job/Qpid-Java-Cpp-Test/ Anybody else seeing this ? Regards, Rajith
Re: [Java Build failure] SessionCreateTest is hanging
I'm still a little unclear on whether you actually saw the test suite complete/abort (due to the timelimit on the JUnit test run) with a failure or not? This particular test does the same thing over and over again, so are you sure it isn't just going [very] slowly and hasn't finished yet? (Possibly instrument the test and see, or increase the JUnit timeout?) As far as I'm aware it is passing in the other CI environment I use to run the C++ profile, yes. I would expect it to pass the next time it runs on the ASF Jenkins nodes given it hasn't been failing previously and there have been no client changes in weeks to suggest it should now. When was the last time you successfully ran the C++ profile on the machine? Although it doesn't appear like a particular change has caused any issue, have you tried reverting the codebase to an earlier timeframe you know worked and running the test again? As mentioned, the test is excluded on all the Java broker profiles so it isn't actually passing there (though you could remove the exclude and check if it does). It has been excluded since the day it was committed, because this takes ages to run. It was also excluded from the C++ profiles at the same time, but that has obviously changed at some point over the years. Robbie On 22 April 2013 23:07, Rajith Attapattu rajit...@gmail.com wrote: There are no local changes. I initially came across this when testing out a patch on a branch. After that, I moved back to trunk, made sure I have the latest and no local changes. From the stack trace below it appears to be hung on a timed wait. But why it doesn't time out beats me. It certainly looks strange, hence the reason why I wanted to reach out and see if others are also noticing this. This can be reproduced (on my machine every time I run the build). main prio=10 tid=0x7f3d1c011000 nid=0xd54 in Object.wait() [0x7f3d21c85000] [junit]java.lang.Thread.State: TIMED_WAITING (on object monitor) [junit] at java.lang.Object.wait(Native Method) [junit] at org.apache.qpid.transport.util.Waiter.await(Waiter.java:54) [junit] at org.apache.qpid.transport.Session.awaitClose(Session.java:1067) [junit] at org.apache.qpid.transport.Session.close(Session.java:1056) Does this test pass on your env? The fact that it pass with the java profile and fails consistently with the cpp profile is interesting. I will try this out on a different env tomorrow and see what happens. Meanwhile I hope we get a jenkins run going or someone else had run it on their local machine. Rajith On Mon, Apr 22, 2013 at 5:42 PM, Robbie Gemmell robbie.gemm...@gmail.com wrote: The last run being 2 days ago is just reflective of the few properly functioning Jenkins nodes currently being overloaded with jobs. It has passed on the several previous CPP profile runs on Jenkins, e.g: https://builds.apache.org/job/Qpid-Java-Cpp-Test/1341/testReport/org.apache.qpid.client/SessionCreateTest/ There are some cases it was rather slow though, but that could just be from running on one of the poorly Jenkins nodes: https://builds.apache.org/job/Qpid-Java-Cpp-Test/1338/testReport/org.apache.qpid.client/SessionCreateTest/ This JIRA was raised some time ago due to the test being really slow, though it was only noticed on the SSL profile: https://issues.apache.org/jira/browse/QPID-3431 Are you sure it has actually hung? Do you have any local changes, and does it work without them? The test doesn't look to have failed in any of the build results on record for the last 2 weeks, and the last change to the client was 3 weeks ago: http://svn.apache.org/r1463158 It isn't actually running at all on the Java broker profiles: java/test-profiles/JavaExcludes:org.apache.qpid.client.SessionCreateTest#* Robbie On 22 April 2013 20:30, Rajith Attapattu rajit...@gmail.com wrote: Hi Folks, org.apache.qpid.client.SessionCreateTest hangs when I run its under the cpp profile. It works well under the java broker profile. It seems the last successful run on Jenkins was 2 days ago https://builds.apache.org/job/Qpid-Java-Cpp-Test/ Anybody else seeing this ? Regards, Rajith
[jira] [Created] (QPID-4767) [legacystore] QMF commands to create a persistent queue with an illegal number of journal files or journal file size should be rejected
Kim van der Riet created QPID-4767: -- Summary: [legacystore] QMF commands to create a persistent queue with an illegal number of journal files or journal file size should be rejected Key: QPID-4767 URL: https://issues.apache.org/jira/browse/QPID-4767 Project: Qpid Issue Type: Bug Components: C++ Broker Reporter: Kim van der Riet Assignee: Kim van der Riet Priority: Minor QMF queries that request a queue to be created with more than 64 journal files (max journal files per queue are 64) should be rejected instead of translated to the maximum value (64). Current behaviour doesn't inform the user that less files are used (only a warning on server side) and is creating something that is not what the user asked for. This behavior applies also to the journal size parameter where the size is larger or smaller than the minimum or maximum allowable value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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] [Resolved] (QPID-4765) Incorrect parameter validation for legacystore wcache-page-size and jfile-size-pgs
[ https://issues.apache.org/jira/browse/QPID-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPID-4765. Resolution: Fixed Incorrect parameter validation for legacystore wcache-page-size and jfile-size-pgs -- Key: QPID-4765 URL: https://issues.apache.org/jira/browse/QPID-4765 Project: Qpid Issue Type: Bug Components: C++ Broker Reporter: Kim van der Riet Assignee: Kim van der Riet Priority: Minor The store module incorrectly changes the size of the page cache to 64kB when the file size parameter is equal to 1 (--jfile-size-pgs=1) for any valid page cache size. This should only happen when the page cache size is set to 128kB. The legacystore file size is specified in terms of the read cache size (which is fixed to 64kB). Hence a jfile-size-pgs set to 1 creates 64kB files, the smallest allowed. However, the write page cache, set by the wcache-page-size parameter, cannot be larger than the physical file size, as libaio uses DMA to write each page, and this cannot be split between files. This can occur for only one legal setting of wcache-page-size, ie 128kB. In this case only, a check must be made to see if the file size parameter jfile-size-pgs==1. If so, then the write cache size exceeds the physical file size, and must be reduced to be the same as the physical file size, ie 64kB. The logic incorrectly makes this change for all legal write page cache size values, not just the maximum of 128kB where this change is required. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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
