Understanding J2SE 1.4 End-of-Life Implications for Apps 11i

The eagle eyed amongst you may have noticed that "Overview of Using Java with Oracle E-Business Suite Release 11i"  (Metalink Note 300482.1) has been updated to reflect the Sun End Of Life for J2SE 1.4  which is fast approaching us (October 2008)

As with Steven's previous article Understanding J2SE 1.3 End-of-Life Implications for Apps 11i the implications are the same now for Apps 11i users for J2SE 1.4

Implications for E-Business Suite Release 11i Users

Here are the implications if your Apps 11i environment is running on servers with J2SE 1.4:

  • If you log a Service Request for your environment, Oracle will continue to perform its usual diagnosis, triage, and search through our knowledge base for existing patches and workarounds.   This assistance may be constrained by limited access to a small number of remaining environments running J2SE 1.4.  It is extremely unlikely that we will issue new Apps patches for new compatibility issues identified with the E-Business Suite and J2SE 1.4.
  • Issues isolated to J2SE 1.4 itself will be referred to your operating system vendor for more assistance.  Depending on your vendor, you may be able to purchase extended support for J2SE 1.4 directly from them.
  • Issues that can't be reproduced in E-Business Suite environments running on J2SE 1.5 (5.0) or 1.6 (6.0) will likely result in a recommendation to upgrade to those later releases.

Sun: "Java SE & Java SE for Business Support Road Map"
Hewlett-Packard: "HP-UX Java - End of Life Policy & Release Naming Terminology"
IBM: "AIX Download and service information" (This page lists the "End of Service" dates for AIX JDK)



We had several issues migrating to Java 1.5 on AIX and were told to downgrade to 1.4 or upgrade to 1.6.

Could you please take a look at SR # 6954407.994 and comment?


Posted by John Stouffer on July 08, 2008 at 12:39 AM PDT #


I've scanned the SR but don't see any explicit recommendations to move off of JDK 1.5. I might have missed something.

I've asked our Java and Platforms Engineering team to look into why (or whether) this recommendation was made. Those two teams will work with the Support Engineer assigned to your SR; watch that SR for any updates.


Posted by Steven Chan on July 08, 2008 at 04:00 AM PDT #

Hello John

From your SR, the recomendation to revert to JDK 1.4 came from the issue described Note 422766.1 "Cache Initialization Failure on AIX platform" The required patch for this fix is not yet released for eBiz 11i, but is hopefully imminent.

If upgrading to JDK 1.6 is feasible in your case (and I can't immediately see any reason why you couldn't) , then it makes more sense to install JDK 1.6 rather than upgrade to 1.5 for sure.

Hope this helps


Posted by Mike Shaw on July 08, 2008 at 06:40 PM PDT #

I also had to back out Java5 on AIX. I did experience the problem in note 422766.1 and have the open SR 6675801.993 since mid January. I also have the closed SR 6664946.994 which explains why we backed out Java5 to Java1.4. We had problems across applications. It appears there were many classes that weren't tested for AIX at Java5. This SR was closed because there was no activity done on Oracle's side. What will change with Java6?

Posted by Bruce Beck on July 17, 2008 at 09:49 PM PDT #

Hello Bruce,

My comment for using JDK 1.6 was a generic recomendation and should also have mentioned that the patch from Note 422766.1 would still be required.

The issue you were having was IllegalAccessError. The original engineer didn't seem to pick up on internal bug 6033099 which discusses the issue, so would suggest raising a new SR to have this issue further investigated. Feel free to email me directly with your SR number in this case.


Posted by Mike Shaw on July 17, 2008 at 10:41 PM PDT #

We have also had a problem with java 1.5 on aix (see SR 6903228.993).

We will need to remain on java 1.4 but your support statement above states we may be required to upgrade if an issue cannot be reproduced on 1.5 or 1.6.
At present we can't upgrade to 1.6 without upgrading our aix maintenance level and there appear to be issues with EBS and java 1.5 on aix so we can't do this either.

Posted by Jim Allman on August 14, 2008 at 01:14 AM PDT #

Hi, Jim,

Thanks for your comment. This has been escalated by a few other customers. I'm sorry to hear that you've been bitten by this one.

Our Applications Platforms Group is working on a patch for this issue right now. I'll provide an update on this blog as soon as it's available.


Posted by Steven Chan on August 14, 2008 at 03:14 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed


« July 2016