Bug 64296 - JMeter 5.2.1 not starting anymore
Summary: JMeter 5.2.1 not starting anymore
Status: RESOLVED WORKSFORME
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: 5.2.1
Hardware: PC All
: P2 normal (vote)
Target Milestone: JMETER_5.2.1
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-01 06:12 UTC by Peter B.
Modified: 2020-06-24 06:49 UTC (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter B. 2020-04-01 06:12:12 UTC
Hello,

Downloaded 5.2.1 Jmeter, worked fine, recorded, replayed everything fine.

Now starting jmeter.bar or java -jar ApacheJmeter.jar throws the same error:

java.lang.ExceptionInInitializerError
        at org.apache.logging.log4j.core.util.WatchManager.<init>(WatchManager.java:53)
        at org.apache.logging.log4j.core.config.AbstractConfiguration.<init>(AbstractConfiguration.java:135)
        at org.apache.logging.log4j.core.config.NullConfiguration.<init>(NullConfiguration.java:32)
        at org.apache.logging.log4j.core.LoggerContext.<clinit>(LoggerContext.java:85)
        at org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.createContext(ClassLoaderContextSelector.java:179)
        at org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.locateContext(ClassLoaderContextSelector.java:153)
        at org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.getContext(ClassLoaderContextSelector.java:78)
        at org.apache.logging.log4j.core.selector.ClassLoaderContextSelector.getContext(ClassLoaderContextSelector.java:65)
        at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:148)
        at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
        at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
        at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:138)
        at org.apache.logging.slf4j.Log4jLoggerFactory.getContext(Log4jLoggerFactory.java:45)
        at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:48)
        at org.apache.logging.slf4j.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:30)
        at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:358)
        at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:383)
        at org.apache.jmeter.JMeter.<clinit>(JMeter.java:125)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
        at java.lang.reflect.Constructor.newInstance(Unknown Source)
        at org.apache.jmeter.NewDriver.main(NewDriver.java:251)
Caused by: java.lang.ArrayIndexOutOfBoundsException
        at java.lang.System.arraycopy(Native Method)
        at org.apache.logging.log4j.core.util.UuidUtil.<clinit>(UuidUtil.java:81)
        ... 23 more


Tried reinstalling java on the machine. Redownloaded a new copy of JMeter and the clean extracted bundle throws the exact same error.
Tried cleaning up java files on the computer, nothing.
Tried with Java 1.8 p202 and 1.8 p241.

Not sure if this is a bug, or something remained somewhere central on the computer.

Downloaded a 5.3 nightly build and it started...

Regards,
Péter
Comment 1 Peter B. 2020-04-27 11:51:19 UTC
Dear whatever,

Why was this bug set to resolved with no comment? Typical developer behavior. The user is stupid, right? 
That thing is not starting since then.
Comment 2 Felix Schumacher 2020-04-30 14:38:18 UTC
Hi Peter,

thanks for taking the time to post an issue, as it shows that you care enough about JMeter to take your time.

Alas, I think this question would probably better have been sent to the users mailing list, as I believe it is a setup problem. Most likely you are having placed some jars into JMeters classpath, that cause the failure, or some environment settings (like a JMETER_HOME) pointing to an old installation.

It helps to add the complete jmeter.log that got written when you try to start JMeter. You should include all third-party plugins, that you might have installed.

And to be fair to the developer that closed your bug, he is a really nice guy and always helpful.
Comment 3 Philippe Mouawad 2020-04-30 15:23:02 UTC
(In reply to Peter B. from comment #1)
> Dear whatever,
> 
> Why was this bug set to resolved with no comment? Typical developer
> behavior. The user is stupid, right? 
> That thing is not starting since then.

Hello Peter,
I'd like to apologize for this.

I was handling another ticket, where I was told no information could be given to me so I was a bit annoyed.

I handled your ticket after it, and I think I wrote something, but then switched to another task and it looks like I just closed your ticket without any information.

No you're not stupid, you have taken the time to open a bug, describe it, provide a stacktrace...

Regards
Philippe
Comment 4 Philippe Mouawad 2020-06-24 06:49:35 UTC
Hello,
I am now closing this ticket as we didn't have feedback from reporter.
If you can provide more context, feel free to reopen it with more details.

Thank you
Comment 5 The ASF infrastructure team 2022-09-24 20:38:19 UTC
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/5282