You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jackson Chung (JIRA)" <ji...@apache.org> on 2011/06/22 09:17:47 UTC
[jira] [Created] (CASSANDRA-2808) add java vendor/versoin to
cassandra startup logging
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
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
[jira] [Updated] (CASSANDRA-2808) add java vendor/versoin to
cassandra startup logging
Posted by "Jackson Chung (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Resolved] (CASSANDRA-2808) add java vendor/versoin to
cassandra startup logging
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-2808.
---------------------------------------
Resolution: Fixed
Fix Version/s: 0.8.2
Reviewer: jbellis
Assignee: Jackson Chung
committed
> 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
> Assignee: Jackson Chung
> Priority: Minor
> Fix For: 0.8.2
>
> 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
[jira] [Commented] (CASSANDRA-2808) add java vendor/versoin to
cassandra startup logging
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053582#comment-13053582 ]
Hudson commented on CASSANDRA-2808:
-----------------------------------
Integrated in Cassandra-0.8 #185 (See [https://builds.apache.org/job/Cassandra-0.8/185/])
> 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
> Assignee: Jackson Chung
> Priority: Minor
> Fix For: 0.8.2
>
> 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