Bug 1075574 - Remove OpenJDK warning during startup
Summary: Remove OpenJDK warning during startup
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Storage Node
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: RHQ 4.11
Assignee: Stefan Negrea
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 1075575
TreeView+ depends on / blocked
 
Reported: 2014-03-12 12:06 UTC by John Sanda
Modified: 2014-07-21 10:13 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1075575 (view as bug list)
Environment:
Last Closed: 2014-07-21 10:13:35 UTC
Embargoed:


Attachments (Terms of Use)

Description John Sanda 2014-03-12 12:06:41 UTC
Description of problem:
During startup, CassandraDaemon.java logs the following WARN statement if OpenJDK is in use,

"OpenJDK is not recommended. Please upgrade to the newest Oracle Java release."

Not only do test on and support OpenJDK, Red Hat has a team dedicated to supporting it as well.

Packaging changes for Cassandra are handled pom.xml in the cassandra-ccm-core module.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Stefan Negrea 2014-03-25 21:08:31 UTC
Updated the Cassandra artifacts by re-compiling the entire project and then updating 1.2.9 with the changed class. All the new artifacts have been published with the -jboss-1 moniker. 


Published the artifacts on JBoss Nexus:
https://repository.jboss.org/nexus/content/repositories/thirdparty-uploads/org/apache/cassandra/


The project POM has been updated to use 1.2.9-jboss-1 of Cassandra.


master branch commit:
https://github.com/rhq-project/rhq/commit/5cbbd1cac8ee864d4bc7080a543a7a3be6a0229c

Comment 3 Heiko W. Rupp 2014-07-21 10:13:35 UTC
Bulk closing of RHQ 4.11 issues, now that RHQ 4.12 is out.

If you find an issue with those, please open a new BZ, linking to the old one.


Note You need to log in before you can comment on or make changes to this bug.