JDK-4626735 : Support Java Web Start on 64-bit AMD and Intel
  • Type: Enhancement
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 1.2.0,5.0
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic,linux,linux_2.6,windows_nt
  • CPU: generic,x86,itanium
  • Submitted: 2002-01-22
  • Updated: 2009-01-27
  • Resolved: 2009-01-27
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Related Reports
Duplicate :  
Duplicate :  
Duplicate :  
rom: Kumar Srinivasan <###@###.###>
Subject: Re: 64-bit JavaWS
To: ###@###.###
Cc: ###@###.###
MIME-Version: 1.0
Content-MD5: o+JhxEuuKhwT7RDcZxIiog==

Sounds good, lets capture this information and put it up
on the JaWS internal home page so that we can refer to it 
when we decide to cross the bridge.

>Andy and I were thinking about 64-bit JavaWS, mostly along the lines
>of what you & I talked about on the phone.  So here's what we think
>we would have to do, to get 64-bit JavaWS.
>1. Recompile JavaWS JNI code under 64-bit & bundle it appropriately
>   so that System.loadLibrary() can find it under 32 or 64 bit.
>2. (optional but desired) Add JNLP field to select 64-bit VM so that
>   JavaWS application developers can deploy a 64-bit JNLP application.
>   This requires a JNLP spec change.
>3. Modify JavaWS application native lib JAR handler to correctly
>   extract 64-bit native libs.  Modify JNLPClassloader to correctly
>   setup environment so apps using System.loadLibrary() can find
>   their native libs.
>Notes: We don't have to recompile any front-end (javawsbin) native
>code because 32-bit process can launch a 64-bit (Java in this case)
>process.  This is true on Solaris and I assume it's true on Windows.
>I'm also assuming that 32 and 64-bit native libs can coexist on
>Win64 in a way that System.loadLibrary() can find the appropriate
>libs (something analagous to sparcv9 subdir on solsparc).
>Also, 2 is optional because anyone who wants to deploy to 64-bit is
>probably in an enterprise environment and can control which JREs are
>available to JavaWS.  Therefore, they can guarantee their app will
>run on 64-bit by tweaking version strings in the app & in the JRE
>configuration.  This is just a workaround though - the correct
>way would be to implement #2 and add a JNLP tag.

EVALUATION 64-bit Javaws and Java Plugin support have been implemented in JRE 6u12, it suppot on both Window 64-bit and Linux 64-bit. Closed this bug as duplicate of bug

EVALUATION 64-bit support is deferred to a future release. ###@###.### 2005-06-01 21:39:43 GMT

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mustang