cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brosius (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5652) Suppress custom exceptions thru jmx
Date Tue, 18 Jun 2013 20:54:21 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-5652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687175#comment-13687175
] 

Dave Brosius commented on CASSANDRA-5652:
-----------------------------------------

really, imo mbeans should be seperate objects that impl the interface and just call into the
real objects, so that these mbean objects can do the exception sanitization stuff (and other
cleaning) outside of real code. but, probably just being pendantic.
                
> Suppress custom exceptions thru jmx
> -----------------------------------
>
>                 Key: CASSANDRA-5652
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5652
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 1.2.5
>            Reporter: Dave Brosius
>            Assignee: Dave Brosius
>            Priority: Trivial
>             Fix For: 1.2.6
>
>         Attachments: 5652.txt
>
>
> startNativeTransport, can send back 
> org.jboss.netty.channel.ChannelException
> which causes jconsole to puke with a bad message such as
> Problem invoking startNativeTransport: java.rmi.UnmarshalException: Error unmarshaling
return header; nested exception is: java.io.EOFException
> convert to RuntimeException so you get something like:
> org.jboss.netty.channel.ChannelException: Failed to bind to: localhost/127.0.0.1:9042

--
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

Mime
View raw message