Problems running Swing application with IDEA 8M1 - java

Is anyone else having trouble running Swing applications from IntelliJ IDEA 8 Milestone 1? Even the simplest application of showing an empty JFrame seems to crash the JVM. I don't get a stack trace or anything, it looks like the JVM itself crashes and Windows shows me a pop-up that says the usual "This process is no longer responding" message.
Console applications work fine, and my Swing code works fine when launching from Netbeans or from the command line. I'm running Windows Vista x64 with the JDK 1.6 Update 10 beta, which may be a configuration the Jetbrains guys haven't run into yet.

Ask your question directly on the IDEA website. They always react fast and the problem you have is probably either fixed or documented.

I have actually experienced problems from using the JDK 6u10 beta myself and had to downgrade to JDK 6u7 for the time being. This solved some of my problems with among other things swing.
Also, i have been running IJ8M1 since the 'release' and I am very satisfied with it, especially if you regard the "beta" tag. It feels snappier and also supports multiple cores which makes my development machine rejoice. ;p
Anyway, i use WinXP32 and IJ8M1 with JDK 6u7 and that is afaik very stable indeed.

IDEA 8 Milestone 1 is a beta(ish) "based on a new platform". This may have changed the way that swing is handled. Also you are running a beta JDK.
You will probably get more help/submit a bug at the Jetbrain forums unless they are on SO also. Here is the bug tracker link

Related

Issues running Java SWT app on macOS M1 machine

I've been using the "Java SWT version" of an app called PasswordSafe for many years on my Mac machines. It has been rock-solid. I've just bought a new iMac with the M1 processor because the "Fusion Drive" in my 2017 vintage iMac died. I installed Java, and the latest version of Java PasswordSafe on my new M1 iMac. Unfortunately, something is not working properly: The "top level" GUI looks normal, and it can open my PasswordSafe database file, but it presents a very garbled interface when I (for example) try to edit a password entry in the database.
I don't know much about Java - or SWT - never having written a single line of code in either. I've contacted the author of PasswordSafe, but he tells me that Java PasswordSafe is no longer being maintained.
In brief summary, my question is, "In trying to repair this broken-ness, Where should I start? I realize that's a very lame question, but let me try to explain what I'm trying to learn:
AIUI, Oracle no longer supports or provides a JRE or JDK that's compatible with the M1. I've read that a third party does provide these tools, but apparently Rosetta allows the Oracle tools to run on the M1. In fact, during installation of Oracle's JRE/JDK, I saw a brief popup notification re Rosetta. My conclusion from this is that the Java software components (JVM or whatever) are operating, although sluggishly, and perhaps with other flaws due to Rosetta imperfections?
The assumption that Java is more or less operational leads me to wonder about SWT. There is another recent question here on SO re issues with the SWT, but in my case, I get no displayed runtime errors - only a mangled interface. But then perhaps I'm not looking in the right place for those errors?
I've done a bit of research on the status of SWT on M1, but found no clues on their website. I haven't found any clear answers on whether or not SWT runs on M1 or not.
So that's what I've got - a very ill-defined situation with no obvious way ahead, and no experience in SWT or Java to guide me.

Why does Java 8 from Netbeans hijack Java 7 running in my browser?

