Understanding J2SE 1.5 End-of-Life Implications for Oracle E-Business Suite
By mzshaw on Jun 24, 2009
As with my previous post about the desupport of Sun's Java 1.4 release, you should be aware that the equivalent end-of-life (EOL) for Sun's J2SE 1.5 is coming up in October 2009.
Implications for E-Business Suite Users
Here are the implications if your Apps 11i or 12 environments are running on servers with J2SE 1.5:
- 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.5. It is extremely unlikely that we will issue new Apps patches for new compatibility issues identified with the E-Business Suite and J2SE 1.5.
- Issues isolated to J2SE 1.5 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.5 directly from them.
- Issues that can't be reproduced in E-Business Suite environments running on J2SE 1.6 (6.0) will likely result in a recommendation to upgrade to those later releases.
Upgrading to Java 1.6
Given that Java 1.4 is already desupported and Java 1.5 is soon to be desupported later this year, we strongly recommend that you upgrade your EBS environments to Java 1.6, a.k.a Java 6. For more information, see:
- 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)