All of a sudden, after years of using OS X Java without any problems, now, when starting ActiveMQ from the commandline a 'bin' application window appears. 'About bin' -> 1.0. When starting tomcat from the commandline an org.apache.catalina.startup.bootstrap window appears. Frustrating as they steal focus from the terminal. Never happened before. Just wondering if anyone knew why they might be suddenly appearing. I've seen lots of references to headless but this is the OS doing this for no apparent reason, rather than the java apps.
Well who knows what happened to Java but this answer provides the solution:
How to set java system properties globally on OS X?
i.e.
~/.profile
export _JAVA_OPTIONS=-Djava.awt.headless=true
Related
This isn't coding related, I hope that's fine. I've been trying to run a modpack through techniclauncher, but I can't get the launcher to even open.
If I have java 64bit installed, anything I open that uses java just stays in the taskbar/task manager for about 3 seconds, then closes with no error message. 32 bit java works, but I need 64bit so I can dedicate more than 1GB of ram to a modpack.
I am on Windows 10 x64 build 1903, my java version is JRE 8u231 but no matter which version of java I install the problem persists.
Things I've tried:
uninstalling/reinstalling
Using revouninstaller from Britec's tutorial
Installing an old version of java (Java 6 had the same problem, same with older versions of java 8)
jarfix
updating graphics drivers (gtx 1070 currently on 441.41)
I have no idea what caused it; it worked fine a few months ago and when I tried to launch a modpack yesterday the launcher wouldn't start. Even the java control panel doesn't work. Any help would be appreciated, thanks in advance!
[EDIT: screenshots of event viewer]
https://gyazo.com/70c9b5599fe3331e927171a6ac279e25
https://gyazo.com/1786c8011182933e3671481966394507
https://gyazo.com/da029d89cfdf0da6a3af4cb5a4c9b083
https://gyazo.com/a0a377129d51ee7b51a4b2aefce8723f
https://gyazo.com/4ad84929c5f1c0e93834289616f4afb2
This all happened at about the same time when I tried to open the Java control panel
The error message seems to indicate the crash has something to do with graphics / Direct3D. Finding the root cause might be difficult, but one thing to try would be updating your graphics drivers.
Another thing to try would be to disable Java's graphics hardware acceleration. The System Properties for Java 2D Technology page has instructions on how to do this. Under Windows, to configure globally for all launched Java applications, set the environment variable _JAVA_OPTIONS to -Dsun.java2d.d3d=false to disable Direct3D acceleration.
Here is my setup:
System76 Gallago Pro
Fedora 30
OpenJDK 1.8.0_201 (I did try Oracle as well)
I installed per IBM's instructions, using the installer script from the command line. I went through the installer menu and got to the success screen. I have done this a half dozen times on other machines and with OS upgrades on this same machine.
When I use the super key to find the program it is there; I click on the icon and my box returns to the desktop - but i Access doesn't start.
If I start via the command line using the start script, I get MSGGEN045 - A graphical user interface is not available.
If I run the java program directly
java -Xmx1024m -jar /opt/ibm/iAccessClientSolutions/acsbundle.jar I get the same message as when using the start script.
How can I get past this error? Or,what else can I do to track down what is happening?
I've had two issues when running iACS on Fedora. The first was the OS had a headless JVM installed by default. The second was something to do with sound.
Based on "MSGGEN045 - A graphical user interface is not available", I'd suspect a headless JVM.
HTH
Edit:
I checked for the headless JVM at the direction of IBM support. I don't remember the exact wording, but the name of the installed package was a dead giveaway. A simple "rpm -qa" was all it took.
I don't have anything Fedora specific but it seems that you either didn't install a Java Runtime Environment or just a headless version of it (jre-headless). Install a full JRE and everything should be fine.
You could check this with yum:
yum list installed | grep jre
Fedora is running wayland and not X11. Java doesn't play nice with wayland as of yet. As far as I know there are no plans yet to fix that. This is a good place to start https://www.ibm.com/developerworks/community/forums/html/topic?id=1b366edf-0e70-40d5-8d92-30d401edd97a
I have Mac OS 10.9.3 installed, and when entering java -version in the Terminal it shows:
java version "1.7.0_55"
Java(TM) SE Runtime Environment (build 1.7.0_55-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.55-b03, mixed mode)
My problem is that applications which use Java don't work when double-clicking on the .app folders. For example, TuxGuitar just does nothing, and Eclipse gives the No Java virtual machine error. When launching them with the command
open TuxGuitar.app
open Eclipse.app
.. they work both. What could be the problem?
I had the same problem and I fixed this by installing a patch from apple at
http://support.apple.com/kb/DL1572?viewlocale=en_US.
Something is different in the environment of the shell you get in Terminal, compared with the environment Finder.app is running in. You need to figure out what's different.
A few relevant facts:
OS X windowed applications do not read your shell startup files like ~/.bash_profile, so changes you make there to your ${PATH} or ${JAVA_HOME} will not affect windowed applications.
It used to be the case that OS X windowed applications read ~/.MacOSX/environment.plist but apparently that's no longer true in 10.9 Mavericks; see for example this other StackOverflow question.
Java on Mac OS X keeps changing, and can be installed and controlled in a variety of ways. So it's hard to give a general answer; it depends on the history of your system.
Java Mac GUI applications can place restrictions on which JVM will run them, in Contents/Info.plist of the application bundle; look for key JVMOptions and in particular at JVMVersion within that.
Things to try:
Open System Preferences and see if you have a Java Control Panel. If you do, you can use it to select which JVMs are available for running GUI applications, and in what order they will be tried.
Open a "clean" shell by running env -i /bin/sh and then try running /Applications/TuxGuitar.app/Contents/MacOS/TuxGuitar inside that shell; you may get a useful error message.
Use /usr/libexec/java_home -V to see a list of JVMs the OS knows about.
/usr/libexec/java_home -v 1.7 to see which JVM the OS would choose for an application that needs Java 7.
I have the exact same issue after upgrading to Mavericks and I noticed it with muCommander.
As I can run the app manually from the command line, I have the following workaround which I am quite happy with:
Create a shell script workflow using Automator:
Spotlight -> Automator -> Workflow -> "Run Shell Script" -> [shell command]
Then save the Worflow, but instead of .workflow, choose file format Application. Now you have an App you can double-click.
Addendum 1: This is not the answer to your original question as I don't know exactly what the problem is (jbyler's answer might point you in the right directions here).
However, I assumed that your question implies Can I get double-click to work again?, and this workaround helped me to do that.
Addendum 2: I have JAVA_HOME set up and the same version installed as you have. This is a screenshot for the Workflow in Automator:
I managed to fix this by installing the developer kit.
http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
I had the same problem. Open the /Applications/TuxGuitar.app/Contents/MacOS/TuxGuitar with your favourite text editor (it's a shell script) and add "-d32" option to the last line "exec java ...." (position doesn't matter). This will launch java in 32-bit mode. Alternatively you can launch TuxGuitar with "-d32" option (it passes arguments to java) from the terminal.
I'm used to run (for testing purposed) java applications from IDE. Start, verify, stop execution in output window in Netbeans. This works flawlessly under linux and windows but under mac osx for reasons beyond me the despite execution being stopped (red stop button greyed out, etc.) the java process persists in the background.
It this some inherent property of mac osx? (most of the applications stay running but I would assume that when I stop java from IDE it should basically kill it)
It is a bug in NetBeans way of launching apps - https://netbeans.org/bugzilla/show_bug.cgi?id=232322
Eclipse RCP plugin application which has a mix of SWT and swing/awt windows getting crashed randomly in Windows 7 64 bit. Especially when i open SWING/awt dialogs. I cant able to debug even when i use -consoleLog in .ini file since it hangs as well along with the application.
The build details are given below.
JRE Version : 1.6_u04
NSIS Installer
.ini config : -vmargs-Xms64m -Xmx1024m
When i change the jre to 1.6_u18 it works fine. As update 18 provides win 7 support. But still some window freezes :(
If i reduce -Xmx value to 512m then it works properly.
Rarely Java Heap space problem also arises.
Pls guide me the proper way of fixing this issue.
Also let me know if we need to adjust Heap space in OS ?
The application installer comes along the with bundles of JRE 1.6_u04 itself. Will there be any issue of max heap size in windows 7?
Please advice !!