Java 7 is my system default JRE. All of my web browsers are configured to invoke JRE7 on a new instance, as default.
Netbeans fires up Java 8 on a new instance, as its 'isolated' default (isolated in terms as from the rest of the system).
Consider scenario: Chrome is up and running fine, then I'm inspired to code and then open Netbeans. When Netbeans loads, Chrome's java gets funky - I can no longer interact with javascript applets (such as chatango handshakes don't happen, scrollbars become non-responsive, any a host of other anomalies occur). I take the step to reinitialize Chrome, and frames either don't load at all, time out, or stack out of the page's "defined" layout.
Keep in mind, I am NOT (purposely) running any java 8 programs outside of Netbeans.
Why does this occur? My suspicion is that JRE8 replaces the pointers for API calls in the system env.. I would have assumed that the JRE sandbox would have extended to that machine version's libraries, but that seems not to be the case. Is this a fundamental incompatibility, or a bug? Must I suffer it until my choice browser developer releases a Java 8+ compatible browser? Am I the only one that even experiences this?
(I appreciate any feedback that is thoughtful, and not around the lines of LMGTFY or other useless quips)
Thanks!
I have seen something similar happen with Firefox. The reason was a faulty graphics card driver.
Both applications, Firefox and a Java application were using 3D acceleration which resulted in a lot of visual artefacts and crashes later on.
You could try the following:
Disabling any acceleration features in Netbeans (Use sun.java2d.noddraw and sun.java2d.d3d)
Disable acceleration features in Chrome.
Update your graphics card driver

Eclipse for Mac OS X

I am Java developer who is using Eclipse on a X86 computer to code. I am considering to buy for other reasons an Desktop Mac computer and I would like to use this computer to do my coding work. I know there is a Eclipse version for Macs, I am asking if there may be some problems/issues related to Macintosh computers. Thanks!
It really depends what you'll be doing.
In terms of the IDE, it will work just fine and you can copy your files/projects over and they will "just work".
However, there are some things you need to be weary of:
Key mappings might be different
You won't be able to do any JavaME programming as there is no Mac toolkit for that.
If you're doing Swing development, make sure you test your code on your target environment as things might look different.
Other than that, Macs work fantastic for Java coding.
No, Eclipse works just as well on a Mac as on a Windows or Linux computer. Key bindings are different though; if you're used to the shortcut keys of Eclipse on Windows, you'll need to get used to different shortcuts on the Mac.
Apple just announced that they are deprecating their Java platform. That may cause some problems in the future. Update: however, I have seen that Eclipse works with the soylatte OpenJDK port.
http://developer.apple.com/tools/eclipse.html
and if you want the non-Apple-bs experience:
http://cdtdoug.blogspot.com/2010/04/mac-gets-no-love.html
From my personal experience, Eclipse actually works better on OS X and Linux than it does on Windows. I'm a professional plugins developer and I do all my coding on Mac. I blog about Eclipse and Mac related topics, so I invite to read it.
Adding to the limitations mentioned in other answers, if you have specific plugins that you need, not all support Macs, although most. For example, The Eclipse TPTP (short for profiler) project doesn’t profile on Mac. There are alternatives in most cases, though (AFAIK, not free in the case of TPTP).
Personal experience for RCP-development: 2G of RAM are not enough (at least not for our project), so the current MacBook Airs are not suitable at all for development. But then, you're talking about desktop Macs anyway, so if you can get the >2G, it should be fine.
During the 64bit transition phase, there were some glitches with missing 64bit Cocoa, but that has been resolved. Some of the extensions may be platform specific: currently, TPTP (Test and Performance Tools Platform Project) still has some limitation.
eclipse for mac works exactly as you know it from your pc. the only thing that differs is the arrangement of some keys (the # is on L, the arrangement of the braces differs a bit)
Eclipse works fine, but with different keybindings.
I have found that sharing files with other computers - e.g. through a source repository - may give you character set conversion issues. If you stay with pure ASCII in your source you should not have any problems.
You can download Eclipse 3.6.1 from eclipse.org directly (where your platform is autodetected) or from http://download.eclipse.org/eclipse/downloads/drops/R-3.6.1-201009090800/index.php#EclipseSDK
I would suggest getting the Java EE version from the frontpage. It contains web stuff I use regularily.

java web start alternative [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
We're looking for an alternative to Java web start that effectively does the same thing, just better implemented. We're having massive trouble with it. We have a few offices of XP desktops, all slightly different and so far only a handful have worked without serious tweaking. Problems are to do with not playing nicely with the proxy settings (using direct connection in Java control panel allows it to work), refusing to run when params like "-Xmx" are set but running fine when they aren't (until it runs out of memory) and other odd problems that we can't fix.
The way web start works is exactly what we want, i.e. connecting to a server that has the app, downloading anything that's changed, keeping a cache of jars, etc. Other teams here use 'clickonce' for their C# apps and it does effectively the same thing but seems to be less trouble.
I'm convinced we're not the only people to have run into this but searching around doesn't really show any alternatives. We've looked into writing a stub local application that is essentially just a URLClassLoader that loads up our app over the network on the fly but unfortunately that's too slow from other offices. Anyone have any ideas?
Thanks
Update
In case anyone is curious as to what eventually happened, we gave webstart another month or so but continued to run into problems so we implemented our own version. It's basically just a stub that has a URL class loader that you point at a webserver. It's < 200 lines of code and it has been working perfectly for months. It's not ideal but until someone improves webstart we'll stick with it.
Update 2018
So, several years later and I'm working on a new project with the same problem. Instead of writing our own webstart implementation this time we're using getdown. We've found it to be a vast improvement over web start and it's been working really well for us.
My company is also experiencing webstart pain especially with JRE 1.6 update 19 and 20. Our problems revolve around the Mixed Code security warning. (everything is properly signed and the problem is intermittent)
Anyhoo, I stumbled across getdown by threerings. I haven't tried it yet, but seems promising https://github.com/threerings/getdown/wiki
I use JWS extensively in my company. The ONLY real problem that I've seen with JWS occurs only when you try to run JWS from cache AND your client's machine has just upgraded to a newer version of Java. The application will fail to launch with a "Unable to launch", "cache file not found" error or something similar.
There are two ways that I use to fix this problem: I either clear the cache and have them reinstall the app, or I simply have them click on the URL again from my website (easiest for my users). In both cases, the problem fixes itself. This would explain why several developers here never see this problem, most likely because their users always click on a URL instead of the installed launcher.
As a workaround, and in some of my mission critical apps, I use either of the following inside a script:
java -jar netx.jar -jnlp http://url/to/my/launch.jnlp
or
javaws http://url/to/my/launch.jnlp
where netx is a third party library.
It is not the prettiest solution, but for me these work 100% of the time.
Now, if I could only figure out how to get the desktop shortcuts from not going to hell... but that's a discussion for another time.
I find all your probles quite strange. i've worked during a certain time in a company distributing its trading software using JWS, and it always worked really fine. Have you considering taking a look at the unofficial Java web start FAQ before dropping the whole technology ?
we also use JWS a lot and since around 1-6_19 it realy started to be a pain. Some apps started up 1-6_19 others didn't then we updated to 1-6_20 and it was sort of the other way around. Then update to 1-6_21/2/3/4 and problems only changing. We might give up. It looks like the development team since Oracle took over changed. Otherwise there is no other explanation to make JWS worse then better.
GetDown seems to be flaky as well. I just tried some of the game websites they advertise as examples in action. They all failed to load in my Firefox. Maybe my Java to Firefox integration is to blame? I've got JRE 7 32-bit installed after JDK 1.6 64-bit.
In general Web Start problems and poor user experience many times are related to the way Java was installed on the users machine. On Windows I noticed that if you install older version of Java after newer (expecting both will co-exist), I start getting problems running applets and WS applications.

Java Applet fails to load with MSJVM

We have a web application that uses a third party java applet for encryption and authentication. It's always been a bit finicky, but right now it has me pulling my hair out.
Over the weekend, we migrated to a MS Load balanced cluster, upgraded our DNS, and rolled out all of the MS patches. Now the applet fails for all of our users who are using the MSJVM. The solution is simple, we just have them install a recent version of Sun, but I cannot figure out why the MSJVM is failing.
Every other configuration works (Firefox, Safari, IE with Sun on Window, Linux or Mac) or I can get to work with a reasonable amount of effort, but nothing I can do will make MSJVM work.
I understand the MSJVM is depreciated, but nothing on the site (http://www.microsoft.com/mscorp/java/default.mspx) indicates that it should no longer work. I am looking for information that will either allow us to make the MSJVM work so we can determine if it's easier to fix or install Sun, or that I can use to force our desktop configuration team to update the company policy on the MSJVM.
Thanks
Update 2009.10.19: It's clear that something disabled the MSJVM. We should reject users who are using that JVM but it hasn't been a priority to update the site. We've just been waiting them to fail and then directing them to install SUN.
Most likely the Java version used by your applet is superior than the one supported by the MSJVM.
I have followed your link but I could not find what that version was. I think is something previous to Java 1.2 ( like java 1.1.17 or soemthing like that )
If you happen to have an error message or a screenshot, troubleshooting would be easier.
But, yes, the definitive answer would be to use the latest version of the Java plugin.
I remember there were scripts ( javascript ) tha help to identify the Java version and provided a link to download the latest one, but I cannot find it now. Take a look at java.sun.com and see if you can find it.
Microsoft's JVM was never Java-compliant: http://en.wikipedia.org/wiki/Microsoft_Java_Virtual_Machine
The MSJVM never got beyond Java 1.1.x, which is very old. So any functionality which appeared with Java 1.2 (Java 2, as it was called), such as Swing, won't work. With the MSJVM, you're pretty much limited to AWT for the UI.
Licensing issues and lawsuits triggered by incompatibilities introduced by Microsoft (such as the delegate keyword) meant that Microsoft never took their JVM further.
As of July 30th 2009 I think it was after being extending numerous times the MS JVM is finally no longer supported and at end of life.
A workaround I have seen used before if you absolutely cannot rewrite it would be to use a custom VB script to launch the application, The script would do a quick change on the registry to make MSJVM the default when the app was launched then swap it back to whatever the setting was for normal operation.
i.e.
Set Registry for MS JVM as default
Launch Application
Reset Registry for Sun JRE 1.5.0_X as default.
I dont have the code handy, you should be able to find VB registry modification with a quick google. I can probably dig it up if your stuck.

Categories

Resources