Testsuite:unifyJRESetting in common
Test name(s):testHiddenJREEntry
Product(s) tested:Jre6u85b11 32bit
OS/architecture:Windows 7 SP1 x86

Reproducible: Always
Reproducible on machine:egtc

Is it a Regression:No as FCS of 6u81 failed as the same issue
(Jre 6u85b01 32bit+Windows 7 SP1 x86:FAILED,It's the same issue.)


Test result on the last GAed release for this train:
(Jre 6u81b08 32bit+Windows 7 SP1 x86:FAILED,It's the same issue.)

[if Fail] Test result on FCS:
(Jre 6u81b08 32bit+Windows 7 SP1 x86:FAILED,It's the same issue.)

Is it a platform specific issue:Yes(This case is only failed on windows,
we verified the case on SLES 11 x86 with the same build 6u85b11:PASS)

Exception/Error from Log: http://aurora-ds3.us.oracle.com:9502/runs%2F584465.ManualSubmit-1/unifyJRESettingScenarios/testHiddenJREEntry.jtr

Copy JDF workspace,install test jre,and run this case
Steps to reproduce:

1.Delete deployment.properties file (if existed)
2.Install jre5u75b07 (e.g. Test JRE is jre6 then install latest jre version of jre5)
3.Install the test JRE
4.Open java control panel and close it to refresh/generate deploment.properties file
Note: On Linux/Unix, Open and then close JCP of both installed JREs to refresh/generate deployment.properties file.
5.Check deployment.properties file and there should be information about two JREs installed above, example, deployment.javaws.jre.0 and deployment.javaws.jre.1
6.In the deployment.properties file, modify the OS name associated with one installed JRE to a different OS, example, deployment.javaws.jre.1.osname=Linux if testing on Windows and you should have deployment.javaws.jre.1.osname=Windows before the change
7.Close and relaunch java control panel, go to Java tab--> View
8.Expected behavior: There should be only two Java Runtime Environment entries listed. The modified (invalid) entry should not be displayed there but it should be available in the deployment.properties file. Check deployment.properties file and there should be another entry entry associated with deployment.javaws.jre.2

Actual behavior:
Step 8:deployment.javaws .jre.1.osname=Linux and deployment.javaws .jre.2.osname=Windows.Plese refer to deployment.properties

Simple scenario for reproduce issue:
0. Clean up Java information from test machine (deployment.properties file, cache and any other)
1. Install JRE
2. Open JCP for recreate deployment.properties
3. Brake platform in string deployment.javaws.jre.0.osname=.... (For example: write Linux instead of Windows)
4. Open JCP again.
If you see more than one declared JRE in deployment.properties file bug reproduced.