https://bz.apache.org/bugzilla/show_bug.cgi?id=64658
--- Comment #7 from Felix Schumacher <[email protected]> --- Hi Marc, to debug your problems hopefully a bit easier, I have added debug messages at the point in the startup sequence, that happens when the splash screen is displayed. To enable the debug logs, you have to add an entry to bin/log4j2.xml <Logger name="org.apache.jmeter.JMeter" level="debug" /> I placed it directly under the entry for name="org.apache.jmeter.junit". On the next start up, you should see the following lines in the jmeter.log file: 2020-08-10 17:59:06,697 DEBUG o.a.j.JMeter: Apply HiDPI on fonts 2020-08-10 17:59:06,697 DEBUG o.a.j.JMeter: Configure PluginManager 2020-08-10 17:59:06,698 INFO o.a.j.JMeter: Loaded icon properties from org/apache/jmeter/images/icon.properties 2020-08-10 17:59:06,720 DEBUG o.a.j.JMeter: Setup tree 2020-08-10 17:59:07,040 DEBUG o.a.j.JMeter: populate command map 2020-08-10 17:59:07,553 DEBUG o.a.j.JMeter: init instance 2020-08-10 17:59:07,553 DEBUG o.a.j.JMeter: constructing main frame commit 44c0c7ee1a18b86528adf07607839614166d60f6 AuthorDate: Mon Aug 10 17:59:56 2020 +0200 Log status on start up, when splash screen is displayed Be more verbose on the init phase, when the startup splash screen is being displayed. This can hopefully be used to pinpoint problems on startup more easily. Bugzilla Id: 64658 --- src/core/src/main/java/org/apache/jmeter/JMeter.java | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) -- You are receiving this mail because: You are the assignee for the bug.
