Special JRE 6u21-b08 Build Now Available for EBS Customers

The painful saga of our recent JRE releases' issues with the Oracle E-Business Suite is almost over.  It is expected that a future release of JRE 1.6 will contain a mainline fix for the "Mismanaged Session Cookie" issues that exist with JRE 1.6.0_18 to 1.6.0_21 build 6 (6u21-b06), inclusive. 

There is an interim workaround until that new release is available.  JRE 1.6.0_21 build 8 (6u21-b08) is now available and certified for Oracle E-Business Suite 11i and R12. This Build of the native plug-in fixes the 'Mismanaged Session Cookie' issue for the JRE 6u21 stream, which could cause a failure of the following functionalities on certain desktop/browser combinations, and particularly prevalent for IE6 and IE7 users:
  • 'File -> Export' functionality
  • Opening attachments in forms
  • Opening an HTML form to a new window from forms.
  • Opening an Applet in a new window from forms
  • Trying to login again after forms session timeout fails
Special release vehicle for this JRE build

This version of the plug-in is only available through patch 10021403 and is not available as a download through the usual channels or through the Java automatic update facility. The standard version of the plug-in remains at JRE 1.6.0_21 build 6 (6u21-b06). This fix will not be available through the usual channels until a future release of JRE 1.6.

This release also fixes the long standing z-ordering issue (HTML Window opens behind Forms Window) for Windows XP users running Internet Explorer. A permanent fix is not yet available for Firefox users or Windows Vista or Windows 7 users, therefore please continue to use one of the workaround options if required.

Summary of options for EBS sysadmins

At this stage, your options are to:
  1. Remain on JRE 1.6.0_17; wait for the upcoming JRE release that includes this fix
  2. Deploy any standard JRE release later than 1.6.0_17, with the understanding that some of your users may encounter issues related to "Mismanaged session cookies"
  3. Deploy JRE 1.6.0_20-b05 (released via patch 9915543)
  4. Deploy JRE 1.6.0_21-b08 (released via patch 10021403)
For further information and requirements please see:
Related Articles
The preceding is intended to outline our general product direction.  It is intended for information purposes only, and may not be incorporated into any contract.   It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision.  The development, release, and timing of any features or functionality described for Oracle‚Äôs products remains at the sole discretion of Oracle.


Due to security issues, options 3 and 4 are your only choices. Is there a way that e-Business can please be added the JRE test plan prior to release?

Posted by Chris Green on August 14, 2010 at 10:11 PM PDT #

Hello, Chris,

Yes, that's a good suggestion. This has been under discussion for quite some time. I'll provide an update on this as soon as I have something substantive to share.


Posted by Steven Chan on August 15, 2010 at 08:03 AM PDT #

Hi Steven,

we've also got this issue in our Forms-based product, starting with JRE 1.6.0_18. We've implemented a workaround in our code: Instead of using AppletContext.showDocument() we now use the Java-to-Javascript bridge (JSObject.getWindow) and let the browser evaluate window.open(, 'blank'). This opens the new window in the same browser process unlike the changed showDocument implementation.


Posted by Andreas Leidner on August 17, 2010 at 10:01 PM PDT #

Hi, Andreas,

Thanks for your comment. Glad to hear that you found a workaround for your application.


Posted by Steven Chan on August 18, 2010 at 12:41 AM PDT #

Currently we (Oracle Support and myself) are working an issue where this patch/release of Java 6u21b08 does not resolve the above issues.

This needs to be given higher priority as this remains to impact our Production environment.

I am happy to show you what is happening via an OWC if you would like. Just give me some heads up so we place the new version back on our DEVP instance for testing.

The SR that is logged for this is:
SR #3-1967898181: Get an extra IE screen when re-printing and login back the application

and I think this is also related:

SR #3-1932535191: When viewing PO Attachment we get Java security error.

Posted by Gwen Franz on August 20, 2010 at 06:16 AM PDT #

Hello, Gwen,

Thank you for letting me know about this. I'm very sorry to hear that this still appears to be an issue for you. This general class of issues has multiple variants, some of which have been very difficult to reproduce because of machine-specific baseline conditions.

I am escalating this to our Sun JRE team. Please monitor your SR for updates; we'll work directly with the Support Engineer assigned to your SR.


Posted by Steven Chan on August 20, 2010 at 07:01 AM PDT #

1.6.0_22 came out last night. Can you confirm / deny if all the regression bugs we've been dealing with are patched in 1.6.0_22 ?

Posted by Jay Weinshenker on October 12, 2010 at 10:51 PM PDT #

Hi, Jay,

Unfortunately not. See:

Warning: E-Business Suite Issues with Sun JRE 1.6.0_22


Posted by Steven Chan on October 13, 2010 at 06:34 AM PDT #

That's unfortunate, but thanks for the quick clarification blog post. Much appreciated.
May _23 be the charm!

Posted by Jay Weinshenker on October 13, 2010 at 11:07 AM PDT #

After applying patch 10021403, when we log into EBS, we are prompted to download and install 6U21-B07 instead of 6U21-B08. Has anyone else experienced this issue?

Posted by S. Sookdeo on October 29, 2010 at 02:14 AM PDT #

That shouldn't happen. Patch 10021403 should deliver 6u21-b08. If you're still experiencing this issue, please log a formal Service Request via My Oracle Support (formerly Metalink) to get one of our specialists engaged.

Please feel free to forward your Service Request number to me if it gets stuck in the support process for some reason.


Posted by Steven Chan on November 02, 2010 at 06:51 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed


« June 2016