Blaze-meter xmpp latest jars

[Sunil Vp]

Hi,

Software version:

Jmeter: 3.3r 1808647

Blaze-meter version: jmeter-plugins-xmpp-1.5.1.jar 

Ejabberd Server: 3.2.16

I had cloned the https://github.com/Blazemeter/jmeter-bzm-plugins/tree/master/xmpp and was adding custom code using it . 

Do get the jar i execute : mvn clean install and copy the jar to  lib/ext folder. 

By installing the latest xmpp plugin from the plugin manager saw that in the lib folder : 

smack-bosh-4.0.7.jar, smack-core-4.0.7.jar, smack-tcp-4.0.7.jar, smack-extensions-4.0.7.jar 

I saw that recently the smack library was updated to version 4.1.0-alpha3, if i have to have the new code repository with the latest smack jars what are the versions of jars that i have to download and place in the lib folder.

Without updating the jars from 4.0.7 i get IncompatibleClassChangeError which is because the new jar built using the update smack which is 4.1.0-alpha3 and 4.0.7 are different.

But after manually replacing the above jars in lib folder from 4.0.7 to 4.1.0-alpha3 i got rid of IncompatibleClassChangeError but login was failing with Sasl error , which is used to work with 4.0.7 smack jars and older code before smack changes.

It would be good if i can get the required jar versions of smack which i have to place in lib folder with the updated code base . 

Thank You. 

With Regards,

Sunil VP

[artem....@blazemeter.com]

Hello,

Thanks for your report. I'm busy on this week and I'll try to investigate in this problem on the next week.

Thanks,
Artem

вторник, 6 февраля 2018 г., 6:39:37 UTC+3 пользователь Sunil Vp написал:

[artem....@blazemeter.com]

I tried to reproduced but i got the following stacktrace (Connect step)

 ERROR c.b.j.x.JMeterXMPPSampler: Error in XMPP Sampler: 

org.jivesoftware.smack.SmackException$NoResponseException: null

at org.jivesoftware.smack.SynchronizationPoint.checkForResponse(SynchronizationPoint.java:176) ~[smack-core-4.1.0-alpha3.jar:4.1.0-alpha3]

at org.jivesoftware.smack.SynchronizationPoint.checkIfSuccessOrWait(SynchronizationPoint.java:110) ~[smack-core-4.1.0-alpha3.jar:4.1.0-alpha3]

at org.jivesoftware.smack.SynchronizationPoint.checkIfSuccessOrWaitOrThrow(SynchronizationPoint.java:93) ~[smack-core-4.1.0-alpha3.jar:4.1.0-alpha3]

at org.jivesoftware.smack.tcp.XMPPTCPConnection.connectInternal(XMPPTCPConnection.java:855) ~[smack-tcp-4.1.0-alpha3.jar:4.1.0-alpha3]

at org.jivesoftware.smack.AbstractXMPPConnection.connect(AbstractXMPPConnection.java:313) ~[smack-core-4.1.0-alpha3.jar:4.1.0-alpha3]

at com.blazemeter.jmeter.xmpp.actions.Connect.perform(Connect.java:21) ~[jmeter-plugins-xmpp-1.5.1.jar:?]

at com.blazemeter.jmeter.xmpp.JMeterXMPPSampler.sample(JMeterXMPPSampler.java:57) [jmeter-plugins-xmpp-1.5.1.jar:?]

at org.apache.jmeter.threads.JMeterThread.executeSamplePackage(JMeterThread.java:498) [ApacheJMeter_core.jar:3.3 r1808647]

at org.apache.jmeter.threads.JMeterThread.processSampler(JMeterThread.java:424) [ApacheJMeter_core.jar:3.3 r1808647]

at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:255) [ApacheJMeter_core.jar:3.3 r1808647]

at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]

Did you had the same and how you fixed it? Maybe I have incorrect config of my ejabberd server. I use 16.01, because i didn't find the same 3.2.16. Could you help me with server configuration, please?

Also I tried to understand why we have such change https://github.com/Blazemeter/jmeter-bzm-plugins/commit/53822a55877af608ad33171576880e9b5c0abe63
And I found, that another project fixed the same issue https://github.com/redsolution/xabber-android/issues/700 with update to version 4.1.3, but this version broke our plugin or we should make a huge refactoring in it.

Thanks,
Artem

вторник, 6 февраля 2018 г., 6:39:37 UTC+3 пользователь Sunil Vp написал:

Hi,