[
https://issues.apache.org/jira/browse/CASSANDRA-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jackson Chung updated CASSANDRA-2808:
-------------------------------------
Attachment: 2808.patch
patch based on trunk
> add java vendor/versoin to cassandra startup logging
> ----------------------------------------------------
>
> Key: CASSANDRA-2808
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2808
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jackson Chung
> Priority: Minor
> Attachments: 2808.patch
>
>
> currently to determine which exact java is being used by the CassandraDaemon
> jvm could be difficult. Some may have use rpm/deb java package, other may
> have used tarbar and set JAVA_HOME, PATH, etc etc.
> It "could be" done, but may take some iteration to get the true answer if
> one's setup is complicated (user is root/cassandra and contains difference
> env settings between cassandra startup user vs the login user)
> It would be very helpful to have this information simply logged in the log
> file, right at the beginning. This helps identifying the java type/version
> quickly without much operation overhead, and easily done in 1-liner:
> logger.info("Java vendor/version: {}/{}", System.getProperty("java.vm.name"),
> System.getProperty("java.version") );
> In OpenJDK java, you will something similar to:
> INFO [main] 2011-06-22 07:08:16,610 AbstractCassandraDaemon.java (line 95)
> Java vendor/version: OpenJDK 64-Bit Server VM/1.6.0_20
> In Java(TM), you will get something like:
> INFO [main] 2011-06-22 00:15:34,936 AbstractCassandraDaemon.java (line 96)
> Java vendor/version: Java HotSpot(TM) 64-Bit Server VM/1.6.0_24
> this little edition will go a long way.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
