Am 25.04.22 um 14:06 schrieb Stuart Kenworthy:
Seem to have identified the issue, but not sure why it is so. When I say a
clean installation, I did have to add a custom jar in there for authentication
purposes. This jar seems to be quietly causing issues with the JMeter
installation, I have
Which is, itself, a plugin.
-Original Message-
From: Stuart Kenworthy
Sent: 25 April 2022 14:58
To: JMeter Users List
Subject: RE: JMeter 5.4.3 unable to open jmx created in 5.2.1
By default JMeter does not know what a plugin is per-se, it would only identify
a missing library. The
Am 25.04.22 um 15:24 schrieb Stuart Kenworthy:
This was the other way around, not a missing plugin, but a custom binary
causing a conflict. The custom jar we use to create tokens for our requests
seems to be creating a conflict somewhere. I could not even open an empty JMX
with the jar in
By default JMeter does not know what a plugin is per-se, it would only identify
a missing library. The only way it would be able to prompt you to install a
missing plugin is if you had the plugin manager already installed.
-Original Message-
From: Steve Kram
Sent: 25 April 2022 14:43
Am 25.04.22 um 15:32 schrieb Tong Sun:
Interesting. How come it could happen?
I mean, when a script I'm opening is using a plug-in that wasn't yet
installed, JMeter would ask me whether to install it, then install all
the missing components for me. It is not like that for you Steve?
That
Am 25.04.22 um 13:36 schrieb Stuart Kenworthy:
I am currently going through an upgrade of our JMeter instances from
5.2.1 to 5.4.3.
Most of our existing scripts were generated in JMeter 5.2.1, and all
have been modified in such so they are all compliant with 5.2.1.
When I try to open any
Not sure why it was happening Instead of fighting it, I just edited the JMX to
figure out what plugin was causing the issue, then manually installed it.
Steve
-Original Message-
From: Tong Sun
Sent: Monday, April 25, 2022 9:33 AM
To: JMeter Users List
Subject: Re: JMeter 5.4.3
Interesting. How come it could happen?
I mean, when a script I'm opening is using a plug-in that wasn't yet
installed, JMeter would ask me whether to install it, then install all
the missing components for me. It is not like that for you Steve?
On Mon, Apr 25, 2022 at 8:15 AM Steve Kram wrote:
Ouch! Glad I'm not savvy enough (or our tests aren't complex enough) to need
custom JARs.
Steve Kram
-Original Message-
From: Stuart Kenworthy
Sent: Monday, April 25, 2022 9:25 AM
To: JMeter Users List
Subject: RE: JMeter 5.4.3 unable to open jmx created in 5.2.1
This was the
This was the other way around, not a missing plugin, but a custom binary
causing a conflict. The custom jar we use to create tokens for our requests
seems to be creating a conflict somewhere. I could not even open an empty JMX
with the jar in the lib folder.
It's even stopping me saving a new
Stuart,
I encountered similar issues when I upgraded JMeter versions. The application
started successfully, but just wouldn't open certain JMX scripts. Turns out
the scripts were using a plug-in that wasn't yet installed, so the system
provided similarly cryptic error messaging.
Seem to have identified the issue, but not sure why it is so. When I say a
clean installation, I did have to add a custom jar in there for authentication
purposes. This jar seems to be quietly causing issues with the JMeter
installation, I have no idea why, it is an internal binary for creating
I am currently going through an upgrade of our JMeter instances from 5.2.1 to
5.4.3.
Most of our existing scripts were generated in JMeter 5.2.1, and all have been
modified in such so they are all compliant with 5.2.1.
When I try to open any of my scripts with either the default JMeter
13 matches
Mail list logo
