This content has been marked as final. Show 7 replies
This is interesting, after a reboot the Java Console tells me its the version "10.0.0.147" of the Java-Plug-in, the JRE has version "1.7.0-b147" now, I am sure it was 1.6.0_25 before. I still get the same FRM-92095 though.
In my frmweb.cfg I use the following lines:
If I understood the documentation right, this should give me dynamic versioning, but requires a JRE with alteast version 1.6.0_24, but it has to be a version 6 JRE, not 7.
You are right this is not supported ;o) - its currently logged as a bug (11782681) and will be fixed as part of our certification tests for Forms - our next certification will be announced in due course.
I also tested JRE 1.7.0 with Forms 10.1.2.3.1 + Forms bundle patch 12433970 and found something similar:
- Forms is configured to use JRE 1.6.0 (1.6.0_26 installed here)
Running this with Java Plugin 1.7.0 / 10.0.0.147 and the next-gen Java plugin (plugin2) activated - which is the default - executes the Forms applet (with JRE 1.6.0_26) fine without any obvious errors. The only thing I found: On the Java console the Java system property deployment.jpi.mode.new is reported with value "true" but the applet's call to System.getProperty("deployment.jpi.mode.new") returns null.
(we test our system requirements which state the next-gen plugin as of 1.6.0_10 must be used. However, the test now reports an incorrect result)
Running the applet with Java Plugin 1.7.0 / 10.0.0.147 and the next-gen Java plugin disabled executes the Forms applet with JRE 1.6.0_26 but System.getProperty("deployment.jpi.mode.new") incorrectly reports "true". And the Java console doesn't react to a key press "s" (to print the system and deployment properties).
I filed Java bug 7072674 for this today (not published yet).
- When Forms is configured to use JRE 1.7.0 I get the same FRM-92095 as you.
Grant, thanks for the Forms bug id. Can you make it visible in Metalink so we can follow this? Regarding the next certification: are there any plans to support IE9 with Forms 10.1.2.3?
thanks for testing this.
Note: Java 6 goes eol in less than 12 months from today!
Now does that mean that we who have standardized on jre6 to deploy forms can continue get updates from
oracle support, if we have accounts? I just got this stuff working and it took a huge amount of effort. I was really hoping for a stable working experience for longer than 11 months into the future.
Problem is explained here as well as possible solutions while waiting for official patch :
I'm transitioning to a new laptop that had JRE 7 factory installed and ran into the Jinitiator too low problem. I just installed jre 6 update 31 side by side with jre 7 and it works just fine now. This is on Windows 7 64 bit (though running 32 bit JRE) with IE 9.
For IE there is a way to keep using the JRE 6 while having JRE 7 installed. You can use the jpi versioning parameter. (THIS WILL NOT WORK IN FIREFOX NOR CHROME)
scenario.) User has JRE 6 installed and installed JRE 7. (native install will cause both versions to coexist on the system)
In the formsweb.cfg we allow users to use dynamic jpi versioning. As a result the highest available JRE version will be used. (JRE 7)
Dynamic CLSID formsweb entry:
Use "Family" CLSID.
This setting will require a valid JRE version belonging to the same major release. (Family) The following value will require JRE6 plugin to be used.
[How Do The Jinitiator And JPI Parameters Work In A Forms Configuration [ID 444105.1]|https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=444105.1]
[Deploying Java Applets With Family JRE Versions in Java Plug-in for Internet Explorer|http://www.oracle.com/technetwork/java/javase/family-clsid-140615.html]