Use IBM JVM in presense of 64 and 32 bit

Question

Hello,
I am running WIN7 and have both the 32 and the 64 bit IBM JVM installed on it, the 64 bit IBM JVM being the system JVM. The latter is mandatory for various applications.
I am experiencing problems with the Java plugin of Firefox (version 31.5.0). The plugin is listed as "always activate" in the Add-ons Manager, and when I look into pluginreg.dat, it looks like the correct (i.e. 32 bit) version:
npjp2.dll|$
C:\Program Files (x86)\IBM\Java70\jre\bin\plugin2\npjp2.dll|$
10.71.0.0|$
1414303728000|0|0|0|$
Next Generation Java Plug-in 10.71.0 for Mozilla browsers|$
IBM Developer Kit for Windows,Java,1.7.0|$
Nevertheless, Java content in an application does not show up. When I click on the little Lego brick left of the web address after I clicked on the link requesting the Java-generated content, it says "IBM Developer Kit for Windows is enabled, Continue allowing" but nothing happens, even when I click on the "Continue allowing" button. What is supposed to happen is that a new window opens displaying the Java-generated content. The web-site is allowed to open new windows, and does so for non-Java content, so it cannot be just popup-blocking which prevents the Java content from showing up.
The last thing various support entries here pointed me to is the "Configure Java" panel. I ran it both for the 64 bit and 32 bit JVM. For both, when I try to enable "Mozilla family" for "Default java for browsers" under the "Advanced" tab, the setting does not save. Which perhaps seems correct for the 64 bit JVM, but not for the 32 bit JVM. So I cannot verify whether this setting would help. On the security tab, the site is listed on the exception site list, so this shouldn't be a problem.
Any help or ideas are greatly appreciated!
Regards+thanks, Irene

Answer 1

Hello,
We do have 64 and 32 bit heteregeneous landscapes with Windows 2000 32 bit x86 and Windows 2003 64 bit ia64.
There are no problems for transports between 32 bit and 64 bit systems.
Problems can happen with differences between the différent operating systems.
We had, for instance, an issue with some scripts (bat files) because Microsoft had the very strange idea to change the syntax of the DIR command between win 2000 and win 2003. If your script need to work in the same way in both OS, you have to detect the OS and have the 2 syntaxes in the script...
We also have systems with a 64 bit CI and 32 bit dialog instances.
Here, the problems may be with memory hungry programs running OK on the 64 bit system and short dumping on 32 bit app servers
We had also a bad surprise with Win 2003 IA64 servers when we discovered that some SAP software is not available on this platform. Exemples : Adobe Services or TREX.