rom: Kumar Srinivasan <  xxxxx@xxxxx  -mail1.sfbay.sun.com>
Subject: Re: 64-bit JavaWS


MIME-Version: 1.0
Content-MD5: o+JhxEuuKhwT7RDcZxIiog==

Steve,
Sounds  customer , 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.
Thanks!

>Kumar,
>
>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.
>
>-Steve

N/A

64-bit support is deferred to a future release.
  xxxxx@xxxxx   2005-06-01 21:39:43 GMT
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
Posted Date : 2009-01-27 14:43:53.0

A growing number of folks are running x86_64 Linux as their desktop. It would be great if we could also run Java Web Start.
If the rest of Java is compiled to 64-bit, how hard could it be to recompile JWS?

I'm using a dual Opteron 64 at work, and I'm thinking of buying a Compaq AMD 64 laptop.  Clearly, AMD 64 is very much established as a desktop cpu, and can no longer be marketed as some sort of exclusive magic server-only chip.

By delaying this RFE any further, we'd be seriously harming java on the linux desktop (of which a considerable number run 64 bit). This RFE needs must be expedited. 

Console redirection on Sun's x4200 servers _requires_ javaws. It's a must, considering Sun sells very nice Ultra 20 & 40 workstations with amd64.

WAKE UP CALL!

um... this is REALLY ridiculous!  I just downloaded the most recent amd64 1.5.07 jdk update.. and still no javaws/plugin!!!  I see that this bug is "open" since 2002? 

So basically,   I can run all of my PC on amd64 (linux, database, all apps etc), even the netbeans ide runs great, but I can't use javaws or the java plugin with the 64bit java..   

I'm reduced to installing the i586 version as well, and linking my firefox to that plugin, and running the javaws from that version.  Probably a stupid question, but WHY???  All our new desktop PCs are AMD64 procssor based, NOT servers here (those are more opteron, or multprocessor based, but some are amd64 of course).  

cheers... we love java.. but there is this new DESKTOP platform out there guys.. and you aren't supporting it  fully!!!

Opps! My customers use JWS for their Accounting/Book keeping application. They depend on this application. I'm suggesting them moving to Suse Linux and use x86_64 based computers. What a mistake!

At least, you could advertise people downloading Java for x86_64 platforms that there is no support for JWS... with big letters!!

This would be useful to me if it were included.  Ken Larson.

Scandalous!
javaws is not working on x86_64 architecture in latest jdk snapshot (1.6-rc-beta103) either. 
Nenad Bulatovic

It's absolutely ridiculous that Sun makes people "vote" to support the concept of WORA.

It's absolutely ridiculous that Sun makes people "vote" to support the concept of  WORA.

/aol  (WORA)

/aol   (WORA)

There are many amd64 and em64t machines now.

Sun should realize the priority of this RFE is very high. Java web start on amd64 should be added to the current release right now!
We are waiting it for a long time and can't wait it in the future release that no one knows the actual release date.

We want to start deploying our java medical imaging applications (which require vast amonts of RAM, hence are 64 bit) via web start, but are stymied by this bug (as well as all other lame aspects of 64 bit JRE like not being installed in the path, , as well as there being no 64 bit Image I/O support on Windows, etc.) - as a long time proponent of Java over .NET for medical applications I want to keep using Java, but at this rate I am going to give up.

At least, you could advertise people downloading Java for x86_64 platforms that there is no support for JWS... with big letters!!

We are deploying the GUI CrossFTP client using java web start, and linux boxes require Java web start for x86_64 platforms. Please improve javaws' support for desktop.

This is just silly. I have a 64 bits dual processors system, everything in my system is 64 bit aware, but I am forced to use  java 32 bits because I need webstart!
Don't get me wrong, I LOVE java and I think you are doing a fantastic job with it (from the technical point of view), but there are thinks like this that really  should be fixed - they give the impression you just don't care.
This request has been open for very long time,  64 bits machines are quite common now, I understand there are issues with 32 bits native libraries, but not supplying ws in 64 bit jse is not a solution.

Uhhh, it's hard to buy a computer today that doesn't at least support x64. It takes 5 years to do the 1 week of work (surprised if it takes that long!) to recompile an app for 64 bit and fix any incompatibilities?

Why is this still an issue? Is there a good reason on Sun's part? If this is so problematic, maybe opening javaws source would fix it!

Its 2007, closing in on 2008, 64bit webstart and applet support should be here already. 

Looks like it must be really really hard to port this feature to 64bit.

LOL!

This bug just turned 6, come on sun! this is pathetic!

... well at least I don't have to worry about 64 bit native libs for my web start application.

Hmmm ... is it really THAT difficult to fix? I'm deploying a WebStart application within our company in a mixed 32bit/64bit/Linux/Windows environment. 
Thought that's what JavaWS was made for, but apparently Sun is dropping it's support for WebStart. How sad, I guess I'll have to start looking for alternatives.

Can this RFE be comitted to the dolphin (Java 7) release? This can still take some time, but the bug is already more than 6 years old, so knowing it will be in the next release would at least allow some sort of planning reliability.

Okay, so where's the source?  Maybe the community can make it work.  This is pretty dang ridiculous.

I guess the majority of desktop Linux users are using the 64 bits version.  
I really would like to know  why key features of Java like Applets and WebStart are missing in Linux AMD64.
This is not critical on Win64 as it runs IE and Firefox as 32 bits applications, so JRE 32 just works fine. 
This is not the case of Linux AMD64.  All  distros comes  with Firefox 64.

I agree with the description that Java Webstart binary doesn't need to be 64bit at all, as long as it has the ability to launch with 64bit JDK, with the associated deployment library usable under 64bit JDK will suffice.

Although majority of GUI application does not need to use 64bit JDK to run, we are seeing a number of internal application would benefit from being able to run under a 64bit JDK due to their heap requirements.

If Sun is uninterested in supported 64-bit WebStart, why not opensource it or at least release an unsupported beta...

Seriously, Sun! This isn't rocket science... Web Start deployment is essential to many of us, and with more and more people moving to 64-bit this is badly needed.

a solution for archlinux 64 bits can be found here: http://even.archlinux-br.org/blog/plugin-java-64bits-com-jre-da-sun-para-archlinux
written in pt_BR.
best regards.

Q: How many Sun engineers does it take to screw in a 64-bit javaws lightbulb? 
A: None, and more than 7 years of time already!  I guess they're waiting for the x86_128 processors!
A2: Just 1 engineer . . . in 64 years.
A3: What?  64-bit?  We're still working on the 16-bit version!
A4: None, it'll take a Microsoft Engineer to do it.  We're just waiting for them to buy us out!
A5: What? You mean someone actually uses this Java stuff we've been doing?
A6: 144.  We're just waiting for the economy to improve so we can afford to hire them on!
A7: None.  It'll take 1 Open Source developer 2 months to do.

It looks like it might be coming!!  See: https://jdk6.dev.java.net/6uNea.html