[
https://issues.apache.org/jira/browse/CASSANDRA-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971051#action_12971051
]
Eric Evans commented on CASSANDRA-1819:
---------------------------------------
Using another app to start Cassandra (using Cassandra's startup script no less)
sounds like too much of a corner-case to warrant inclusion. Even if it
weren't, the ability to specify an alternate Main-Class doesn't seem like much
of a generic solution.
I'm going to close this as Invalid. If you disagree, feel free to reopen and
we can take the discussion to a wider group.
> bin/cassandra is hardwired to run CassandraDaemon and in some instances it is
> necessary to run a custom "main"
> --------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-1819
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1819
> Project: Cassandra
> Issue Type: Improvement
> Components: Packaging
> Affects Versions: 0.7.0 rc 1
> Reporter: B. Todd Burruss
> Assignee: B. Todd Burruss
> Priority: Minor
> Fix For: 0.7.0
>
> Attachments: patch.txt
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> In my particular case we use Zabbix as a monitoring tool and it requires an
> agent to run in the JVM. so the solution is to start the agent, then call
> CassandraDaemon.main.
> my solution for a more generic "bin/cassandra" script is to check if a
> CLASSNAME is provided in the environment. if so use it, if not use the
> default CassandraDaemon.
> patch attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
