Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

incompatibility with gatling-2.2.2 #11

Open
ksgr999 opened this issue Nov 15, 2016 · 6 comments
Open

incompatibility with gatling-2.2.2 #11

ksgr999 opened this issue Nov 15, 2016 · 6 comments

Comments

@ksgr999
Copy link

ksgr999 commented Nov 15, 2016

With latest version of gatling-2.2.2 Unable to use this plugin...
I have gatling-amqp_2.11:0.5 in project dependencies...

When run performance test getting the below error.
Missing or invalid dependency detected while loading class file 'AmqpProtocol.class'.
Could not access type Protocol in package io.gatling.core.config,
because it (or its dependencies) are missing. Check your build definition for
missing or conflicting dependencies. (Re-run with -Ylog-classpath to see the problematic classpath.)
A full rebuild may help if 'AmqpProtocol.class' was compiled against an incompatible version of io.gatling.core.config.
one error found

Can you help me on this one to work on gatling-2.2.2

@ksgr999 ksgr999 changed the title Unable to import io.gatling.amqp incompatibility with gatling-2.2.2 Nov 15, 2016
@maiha
Copy link
Owner

maiha commented Nov 17, 2016

Hi, @ksgr999
I'm sorry that I've left AMQP job, so this library still lives with gatling-2.2.0.
Could you try @LuboVarga 's fork? It supports 2.2.2 I think.
https://github.com/LuboVarga/gatling-amqp

Best regards,

@LuboVarga
Copy link
Contributor

Thanks for suggestion, but unfortunately my fork still have not finished migration to gatling-2.2.2. There are major changes which are not compatible with philosophy of amqp plugin code/actor structure. I am on a good way, but these days I have no time to finish migration.

On the other side, my fork have some nice improvements in "rpc" way of using amqp. You can make request through amqp with correlation id (by default, generated automatically) and than wait for response (each step should have its own queue!). Response is correlated by correlation id from last request (stored in session) by default. Than you can see also "response" time for request.

If my memory is ok, this is last working branch for my fork: https://github.com/LuboVarga/gatling-amqp/commits/moreStepsInSingleAction (still on older gatling base!)

WIP branch with migration to new gatling is here: https://github.com/LuboVarga/gatling-amqp/tree/migratingToGatling2.2.2

@maiha
Copy link
Owner

maiha commented Nov 19, 2016

@ LuboVarga Thanks for information and nice work!
I'd like to check your 2.2.2 branch in this weekend.

@maiha
Copy link
Owner

maiha commented Nov 20, 2016

Found that some '???' implementations still exist although it can be compiled on 2.2.2.
So then, we have much more time to satisfy backward compatibility.
I'd like to finish it within this year :)

@LuboVarga
Copy link
Contributor

I would be also pleased. I do not have currently enough time to help (push migration further), but it can change from week to week. I will have migration need on my mind and I will try to make it work, if I would have time.

PS: I was a bit lost when making migration done. It is probably due to gatling 2.2.2 has changed a bit philosophy of how actors are done (hidden behind io.gatling.core.action.Action instead directly working with Actor).

@klai05
Copy link

klai05 commented Dec 23, 2021

Hi Community and @LuboVarga / @maiha,

I got the same error and I reported this issue in another thread.

Can you please help me?

Please see my error logs here: Tinkoff/gatling-amqp-plugin#37

Thanks,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants