[ https://issues.apache.org/jira/browse/CASSANDRA-5652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686607#comment-13686607 ]
Sylvain Lebresne commented on CASSANDRA-5652: --------------------------------------------- lgtm, though provided jconsole can handle it, I'd replace the exception by something like: {noformat} new RuntimeException("Error starting native transport: " + e.getMessage(), e); {noformat} so we don't lose the original stack trace (but if it's still too hard to handle for JMX, let's just ship it as in you patch). > 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