New answers tagged java
Try /nix/store/...-oraclejdk-8u60/ Intellij expects the root of JAVA_HOME, and appends bin/java itself.
According to my blog my solution was set JAVA_OPTS with $CATALINA_HOME/conf/tomcat7.conf, e.g.: # You can pass some parameters to java here if you wish to #JAVA_OPTS="-Xminf0.1 -Xmaxf0.3" JAVA_OPTS="-Xms512M -Xmx1024M -Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=9090 -Dcom.sun.management.jmxremote.ssl=false ...
I was reading my question and found the answer in it. This is what I have done: I Undone all the changes to /root/.bash_profile and /etc/profile Then I created a folder called jdk in the /user/local/ folder like so mkdir /user/local/jdk Since this is were the jdk is expected to be located in. Then I copied the jdk files to that newcp -R ...
You want to point it to the JRE. Back in here I have JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64/jre/ In Debian, I usually put this on my /etc/profile export JAVA_HOME=$(readlink -f /usr/bin/java | sed "s:bin/java::")
I see this also when using Java based apps. I have tracked this issue down to Java not null terminating the WM_CLASS string. Mutter seems to return this invalid string as a result and gnome-shell uses this invalid string for matching the application name which obviously fails. It is a bug in Java as the WM_CLASS string is supposed to be null terminated. ...
keytool does not log information; it only writes to the standard output and standard error. Its documentation lists several cases where it will use one or the other, and does not mention logging.
The last Fedora 23 updates seem to include a fix. Now the mouse works again as expected in Java programs. Even with the default DESKTOP_SESSION=gnome environment variable setting. (With sqldeveloper-126.96.36.199 you also does not have to unset the GNOME_DESKTOP_SESSION_ID environment variable anymore - was necessary in previous versions.) I suspect that the ...
Your use of & to background the first process is correct here, as I presume that bignibou-server needs to be running during your tests? By far the simplest method of introducing a delay before initiating your tests is to use the sleep command: ./gradlew assemble java -jar bignibou-server/build/libs/bignibou-server.jar & sleep 60 ...
The mcelog you posted suggests it's a memory issue: Generic CACHE Level-2 Generic Error I suggest you test your machine's hardware using Ubuntu's memtest, you can find an entry for memtest as a menu entry when you boot your machine.
Window focus is the job of the window manager. I presume you are using one. The best way to focus a window is: xdotool search --name 'Window title' windowactivate xdotool uses 2 mechanisms to send key events, the XTEST extension for events to send to the current focus, and XSendEvent() to send events to a given window. The latter generates events with a ...
Top 50 recent answers are included