0.18 release update - upcoming dates
Hi, folks. The time for 0.18 alpha is rapidly approaching, and beta soon after. I've adjusted the dates to allow a little more time for development, since this warning comes rather late. 0.18 alpha, 18 June Deadline for major features and disruptive changes 0.18 beta, 2 JulyWe branch for release, and 0.19 opens Contact me if there's something you'd like to get in for 0.18, and we can figure out where it fits. Thanks, Justin - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
intrusive_ptr::reset new?
There's currently a build error in qpid/broker/MessageDeque.cpp that boost::intrusive_ptr has no member reset() - is reset() a new feature? Google trolling suggests so… my error is happening on stock RHEL 5, which has Boost 1.33 -Steve - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-3902) Add formal message categories to C++ Broker log messages
[
https://issues.apache.org/jira/browse/QPID-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293211#comment-13293211
]
Rajith Attapattu commented on QPID-3902:
Instead of classifying categories by source dirs, can we not get each Header
file to define the category it wants to be logged under?
(The categories could be some sort of int index for fast comparing as Alan
suggested).
My suggestion on breaking the files under "broker" dir is not going to be
possible without something along the lines described above.
In the java world this seems to be used quite successfully.
> Add formal message categories to C++ Broker log messages
>
>
> Key: QPID-3902
> URL: https://issues.apache.org/jira/browse/QPID-3902
> Project: Qpid
> Issue Type: Improvement
>Reporter: Chuck Rolke
> Attachments: qpid-log-src-tabbed2.txt
>
>
> h3. This is a proposal to add log categories to C++ Broker log messages.
> h4. Problem Statement
> There are difficulties working with C++ Broker logging when appplying a log
> filter criterion. What precise FILTERTEXT can a user specify for:
> {noformat}
> --log-enable debug+:FILTERTEXT
> {noformat}
> Even after the fix from QPID-3891 it is not intuitive what to specify for a
> FILTERTEXT and any useful filter requires detailed knowledge of the source
> code.
> h4. Proposal
> A log category is a high-level classification of the nature of the logged
> event that is not tied to a particular source module or code function name.
> This log category would become the target for FILTERTEXT log filters.
> The following list is the proposed log category definition. Each log category
> name is followed by a list of source code directory names that would
> generally produce logs using that log category.
> ||Category||Source code directory||
> |Security|acl ssl gssapi sasl cyrus|
> |Broker | broker|
> |Management| agent console qmf|
> |Amqp|amqp_0_10 framing|
> |System| log sys types xml thread mutex fork pipe time ...|
> |HA| cluster ha replication|
> |Messaging| messaging client|
> |Store| store|
> |IO| tcp rdma AsynchIO socket epoll|
> |Test| |
> |Unspecified| |
> There is no strict rule that a module produce only log entries of a specific
> category.
> The category would be inserted into each log message after the time of day
> but before the message text.
> {noformat}
> 2012-03-06 16:55:38 [Management] SEND PackageInd
> package=org.apache.qpid.broker to=schema.package
> {noformat}
> A user could then filter log messages by using the category names:
> {noformat}
> --log-enable debug+:Management
> {noformat}
> This scheme would have a number of benefits:
> 1. On a per-message basis the filter comparisons would be using enumeration
> values and not strings.
> 2. The feature could be documented sensibly.
> 3. Log files would be easier to interpret manually or by event management
> systems.
> The classifications could be phased in gradually. The current
> QPID_LOG(LEVEL, MESSAGE) would produce [Unspecfied] events while the new
> QPID_LOG_CAT(LEVEL, CATEGORY, MESSAGE) would produce events using an actual
> category.
> Similar additions are made for the QPID_MSG entries.
--
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] [Comment Edited] (QPID-3902) Add formal message categories to C++ Broker log messages
[
https://issues.apache.org/jira/browse/QPID-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293205#comment-13293205
]
Rajith Attapattu edited comment on QPID-3902 at 6/12/12 12:07 AM:
--
(*) I echo Justin's comment about Network and Protocol instead of IO and AMQP.
(*) For Protocol we should really have something like
[Protocol][{PROTOCOL_NAME}-{VERSION}]... bcos we will mostly likely end up with
supporting multiple protocol versions in the same broker. So it will be very
useful to filter by a specific version. Ex. [Protocol][AMQP-0-10]
(*) I also think that BROKER is too broad a category to be really useful. A lot
of things are lumped in there. I'm not sure if the following is possible , but
if you can have more granular categories for BROKER it might be more useful.
Ex. QUEUEING -- for logs related in putting/pulling messages from queues, flow
control etc..
ROUTING -- logs related to routing messages (would be more relevant going
forward)
SUBSCRIPTION -- logs related to subscription state (capacity, acks ..etc)
(*) Another general category could be CONFIGURATION. Often times customers
wants to see logs to verify if they've got the config right. It's really a
separate category from any of the above. We currently don't have much here.
was (Author: rajith):
(*) I echo Justin's comment about Network and Protocol instead of IO and
AMQP.
(*) For Protocol we should really have something like [Protocol][AMQP-0-10]...
bcos we will mostly likely end up with supporting multiple protocol versions in
the same broker. So it will be very useful to filter by a specific version.
(*) I also think that BROKER is too broad a category to be really useful. A lot
of things are lumped in there. I'm not sure if the following is possible , but
if you can have more granular categories for BROKER it might be more useful.
Ex. QUEUEING -- for logs related in putting/pulling messages from queues, flow
control etc..
ROUTING -- logs related to routing messages (would be more relevant going
forward)
SUBSCRIPTION -- logs related to subscription state (capacity, acks ..etc)
(*) Another general category could be CONFIGURATION. Often times customers
wants to see logs to verify if they've got the config right. It's really a
separate category from any of the above. We currently don't have much here.
> Add formal message categories to C++ Broker log messages
>
>
> Key: QPID-3902
> URL: https://issues.apache.org/jira/browse/QPID-3902
> Project: Qpid
> Issue Type: Improvement
>Reporter: Chuck Rolke
> Attachments: qpid-log-src-tabbed2.txt
>
>
> h3. This is a proposal to add log categories to C++ Broker log messages.
> h4. Problem Statement
> There are difficulties working with C++ Broker logging when appplying a log
> filter criterion. What precise FILTERTEXT can a user specify for:
> {noformat}
> --log-enable debug+:FILTERTEXT
> {noformat}
> Even after the fix from QPID-3891 it is not intuitive what to specify for a
> FILTERTEXT and any useful filter requires detailed knowledge of the source
> code.
> h4. Proposal
> A log category is a high-level classification of the nature of the logged
> event that is not tied to a particular source module or code function name.
> This log category would become the target for FILTERTEXT log filters.
> The following list is the proposed log category definition. Each log category
> name is followed by a list of source code directory names that would
> generally produce logs using that log category.
> ||Category||Source code directory||
> |Security|acl ssl gssapi sasl cyrus|
> |Broker | broker|
> |Management| agent console qmf|
> |Amqp|amqp_0_10 framing|
> |System| log sys types xml thread mutex fork pipe time ...|
> |HA| cluster ha replication|
> |Messaging| messaging client|
> |Store| store|
> |IO| tcp rdma AsynchIO socket epoll|
> |Test| |
> |Unspecified| |
> There is no strict rule that a module produce only log entries of a specific
> category.
> The category would be inserted into each log message after the time of day
> but before the message text.
> {noformat}
> 2012-03-06 16:55:38 [Management] SEND PackageInd
> package=org.apache.qpid.broker to=schema.package
> {noformat}
> A user could then filter log messages by using the category names:
> {noformat}
> --log-enable debug+:Management
> {noformat}
> This scheme would have a number of benefits:
> 1. On a per-message basis the filter comparisons would be using enumeration
> values and not strings.
> 2. The feature could be documented sensibly.
> 3. Log files would be easier to interpret manually or by event management
> systems.
> The classifications could be phas
[jira] [Commented] (QPID-3902) Add formal message categories to C++ Broker log messages
[
https://issues.apache.org/jira/browse/QPID-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293205#comment-13293205
]
Rajith Attapattu commented on QPID-3902:
(*) I echo Justin's comment about Network and Protocol instead of IO and AMQP.
(*) For Protocol we should really have something like [Protocol][AMQP-0-10]...
bcos we will mostly likely end up with supporting multiple protocol versions in
the same broker. So it will be very useful to filter by a specific version.
(*) I also think that BROKER is too broad a category to be really useful. A lot
of things are lumped in there. I'm not sure if the following is possible , but
if you can have more granular categories for BROKER it might be more useful.
Ex. QUEUEING -- for logs related in putting/pulling messages from queues, flow
control etc..
ROUTING -- logs related to routing messages (would be more relevant going
forward)
SUBSCRIPTION -- logs related to subscription state (capacity, acks ..etc)
(*) Another general category could be CONFIGURATION. Often times customers
wants to see logs to verify if they've got the config right. It's really a
separate category from any of the above. We currently don't have much here.
> Add formal message categories to C++ Broker log messages
>
>
> Key: QPID-3902
> URL: https://issues.apache.org/jira/browse/QPID-3902
> Project: Qpid
> Issue Type: Improvement
>Reporter: Chuck Rolke
> Attachments: qpid-log-src-tabbed2.txt
>
>
> h3. This is a proposal to add log categories to C++ Broker log messages.
> h4. Problem Statement
> There are difficulties working with C++ Broker logging when appplying a log
> filter criterion. What precise FILTERTEXT can a user specify for:
> {noformat}
> --log-enable debug+:FILTERTEXT
> {noformat}
> Even after the fix from QPID-3891 it is not intuitive what to specify for a
> FILTERTEXT and any useful filter requires detailed knowledge of the source
> code.
> h4. Proposal
> A log category is a high-level classification of the nature of the logged
> event that is not tied to a particular source module or code function name.
> This log category would become the target for FILTERTEXT log filters.
> The following list is the proposed log category definition. Each log category
> name is followed by a list of source code directory names that would
> generally produce logs using that log category.
> ||Category||Source code directory||
> |Security|acl ssl gssapi sasl cyrus|
> |Broker | broker|
> |Management| agent console qmf|
> |Amqp|amqp_0_10 framing|
> |System| log sys types xml thread mutex fork pipe time ...|
> |HA| cluster ha replication|
> |Messaging| messaging client|
> |Store| store|
> |IO| tcp rdma AsynchIO socket epoll|
> |Test| |
> |Unspecified| |
> There is no strict rule that a module produce only log entries of a specific
> category.
> The category would be inserted into each log message after the time of day
> but before the message text.
> {noformat}
> 2012-03-06 16:55:38 [Management] SEND PackageInd
> package=org.apache.qpid.broker to=schema.package
> {noformat}
> A user could then filter log messages by using the category names:
> {noformat}
> --log-enable debug+:Management
> {noformat}
> This scheme would have a number of benefits:
> 1. On a per-message basis the filter comparisons would be using enumeration
> values and not strings.
> 2. The feature could be documented sensibly.
> 3. Log files would be easier to interpret manually or by event management
> systems.
> The classifications could be phased in gradually. The current
> QPID_LOG(LEVEL, MESSAGE) would produce [Unspecfied] events while the new
> QPID_LOG_CAT(LEVEL, CATEGORY, MESSAGE) would produce events using an actual
> category.
> Similar additions are made for the QPID_MSG entries.
--
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: FW: FAILED (b=50, w=18): qpid-cpp - trunk - Nightly
Ah, that's better. ./qpid/broker/TopicKeyNode.h:211: error: expected `;' before 'child' ./qpid/broker/TopicKeyNode.h:212: error: 'child' was not declared in this scope On Mon, 2012-06-11 at 14:55 -0500, Steve Huston wrote: > Did someone see build problems on Linux starting overnight? Same issues on > Windows as well. > > -Steve > > -Original Message- > From: CDash [mailto:cd...@riverace.com] > Sent: Sunday, June 10, 2012 9:13 PM > To: cd...@riverace.com > Subject: FAILED (b=50, w=18): qpid-cpp - trunk - Nightly > > A submission to CDash for the project qpid-cpp has build errors and build > warnings. > You have been identified as one of the authors who have checked in changes > that are part of this submission or you are listed in the default contact > list. > > Details on the submission can be found at > http://www.riverace.com/CDash-1.4.2/buildSummary.php?buildid=2010 > > Project: qpid-cpp > Site: Riverace: RHEL5 > Build Name: trunk > Build Time: 2012-06-10T21:01:22 EDT > Type: Nightly > Errors:50 > Warnings:18 > > > *Error* (first 5) > src/qpid/broker/TopicKeyNode.h line sourceline > (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010) > /.../cpp/src/qpid/broker/TopicKeyNode.h:169: error: type/value mismatch at > argument 2 in template parameter list for > ‘template (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010) > /.../cpp/src/qpid/broker/TopicKeyNode.h:169: error: expected a type, got > ‘qpid::broker::TopicKeyNode::shared_ptr’ > > src/qpid/broker/TopicKeyNode.h line sourceline > (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010) > /.../cpp/src/qpid/broker/TopicKeyNode.h:169: error: template argument 4 is > invalid > > src/qpid/broker/TopicKeyNode.h line sourceline > (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010) > /.../cpp/src/qpid/broker/TopicKeyNode.h:171: error: ISO C++ forbids > declaration of ‘shared_ptr’ with no type > > src/qpid/broker/TopicKeyNode.h line sourceline > (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010) > /.../cpp/src/qpid/broker/TopicKeyNode.h:171: error: extra qualification > ‘qpid::broker::TopicKeyNode::’ on member ‘shared_p > > > *Warnings* (first 5) > src/qpid/broker/TopicKeyNode.h line 211 > (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=1&buildid=2010) > /.../cpp/src/qpid/broker/TopicKeyNode.h:211: note: say ‘typename > qpid::broker::TopicKeyNode::shared_ptr’ if a type is meant > > cc1plus: warnings being treated as errors > > /.../cpp/src/qpid/broker/TopicKeyNode.h: At global scope: > /.../cpp/src/qpid/broker/TopicKeyNode.h: In instantiation of ‘bool > qpid::broker::TopicKeyNode::iterateMatchChildren(const > qpid::broker::TokenIteratorsrc/qpid/broker/TopicKeyNode.h line 337 > (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=1&buildid=2010) > /.../cpp/src/qpid/broker/TopicKeyNode.h:337: warning: unused parameter > ‘iter’ > > include/qpid/messaging/Duration.h line 53 > (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=1&buildid=2010) > /.../cpp/include/qpid/messaging/Duration.h:53: Warning(378): operator!= > ignored > > include/qmf/engine/ConnectionSettings.h line 110 > (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=1&buildid=2010) > /.../cpp/include/qmf/engine/ConnectionSettings.h:110: Warning(472): > Overloaded transportTcp(qmf::engine::ConnectionSettings *self > > -CDash on www.riverace.com > > > - > 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: FW: FAILED (b=50, w=18): qpid-cpp - trunk - Nightly
I just downloaded trunk and tried it when I saw your email. I did make -j8, and the compile did indeed fail, but I didn't feel like scrolling back to see where the failure was, so I then did "make", thinking to compile one file at a time to make the failure easier to see. ( I do this sometimes. ) But now it's not failing. < twilight zone music /> On Mon, 2012-06-11 at 14:55 -0500, Steve Huston wrote: > Did someone see build problems on Linux starting overnight? Same issues on > Windows as well. > > -Steve > > -Original Message- > From: CDash [mailto:cd...@riverace.com] > Sent: Sunday, June 10, 2012 9:13 PM > To: cd...@riverace.com > Subject: FAILED (b=50, w=18): qpid-cpp - trunk - Nightly > > A submission to CDash for the project qpid-cpp has build errors and build > warnings. > You have been identified as one of the authors who have checked in changes > that are part of this submission or you are listed in the default contact > list. > > Details on the submission can be found at > http://www.riverace.com/CDash-1.4.2/buildSummary.php?buildid=2010 > > Project: qpid-cpp > Site: Riverace: RHEL5 > Build Name: trunk > Build Time: 2012-06-10T21:01:22 EDT > Type: Nightly > Errors:50 > Warnings:18 > > > *Error* (first 5) > src/qpid/broker/TopicKeyNode.h line sourceline > (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010) > /.../cpp/src/qpid/broker/TopicKeyNode.h:169: error: type/value mismatch at > argument 2 in template parameter list for > ‘template (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010) > /.../cpp/src/qpid/broker/TopicKeyNode.h:169: error: expected a type, got > ‘qpid::broker::TopicKeyNode::shared_ptr’ > > src/qpid/broker/TopicKeyNode.h line sourceline > (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010) > /.../cpp/src/qpid/broker/TopicKeyNode.h:169: error: template argument 4 is > invalid > > src/qpid/broker/TopicKeyNode.h line sourceline > (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010) > /.../cpp/src/qpid/broker/TopicKeyNode.h:171: error: ISO C++ forbids > declaration of ‘shared_ptr’ with no type > > src/qpid/broker/TopicKeyNode.h line sourceline > (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010) > /.../cpp/src/qpid/broker/TopicKeyNode.h:171: error: extra qualification > ‘qpid::broker::TopicKeyNode::’ on member ‘shared_p > > > *Warnings* (first 5) > src/qpid/broker/TopicKeyNode.h line 211 > (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=1&buildid=2010) > /.../cpp/src/qpid/broker/TopicKeyNode.h:211: note: say ‘typename > qpid::broker::TopicKeyNode::shared_ptr’ if a type is meant > > cc1plus: warnings being treated as errors > > /.../cpp/src/qpid/broker/TopicKeyNode.h: At global scope: > /.../cpp/src/qpid/broker/TopicKeyNode.h: In instantiation of ‘bool > qpid::broker::TopicKeyNode::iterateMatchChildren(const > qpid::broker::TokenIteratorsrc/qpid/broker/TopicKeyNode.h line 337 > (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=1&buildid=2010) > /.../cpp/src/qpid/broker/TopicKeyNode.h:337: warning: unused parameter > ‘iter’ > > include/qpid/messaging/Duration.h line 53 > (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=1&buildid=2010) > /.../cpp/include/qpid/messaging/Duration.h:53: Warning(378): operator!= > ignored > > include/qmf/engine/ConnectionSettings.h line 110 > (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=1&buildid=2010) > /.../cpp/include/qmf/engine/ConnectionSettings.h:110: Warning(472): > Overloaded transportTcp(qmf::engine::ConnectionSettings *self > > -CDash on www.riverace.com > > > - > 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: FAILED (b=50, w=18): qpid-cpp - trunk - Nightly
Great - thanks for checking! > -Original Message- > From: Chuck Rolke [mailto:cro...@redhat.com] > Sent: Monday, June 11, 2012 4:08 PM > To: dev@qpid.apache.org > Subject: Re: FAILED (b=50, w=18): qpid-cpp - trunk - Nightly > > Ted fixed this with r1348926 today. > > - Original Message - > > From: "Steve Huston" > > To: dev@qpid.apache.org > > Sent: Monday, June 11, 2012 3:55:35 PM > > Subject: FW: FAILED (b=50, w=18): qpid-cpp - trunk - Nightly > > > > Did someone see build problems on Linux starting overnight? Same > > issues on Windows as well. > > > > -Steve > > > > -Original Message- > > From: CDash [mailto:cd...@riverace.com] > > Sent: Sunday, June 10, 2012 9:13 PM > > To: cd...@riverace.com > > Subject: FAILED (b=50, w=18): qpid-cpp - trunk - Nightly > > > > A submission to CDash for the project qpid-cpp has build errors and > > build warnings. > > You have been identified as one of the authors who have checked in > > changes that are part of this submission or you are listed in the > > default contact list. > > > > Details on the submission can be found at > > http://www.riverace.com/CDash-1.4.2/buildSummary.php?buildid=2010 > > > > Project: qpid-cpp > > Site: Riverace: RHEL5 > > Build Name: trunk > > Build Time: 2012-06-10T21:01:22 EDT > > Type: Nightly > > Errors:50 > > Warnings:18 > > > > > > *Error* (first 5) > > src/qpid/broker/TopicKeyNode.h line sourceline > > (http://www.riverace.com/CDash- > 1.4.2/viewBuildError.php?type=0&buildid > > =2010) > > /.../cpp/src/qpid/broker/TopicKeyNode.h:169: error: type/value > > mismatch at argument 2 in template parameter list for > > ‘template > (http://www.riverace.com/CDash- > 1.4.2/viewBuildError.php?type=0&buildid=2010) > > /.../cpp/src/qpid/broker/TopicKeyNode.h:169: error: expected a > > type, got > > ‘qpid::broker::TopicKeyNode::shared_ptr’ > > > > src/qpid/broker/TopicKeyNode.h line sourceline > > (http://www.riverace.com/CDash- > 1.4.2/viewBuildError.php?type=0&buildid > > =2010) > > /.../cpp/src/qpid/broker/TopicKeyNode.h:169: error: template argument > > 4 is > > invalid > > > > src/qpid/broker/TopicKeyNode.h line sourceline > > (http://www.riverace.com/CDash- > 1.4.2/viewBuildError.php?type=0&buildid > > =2010) > > /.../cpp/src/qpid/broker/TopicKeyNode.h:171: error: ISO C++ forbids > > declaration of ‘shared_ptr’ with no type > > > > src/qpid/broker/TopicKeyNode.h line sourceline > > (http://www.riverace.com/CDash- > 1.4.2/viewBuildError.php?type=0&buildid > > =2010) > > /.../cpp/src/qpid/broker/TopicKeyNode.h:171: error: extra > > qualification ‘qpid::broker::TopicKeyNode::’ on member > > ‘shared_p > > > > > > *Warnings* (first 5) > > src/qpid/broker/TopicKeyNode.h line 211 > > (http://www.riverace.com/CDash- > 1.4.2/viewBuildError.php?type=1&buildid > > =2010) > > /.../cpp/src/qpid/broker/TopicKeyNode.h:211: note: say ‘typename > > qpid::broker::TopicKeyNode::shared_ptr’ if a type is meant > > > > cc1plus: warnings being treated as errors > > > > /.../cpp/src/qpid/broker/TopicKeyNode.h: At global scope: > > /.../cpp/src/qpid/broker/TopicKeyNode.h: In instantiation of ‘bool > > qpid::broker::TopicKeyNode::iterateMatchChildren(const > > qpid::broker::TokenIteratorsrc/qpid/broker/TopicKeyNode.h line 337 > > (http://www.riverace.com/CDash- > 1.4.2/viewBuildError.php?type=1&buildid > > =2010) > > /.../cpp/src/qpid/broker/TopicKeyNode.h:337: warning: unused parameter > > ‘iter’ > > > > include/qpid/messaging/Duration.h line 53 > > (http://www.riverace.com/CDash- > 1.4.2/viewBuildError.php?type=1&buildid > > =2010) > > /.../cpp/include/qpid/messaging/Duration.h:53: Warning(378): > > operator!= > > ignored > > > > include/qmf/engine/ConnectionSettings.h line 110 > > (http://www.riverace.com/CDash- > 1.4.2/viewBuildError.php?type=1&buildid > > =2010) > > /.../cpp/include/qmf/engine/ConnectionSettings.h:110: Warning(472): > > Overloaded transportTcp(qmf::engine::ConnectionSettings *self > > > > -CDash on www.riverace.com > > > > > > - > > 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 - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: FAILED (b=50, w=18): qpid-cpp - trunk - Nightly
Ted fixed this with r1348926 today. - Original Message - > From: "Steve Huston" > To: dev@qpid.apache.org > Sent: Monday, June 11, 2012 3:55:35 PM > Subject: FW: FAILED (b=50, w=18): qpid-cpp - trunk - Nightly > > Did someone see build problems on Linux starting overnight? Same > issues on > Windows as well. > > -Steve > > -Original Message- > From: CDash [mailto:cd...@riverace.com] > Sent: Sunday, June 10, 2012 9:13 PM > To: cd...@riverace.com > Subject: FAILED (b=50, w=18): qpid-cpp - trunk - Nightly > > A submission to CDash for the project qpid-cpp has build errors and > build > warnings. > You have been identified as one of the authors who have checked in > changes > that are part of this submission or you are listed in the default > contact > list. > > Details on the submission can be found at > http://www.riverace.com/CDash-1.4.2/buildSummary.php?buildid=2010 > > Project: qpid-cpp > Site: Riverace: RHEL5 > Build Name: trunk > Build Time: 2012-06-10T21:01:22 EDT > Type: Nightly > Errors:50 > Warnings:18 > > > *Error* (first 5) > src/qpid/broker/TopicKeyNode.h line sourceline > (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010) > /.../cpp/src/qpid/broker/TopicKeyNode.h:169: error: type/value > mismatch at > argument 2 in template parameter list for > ‘template (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010) > /.../cpp/src/qpid/broker/TopicKeyNode.h:169: error: expected a > type, got > ‘qpid::broker::TopicKeyNode::shared_ptr’ > > src/qpid/broker/TopicKeyNode.h line sourceline > (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010) > /.../cpp/src/qpid/broker/TopicKeyNode.h:169: error: template argument > 4 is > invalid > > src/qpid/broker/TopicKeyNode.h line sourceline > (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010) > /.../cpp/src/qpid/broker/TopicKeyNode.h:171: error: ISO C++ forbids > declaration of ‘shared_ptr’ with no type > > src/qpid/broker/TopicKeyNode.h line sourceline > (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010) > /.../cpp/src/qpid/broker/TopicKeyNode.h:171: error: extra > qualification > ‘qpid::broker::TopicKeyNode::’ on member ‘shared_p > > > *Warnings* (first 5) > src/qpid/broker/TopicKeyNode.h line 211 > (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=1&buildid=2010) > /.../cpp/src/qpid/broker/TopicKeyNode.h:211: note: say ‘typename > qpid::broker::TopicKeyNode::shared_ptr’ if a type is meant > > cc1plus: warnings being treated as errors > > /.../cpp/src/qpid/broker/TopicKeyNode.h: At global scope: > /.../cpp/src/qpid/broker/TopicKeyNode.h: In instantiation of ‘bool > qpid::broker::TopicKeyNode::iterateMatchChildren(const > qpid::broker::TokenIteratorsrc/qpid/broker/TopicKeyNode.h line 337 > (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=1&buildid=2010) > /.../cpp/src/qpid/broker/TopicKeyNode.h:337: warning: unused > parameter > ‘iter’ > > include/qpid/messaging/Duration.h line 53 > (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=1&buildid=2010) > /.../cpp/include/qpid/messaging/Duration.h:53: Warning(378): > operator!= > ignored > > include/qmf/engine/ConnectionSettings.h line 110 > (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=1&buildid=2010) > /.../cpp/include/qmf/engine/ConnectionSettings.h:110: Warning(472): > Overloaded transportTcp(qmf::engine::ConnectionSettings *self > > -CDash on www.riverace.com > > > - > 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
[jira] [Commented] (QPID-3902) Add formal message categories to C++ Broker log messages
[
https://issues.apache.org/jira/browse/QPID-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293021#comment-13293021
]
Justin Ross commented on QPID-3902:
---
I have a slight preference for "Network" over "IO" and "Protocol" over "Amqp".
The former because it's slightly more descriptive, and the latter because it
identifies a general role as the other categories do.
> Add formal message categories to C++ Broker log messages
>
>
> Key: QPID-3902
> URL: https://issues.apache.org/jira/browse/QPID-3902
> Project: Qpid
> Issue Type: Improvement
>Reporter: Chuck Rolke
> Attachments: qpid-log-src-tabbed2.txt
>
>
> h3. This is a proposal to add log categories to C++ Broker log messages.
> h4. Problem Statement
> There are difficulties working with C++ Broker logging when appplying a log
> filter criterion. What precise FILTERTEXT can a user specify for:
> {noformat}
> --log-enable debug+:FILTERTEXT
> {noformat}
> Even after the fix from QPID-3891 it is not intuitive what to specify for a
> FILTERTEXT and any useful filter requires detailed knowledge of the source
> code.
> h4. Proposal
> A log category is a high-level classification of the nature of the logged
> event that is not tied to a particular source module or code function name.
> This log category would become the target for FILTERTEXT log filters.
> The following list is the proposed log category definition. Each log category
> name is followed by a list of source code directory names that would
> generally produce logs using that log category.
> ||Category||Source code directory||
> |Security|acl ssl gssapi sasl cyrus|
> |Broker | broker|
> |Management| agent console qmf|
> |Amqp|amqp_0_10 framing|
> |System| log sys types xml thread mutex fork pipe time ...|
> |HA| cluster ha replication|
> |Messaging| messaging client|
> |Store| store|
> |IO| tcp rdma AsynchIO socket epoll|
> |Test| |
> |Unspecified| |
> There is no strict rule that a module produce only log entries of a specific
> category.
> The category would be inserted into each log message after the time of day
> but before the message text.
> {noformat}
> 2012-03-06 16:55:38 [Management] SEND PackageInd
> package=org.apache.qpid.broker to=schema.package
> {noformat}
> A user could then filter log messages by using the category names:
> {noformat}
> --log-enable debug+:Management
> {noformat}
> This scheme would have a number of benefits:
> 1. On a per-message basis the filter comparisons would be using enumeration
> values and not strings.
> 2. The feature could be documented sensibly.
> 3. Log files would be easier to interpret manually or by event management
> systems.
> The classifications could be phased in gradually. The current
> QPID_LOG(LEVEL, MESSAGE) would produce [Unspecfied] events while the new
> QPID_LOG_CAT(LEVEL, CATEGORY, MESSAGE) would produce events using an actual
> category.
> Similar additions are made for the QPID_MSG entries.
--
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
FW: FAILED (b=50, w=18): qpid-cpp - trunk - Nightly
Did someone see build problems on Linux starting overnight? Same issues on Windows as well. -Steve -Original Message- From: CDash [mailto:cd...@riverace.com] Sent: Sunday, June 10, 2012 9:13 PM To: cd...@riverace.com Subject: FAILED (b=50, w=18): qpid-cpp - trunk - Nightly A submission to CDash for the project qpid-cpp has build errors and build warnings. You have been identified as one of the authors who have checked in changes that are part of this submission or you are listed in the default contact list. Details on the submission can be found at http://www.riverace.com/CDash-1.4.2/buildSummary.php?buildid=2010 Project: qpid-cpp Site: Riverace: RHEL5 Build Name: trunk Build Time: 2012-06-10T21:01:22 EDT Type: Nightly Errors:50 Warnings:18 *Error* (first 5) src/qpid/broker/TopicKeyNode.h line sourceline (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010) /.../cpp/src/qpid/broker/TopicKeyNode.h:169: error: type/value mismatch at argument 2 in template parameter list for ‘templatehttp://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010) /.../cpp/src/qpid/broker/TopicKeyNode.h:169: error: expected a type, got ‘qpid::broker::TopicKeyNode::shared_ptr’ src/qpid/broker/TopicKeyNode.h line sourceline (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010) /.../cpp/src/qpid/broker/TopicKeyNode.h:169: error: template argument 4 is invalid src/qpid/broker/TopicKeyNode.h line sourceline (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010) /.../cpp/src/qpid/broker/TopicKeyNode.h:171: error: ISO C++ forbids declaration of ‘shared_ptr’ with no type src/qpid/broker/TopicKeyNode.h line sourceline (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010) /.../cpp/src/qpid/broker/TopicKeyNode.h:171: error: extra qualification ‘qpid::broker::TopicKeyNode::’ on member ‘shared_p *Warnings* (first 5) src/qpid/broker/TopicKeyNode.h line 211 (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=1&buildid=2010) /.../cpp/src/qpid/broker/TopicKeyNode.h:211: note: say ‘typename qpid::broker::TopicKeyNode::shared_ptr’ if a type is meant cc1plus: warnings being treated as errors /.../cpp/src/qpid/broker/TopicKeyNode.h: At global scope: /.../cpp/src/qpid/broker/TopicKeyNode.h: In instantiation of ‘bool qpid::broker::TopicKeyNode::iterateMatchChildren(const qpid::broker::TokenIteratorsrc/qpid/broker/TopicKeyNode.h line 337 (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=1&buildid=2010) /.../cpp/src/qpid/broker/TopicKeyNode.h:337: warning: unused parameter ‘iter’ include/qpid/messaging/Duration.h line 53 (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=1&buildid=2010) /.../cpp/include/qpid/messaging/Duration.h:53: Warning(378): operator!= ignored include/qmf/engine/ConnectionSettings.h line 110 (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=1&buildid=2010) /.../cpp/include/qmf/engine/ConnectionSettings.h:110: Warning(472): Overloaded transportTcp(qmf::engine::ConnectionSettings *self -CDash on www.riverace.com - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-4054) C++ Broker connection limits require better granularity
Chuck Rolke created QPID-4054: - Summary: C++ Broker connection limits require better granularity Key: QPID-4054 URL: https://issues.apache.org/jira/browse/QPID-4054 Project: Qpid Issue Type: Improvement Components: C++ Broker Affects Versions: 0.16 Reporter: Chuck Rolke Assignee: Chuck Rolke A single command line switch sets the connection limit value for all users. Typical customers require different limits for different users. This issue tracks moving the user limit specification to the ACL file. -- 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-4053) Performance Test Framework: QueueDelete can timeout if test ends when too many unprocessed messages remain on test queue
Keith Wall created QPID-4053:
Summary: Performance Test Framework: QueueDelete can timeout if
test ends when too many unprocessed messages remain on test queue
Key: QPID-4053
URL: https://issues.apache.org/jira/browse/QPID-4053
Project: Qpid
Issue Type: Bug
Components: Java Performance Tests
Affects Versions: 0.17
Reporter: Keith Wall
There is a problem in the new Performance Test Framework. If a test utilising
the maxiumumDuration feature completes with too many messages left on a queue
(as would be the case where number of producers out-number consumers), the
QueueDelete command issued by the framework can apparently fail owing to a
timeout exception. The command does in fact complete successfully server side,
it is just the client gives up awaiting the response. This can cause a
spurious test failure.
I see this with VaryingNumberOfParticipants.json when maximumDuration is set to
100seconds.
{code}
org.apache.qpid.AMQTimeoutException: Server did not respond in a timely fashion
[error code 408: Request Timeout]
at
org.apache.qpid.client.util.BlockingWaiter.block(BlockingWaiter.java:177)
at
org.apache.qpid.client.protocol.BlockingMethodFrameListener.blockForFrame(BlockingMethodFrameListener.java:122)
at
org.apache.qpid.client.protocol.AMQProtocolHandler.writeCommandFrameAndWaitForReply(AMQProtocolHandler.java:656)
at
org.apache.qpid.client.protocol.AMQProtocolHandler.syncWrite(AMQProtocolHandler.java:677)
at
org.apache.qpid.client.protocol.AMQProtocolHandler.syncWrite(AMQProtocolHandler.java:671)
at
org.apache.qpid.client.AMQSession_0_8.sendQueueDelete(AMQSession_0_8.java:429)
at
org.apache.qpid.disttest.jms.QpidQueueCreator.deleteQueue(QpidQueueCreator.java:88)
at
org.apache.qpid.disttest.jms.QpidQueueCreator.deleteQueues(QpidQueueCreator.java:55)
at
org.apache.qpid.disttest.jms.ControllerJmsDelegate.deleteQueues(ControllerJmsDelegate.java:198)
at
org.apache.qpid.disttest.controller.TestRunner.deleteQueues(TestRunner.java:232)
at
org.apache.qpid.disttest.controller.TestRunner.runParts(TestRunner.java:139)
at
org.apache.qpid.disttest.controller.TestRunner.run(TestRunner.java:103)
at
org.apache.qpid.disttest.controller.Controller.runAllTests(Controller.java:172)
at
org.apache.qpid.disttest.ControllerRunner.runTest(ControllerRunner.java:120)
at
org.apache.qpid.disttest.ControllerRunner.runTests(ControllerRunner.java:105)
at
org.apache.qpid.disttest.ControllerRunner.runController(ControllerRunner.java:80)
at
org.apache.qpid.disttest.ControllerRunner.main(ControllerRunner.java:69)
{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.org
[jira] [Created] (QPID-4052) HAClusterTwoNodeTest.testSecondaryDesignatedAsPrimaryAfterOrginalPrimaryStopped occasionally fails on Apache CI
Keith Wall created QPID-4052:
Summary:
HAClusterTwoNodeTest.testSecondaryDesignatedAsPrimaryAfterOrginalPrimaryStopped
occasionally fails on Apache CI
Key: QPID-4052
URL: https://issues.apache.org/jira/browse/QPID-4052
Project: Qpid
Issue Type: Bug
Components: Java Broker BDB Store, Java Tests
Affects Versions: 0.17
Reporter: Keith Wall
Assignee: Keith Wall
Fix For: 0.17
New HA test is showing occasionally failures on Apache CI e.g. builds 297 and
298.
https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-BDB-TestMatrix/297/jdk=JDK%201.6%20%28latest%29,label=Ubuntu,profile=java-bdb.0-10/testReport/junit/org.apache.qpid.server.store.berkeleydb/HAClusterTwoNodeTest/testSecondaryDesignatedAsPrimaryAfterOrginalPrimaryStopped/
https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-BDB-TestMatrix/298/jdk=JDK%201.6%20%28latest%29,label=Ubuntu,profile=java-bdb.0-10/testReport/org.apache.qpid.server.store.berkeleydb/HAClusterTwoNodeTest/testSecondaryDesignatedAsPrimaryAfterOrginalPrimaryStopped/
{code}
javax.jms.JMSException: Error creating connection: Connection refused
at
org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:159)
at
org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:134)
at
org.apache.qpid.test.utils.QpidBrokerTestCase.getConnection(QpidBrokerTestCase.java:1038)
at
org.apache.qpid.server.store.berkeleydb.HAClusterTwoNodeTest.testSecondaryDesignatedAsPrimaryAfterOrginalPrimaryStopped(HAClusterTwoNodeTest.java:189)
at
org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:237)
at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:139)
Caused by: org.apache.qpid.AMQConnectionFailureException: Connection refused
at org.apache.qpid.client.AMQConnection.(AMQConnection.java:444)
at
org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:155)
Caused by: org.apache.qpid.transport.TransportException: Error connecting to
broker
at
org.apache.qpid.transport.network.io.IoNetworkTransport.connect(IoNetworkTransport.java:82)
at org.apache.qpid.transport.Connection.connect(Connection.java:235)
at
org.apache.qpid.client.AMQConnectionDelegate_0_10.makeBrokerConnection(AMQConnectionDelegate_0_10.java:219)
at
org.apache.qpid.client.AMQConnection.makeBrokerConnection(AMQConnection.java:588)
at org.apache.qpid.client.AMQConnection.(AMQConnection.java:367)
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)
at
org.apache.qpid.transport.network.io.IoNetworkTransport.connect(IoNetworkTransport.java:78)
{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.org
