JDK-7149113 : RegDeploy: in some cases DeploymentToolkit deployJava.getPlugin().isPlugin2() returns incorrect info
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 7u4
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows
  • CPU: generic
  • Submitted: 2012-02-27
  • Updated: 2012-03-05
  • Resolved: 2012-03-05
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7
7u4Resolved
Related Reports
Duplicate :  
JDK-7148304 - Java control panel: switch to old plugin check box is not working
Description
Desc:
  1. This issue has been initially detected with 7u4 b11 + FX 2.1
  2. When we switch to old plugin DeploymentToolkit deployJava.getPlugin().isPlugin2() still returns 1.
  3. It's hard to reproduce with 7u4 b13 + FX 2.1 ( b14 ) because of CR 7148846 ( switching to old plugin doesn't work ), but it still happens.
  4. I managed to reproduce this issue variation: new plugin actually works, but deployJava.getPlugin().isPlugin2() != 1.
  See screenshot and *.PML log attached ( PML log stared just before clicking on button that calls DT 
  methods including deployJava.getPlugin().isPlugin2() )
Comments
EVALUATION Closing as duplicate of 7148304. Please reopen if you can reproduce it on build where 7148304 is fixed.
05-03-2012
EVALUATION I do not think PML is complete, you need to start it before you load test page. E.g. there is no native DT plugin loaded at all ... (Is it loaded if you inspect process with process explorer?) What DT does is simply reads value of "UseNewJavaPlugin" key under HKLM/Software/JavaSoft/Java Plug-in/10.4.0 I do not see attempt to read it in your log but it should contain 1 when we report TRUE from isPlugin2(). This value could be updated from installation code and control panel setting and only reflect what "control panel thinks". Browser does not pay attention to this registry key. So, what i think happens: we failed to disable old plugin but marked it "disabled" in the control panel. I suspect that this is another manifestation of 7148304 and we need to retest once next 7u4 build is available (or you could try to compare latest JRE8 promotion (problem should be reproducible) vs latest deploy team nightly (problem should be fixed).
27-02-2012