‎2021 Sep 23 12:52 PM
When a SAPGUI Java 7.7 session in Eclipse is inactive for a long time, the session expires and it completely crashes Eclipse.
Normal behaviour under Windows and JavaGUI up to 7.5 is that we get a disconnection message the next time we try to do anything in an expired session. In Eclipse we see the same behaviour and it simply closes the open SAPGUI tab.
Since updating my SAPGUI on my Mac to 7.7 however, when the timeout is reached it completely crashes Eclipse. i.e. If I leave eclipse for long enough with a SAPGUI session inactive the entire Eclipse app disappears and I have to start it again.
It behaved properly on my system running MacOS / JavaGUI 7.5 / Eclipse 2020-06.
I upgraded to JavaGUI 7.7 and it started to crash. Did a clean install of Eclipse 2020-09 and JavaGUI 7.7 SP3 and still the same.
Is anyone else experiencing this / know how to stop it from happening?
‎2021 Nov 11 11:30 AM
Hello mike.pokraka
Since Eclipse 2021-06 you should use JAVA 11 instead of JAVA 8 as all new SAP Tools compiled now with JAVA 11
See also the Blog – SapMachine and SAP HANA Studio
‎2021 Nov 11 8:05 PM
Hi roland.kramer,
Thanks for the info, I should have mentioned that I have already updated my Eclipse to run the JVM supplied with JavaGUI.
My current system details:
-----
Java VM: SAP SE Version 11.0.12+7-LTS-sapmachine
Java FX: 11.0.12+4
Bit Mode: 64
OS: Mac OS X(x86_64) Version 12.0.1
Java Directory: /Applications/SAP Clients/SAPGUI 7.70rev3/SAPGUI 7.70rev3.app/Contents/Resources/jre/Contents/Home
-----
Regards,
Mike
‎2021 Nov 16 7:10 AM
Small update: I added a timeout to my 7.52 NPL system and got the usual dialog box on expiry, no crash. So this is partly related to the backend system, which in my case is S/4 1909 7.55
Latest ADT 3.22.1 still has this issue.
‎2022 Apr 25 8:55 PM
Just in case someone seems this and thinks it's an old thread, it's still happening on Eclipse 2022-03 with ADT 3.24
I may be in a position to raise an OSS in a week or so.
‎2022 Apr 26 1:20 PM
Hello Mike,
from our perspective, a ticket / incident would be great. Unfortunately this behaviour is currently not reproducible on our machines. Your support information might help in this case, so please add them to the ticket. You can create the support information zip file by executing 'Help -> Collect Support Information...'. The component for this case is 'BC-DWB-AIE'.
Please let me know, when you have created the incident.
Thanks and kind regards,
Yannic