Re: Eclipse project files for Java code

2011-01-12 Thread Marnie McCormack
I think Martin's suggestion to have a pom for project file generation is a great one ! Regards, Marnie On Mon, Jan 10, 2011 at 2:12 AM, Martin Ritchie ritch...@apache.org wrote: On 4 January 2011 18:07, Robert Godfrey rob.j.godf...@gmail.com wrote: On 4 January 2011 16:59, Andrew Kennedy

[jira] Resolved: (QPID-2991) Add message counts for both directions to connection stats

2011-01-12 Thread Gordon Sim (JIRA)
[ https://issues.apache.org/jira/browse/QPID-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-2991. -- Resolution: Fixed Add message counts for both directions to connection stats

[jira] Created: (QPID-2996) qmf/SchemaMethod.cpp fails to compile on s390

2011-01-12 Thread JIRA
qmf/SchemaMethod.cpp fails to compile on s390 - Key: QPID-2996 URL: https://issues.apache.org/jira/browse/QPID-2996 Project: Qpid Issue Type: Bug Components: C++ Broker Affects

[jira] Commented: (QPID-2996) qmf/SchemaMethod.cpp fails to compile on s390

2011-01-12 Thread JIRA
[ https://issues.apache.org/jira/browse/QPID-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12980723#action_12980723 ] Dan Horák commented on QPID-2996: - happens when building for the s390 architecture (32-bit)

[jira] Commented: (QPID-2982) Inconsistent management messages in a cluster

2011-01-12 Thread Alan Conway (JIRA)
[ https://issues.apache.org/jira/browse/QPID-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12980848#action_12980848 ] Alan Conway commented on QPID-2982: --- I am able to reproduce this, thanks. I'm

QIP proposal: Easy Broker Info

2011-01-12 Thread mick
Index Easy Broker Info Service Status Draft Summary Brokers write simple name-value pairs, one to a line, into PID files in /var/run/qpid. The names are tree-structured. Files are updated periodically, and taken down when broker shuts down normally. This

Re: QIP proposal: Easy Broker Info

2011-01-12 Thread Justin Ross
On Wed, 12 Jan 2011, mick wrote: I like this proposal. It combines low ambition and high utility, a good combination! From a QIP standpoint, however, I think the utility part needs more explanation. It's not hard for me to imagine uses of this, but it ought to be explicit. Testing in

Re: QIP proposal: Easy Broker Info

2011-01-12 Thread Andrew Stitcher
On Wed, 2011-01-12 at 15:31 -0500, Justin Ross wrote: ... Summary Brokers write simple name-value pairs, one to a line, into PID files in /var/run/qpid. The names are tree-structured. Files are updated periodically, and taken down when broker shuts down

Re: QIP proposal: Easy Broker Info

2011-01-12 Thread Rajith Attapattu
Sorry for discussing something slightly off topic, but I thought it might be worth mentioning it here. There was an idea floating around (I believe it was Rafi who initiated it) about having live and passive backups for a broker. The current clustering solution in 'some ways' provide the live

JMS Coding Style and More (Fwd: ACTION-234 complete)

2011-01-12 Thread Andrew Kennedy
All, This is in relation to the implementation of a change [1] I requested in the latest draft of the W3C's SOAP-JMS spec. However I still think the fixed, and now working, example JMS code [2] is flawed, or at best misleading. Would anyone with strong JMS-coding-style opinions care to

Re: QIP proposal: Easy Broker Info

2011-01-12 Thread Andrew Kennedy
On 12 Jan 2011, at 19:43, mick wrote: Solution Brokers write information about themselves to files in a well-known directory ( i.e. /var/run/qpid ). This allows any running program or script to easily discover what brokers are running, what ports they are