Discoverer 10.1.2.48.18 and Java 1.4.2_06

Question

Hi Discov Gurus,
We have discoverer Version 10.1.2.48.18 installed on the server. When some user wants to access discoverer reports he goes to Internet Explorer and gives the URL that points to discoverer PLUS.
DIscoverer PLUS works default with Java 1.4.2_06 but if the User PC has multiple Java or JRE versions the Discoverer Plus opens with New JRE version say JRE 1.6.0_06.
The problem is the Java Applet hangs sometime with the new JRE version. I cannot remove this new version of JRE as
some other applications need this new Version of JRE.
Question is how can i force discoverer to use the old JRE 1.4.2_06 version.
Thanks,

Answer 1

Hi,
I had this same issue when upgrading from 9.0.4 to 10.1.2.2. Someone else in the forum had a solution. You could probably search for it. However, here are the details:
The fillowing are the notes from Oracle:
Applies to:
Oracle Discoverer - Version: 10.1.2.2 to 10.1.2.3 This problem can occur on any platform.
Symptoms
The user interaction performance using Discoverer Plus 10g (10.1.2) when configured with Sun java plug-in (JRE/JVM) 1.6.0_03 or higher.
Every action in Discoverer takes longer. For example:
displaying the Create/Open Workbook wizard
displaying the Help > About window.
The problem does not exist with JInitiator or with Sun plugin 1.4 or 1.5 and earlier versions of 1.6
JRE 1.6.0 - works correctly, runs with 1.5.0-like speed JRE 1.6.0_01 - works correctly JRE 1.6.0_02 - works correctly JRE 1.6.0_03 - here the problem is observed for the first time. The issue is then observed in all subsequent versions (e.g., _04, _05, _06, _07 and the new_10)
The problem does not exist when an entry for the Discoverer server exists in the local hosts file on the client PC (C:\WINDOWS\system32\drivers\etc\hosts).
Cause
Sun's Java plug-in performs reverse DNS lookups when connecting to the Application Server. This can be observed with a network sniffer trace (Wire Shark).
There is a change in the DNS handling in Sun plug-in 1.6.0_03 and higher.
This issue may be more prevalent if you are accessing Discoverer Plus via a firewall, proxy server
Solution
To implement the solution, please execute the following steps:
Ensure the external facing IP address of the Discoverer server has a reverse DNS entry in the DNS server.
For example:
nslookup <IP address> must resolve to the <machinename.domainname>
and
nslookup <machinename.domainname> must resolve to <IP address>
An alternative or temporary solution would be to add an entry to the local PC host file as described above.
Hope this helps,
Nancy