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 <sk...@oasysic.com> Sent: 25 April 2022 14:43 To: JMeter Users List <user@jmeter.apache.org> Subject: RE: JMeter 5.4.3 unable to open jmx created in 5.2.1 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 <suntong...@gmail.com> Sent: Monday, April 25, 2022 9:33 AM To: JMeter Users List <user@jmeter.apache.org> Subject: Re: JMeter 5.4.3 unable to open jmx created in 5.2.1 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 <sk...@oasysic.com> wrote: > 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. > > Installing the missing component allowed the new version to > successfully open the JMX. > > Steve Kram > > > -----Original Message----- > From: Stuart Kenworthy <stuart.kenwor...@bjss.com> > Sent: Monday, April 25, 2022 8:06 AM > To: JMeter Users List <user@jmeter.apache.org> > Subject: RE: JMeter 5.4.3 unable to open jmx created in 5.2.1 > > 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 auth tokens. I also noticed my log files did not > go through so the full call error is: > > java.lang.NoSuchMethodError: > org.apache.jmeter.save.converters.HashTreeConverter.readBareItem(Lcom/ > thoughtworks/xstream/io/HierarchicalStreamReader;Lcom/thoughtworks/xst > ream/converters/UnmarshallingContext;Ljava/lang/Object;)Ljava/lang/Obj > ect; > > so may be a conflict in xstream libraries but once again no real > information being provided by JMeter and there is no reference to > these packages in the custom jar. > > From: Stuart Kenworthy <stuart.kenwor...@bjss.com> > Sent: 25 April 2022 12:36 > To: JMeter Users List <user@jmeter.apache.org> > Subject: JMeter 5.4.3 unable to open jmx created in 5.2.1 > > 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 > properties files, or our customised properties files we get an > exception > java.lang.NoSuchMethodError: > org.apache.jmeter.save.converters.HashTreeConverter.readBareItem > > The full log sanitised log file has been included in the exception in > a clean instance of jmeter 5.4.3. > > The script being loaded (portalLogOut.jmx) is one of our simplest. It > was created in 5.2.1 and contains a single TestFragmentController, > which contains a HttpTestSamplerGui, JSR223PostProcessor and Header Manager. > > As we are not undertaking a major release upgrade, I was expecting > this to be a trivial move. > > I am struggling to find any other evidence of this occurring in the > wild but also cannot find a recommended upgrade path from 5.2.1 to 5.4.3. > > I would like to avoid going through every version in between if I can. > > Any advice on how to resolve this issue? > > Thanks > > The information included in this email and any files transmitted with > it may contain information that is confidential and it must not be > used by, or its contents or attachments copied or disclosed to, > persons other than the intended addressee. If you have received this > email in error, please notify BJSS. In the absence of written > agreement to the contrary BJSS' relevant standard terms of contract > for any work to be undertaken will apply. Please carry out virus or > such other checks as you consider appropriate in respect of this > email. BJSS does not accept responsibility for any adverse effect upon > your system or data in relation to this email or any files transmitted > with it. BJSS Limited, a company registered in England and Wales > (Company Number 2777575), VAT Registration Number 613295452, > Registered Office Address, 1 Whitehall Quay, Leeds, LS1 4HR > > The information included in this email and any files transmitted with > it may contain information that is confidential and it must not be > used by, or its contents or attachments copied or disclosed to, > persons other than the intended addressee. If you have received this > email in error, please notify BJSS. In the absence of written > agreement to the contrary BJSS' relevant standard terms of contract > for any work to be undertaken will apply. Please carry out virus or > such other checks as you consider appropriate in respect of this > email. BJSS does not accept responsibility for any adverse effect upon > your system or data in relation to this email or any files transmitted > with it. BJSS Limited, a company registered in England and Wales > (Company Number 2777575), VAT Registration Number 613295452, > Registered Office Address, 1 Whitehall Quay, Leeds, LS1 4HR > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org > For additional commands, e-mail: user-h...@jmeter.apache.org > > B KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB [ X ܚX KK[XZ[ \ \ ][ X ܚX P Y]\ \X K ܙ B ܈Y][ۘ[ [X[ K[XZ[ \ \ Z[ Y]\ \X K ܙ B The information included in this email and any files transmitted with it may contain information that is confidential and it must not be used by, or its contents or attachments copied or disclosed to, persons other than the intended addressee. If you have received this email in error, please notify BJSS. In the absence of written agreement to the contrary BJSS' relevant standard terms of contract for any work to be undertaken will apply. Please carry out virus or such other checks as you consider appropriate in respect of this email. BJSS does not accept responsibility for any adverse effect upon your system or data in relation to this email or any files transmitted with it. BJSS Limited, a company registered in England and Wales (Company Number 2777575), VAT Registration Number 613295452, Registered Office Address, 1 Whitehall Quay, Leeds, LS1 4HR
