[jira] Created: (QPID-2472) QpidCompositeRollingAppender log4j configuration is misleading
QpidCompositeRollingAppender log4j configuration is misleading -- Key: QPID-2472 URL: https://issues.apache.org/jira/browse/QPID-2472 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.5, 0.6 Reporter: Andrew Kennedy Fix For: 0.7 The QpidCompositeRollingAppender logging appender configuration is misleading. The configuration file states that the default rollover size is 1MB, wheras the actual default in the code is 10 MB. Additionally, the 'CompressBackupFiles' flag controls both the creation of backups in a separate directory on rollover, and the compression of these files. This property should either be renamed or backing up of files to a separate location should be enabled based on the presence of the 'backupFilesToPath' property instead. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2472) QpidCompositeRollingAppender log4j configuration is misleading
[ https://issues.apache.org/jira/browse/QPID-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Kennedy updated QPID-2472: - Attachment: 0001-QPID-2472-Correct-log4j-XML-configuration-comments.patch Correct the default rollover file size in the log4j XML configuration to match code value of 10 MB QpidCompositeRollingAppender log4j configuration is misleading -- Key: QPID-2472 URL: https://issues.apache.org/jira/browse/QPID-2472 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.5, 0.6 Reporter: Andrew Kennedy Fix For: 0.7 Attachments: 0001-QPID-2472-Correct-log4j-XML-configuration-comments.patch The QpidCompositeRollingAppender logging appender configuration is misleading. The configuration file states that the default rollover size is 1MB, wheras the actual default in the code is 10 MB. Additionally, the 'CompressBackupFiles' flag controls both the creation of backups in a separate directory on rollover, and the compression of these files. This property should either be renamed or backing up of files to a separate location should be enabled based on the presence of the 'backupFilesToPath' property instead. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2360) declaring virtualhost level firewall configuration in virtualhosts.xml leads to NPE on startup
[ https://issues.apache.org/jira/browse/QPID-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850870#action_12850870 ] Robbie Gemmell commented on QPID-2360: -- The configuration changes dont fully account for the Security configuration, particularly the ability to reload the security configuration at runtime (eg to update the Firewall configuration). ServerConfiguration.reparseConfigFIleSecuritySections() expects the virtualhost configuration properties to be part of the main configuration, which is not the case now when an external virtualhosts configuration file is used. As such this needs updated to determine whether an external file was used to configure the virtualhost such that the configuration sections are properly reparsed. This is not detected by the firewall related unit/system tests in ServerConfiguration and FirewallConfigTest, as some utilise only broker level security configuration, and the others utilise virtualhost level configuration but when the main config is reparsed and the virtualhosts file isnt, it will return an empty subset of virtualhost security and the firewall will then deny by default, which is what the tests expect to occur and so no problem is found. The updated (trunk) patch contains a number of .orig files, presumably from 'unclean' patch runs. It also still contains some seemingly unrelated modifications (eg in AlertingTest, which now fails when run). If these are unrelated but still required changes, a new JIRA should be raised for them to allow proper tracking of the issue. declaring virtualhost level firewall configuration in virtualhosts.xml leads to NPE on startup -- Key: QPID-2360 URL: https://issues.apache.org/jira/browse/QPID-2360 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.6 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.7 Attachments: 0001-QPID-2630-QPID-2631-branch.patch, 0001-QPID-2630-QPID-2631-trunk.patch Declaring virtualhost level firewall configuration in virtualhosts.xml leads to NPE on startup. After moving the same configuration into config.xml the broker then loads ok and the configuration works as expected. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Assigned: (QPID-2465) Ant 1.8.x javac task prints warning message during builds
[ https://issues.apache.org/jira/browse/QPID-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-2465: Assignee: Robbie Gemmell Ant 1.8.x javac task prints warning message during builds - Key: QPID-2465 URL: https://issues.apache.org/jira/browse/QPID-2465 Project: Qpid Issue Type: Bug Components: Ant Build System Affects Versions: 0.6 Environment: Ant 1.8.0 Reporter: Andrew Kennedy Assignee: Robbie Gemmell Priority: Minor Fix For: 0.7 Attachments: 0001-QPID-2465-Set-javac-includeantruntime-property-in-b.patch When building Qpid with Ant version 1.8.0 the javac task prints a warning about the includeantruntime property not being set. This property should be set to false. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2465) Ant 1.8.x javac task prints warning message during builds
[ https://issues.apache.org/jira/browse/QPID-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-2465: - Status: Ready To Review (was: In Progress) Ant 1.8.x javac task prints warning message during builds - Key: QPID-2465 URL: https://issues.apache.org/jira/browse/QPID-2465 Project: Qpid Issue Type: Bug Components: Ant Build System Affects Versions: 0.6 Environment: Ant 1.8.0 Reporter: Andrew Kennedy Assignee: Robbie Gemmell Priority: Minor Fix For: 0.7 Attachments: 0001-QPID-2465-Set-javac-includeantruntime-property-in-b.patch When building Qpid with Ant version 1.8.0 the javac task prints a warning about the includeantruntime property not being set. This property should be set to false. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Assigned: (QPID-2472) QpidCompositeRollingAppender log4j configuration is misleading
[ https://issues.apache.org/jira/browse/QPID-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-2472: Assignee: Robbie Gemmell QpidCompositeRollingAppender log4j configuration is misleading -- Key: QPID-2472 URL: https://issues.apache.org/jira/browse/QPID-2472 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.5, 0.6 Reporter: Andrew Kennedy Assignee: Robbie Gemmell Fix For: 0.7 Attachments: 0001-QPID-2472-Correct-log4j-XML-configuration-comments.patch The QpidCompositeRollingAppender logging appender configuration is misleading. The configuration file states that the default rollover size is 1MB, wheras the actual default in the code is 10 MB. Additionally, the 'CompressBackupFiles' flag controls both the creation of backups in a separate directory on rollover, and the compression of these files. This property should either be renamed or backing up of files to a separate location should be enabled based on the presence of the 'backupFilesToPath' property instead. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2465) Ant 1.8.x javac task prints warning message during builds
[ https://issues.apache.org/jira/browse/QPID-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850879#action_12850879 ] Robbie Gemmell commented on QPID-2465: -- Patch commited. Ant 1.8.x javac task prints warning message during builds - Key: QPID-2465 URL: https://issues.apache.org/jira/browse/QPID-2465 Project: Qpid Issue Type: Bug Components: Ant Build System Affects Versions: 0.6 Environment: Ant 1.8.0 Reporter: Andrew Kennedy Assignee: Robbie Gemmell Priority: Minor Fix For: 0.7 Attachments: 0001-QPID-2465-Set-javac-includeantruntime-property-in-b.patch When building Qpid with Ant version 1.8.0 the javac task prints a warning about the includeantruntime property not being set. This property should be set to false. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2472) QpidCompositeRollingAppender log4j configuration is misleading
[ https://issues.apache.org/jira/browse/QPID-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850883#action_12850883 ] Robbie Gemmell commented on QPID-2472: -- Updating the comment to make it clear that the unconfigured default is 10MB and not 1MB is good, but I think the update to use a 10MB configuration setting is a making it a bit too large and it should be left at 1MB. QpidCompositeRollingAppender log4j configuration is misleading -- Key: QPID-2472 URL: https://issues.apache.org/jira/browse/QPID-2472 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.5, 0.6 Reporter: Andrew Kennedy Assignee: Robbie Gemmell Fix For: 0.7 Attachments: 0001-QPID-2472-Correct-log4j-XML-configuration-comments.patch The QpidCompositeRollingAppender logging appender configuration is misleading. The configuration file states that the default rollover size is 1MB, wheras the actual default in the code is 10 MB. Additionally, the 'CompressBackupFiles' flag controls both the creation of backups in a separate directory on rollover, and the compression of these files. This property should either be renamed or backing up of files to a separate location should be enabled based on the presence of the 'backupFilesToPath' property instead. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Resolved: (QPID-2454) [Patch] Messages set with a TTL expire immediately when sent on qpid queues with LVQ ordering
[ https://issues.apache.org/jira/browse/QPID-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-2454. -- Resolution: Fixed Clearly more tests are needed in this area, but no reason not to mark this bug fixed now change has been made. [Patch] Messages set with a TTL expire immediately when sent on qpid queues with LVQ ordering - Key: QPID-2454 URL: https://issues.apache.org/jira/browse/QPID-2454 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.5, 0.6, 0.7 Environment: RHEL-5 or later Reporter: Siddhesh Poyarekar Attachments: qpidc-clear-lvq-on-expire.patch Problem Description: MRG LVQ becomes unstable when msg TTLs are used and a message expires. Sometimes when messages expire, it seems to upset the LVQ mechanism. Eg. Once a message with key 'X' has expired, any subsequent messages sent to the LVQ with key 'X' are expired immediately, and never made available to client applications. Once an LVQ begins exhibiting this behaviour, This behaviour continues until the broker is restarted. At this point, another side effect is that the msgDepth and byteDepth properties on an LVQ do not always agree, i.e, when msgDepth is zero, byteDepth is not zero. How Reproducible: Always: Steps to Reproduce: * Create a queue with queue ordering as lvq or lvq-no-browse * Build and run attached producer for 1 minute * Stop the producer for a minute to allow messages to expire * Use qpid-tool to monitor the queue depth and wait for the message to be dequeued (usually takes about 10 minutes) * Once message has expired, restart the producer * Watch queue properties with qpid-tool Actual Results: The queue depth is always 0, but the byte depth is not. Occasionally, one will get the following error message from the producer: Unexpected exception: Attempted size underflow on dequeue Expected Results: The queue depth should not be 0 (at least till the time expired messages are purged). Also, when queue depth is 0, byte depth should be 0. Additional Information: The root cause seems to be that the lvq object in the Queue that holds mapping from key to messages (Queue::lvq) is not cleared when messages are expired (Queue::purgeExpired), which leads to incorrect accounting when the next message arrives in the queue with the same LVQ key as the message that expired. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: 0.6 Release
On 03/26/2010 03:54 PM, Alan Conway wrote: On 03/26/2010 10:57 AM, Robbie Gemmell wrote: +1 on the thanks. +1 from me too many thanks. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: 0.6 valgrind errors
On Sun, 2010-03-28 at 19:01 -0400, Jeff Laughlin wrote: make check asked me to send these valgrind errors to this address. Enjoy. FWIW: Linux kamikaze 2.6.26-2-686 #1 SMP Wed Nov 4 20:45:37 UTC 2009 i686 GNU/Linux You haven't given quite enough information: What version of the qpid code caused this? (If from the svn repo which branch/revision) Exactly which version of Linux is this? distro etc. [FWIW this looks like an issue in the c library rather than in the qpid code, but it's hard to tell] Andrew - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2389) 0.6 RC from SVN fails to build with make[1]: execvp: ./rubygen.mk: Permission denied
[ https://issues.apache.org/jira/browse/QPID-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850897#action_12850897 ] Carl Trieloff commented on QPID-2389: - Have you tried a full tree checkout and then building from the C++ dir. reason I ask is that a few things have been moved around and this would resolve unforeseen dependancies not yet corrected 0.6 RC from SVN fails to build with make[1]: execvp: ./rubygen.mk: Permission denied -- Key: QPID-2389 URL: https://issues.apache.org/jira/browse/QPID-2389 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.6 Environment: Debian GNU/Linux 5.0.3 (lenny) Reporter: Jeff Laughlin Checked out 906327 from 0.6 branch, ./bootstrap, ./configure, then make and I get jlaugh...@kamikaze:~/qpid/broker/svn/0.6-release-cpp$ make Making all in managementgen make[1]: Entering directory `/home/jlaughlin/qpid/broker/svn/0.6-release-cpp/managementgen' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/jlaughlin/qpid/broker/svn/0.6-release-cpp/managementgen' Making all in etc make[1]: Entering directory `/home/jlaughlin/qpid/broker/svn/0.6-release-cpp/etc' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/jlaughlin/qpid/broker/svn/0.6-release-cpp/etc' Making all in src make[1]: Entering directory `/home/jlaughlin/qpid/broker/svn/0.6-release-cpp/src' ./rubygen.mk make[1]: execvp: ./rubygen.mk: Permission denied make[1]: *** [rubygen.mk] Error 127 make[1]: Leaving directory `/home/jlaughlin/qpid/broker/svn/0.6-release-cpp/src' make: *** [all-recursive] Error 1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Commented: (QPID-2220) Assisting manual recovery from a complete persistent cluster crash.
[ https://issues.apache.org/jira/browse/QPID-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850901#action_12850901 ] Alan Conway commented on QPID-2220: --- As of r916475, the last survivor in a cluster automatically marks its store as clean, so the only way we can end up with no clean store is if N1 members fail so close together that none of them receives a config-change showing them to be the last member. For that we need a counter from the store as described above. Assisting manual recovery from a complete persistent cluster crash. --- Key: QPID-2220 URL: https://issues.apache.org/jira/browse/QPID-2220 Project: Qpid Issue Type: Improvement Components: C++ Broker Affects Versions: 0.5 Reporter: Alan Conway Assignee: Alan Conway If every member of a persistent cluster crashes then manual intervention is required to identify which store is most up-to-date, so it can be used to recover. We need to provide tools to assist in this identification. The cluster can save a config-change counter with each config change (cluster membership change). In recovery, the broker with the highest config-change counter has the best store. However if the last brokers in the cluster crash so close together that none can record a config-change we need an additional decider. The store at http://qpidcomponents.org/download.html#persistence maintains a global Persistence ID, a 64 bit value that is incremented for each enqueue, dequeue. If the cluster stores (config-change,PID) pairs then in recovery we can use actual-PID - config-change PID as a tiebreaker. Proposed change to MessageStore API: /** Returns a monotonically increasing value reflecting changes to the store. * The value can wrap-around to 0. * Stores need not implement this function, they can simply return 0. */ uint64_t getChangeCounter(); The default implementation just returns 0 and the cluster must fall back to relying on config-change counts. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2360) declaring virtualhost level firewall configuration in virtualhosts.xml leads to NPE on startup
[ https://issues.apache.org/jira/browse/QPID-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Kennedy updated QPID-2360: - Attachment: (was: 0001-QPID-2630-QPID-2631-branch.patch) declaring virtualhost level firewall configuration in virtualhosts.xml leads to NPE on startup -- Key: QPID-2360 URL: https://issues.apache.org/jira/browse/QPID-2360 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.6 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.7 Attachments: 0001-QPID-2630-QPID-2631-trunk.patch Declaring virtualhost level firewall configuration in virtualhosts.xml leads to NPE on startup. After moving the same configuration into config.xml the broker then loads ok and the configuration works as expected. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2360) declaring virtualhost level firewall configuration in virtualhosts.xml leads to NPE on startup
[ https://issues.apache.org/jira/browse/QPID-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Kennedy updated QPID-2360: - Attachment: (was: 0001-QPID-2630-QPID-2631-trunk.patch) declaring virtualhost level firewall configuration in virtualhosts.xml leads to NPE on startup -- Key: QPID-2360 URL: https://issues.apache.org/jira/browse/QPID-2360 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.6 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.7 Declaring virtualhost level firewall configuration in virtualhosts.xml leads to NPE on startup. After moving the same configuration into config.xml the broker then loads ok and the configuration works as expected. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Rawhide compatibility patch
Hello! This little patch is vital to make current trunk (r928701) compile on Fedora Rawhide with Boost 1.41.0. As far as I recall, I was compiling with this patch cleanly on previous versions as well but I will verify the compilation on RHEL5 with this patch applied soon. The other line adds libpthread linking option. It works but you may want to add it elsewhere if you choose. Best regards, Ján fedora-release-14-0.4.noarch glibc-2.11.90-16.x86_64 gcc-4.4.3-13.fc14.x86_64 gcc-c++-4.4.3-13.fc14.x86_64 boost-1.41.0-7.fc13.x86_64 -- Red Hat Czech, MRG Quality Assurance Associate diff --git a/cpp/src/Makefile.am b/cpp/src/Makefile.am index 2256ca7..add15bb 100644 --- a/cpp/src/Makefile.am +++ b/cpp/src/Makefile.am @@ -314,6 +314,8 @@ EXTRA_DIST +=\ libqpidcommon_la_LIBADD = \ -lboost_program_options \ -lboost_filesystem \ + -lboost_system \ + -lpthread \ -luuid \ $(LIB_DLOPEN) \ $(LIB_CLOCK_GETTIME) - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Rawhide compatibility patch
On Mon, Mar 29, 2010 at 04:30:29PM +0200, Ján Sáreník wrote: This little patch is vital to make current trunk (r928701) compile on Fedora Rawhide with Boost 1.41.0. As far as I recall, I was compiling with this patch cleanly on previous versions as well but I will verify the compilation on RHEL5 with this patch applied soon. The other line adds libpthread linking option. It works but you may want to add it elsewhere if you choose. Oops, I will file a JIRA... - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-2473) current libraries: new options needed to link with
[ https://issues.apache.org/jira/browse/QPID-2473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Sarenik updated QPID-2473: -- Attachment: qpid-rawhide.diff current libraries: new options needed to link with -- Key: QPID-2473 URL: https://issues.apache.org/jira/browse/QPID-2473 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.7 Environment: Linux slanina.virtual 2.6.34-0.16.rc2.git0.fc14.x86_64 #1 SMP Tue Mar 23 02:02:52 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux fedora-release-14-0.4.noarch (Rawhide x86_64) glibc-2.11.90-16.x86_64 gcc-4.4.3-13.fc14.x86_64 gcc-c++-4.4.3-13.fc14.x86_64 boost-1.41.0-7.fc13.x86_64 Reporter: Jan Sarenik Assignee: Gordon Sim Attachments: qpid-rawhide.diff The little attached patch is vital to make current trunk (r928701) compile on Fedora Rawhide with Boost 1.41.0. The other line adds libpthread linking option. It works but you may want to add it elsewhere if you choose to do so. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Created: (QPID-2473) current libraries: new options needed to link with
current libraries: new options needed to link with -- Key: QPID-2473 URL: https://issues.apache.org/jira/browse/QPID-2473 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.7 Environment: Linux slanina.virtual 2.6.34-0.16.rc2.git0.fc14.x86_64 #1 SMP Tue Mar 23 02:02:52 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux fedora-release-14-0.4.noarch (Rawhide x86_64) glibc-2.11.90-16.x86_64 gcc-4.4.3-13.fc14.x86_64 gcc-c++-4.4.3-13.fc14.x86_64 boost-1.41.0-7.fc13.x86_64 Reporter: Jan Sarenik Assignee: Gordon Sim Attachments: qpid-rawhide.diff The little attached patch is vital to make current trunk (r928701) compile on Fedora Rawhide with Boost 1.41.0. The other line adds libpthread linking option. It works but you may want to add it elsewhere if you choose to do so. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Rawhide compatibility patch
I do have the same concern as Robbie. There were several incidents where changes were made in one and not the other. Now that there was ample time for all concerned to get a feel for both build systems, I believe it's time we get rid of one. Rajith On Mon, Mar 29, 2010 at 11:57 AM, Robbie Gemmell robbie.gemm...@gmail.com wrote: On 29 March 2010 14:56, Andrew Stitcher astitc...@redhat.com wrote: On Mon, 2010-03-29 at 16:30 +0200, Ján Sáreník wrote: snip Unfortunately the approach of unconditionally linking boost_system doesn't work for boost versions prior to 1.35 (or somewhere close to there) we already have some conditional logic in the cmake build to deal correctly with this, i must say I thought we already had this in the autotools build as well, but it becomes difficult to remember the details of 2 build systems. /snip Is there any plan to migrate and ease the burden of having 2 systems? It seems like a long time since the CMake system was added with that intent. Robbie - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/ - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
RE: Rawhide compatibility patch
-Original Message- From: Rajith Attapattu [mailto:rajit...@gmail.com] I do have the same concern as Robbie. There were several incidents where changes were made in one and not the other. Now that there was ample time for all concerned to get a feel for both build systems, I believe it's time we get rid of one. Right... As far as I know, the biggest impediment to moving ahead with Cmake is the Linux packaging; also I'm not sure what part autoconf plays in the mysterious Apache source release process. The daily builds are running fine, from what I see (I have a RHEL 5 daily). -Steve On Mon, Mar 29, 2010 at 11:57 AM, Robbie Gemmell robbie.gemm...@gmail.com wrote: On 29 March 2010 14:56, Andrew Stitcher astitc...@redhat.com wrote: On Mon, 2010-03-29 at 16:30 +0200, Ján Sáreník wrote: snip Unfortunately the approach of unconditionally linking boost_system doesn't work for boost versions prior to 1.35 (or somewhere close to there) we already have some conditional logic in the cmake build to deal correctly with this, i must say I thought we already had this in the autotools build as well, but it becomes difficult to remember the details of 2 build systems. /snip Is there any plan to migrate and ease the burden of having 2 systems? It seems like a long time since the CMake system was added with that intent. Robbie - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/ - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
RE: Access to qpidd original arg list from {platform specific}QpiddBroker.cpp ?
Looks nice, Kerry! I don't have many answers for you at this point, but one note... Use of event log There is already a logging option to put stuff in the windows event log. As a side note, if anyone has any other suggestions related to this or other service features, please let me know and I'll see if I can add it. The installer build is going to be checked in sometime soon. This builds a WiX-based installer; it may be nice to add the ability to install the broker as a service during the install. -Steve - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
