12-16-2014 2:48 PM
Hello,
I am experiencing problems with the SAPGUI7.30rev9 java client using two screen. Attached a log.
My operating system is Ubuntu 14.04 and the jre is openjdk7.
When I disconnect one of the monitors then the client works well, when the two monitors are plugged the client throws a NullPointerException.
Thanks in advance
Best Regards
12-16-2014 4:17 PM
You should be using Sun JDK, not OpenJDK
Also test with patch 10 of the JavaGUI 7.30 or the JavaGUI 7,40 released recently.
Jude
12-16-2014 8:14 PM
Hello,
Looking at the code which fails inside the JVM, I would expect any Java application to be affected using that OpenJDK version.
I found a bug report at Oracle, that indicates that this has also been an issue in the Oracle JRE, but has been fixed some time ago.
Anyway, as indicated in the system requirements, please use the latest JRE from Oracle. You can find it at http://www.oracle.com/technetwork/java/javase/downloads/index.html
Best regards
Rolf-Martin
01-12-2015 6:03 PM
Hello,
Thanks for the answers.
I have installed the oracle jdk:
java -version
java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)
But the problem still occurs with 7.30rev9.
I have installed the new version 7.40 and the problem persists:
./guilogon
Exception in thread "SETTINGSReader" java.lang.NullPointerException
at sun.awt.X11.XToolkit.getScreenInsets(XToolkit.java:717)
at com.sap.platin.base.config.Defaults.calcDefaultValue(Defaults.java:202)
at com.sap.platin.base.config.Defaults.getDefaultValue(Defaults.java:96)
at com.sap.platin.base.config.SettingsTable.put(SettingsTable.java:126)
at com.sap.platin.base.util.AbstractPersistentHashMap.putReadData(AbstractPersistentHashMap.java:859)
at com.sap.platin.base.util.AbstractPersistentHashMap.readData(AbstractPersistentHashMap.java:832)
Best Reggards
01-15-2015 11:15 AM
Hello,
we have installed Oracle JRE 1.8 update 25 64bit on Ubuntu 14.04 with two monitors connected and SAP GUI for Java 7.40. We were able to logon to a system without seeing this issue.
Unfortunately we can not tell what the difference in your environment is still triggering this problem.
Best regards
Rolf-Martin