Management Console not compatible with Java 1.6.29?

Confirming.

As a personal work-around, installed a parallel installation of IBM JRE and it seems to work fine.  Not sure which version of Sun Java this is aligned with.

Hi !

Doesn't seem to work with 7.6.2.5. Is this fixed on all platforms ? NMC running on Linux shows Build 681 but with Java 6u29 login is still not possible.

Thanks

Hi Omega,

I'm researching this.. Hopefully report back soon.

Allan

Allan,

While you are researching it, I will report that I have an RHEL5 system (32-bit) that I installed Oracle JRE 1.6.0_29 on last Friday as I was starting to play with gstclreport.  It was failing (unable to verify password).  I have fixed it by downgrading the java install on this system back to Oracle JRE 1.6.0_26.  I am running the 7.6.2.5 version of NetWorker (client and nmc) on this system.

Frank

Did you clean the Java cache on the workstation you are using NMC on?

One problem is, that on linux the rpm package name for the nmc is still lgtonmc-7.6.2-1, even if the package itself probably is updated. I haven't updated the nmc rpm package after the first 7.6.2 install because the package version always has been the same. I now realized, that also the nmc package has been updated for every new 7.6.2.x version, but because the rpm package version always been the same it hasn't been updated.

(Using yum (-nogpg) update *rpm on CentOS 4&5)

A workaround is to force the install with yum --reinstall or on CentOS 4 using rpm --force. Just did that on my linux NMC server. Seems to work ok. The build reported is (still?) 681, though?

An update to this...

It doesn't still work with Javas > 1.6.27?

I have uppgraded two Windows (32bit) servers to 7.6.2.5 and one linux (64bit) server, (Did the nmc rpm --force install), but this does not help.  I get authentication error on all of them with Java 1.6.29. But 1.6.26 works okay.

EMC is probably working madly on this issue, but at least there is a workaround. Downgrade your client java to 1.6.26 (and look out for all the vulnerabilities...).

Hi Everyone,

Thanks for the communication on the Java 1.6.29 error.  It does appear to be valid (as many have pointed out  ).  A quick search found a couple other companies warning about 1.6.29 too:

http://www.dnb.nl/en/statistics/eline-bb/nieuws/dnb260274.jsp

http://www.loweslink.com/systemrequirements.htm

A bit of research shows that it looks like Oracle made some change in their API that affects our SSL socket read handling, hence failure to authenticate. The changes were made not only in Java 6 Update 29 (1.6.29), but also in Java 7 Update 1 (7.0.1). We don’t know if the change was intentional, or if it is a bug. We are checking with Oracle on this.

The good news is we do have a fix that will work with all available Java updates regardless of their specific API implementation, and it will be available soon. It appears the easiest route at this point is to stick with 1.6.26 until that fix is available. 

As I hear more, I’ll update this thread.

Thanks,

Allan                              

Technical Advisory:

http://solutions.emc.com/emcsolutionview.asp?id=esg125257