Forum Stats

  • 3,826,347 Users
  • 2,260,631 Discussions
  • 7,896,911 Comments

Discussions

How to test whether the "Java Auto Update" is turned on in JRE 1.8.0_66-b33 delivered via Patch 220

Mariana Angelova
Mariana Angelova Member Posts: 2
edited Nov 24, 2015 11:17AM in Java 8 Questions


Any idea how to test in an Enterprise environment whether the JRE 1.8.0_66 (pre-build 33) is built with "Java Auto Update" ON or OFF before it expires on 19 Jan 2016?

It's absolutely not acceptable to let the enterprise users to see the 'Java version is out of date' dialog once it expires.

There is no Auto Update Off Build JRE8u66-b33  offered via the "Deploying JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite 11i ( Doc ID 290807.1  )", which fixes the java performance issue.

For details see: https://blogs.oracle.com/stevenChan/entry/jre8u60_ie_delay_fixed.

The workaround via  Note 1608866.1   deployment.expiration.check.enabled=false  in the deployment.properties, doesn't seem to work any more in 1.8.0_66

The same statement can be found in:  "Handling the New JRE Security Dialogs ( Doc ID 1553875.1  ) .. .  “.. It will not be available for JDK 8 and later releases.”

Thanks in advance

Kind regards

Mariana Angelova

Answers

  • Unknown
    edited Nov 23, 2015 10:54AM
    Any idea how to test in an Enterprise environment whether the JRE 1.8.0_66 
    (pre-build 33) is built with "Java Auto Update" ON or OFF before it 
    expires on 19 Jan 2016?
    

    I'm not sure I understand your question.

    Why can't you just do a test install and then check to see what the setting is?..

    There is no Auto Update Off Build JRE8u66-b33  offered via the "Deploying JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite 11i ( Doc ID 290807.1  )", which fixes the java performance issue.
    For details see: https://blogs.oracle.com/stevenChan/entry/jre8u60_ie_delay_fixed.
    
    The workaround via  Note 1608866.1   deployment.expiration.check.enabled=false  in the deployment.properties, doesn't seem to work any more in 1.8.0_66
    The same statement can be found in:  "Handling the New JRE Security Dialogs ( Doc ID 1553875.1  ) .. .  “.. It will not be available for JDK 8 and later releases.” 
    

    That link is to a new/recent announcement. If you find a bug/issue with the product you need to open an SR with Oracle support

  • Mariana Angelova
    Mariana Angelova Member Posts: 2
    edited Nov 24, 2015 5:32AM


    Thanks for your responce. The problem is that deployment.expiration.check.enabled=false does not work any more with JRE 8.

    Please check: "Handling the New JRE Security Dialogs ( Doc ID 1553875.1  )

    "...The deployment property option to suppress the old JRE warning will only be available for JDK 7.  It will not be available for JDK 8 and later releases...  . Please note that there may be some difficulty in getting the property to work the first time around.  See also support note 1608866.1."

  • Unknown
    edited Nov 24, 2015 11:17AM
    Mariana Angelova wrote:
    
    
    Thanks for your responce. The problem is that deployment.expiration.check.enabled=false does not work any more with JRE 8. Please check: "Handling the New JRE Security Dialogs ( Doc ID 1553875.1  ) "...The deployment property option to suppress the old JRE warning will only be available for JDK 7.  It will not be available for JDK 8 and later releases...  . Please note that there may be some difficulty in getting the property to work the first time around.  See also support note 1608866.1."

    Since that is INTENTIONAL it is not a bug.

    All I can do is refer you to the Oracle docs for the configuration settings:

    Deployment Configuration File and Properties

    Set to true to prompt users to update the JRE when an out-of-date JRE is found on their system. Set to false to suppress the prompt.
    Note: To ensure that the expiration check is disabled, use the -userConfig deployment.expiration.check.enabled false option with the javaws command. If this property is changed in the deployment.properties file, open the Java Control Panel before starting an application to ensure that the native cache is synchronized with the file. Otherwise, the change might be ignored the first time an application is started.
    

    Did you do that check for the 'might be ignored the first time'?

    Also this link has some additional info that MAY be helpful. Can't tell if they are using that later version you mention.

    https://foigus.wordpress.com/2015/02/20/managing-java-7-and-8-updates/