-
Notifications
You must be signed in to change notification settings - Fork 42
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
[com.sngular.kloadgen.serializer.ProtobufSerializer - NullPointerException]: #332
Comments
Hi @nrellanti Thank you for your collaboration. We are looking at it and we will get back to you as soon as possible. |
Hi @nrellanti , could you add the complete protobuf file as there are missing parts such as the Order. Thank you. |
@AdrianLagarteraSngular , please see the attached complete messaging_intra_order_proto.txt protobuf file referencing in the messaging_unified_order_proto.txt |
@nrellanti Sorry for the delay, checking the For example in the |
@AdrianLagarteraSngular , |
Added a trim statement to avoid problem when cast the schemas from classpath
Removed some unused test files
@nrellanti Hi, we have added some changes in the attached branch to fix the problem, to avoid errors, if you are using schema registry to find the file, the subject and the filename must have the same name, in next versions we will fix this so the subject can be different from the filename and it will still work. On the other hand if you don't use schema registry you can indicate the classpath in jmeter and it will also work without schema registry, just put the files you use in the same folder. Best regards and thank you very much |
Hi @AdrianLagarteraSngular , Thanks for sharing the information and trying to work around this issue. Example: We're importing child schema like this because we have seen standard practices for google's well-known schema also registering the same way and importing in any schema. In the same way, we're importing other custom or child schemas into the parent schema. The latest Kloadgen jar is not supporting this use case. Can you please advise on the above scenario? Thank you, |
Apparently the original project was renamed into cmak to avoid break the TOS of kafka having the kafka in the name of unofficial tool
Hi, sorry for don't answer before Using the given params you put on your last message @vishaldhanani I will put the steps you need to do to cover your scenario:
Let me know if it has been useful for you, or if you find new issues, and thanks for your patience. |
Hi @AdrianLagarteraSngular, Thank you for sharing the complete process. Basically, Google's well-known schema is registered as below, and based on those schemas we are following the same process to register custom schema. I think we cannot change this process to register all custom schema for only testing purposes the way you have shared in the above response. Looking forward if you can handle this kind of use case in the Kloadgen plugin. Thank you, |
Hi @vishaldhanani , We are taking a look at your last answer, sorry for the delay. |
Hi @vishaldhanani , We have introduced a fix to get the subject from the subject of the reference, so your scenery should be processed correctly. Please, could you check if this solution is valid for you? Thanks in advance. |
Hi @alfredo9f, I appreciate your reply. We'll check the most recent changes and let you know if there are any problems. Thank you, |
Hi @alfredo9f , Getting below error 2023-03-23 09:32:31,932 ERROR c.s.k.l.i.ProtobufLoadGenerator: Please make sure that properties data type and expression function return type are compatible with each other Please suggest! |
Hi @nrellanti , Please, could you tell me if you have the schema 'MESSAGING-UNIFIED-ORDER' loaded in your schema registry and what 'Strategy Name' are you using in your test? Thanks in advance. |
Hi @alfredo9f, Yes, I also tested with the latest changes and got the same error as @nrellanti getting it. We are using TopicNameStragtegy to register the schemas and we already have registered schemas for Please advise! Thank you, |
Hi @vishaldhanani , We did a small fix so now should works. Please, could you check if now is ok for you? Thanks in advance! |
@alfredo9f , |
Hi @nrellanti , Thanks to all for the checks. We will wait your confirm :) |
Hello @jemacineiras , yes it is failing, I checked both in windows and Mac machines with latest version of JMeter 5.6.2. Could you please have a look the logs posted in the previous chat. |
@jemacineiras Thank you! |
Hello @jemacineiras, I'm getting below error when I tested with branch #332 code 2024-01-12 11:32:58,844 ERROR o.a.j.t.JMeterThread: Error while processing sampler: 'Java Request'. |
Hello @jemacineiras , Thank you for Fix, I will test and update the results here. |
Hello @jemacineiras , 2024-01-23 11:12:34,945 INFO o.a.j.e.StandardJMeterEngine: Running the test! |
Hi @nrellanti , can you pease re attach the jmx file since the previous was lost? it seems something is missing or is not right configured. Cheers. |
Hello @jemacineiras , I will add jmx file at the earliest. Meanwhile, please have a look on this error 2024-01-26 09:41:26,455 INFO o.a.j.e.StandardJMeterEngine: Running the test! |
Hi @nrellanti, This error is with the code I just pushed today ? Cheers |
Hello @jemacineiras , Just couple of minutes ago, I pulled the code and generated jar file and executed on JMeter version 5.6.2. However, I have not tested on JMeter 5.6.3. I will test on JMeter 5.6.3. Will update results in a couple of minutes. |
Hi @nrellanti, Cheers |
Hello @jemacineiras , Here is the error on JMeter 5.6.3 2024-01-26 09:58:45,704 ERROR o.a.j.t.JMeterThread: Error while processing sampler: 'Java Request'. |
HI @nrellanti |
@jemacineiras , |
Hi @nrellanti |
Hi @jemacineiras, Please see the logs on JMeter 5.6.2 and JMeter 5.6.3 with your quick fix code. |
Hi @jemacineiras , Please see the logs executed on #332 Fix generator creation build on Mon 29, 2024. |
Hi @nrellanti, still don´t get it.. that imported proto is in the classpath but for any reason looks like is not find it. Will keep digging. |
Hi @jemacineiras, If you need a reference of our current failure for this ticket is here - #332 (comment) Let us know if need anything to understand more this issue. Appreciate you guys! |
Hello @jemacineiras , Tested your changes in the 332 branch java: cannot find symbol |
…on (#430) * #332 Add Files Modified To Solve Exception Added a trim statement to avoid problem when cast the schemas from classpath * #332 Add get dependencies and build proto. * #332 Add Test And Documentation Removed some unused test files * #332 Add Topic Name Strategy * #332 Change image from kafka manager to newest version Apparently the original project was renamed into cmak to avoid break the TOS of kafka having the kafka in the name of unofficial tool * Get the schema name from the schema references of imported classes * #332 Removed generator set up by TopicNameStrategy * #332 refactor * #332 refactor * #332 refactor * #332 updated pom version * #332 fixes PR * #332 fixes PR * update pom * Merge with Master * #340 update dependencies * #332 Adding google proto types * #332 Fixing size serializer. * #332 Include proto files in package * #332 Fix styles and pom version * #332 Fix styles and pom version * #332 Fix styles and test * #332 Fix styles * #332 Try to process multi level protobuff dependencies * #332 Try to process multi level protobuff dependencies * #332 Fix jdk build version * #332 Fix checkstyle issues * #332 Fix Style * #332 Fix Google dependencies * #332 Fix Google dependencies * #332 Fix generator calculation * #332 Fix generator calculation * #332 Merge with master. * #332 Update POM. * #332 Fix Protobuf Apicurio Extractor. * #332 fix new version static error * #332 fix new version static error * #332 fix Generator creation * #332 fix Random Object generation * #332 fix Serializer generation * #332 fix generator creation * #332 add test * Update pom.xml version and developers * Update pom-maven-central.xml --------- Co-authored-by: Adrian Lagartera <[email protected]> Co-authored-by: Alfredo González Fernández <[email protected]> Co-authored-by: David Hernández González <[email protected]> Co-authored-by: Jan Duinkerken Rodríguez <[email protected]>
What happened?
Caused by: java.lang.NullPointerException: Parameter specified as non-null is null: method com.squareup.wire.schema.internal.parser.ProtoParser$Companion.parse, parameter data
KloadGen Version
kloadgen-5.2.10.jar
Relevant log output
Have you added your JMX Testplan or a replica?
Have you added your Schema or a replica?
The text was updated successfully, but these errors were encountered: