Java 1.4.2 at EOL

Hi
I was wondering, we are using java code within oracle.
10g currently uses java 1.4.2 as the basis for this functionality. Are there plans to move this to 1.5 or 1.6 as 1.4 has now reached the end of life and will not be supported by sun?
Steven Jackson

Oracle 11g includes a JVM 1.5 and a pluggable
interface to upgrade the JVM to newest releases.Marcelo,
Do you happen to have a pointer to the documentation on this pluggable interface? I've not heard anything about it, and I can't seem to find any information about it in the documentation, but perhaps I'm just not searching for the right term...
Justin

Similar Messages

Fedora 13: After upgrading from FF3.6 to FF6.0.2 I no longer have a Java plugin. How do I configure the Java Plugin for FF 6 ? There is no Java Plugin at the site

I am Fedora 13x64 bit. I just installed FF v6.0.2 from the FF download site. I backed up the existing FF 3.6 as firefox_old
I need to have a Java plugin to access company site, how do I configure the Java Plugin ?
At the Plugin area in FF6 there is no Java Plugin available, even after a search.
I have Java 1.6.0 installed in the OS at:
/usr/lib/jvm/java-1.6.0/jre/lib/amd64/libnpjp2.so
I googled how to configure Java Plugin for FF 6 for Fedora 13 and the trick was to create a soft link from /home/<userID>/.mozilla/plugins to the above libnpjp2.so

AVtech wrote:
. . . If a person can't get an answer here I don't know where else to turn since Sun certainly wouldn't offer tech support for a free product . . .These forums are user forums, and only occasionally visited by Sun employees. Sun does provide Java technical support options, although (of course) at a charge.
See:
http://developers.sun.com/services/
. . . I guess we'll just use JRE 5 until it's unsupported, whenever that will be. I'm still waiting for an answer on that question, too. See:
http://java.sun.com/products/archive/eol.policy.html
http://www.sun.com/service/eosl/
This document (part IV and Appendix) has some debugging and troubleshooting information that may allow someone involved in the problem to resolve the cause:
See:
http://java.sun.com/javase/6/docs/technotes/guides/plugin/developer_guide/contents.htm
Any steps that you can take to isolate the problem to specific Java versions, browsers, applets, web sites, operating systems (and versions), etc, would enhance the possibility of getting help.
You can try the applets at this Sun location and see if any of them are "slow".
See:
http://java.sun.com/javase/6/docs/technotes/samples/demos.html

Warning for users of older versions of Java thinking of upgrading to 10.6

I'm a pediatric oncologist and I use a MacBook Pro at work for many aspects of patient care. We have web based system that allows us to look at radiology scans from any computer via a browser. This system requires Java 1.4.2 to work -- it will not work with newer versions of Java.
In OS X 10.5, I would simply switch to Java 1.4.2 when needed and back when I was done. Unfortunately, Snow Leopard only installs Java 1.6. This leaves me completely unable to look at scans from my MacBook Pro.
Off the top of my head, if there was a way to take the Java 1.4.2 package from OS X 10.5 and install it on OS X 10.6, and to use Java Preferences to switch between Java versions, that would be a great solution for me, even with the understanding that Java 1.4.2 is EOL'ed and that no updates would be expected.
Today I contacted Apple Support, and the official word is that there is no way to install Java 1.4.2 under Snow Leopard, and that my only option at this point in time is to go back to OS X 10.5.
Unless someone can figure out a way to hack Java 1.4.2 from OS X 10.5 into Snow Leopard, that is.

I was able to get Java 1.4.2 working with Safari in Snow Leopard tonight. Here's how to do it.
1. Install Java 1.4.2 as outlined in this link:
http://wiki.oneswarm.org/index.php/OSX_10.6_SnowLeopard
Alternatively, extract Java 1.4.2 from the Java For Mac OS X 10.5 Update 4 installation package, and install it in a similar manner:
http://support.apple.com/downloads/Javafor_Mac_OS_X_10_5_Update4
2. Make sure that Java 1.4.2 is the first 32-bit application in the list. Under Java Preferences, my list reads:
Java SE 6 64-bit
J2SE 1.4.2 32-bit
Java SE 6 32-bit
3. Open Safari in 32-bit mode via the Get Info window for Safari. This is where I was getting screwed up. It finally occurred to me that Java 1.4.2 is a 32-bit application, but if Safari was opening in 64-bit mode, it wouldn't use the 32-bit Java apps.
Once I opened Safari in 32-bit mode, Safari was able to use Java 1.4.2.

Update jdk from Oracle 11g? (version is EOL)

When does Oracle plan to update the jdk and jvm used in Oracle 11g stored procedures?
Oracle 11g ships with java 1.5, which reached EOL in October, 2009.
(See [http://www.oracle.com/technetwork/java/eol-135779.html] )
Thus, the compiler and VM used to provide Java functionality in the Oracle Database are ~2.5 years beyond the era when they were officially supported.
Edited by: 921895 on Mar 19, 2012 9:55 AM

Currently , the java version in the database cannot be upgraded - this is being looked upon as a future option.
OracleJVM Install and Upgrade FAQ [ID 825306.1]
Possible to Upgrade JDK Classes Supplied with Database Version 8i-10g? [ID 342810.1]
HTH
Srini

Weblogic 10 support for java 1.4

Hi,
My application is currently running on weblogic 8.1 sp3. We are upgrading to weblogic 10 on Solaris 10.
Can I run weblogic 10 on java 1.4 in Solaris 10.
This may not sound logical, but I need answers.
Thanks in advance,
Rama

Rama,
You also need to consider the End of Life policy for JDK 1.4, unless you have a "Business Release" you will run out of support in October 2008. My understanding is BEA/Oracle will continue to support WL8 but only as far as they can. Have a look at http://java.sun.com/products/archive/eol.policy.html for more details.
Regards, Geoff

Java EE End Of Support

I've found information here [http://java.sun.com/products/archive/eol.policy.html] that indicates that support for Java SE 1.4 ends summer 2008, and Java SE 1.5 ends in October 2009. Does the same apply to Java EE 1.4 and 1.5? If not, what are the EOS dates for Java EE 1.4 and 1.5?

http://forums.oracle.com/forums/search.jspa?objID=f61&q=desupport
Desupport Information

Monitoring memory and thread management for Java 1.4.2_04

Hi,
I have an application which is using Java version 1.4.2_04. The application deployed in Customer site is having some memory issues. There are observing java.exe going 100% in Task Manager. The same application (of higher version)
uses Java 1.5 is not seeing any issues.
Now Customer needs the root cause of the issue and i would like to check the code which is causing the issue. I came to know we can monitor threads and memory using JConsole. Since we are using Java 1.4, i installed Java 1.6 on a remote machine and tried connecting to the problematic machine. But it failed to connect.
i have added the option "-Dcom.sun.management.jmxremote.port=8880" when starting JVM (this i have provided inside ServletExec batch file, ServletExec is my web server).
Any idea how to connect to the problematic machine from remote using JConsole. Or any other tools i can use on Java 1.4 to nail down the problem..
Please provide pointers.
I have another doubt on Java version 1.4, since there were many memory issues, am i hitting any defect in Java 1.4

hari.r wrote:
Please provide pointers.You need to tell you sales/marketing/business requirements people that they must come up with an end of life policy for customers on older versions.
Unless your company has a service contract with Sun you right now, can no longer insure that the VM will remain secure nor even really running.
See the following for the java VMs that you are using.
[http://java.sun.com/products/archive/eol.policy.html]

Java 4, 5, 7 (JRE/JDK) documentation - full release history

Good day,
Does anyone know if Oracle plans to update their documentation for Java 4, 5, 6, and 7 to reflect all updates that tie to the most recent security advisory posted for February 2012 (http://www.oracle.com/technetwork/topics/security/javacpufeb2012-366318.html)
The most recent releases denoted in the February 2012 advisory are as follows:
Java 4 (1.4.2): 1.4.2_35 and earlier
Java 5 (1.5.0): 5.0 Update 33 and earlier
Java 6 (1.6.0): 6 Update 30 and earlier
Java 7 (1.7.0): Java 7 Update 3
Java 4: http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-javase14-419411.html (last denoted update on this documentation link is 1.4.2_30)
Java 5: http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-javase5-419410.html (last denoted update on this documentation link is 5.0 Update 22)
Java 6: http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-javase6-419409.html (last denoted update on this documentation link is 6.0 Update 30; looks to be current)
Java 7: http://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-javase7-521261.html (last denoted update on this documentation link is 7.0 Update 2)
I'm really just looking to acquire reliable URL locations that are updated more frequently that speak to the update releases and dates of each.
Thank you,
Chris

Thanks for the response. The most recent security advisory from Oracle implies that updates are still being actively developed for Java systems that may be EOL. It seems to me that whether or not a product is supported by Oracle has no bearing on whether or not updates are developed, exist, and are available for installation. I'm just trying to make sense of the gap in the release history based on the links I provided. As noted before, the February 2012 advisory (http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-javase14-419411.html ) states that 1.4.2_35 and earlier are "Affected product releases and versions". So, if 1.4.2_35 and earlier are affected by CVE-2012-0499 (a significant issue per CVSS score) and the only vendor information I have to refer to is this link that only has information up to 1.4.2_30 what good is it when trying to identify other patch/hotfixes/updates between _.35 (or _.36) and the noted ._30? Are you suggesting that any update released after the last denoted update/version in the aforementioned links for Java 4, 5, 6, or 7 are only available for paying customers? If I'm not mistaken, Java 4 has always been a free product so that begs the question, why wouldn't support continue as free? Maybe support can continue if a customer wants to pay for it IF the product goes EOL?
I'm only here asking these questions because the support line from Oracle told me I may have better luck in achieving answers to this question in the forums. I basically got the run-around that there is no product specific support line or department for Java.
Thanks again!

Oracle Waveset with Java 7 (JDK 1.7)?

Hi
has anyone attempted to run Oracle Waveset with Java 7 (with Weblogic)? does it work? We're planning an upgrade and we're thinking of going directly to Java 7 (instead of Java 6 which will be EOL this autumn).
the latest certification matrix (updated in May 2011) does not mention Java 7.
thanks, Peter

Hi,
As the warning message suggests, You need to check the Supported Platforms for your XI 3.1 version: www.service.sap.com/pam ... and look under section "Web Intelligence, Desktop Intelligence, Dashboard and Analytics Data Sources"
here the SP05 one for Windows : http://service.sap.com/~form/sapnet?_SHORTKEY=01200252310000087200&_SCENARIO=01100035870000000202&_OBJECT=012002523100019873322011E
Basically, you need to use ORA 10 or 11. Else, you aren't supported, and probably wasting your time.
Regards,
H

Which java version should I code the SCJD assignment?

Hi All,
I am planning to take SCJD (maybe within a year or earlier). But I am confused as to in which version of java should I submit the assignment(CX-310-252A). I read in "All in one Java 2 SCJP..." book by Kathy Seirra that we must not use a verison (of java) that is more than 18 months older than the current production java version as it would be deemed "out-of-date" by the exam assessors (pg 563).
So going by the same line of thought, does it mean that I can submit the aasignment only in 1.6 (release date-dec 12 2006) and not in java 1.5 or 1.4. Also, if 1.7 gets released early next year and if I am coding in 1.6, then I would have to submit the assignment by june 2008 (or else it would become outdated).
The various java version release dates can be found at: http://mindprod.com/jgloss/javareleasedates.html
Please help me solve this version confusion. (I prefer submitting in 1.4 as I have completed SCJP 1.4)
SCJP 85%, SCWCD 91%
"Once we accept our limits, we go beyond them"

1.5 is no longer a valid platform 18 months after the
initial public release of 1.6.
What that means is that your code should work on 1.6
without modifications from that date.Where did you find that information?
It's a bit strange since this is what The EOL for Java says:
"Technology EOL Policy
Major Product Family Releases
This would include such products as Java 2 Platform,
Standard Edition 1.4.2 and 5.0. The Java technology policy
is to support the current shipping version of Java
Standard Edition plus two back versions. Once the
End-of-Life process starts on a major product family
release, a notice will be posted on all relevant download
pages stating that the product has entered the EOL
process and how long the process will continue until the
product is no longer supported by Sun."http://java.sun.com/products/archive/eol.policy.html
So that means that 1.4.2 will enter EOL when Java 7 is released. How can a version that hasn't entered the EOL life cycle not be valid?
Kaj

Any news or ETA on Java 1.7 support for Coherence 3.7?

We're currently in the process of preparing for a rather large upgrade to our existing cluster that is running on older JVMs and an older version of Coherence. One motivating factor is to get on a supported JVM / Coherence version instead of just an "enduring support" version.
As part of this effort, we are going to be doing a lot of regression testing of our applications. From what I understand, Java 1.6 will be EOL in November of 2012 - so it would seem prudent to consider upgrading to Java 1.7 at this same time (although upgrading JVMs in a rolling fashion isn't as big of a deal as upgrading to a major version of coherence since the cluster can have heterogeneous JVM versions but not heterogenous protocol versions)
Is there an ETA for when Coherence will be supported on Java 1.7?

cfelde wrote:
It doesn't support 1.7?
We've run Coherence on 1.7 under various installations for some time with no issues. In fact we've seen significant performance gains.
http://docs.oracle.com/cd/E24290_01/coh.371/e22837/gs_install.htm#CIHDECEA
It says "1.6 update 23 JVM or later", but it doesn't include 1.7? Also given that 7 is binary-compatible with 6 (in a most cases at least: http://www.oracle.com/technetwork/java/javase/compatibility-417013.html#incompatibilities), it didn't look like a big risk up front.
There were a few other reported incompatibilities with other software out there and Java 7 besides those listed in the compatibility list, so I would be a bit careful about it.
Or are you talking about compiling and having a Java 7 compiled coherence jar?I don't think you would see anything like that with 3.7. After all 3.7 still has to run on Java 6 and Java 6 would not be able to load Java 7 compiled class files.
Best regards,
Robert

Upgrading from 1.4.2_04 to 1.4.2_06, 1.4.2_07 or 1.4.2_08 ?

I am in need to upgrade my JMV from 1.4.2_04 due to known JVM issues solved in 1.4.2_06 and newer.
I seek the most stable version and therefore need to pick between 06, 07 or the latest 08.
Which version is considered the less risky more used and more stable atm?

Note that 1.4.2_06 and 1.4.2_07 have
"completed the Sun EOL process and are no longer supported under standard support contracts. These products are down-revision products that may have various bugs, Y2000, and possibly security issues associated with them. Sun in no way recommends these products be used in a live, production environment. Any use of product on this page is at the sole discretion of the developer and Sun assumes no responsiblity for any resulting problems."
[url http://java.sun.com/products/archive/eol.policy.html]Java Technology EOL Policy

Build detection problem when updating 1.4.2_04 to 1.4.2_06 or higher

When using the object tag in internet explorer to deploy Java we have a problem updating between builds
example:
updating Java from 1.4.2_04 to 1.4.2_06
it seems that the object version attribute only checks 1.4.2 and not the build number, so our client. therefore strarts.
We had expected that if the version number was changed to _06 and the new er 1.4.2_06 installer was updated to the web server that the installation would be carried out
Does this mean that my customers that are within a secure (closed) intranet can only update between versions and not builds
Thax

Note that 1.4.2_06 and 1.4.2_07 have
"completed the Sun EOL process and are no longer supported under standard support contracts. These products are down-revision products that may have various bugs, Y2000, and possibly security issues associated with them. Sun in no way recommends these products be used in a live, production environment. Any use of product on this page is at the sole discretion of the developer and Sun assumes no responsiblity for any resulting problems."
[url http://java.sun.com/products/archive/eol.policy.html]Java Technology EOL Policy

About clsid and more in object tag for deployment

I've found it a bit hard to get up-to-date information about the best-practice for writing applet/object/embed tags in html when deploying java applets. Anyway, I found this.

<object classid="java:com.myCompany.MyApplet.class"
        type="application/x-java-applet"
        archive="../MyApplet.jar"
        width="400" height="600">
    <param name="mayscript" value="true" />
    <param name="someParameter" value="someValue" />
    
    <param name="archive" value="../MyApplet.jar" />

    
    <object classid="clsid:8AD9C840-044E-11D1-B3E9-00805F499D93"
            codebase="http://java.sun.com/update/1.5.0/jinstall-1_5_0-windows-i586.cab"
            width="400" height="600" >
    <param name="code" value="com.myCompany.MyApplet" />
    <param name="archive" value="../MyApplet.jar" />
    <param name="mayscript" value="true" />
    <param name="someParameter" value="someValue" />
    <strong>
        Some error message...<br />
        <a href="http://java.sun.com/products/plugin/downloads/index.html">Download!</a>
    </strong>
    </object>

</object>
This code works in Firefox 2/3 and IE7 (on Vista). Would you experts here say this is an acceptable way of doing it, or do you have a better way to recommend?
But there is one thing that was really hard to find googling, and that is what should the clsid ("clsid:8AD9C840-044E-11D1-B3E9-00805F499D93") and codebase ("http://java.sun.com/update/1.5.0/jinstall-1_5_0-windows-i586.cab") be if I want the applet to run in the latest Java version? Or at least 1.6.0 instead of 1.5.0 since I compile the applet using jdk1.6.0_06.
And wouldn't www.java.com be a more user-friendly download link instead of http://java.sun.com/products/plugin/downloads/index.html? On this site it says "The above default release, 1.4, is the latest release of Java Plug-in." and links to http://java.sun.com/j2se/1.4.2/download.html, which in term says "J2SE 1.4.2 is in its Java Technology End of Life (EOL) transition period." Why couldn't Sun keep their web sites a bit more up-to-date?

>
Isn't it anybody here that wants to share...>I look at questions with Dukes, but when I open a thread and it turns out it has less than 10 dukes, I take it is 'less than imperative' to the original poster to fix the problem - so often move on to the next thread/post.
What do you think 3 Dukes indicates to someone like me? (Oh go on, guess - it'll be fun.)
>
... how you usually write your applet/object/embed tags in the html file? I'm interested in "new" development for Java 6, i.e. no legacy support for older code needed.>You might check out the deployJava.js which is described in the latest [deployment advice|https://jdk6.dev.java.net/deployment_advice.html].
If you find that answer works for you, and you appreciate the advice, the best way to show it is to raise those Dukes before assignation.

PB12.6 compatiblity with Oracle JRE 1.3.1_02

Hello
I am currently using PB12.6 .
we need to call the Java bean through OLE connection. Java bean is built in JRE_1.3.1_02 version. Here is code
ctisActiveXName = 'Java Bean Class'
ioleServer = CREATE OLEObject
llResult = ioleServer.ConnectToNewObject (ctisActiveXName)
However PB12.6 get crashed at above line.
This code works fine in PB12.0 . Note that we cant change the Java component built in JRE_1.3.1_02.
How can I make it work in PB12.6?
Any help is highly appreciated.
Thanks
Amol

Hello Amol,
To simulate your problem, I used this excellent sample Wrap a Java bean in a COM object - Real's Java How-to to bundle a JavaBeans as an ActiveX object using the ActiveX Bridge technology
I had to install very old JDK 1.3.1_02 and Java Plugin 1.3.1 into my Windows 7 box
Here are my observations after coding below script (I also used excellent document http://scn.sap.com/community/developer-center/powerbuilder/blog/2014/09/24/how-to-capture-error-messages-from-an-activex-control from Roland Smith to create n_oleobject OLE object)
+ PowerBuilder 12.1 and 12.5.2 are working without any crashes
+ PowerBuilder 12.6 is crashing directly at line ConnectToNewObject
My real concern is that
* the COM object (which is in fact a Java object) is using an EOL JDK and EOL technology
* PB 12.6 is not compatible with this JDK
I'm not sure if we can support COM objects developped with obsolete technologies.
n_oleobject   objJava
string    strFromjava
integer   li_rc
objJava = CREATE n_oleobject
li_rc = objJava.ConnectToNewObject("JavaBeanSays.Bean")
If li_rc = 0 Then
   try
strFromJava = objJava.getHello()
MessageBox("From PB via JavaCom", strFromJava)
objJava.setHello("Bonjour le monde")
strFromJava = objJava.getHello()
MessageBox("From PB via JavaCom", strFromJava)
   catch ( RuntimeError rte )
      PopulateError(objJava.ErrorCode, objJava.ErrorText)
      MessageBox("OLE Runtime Error #" + &
            String(Error.Number), Error.Text, StopSign!)
      objJava.DisconnectObject()
      Return
   end try
   objJava.DisconnectObject()
Else
   MessageBox("OLE Connect Error #" + String(li_rc), &
         "Connect To Object Failed!", StopSign!)
End If
DESTROY objjava
Thanks
Jacob

Java 1.4.2 at EOL

Similar Messages

Maybe you are looking for