Deep has exactly put his finger on the nail. The reason we disallow JMX from Stratos is for security reasons. So the workaround is to create a *properly secured* admin service that runs locally, exposes the JMX with the right multi-tenant security controls, and can be called remotely.
Paul On 3 July 2012 11:27, Deependra Ariyadewa <[email protected]> wrote: > > > On Fri, Jun 29, 2012 at 5:12 PM, Harsha Kumara <[email protected]> wrote: > >> Hi! >> >> I have a requirement to monitor and manage cassandra cluster.Cassandra >> offer JMX support.I able to get mBean server connection for local running >> instance via ManagementFactory.getPlatformMBeanServer().But I need to >> connect external cassandra cluster node to perform operations.For a JMX >> disabled carbon deployment,I won't be able to connect external cassandra >> cluster node.Is there's any alternatives which can overcome this problem? >> > > In a normal deployment we my not deploy the admin UI in the nodes running > Cassandra service. Best practice is to monitor the Cassandra cluster from > outside. > > If devops decide to close JMX ports in the deployment there will be no > method to manage the Cassandra cluster. Therefore it is always good to > implement management function through web services. > > Thanks, > > Deependra. > > > >> Thanks. >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Deependra Ariyadewa > WSO2, Inc. http://wso2.com/ http://wso2.org > > email [email protected]; cell +94 71 403 5996 ; > Blog http://risenfall.wordpress.com/ > PGP info: KeyID: 'DC627E6F' > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo [email protected] wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions.
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
