How to use other JDK instead of that come with Cloudera Manaager 5?

If you have deployed the 45 jdk to your cluster, it will still be present
after installing CM5 beta 1. Are you seeing processes using 41 instead of
45?

The most comprehensive solution is to uninstall the 41 package
(oracle-j2sdk1.7) from your nodes. We will update the bundled JDK in future
releases.

--phil

To unsubscribe from this group and stop receiving emails from it, send an email to scm-users+unsubscribe@cloudera.org.

Hi Philip,

     Yes! It did not use the version 45 JDK which I already installed. It
use the version come with Cloudera Manager 5.
Version 45 JDK still in my cluster, but not been used.

Best Regards.
James



2013/11/2 Philip Langdale <philipl@cloudera.com>
To unsubscribe from this group and stop receiving emails from it, send an email to scm-users+unsubscribe@cloudera.org.

Hi James,

Yes, I'm afraid there's a bug in the java enumeration logic that means it
picks the lowest numbered update. This should be fixed in the next beta
releases of CDH5 and CM5.

--phil

To unsubscribe from this group and stop receiving emails from it, send an email to scm-users+unsubscribe@cloudera.org.

Hi Philip,

     Could you kindly let me know when will the next beta release be
available?

Best Regards,
James


2013/11/5 Philip Langdale <philipl@cloudera.com>
To unsubscribe from this group and stop receiving emails from it, send an email to scm-users+unsubscribe@cloudera.org.

I can't say exactly, but it will be in the new year.

--phil

To unsubscribe from this group and stop receiving emails from it, send an email to scm-users+unsubscribe@cloudera.org.