[jira] Assigned: (QPID-1694) jmx console saves its settings ini file direcly in the user home directory
[ https://issues.apache.org/jira/browse/QPID-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Gemmell reassigned QPID-1694: Assignee: Martin Ritchie (was: Robert Gemmell) Hi Martin, can you review this change please, thanks. > jmx console saves its settings ini file direcly in the user home directory > -- > > Key: QPID-1694 > URL: https://issues.apache.org/jira/browse/QPID-1694 > Project: Qpid > Issue Type: Bug > Components: Java Management : JMX Console >Affects Versions: M2.1, M3, M4 >Reporter: Robert Gemmell >Assignee: Martin Ritchie >Priority: Minor > Fix For: Eclipse MC M5 > > > The jmx management console saves an ini file to retain users customised > navigation settings, however it does so directly in the user home directory. > This is a bit ugly and at the very least should be moved into a hidden > subdirectory. -- 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-1694) jmx console saves its settings ini file direcly in the user home directory
[ https://issues.apache.org/jira/browse/QPID-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Gemmell updated QPID-1694: - Status: Ready To Review (was: In Progress) > jmx console saves its settings ini file direcly in the user home directory > -- > > Key: QPID-1694 > URL: https://issues.apache.org/jira/browse/QPID-1694 > Project: Qpid > Issue Type: Bug > Components: Java Management : JMX Console >Affects Versions: M2.1, M3, M4 >Reporter: Robert Gemmell >Assignee: Robert Gemmell >Priority: Minor > Fix For: Eclipse MC M5 > > > The jmx management console saves an ini file to retain users customised > navigation settings, however it does so directly in the user home directory. > This is a bit ugly and at the very least should be moved into a hidden > subdirectory. -- 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-1648) Enable live reconfiguration of Log4J settings for the Java broker via JMX
[ https://issues.apache.org/jira/browse/QPID-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Gemmell reassigned QPID-1648: Assignee: Martin Ritchie (was: Robert Gemmell) Hi Martin, Aidan already committed this patch for me previously but could you review it please, thanks. > Enable live reconfiguration of Log4J settings for the Java broker via JMX > - > > Key: QPID-1648 > URL: https://issues.apache.org/jira/browse/QPID-1648 > Project: Qpid > Issue Type: New Feature > Components: Java Broker, Java Management : JMX Console >Reporter: Robert Gemmell >Assignee: Martin Ritchie > Fix For: Eclipse MC M5 > > Attachments: log4j_config_changes.patch, QPID-1648_24feb2009.patch > > > It would be useful to be able to update the Log4J settings for a running Java > broker via JMX, incase it was desirable to adjust logging to investigate an > issue which became apparent after startup. > Whilst Log4J supports monitoring its own configuration file for updates, the > broker must be started with this enabled for it to be of any use, and > updating the settings by manually modifying the xml file runs the risk of > accidentally rendering the file invalid, which could lead to serious issues > when the update is detected and applied by Log4j. > In order to address these issues, adding the ability to to update the > settings via JMX would allow users to be able to adjust the Log4J settings in > 2 ways: by modifying the xml file programatically rather than by hand, or by > modifying the Log4J runtime settings directly, allowing (temporary) updates > even where Log4J has not been instructed to monitor its configuration file > for change. -- 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-1511) JMX Interface does not require authentication
[ https://issues.apache.org/jira/browse/QPID-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Gemmell reassigned QPID-1511: Assignee: Robert Gemmell > JMX Interface does not require authentication > - > > Key: QPID-1511 > URL: https://issues.apache.org/jira/browse/QPID-1511 > Project: Qpid > Issue Type: Improvement > Components: Java Broker, Java Management : JMX Console >Reporter: Martin Ritchie >Assignee: Robert Gemmell > Fix For: Eclipse MC M5 > > Attachments: create_example_ssl_certstores.sh, > QPID-1511_29jan2009.patch > > > Summary: > JMX Interface uses the default RMI connector which has no authentication > mechanism. We should not be shipping a JMX interface that doesn't have > authentication. The interface has been disabled by default for M4 but this > should be modified based on the outcome of the discussion on qpid-dev to > authenticate all connections. -- 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-1511) JMX Interface does not require authentication
[ https://issues.apache.org/jira/browse/QPID-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Gemmell updated QPID-1511: - Status: Ready To Review (was: In Progress) > JMX Interface does not require authentication > - > > Key: QPID-1511 > URL: https://issues.apache.org/jira/browse/QPID-1511 > Project: Qpid > Issue Type: Improvement > Components: Java Broker, Java Management : JMX Console >Reporter: Martin Ritchie >Assignee: Robert Gemmell > Fix For: Eclipse MC M5 > > Attachments: create_example_ssl_certstores.sh, > QPID-1511_29jan2009.patch > > > Summary: > JMX Interface uses the default RMI connector which has no authentication > mechanism. We should not be shipping a JMX interface that doesn't have > authentication. The interface has been disabled by default for M4 but this > should be modified based on the outcome of the discussion on qpid-dev to > authenticate all connections. -- 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-1511) JMX Interface does not require authentication
[ https://issues.apache.org/jira/browse/QPID-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Gemmell reassigned QPID-1511: Assignee: Martin Ritchie (was: Robert Gemmell) Hi Martin, Aidan already committed this patch for me previously but could you review it please, thanks. > JMX Interface does not require authentication > - > > Key: QPID-1511 > URL: https://issues.apache.org/jira/browse/QPID-1511 > Project: Qpid > Issue Type: Improvement > Components: Java Broker, Java Management : JMX Console >Reporter: Martin Ritchie >Assignee: Martin Ritchie > Fix For: Eclipse MC M5 > > Attachments: create_example_ssl_certstores.sh, > QPID-1511_29jan2009.patch > > > Summary: > JMX Interface uses the default RMI connector which has no authentication > mechanism. We should not be shipping a JMX interface that doesn't have > authentication. The interface has been disabled by default for M4 but this > should be modified based on the outcome of the discussion on qpid-dev to > authenticate all connections. -- 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-1648) Enable live reconfiguration of Log4J settings for the Java broker via JMX
[ https://issues.apache.org/jira/browse/QPID-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Gemmell reassigned QPID-1648: Assignee: Robert Gemmell > Enable live reconfiguration of Log4J settings for the Java broker via JMX > - > > Key: QPID-1648 > URL: https://issues.apache.org/jira/browse/QPID-1648 > Project: Qpid > Issue Type: New Feature > Components: Java Broker, Java Management : JMX Console >Reporter: Robert Gemmell >Assignee: Robert Gemmell > Fix For: Eclipse MC M5 > > Attachments: log4j_config_changes.patch, QPID-1648_24feb2009.patch > > > It would be useful to be able to update the Log4J settings for a running Java > broker via JMX, incase it was desirable to adjust logging to investigate an > issue which became apparent after startup. > Whilst Log4J supports monitoring its own configuration file for updates, the > broker must be started with this enabled for it to be of any use, and > updating the settings by manually modifying the xml file runs the risk of > accidentally rendering the file invalid, which could lead to serious issues > when the update is detected and applied by Log4j. > In order to address these issues, adding the ability to to update the > settings via JMX would allow users to be able to adjust the Log4J settings in > 2 ways: by modifying the xml file programatically rather than by hand, or by > modifying the Log4J runtime settings directly, allowing (temporary) updates > even where Log4J has not been instructed to monitor its configuration file > for change. -- 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-1648) Enable live reconfiguration of Log4J settings for the Java broker via JMX
[ https://issues.apache.org/jira/browse/QPID-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Gemmell updated QPID-1648: - Status: Ready To Review (was: In Progress) > Enable live reconfiguration of Log4J settings for the Java broker via JMX > - > > Key: QPID-1648 > URL: https://issues.apache.org/jira/browse/QPID-1648 > Project: Qpid > Issue Type: New Feature > Components: Java Broker, Java Management : JMX Console >Reporter: Robert Gemmell >Assignee: Robert Gemmell > Fix For: Eclipse MC M5 > > Attachments: log4j_config_changes.patch, QPID-1648_24feb2009.patch > > > It would be useful to be able to update the Log4J settings for a running Java > broker via JMX, incase it was desirable to adjust logging to investigate an > issue which became apparent after startup. > Whilst Log4J supports monitoring its own configuration file for updates, the > broker must be started with this enabled for it to be of any use, and > updating the settings by manually modifying the xml file runs the risk of > accidentally rendering the file invalid, which could lead to serious issues > when the update is detected and applied by Log4j. > In order to address these issues, adding the ability to to update the > settings via JMX would allow users to be able to adjust the Log4J settings in > 2 ways: by modifying the xml file programatically rather than by hand, or by > modifying the Log4J runtime settings directly, allowing (temporary) updates > even where Log4J has not been instructed to monitor its configuration file > for change. -- 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-1738) MbeanType view does not adequately indicate button functionality
[ https://issues.apache.org/jira/browse/QPID-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Gemmell reassigned QPID-1738: Assignee: Martin Ritchie (was: Robert Gemmell) Hi Martin, can you review this change please, thanks. > MbeanType view does not adequately indicate button functionality > > > Key: QPID-1738 > URL: https://issues.apache.org/jira/browse/QPID-1738 > Project: Qpid > Issue Type: Bug > Components: Java Management : JMX Console >Affects Versions: M2.1, M3, M4 >Reporter: Robert Gemmell >Assignee: Martin Ritchie >Priority: Minor > Fix For: Eclipse MC M5 > > > The MbeanType view does not adequately indicate its buttons functionality, > leaving users uncertain what they should do. The can be made more clear by > updating the text to indicate the button's purpose. -- 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-1738) MbeanType view does not adequately indicate button functionality
[ https://issues.apache.org/jira/browse/QPID-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Gemmell updated QPID-1738: - Status: Ready To Review (was: In Progress) > MbeanType view does not adequately indicate button functionality > > > Key: QPID-1738 > URL: https://issues.apache.org/jira/browse/QPID-1738 > Project: Qpid > Issue Type: Bug > Components: Java Management : JMX Console >Affects Versions: M2.1, M3, M4 >Reporter: Robert Gemmell >Assignee: Robert Gemmell >Priority: Minor > Fix For: Eclipse MC M5 > > > The MbeanType view does not adequately indicate its buttons functionality, > leaving users uncertain what they should do. The can be made more clear by > updating the text to indicate the button's purpose. -- 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-1738) MbeanType view does not adequately indicate button functionality
MbeanType view does not adequately indicate button functionality Key: QPID-1738 URL: https://issues.apache.org/jira/browse/QPID-1738 Project: Qpid Issue Type: Bug Components: Java Management : JMX Console Affects Versions: M4, M3, M2.1 Reporter: Robert Gemmell Assignee: Robert Gemmell Priority: Minor Fix For: Eclipse MC M5 The MbeanType view does not adequately indicate its buttons functionality, leaving users uncertain what they should do. The can be made more clear by updating the text to indicate the button's purpose. -- 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
Build failure for C++ tests with VC2008 and Boost 1.38
Where to Jira?
I see:
ClientSessionTest.cpp
.\ClientSessionTest.cpp(149) : error C2447: '{' : missing function
header (old-style formal list?)
.\ClientSessionTest.cpp(170) : error C2447: '{' : missing function
header (old-style formal list?)
I'm using VS2008 with Boost 1.38, QPID_AUTO_TEST_CASE_EXPECTED_FAILURES
expands to BOOST_AUTO_TEST_CASE_EXPECTED_FAILURES, but that doesn't seem
to expand to something that ends with the start of a function definition.
Rather it expands to:
struct testSuspend0Timeout_id; static struct
testSuspend0Timeout_exp_fail_num_spec : boost::unit_test::ut_detail::
auto_tc_exp_fail {
testSuspend0Timeout_exp_fail_num_spec() : boost::unit_test::ut_detail::
auto_tc_exp_fail( 1 ) {} }
testSuspend0Timeout_exp_fail_num_spec_inst;
{
ClientSessionFixture fix;
fix.session.suspend();
I don't have older boost versions installed - is this a boost change?
James
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
