You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2012/11/18 00:00:13 UTC
[jira] [Commented] (CASSANDRA-4893) Don't throw internal exceptions
over JMX
[ https://issues.apache.org/jira/browse/CASSANDRA-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499548#comment-13499548 ]
Jonathan Ellis commented on CASSANDRA-4893:
-------------------------------------------
I want to get rc1 out really, really badly. If you can expedite review of this [~nickmbailey] that would be great. Otherwise, we've waited this long, it won't kill us to push it to 1.3.
> Don't throw internal exceptions over JMX
> ----------------------------------------
>
> Key: CASSANDRA-4893
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4893
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.6, 1.2.0 beta 1
> Reporter: Nick Bailey
> Assignee: Yuki Morishita
> Fix For: 1.2.1
>
> Attachments: 0001-remove-cassandra-specific-exceptions-from-JMX-interf.patch
>
>
> Similarly to how we don't return internal objects over JMX we shouldn't throw internal exceptions over jmx as well.
> The one example I encountered was throwing ConfigurationException for the move() command. We should check the rest of our jmx as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira