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

[com.sngular.kloadgen.serializer.ProtobufSerializer - NullPointerException]: #332

Open
2 tasks done
nrellanti opened this issue Jan 31, 2023 · 76 comments · Fixed by #355
Open
2 tasks done

[com.sngular.kloadgen.serializer.ProtobufSerializer - NullPointerException]: #332

nrellanti opened this issue Jan 31, 2023 · 76 comments · Fixed by #355
Assignees
Labels
bug Something isn't working

Comments

@nrellanti
Copy link

nrellanti commented Jan 31, 2023

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

2023-01-31 11:47:41,804 INFO o.a.j.e.StandardJMeterEngine: Running the test!
2023-01-31 11:47:41,804 INFO o.a.j.s.SampleEvent: List of sample_variables: []
2023-01-31 11:47:41,819 INFO o.a.j.p.j.s.JavaSampler: Created class: com.sngular.kloadgen.sampler.KafkaProducerSampler. Uses tearDownTest: 
2023-01-31 11:47:41,819 INFO o.a.j.g.u.JMeterMenuBar: setRunning(true, *local*)
2023-01-31 11:47:42,227 INFO o.a.j.e.StandardJMeterEngine: Starting ThreadGroup: 1 : Thread Group
2023-01-31 11:47:42,227 INFO o.a.j.e.StandardJMeterEngine: Starting 1 threads for group Thread Group.
2023-01-31 11:47:42,227 INFO o.a.j.e.StandardJMeterEngine: Thread will continue on error
2023-01-31 11:47:42,227 INFO o.a.j.t.ThreadGroup: Starting thread group... number=1 threads=1 ramp-up=1 delayedStart=false
2023-01-31 11:47:42,227 INFO o.a.j.t.ThreadGroup: Started thread group number 1
2023-01-31 11:47:42,227 INFO o.a.j.e.StandardJMeterEngine: All thread groups have been started
2023-01-31 11:47:42,227 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-1
2023-01-31 11:47:42,606 ERROR c.s.k.p.o.ObjectCreatorFactoryHelper: Please, make sure that the schema sources fed are correct
com.google.protobuf.Descriptors$DescriptorValidationException: demo.UnifiedOrder.OrderDetails.total_weight: ".demo.Order.Dimension" is not defined.
	at com.google.protobuf.Descriptors$DescriptorPool.lookupSymbol(Descriptors.java:2465) ~[kloadgen-5.2.10.jar:?]
	at com.google.protobuf.Descriptors$FieldDescriptor.crossLink(Descriptors.java:1480) ~[kloadgen-5.2.10.jar:?]
	at com.google.protobuf.Descriptors$FieldDescriptor.access$1000(Descriptors.java:991) ~[kloadgen-5.2.10.jar:?]
	at com.google.protobuf.Descriptors$Descriptor.crossLink(Descriptors.java:954) ~[kloadgen-5.2.10.jar:?]
	at com.google.protobuf.Descriptors$Descriptor.crossLink(Descriptors.java:950) ~[kloadgen-5.2.10.jar:?]
	at com.google.protobuf.Descriptors$Descriptor.access$800(Descriptors.java:629) ~[kloadgen-5.2.10.jar:?]
	at com.google.protobuf.Descriptors$FileDescriptor.crossLink(Descriptors.java:581) ~[kloadgen-5.2.10.jar:?]
	at com.google.protobuf.Descriptors$FileDescriptor.buildFrom(Descriptors.java:313) ~[kloadgen-5.2.10.jar:?]
	at com.google.protobuf.Descriptors$FileDescriptor.buildFrom(Descriptors.java:282) ~[kloadgen-5.2.10.jar:?]
	at com.github.os72.protobuf.dynamic.DynamicSchema.init(DynamicSchema.java:241) ~[kloadgen-5.2.10.jar:?]
	at com.github.os72.protobuf.dynamic.DynamicSchema.<init>(DynamicSchema.java:203) ~[kloadgen-5.2.10.jar:?]
	at com.github.os72.protobuf.dynamic.DynamicSchema.<init>(DynamicSchema.java:42) ~[kloadgen-5.2.10.jar:?]
	at com.github.os72.protobuf.dynamic.DynamicSchema$Builder.build(DynamicSchema.java:298) ~[kloadgen-5.2.10.jar:?]
	at com.sngular.kloadgen.processor.util.SchemaProcessorUtils.buildProtoDescriptor(SchemaProcessorUtils.java:170) ~[kloadgen-5.2.10.jar:?]
	at com.sngular.kloadgen.processor.objectcreatorfactory.impl.ProtobufObjectCreatorFactory.<init>(ProtobufObjectCreatorFactory.java:45) ~[kloadgen-5.2.10.jar:?]
	at com.sngular.kloadgen.processor.objectcreatorfactory.ObjectCreatorFactoryHelper.getInstance(ObjectCreatorFactoryHelper.java:29) ~[kloadgen-5.2.10.jar:?]
	at com.sngular.kloadgen.processor.SchemaProcessor.processSchema(SchemaProcessor.java:31) ~[kloadgen-5.2.10.jar:?]
	at com.sngular.kloadgen.loadgen.impl.ProtobufLoadGenerator.setUpGenerator(ProtobufLoadGenerator.java:34) ~[kloadgen-5.2.10.jar:?]
	at com.sngular.kloadgen.sampler.SamplerUtil.configureValueGenerator(SamplerUtil.java:346) ~[kloadgen-5.2.10.jar:?]
	at com.sngular.kloadgen.sampler.KafkaProducerSampler.setupTest(KafkaProducerSampler.java:71) ~[kloadgen-5.2.10.jar:?]
	at org.apache.jmeter.protocol.java.sampler.JavaSampler.sample(JavaSampler.java:194) ~[ApacheJMeter_java.jar:5.5]
	at org.apache.jmeter.threads.JMeterThread.doSampling(JMeterThread.java:651) ~[ApacheJMeter_core.jar:5.5]
	at org.apache.jmeter.threads.JMeterThread.executeSamplePackage(JMeterThread.java:570) ~[ApacheJMeter_core.jar:5.5]
	at org.apache.jmeter.threads.JMeterThread.processSampler(JMeterThread.java:501) ~[ApacheJMeter_core.jar:5.5]
	at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:268) ~[ApacheJMeter_core.jar:5.5]
	at java.lang.Thread.run(Thread.java:834) ~[?:?]
2023-01-31 11:47:42,621 ERROR o.a.j.t.JMeterThread: Error while processing sampler: 'Kafka Producer Properties'.
java.lang.IllegalArgumentException: Could not parse Protobuf
	at io.confluent.kafka.schemaregistry.protobuf.ProtobufSchema.toProtoFile(ProtobufSchema.java:462) ~[kloadgen-5.2.10.jar:?]
	at io.confluent.kafka.schemaregistry.protobuf.ProtobufSchema.<init>(ProtobufSchema.java:337) ~[kloadgen-5.2.10.jar:?]
	at io.confluent.kafka.schemaregistry.protobuf.ProtobufSchema.<init>(ProtobufSchema.java:326) ~[kloadgen-5.2.10.jar:?]
	at com.sngular.kloadgen.loadgen.impl.ProtobufLoadGenerator.setUpGenerator(ProtobufLoadGenerator.java:44) ~[kloadgen-5.2.10.jar:?]
	at com.sngular.kloadgen.sampler.SamplerUtil.configureValueGenerator(SamplerUtil.java:352) ~[kloadgen-5.2.10.jar:?]
	at com.sngular.kloadgen.sampler.KafkaProducerSampler.setupTest(KafkaProducerSampler.java:71) ~[kloadgen-5.2.10.jar:?]
	at org.apache.jmeter.protocol.java.sampler.JavaSampler.sample(JavaSampler.java:194) ~[ApacheJMeter_java.jar:5.5]
	at org.apache.jmeter.threads.JMeterThread.doSampling(JMeterThread.java:651) ~[ApacheJMeter_core.jar:5.5]
	at org.apache.jmeter.threads.JMeterThread.executeSamplePackage(JMeterThread.java:570) ~[ApacheJMeter_core.jar:5.5]
	at org.apache.jmeter.threads.JMeterThread.processSampler(JMeterThread.java:501) ~[ApacheJMeter_core.jar:5.5]
	at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:268) ~[ApacheJMeter_core.jar:5.5]
	at java.lang.Thread.run(Thread.java:834) ~[?:?]
Caused by: java.lang.NullPointerException: Parameter specified as non-null is null: method com.squareup.wire.schema.internal.parser.ProtoParser$Companion.parse, parameter data
	at com.squareup.wire.schema.internal.parser.ProtoParser$Companion.parse(ProtoParser.kt) ~[kloadgen-5.2.10.jar:?]
	at io.confluent.kafka.schemaregistry.protobuf.ProtobufSchema.toProtoFile(ProtobufSchema.java:455) ~[kloadgen-5.2.10.jar:?]
	... 11 more
2023-01-31 11:47:42,621 INFO o.a.j.t.JMeterThread: Thread is done: Thread Group 1-1
2023-01-31 11:47:42,621 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-1
2023-01-31 11:47:42,628 INFO o.a.j.e.StandardJMeterEngine: Notifying test listeners of end of test
2023-01-31 11:47:42,628 INFO o.a.j.g.u.JMeterMenuBar: setRunning(false, *local*)

Have you added your JMX Testplan or a replica?

  • I have added a JMX testplan

Have you added your Schema or a replica?

  • I have added the Schema
@jemacineiras jemacineiras added the bug Something isn't working label Feb 1, 2023
@mseijasm
Copy link
Contributor

mseijasm commented Feb 1, 2023

Hi @nrellanti

Thank you for your collaboration. We are looking at it and we will get back to you as soon as possible.

@AdrianLagartera AdrianLagartera self-assigned this Feb 3, 2023
@AdrianLagartera
Copy link
Member

Hi @nrellanti , could you add the complete protobuf file as there are missing parts such as the Order.

Thank you.

@nrellanti
Copy link
Author

nrellanti commented Feb 3, 2023

@AdrianLagarteraSngular , please see the attached complete messaging_intra_order_proto.txt protobuf file referencing in the messaging_unified_order_proto.txt

@AdrianLagartera
Copy link
Member

AdrianLagartera commented Feb 14, 2023

@nrellanti Sorry for the delay, checking the messaging_intra_order_proto.txt file there are some references to classes that it does not have, could it be that it is a schema in a previous version?

For example in the messaging_unified_order_proto.txt the first reference to the .demo.Order.CustomerAccount class does not exist in the messaging_intra_order_proto.txt file

@nrellanti
Copy link
Author

nrellanti commented Feb 14, 2023

@AdrianLagarteraSngular ,
Here is the corrected messaging_intra_order_proto.txt file

AdrianLagartera added a commit that referenced this issue Feb 22, 2023
Added a trim statement to avoid problem when cast the schemas from classpath
AdrianLagartera added a commit that referenced this issue Mar 1, 2023
Removed some unused test files
@AdrianLagartera
Copy link
Member

@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

@vishaldhanani
Copy link

Hi @AdrianLagarteraSngular , Thanks for sharing the information and trying to work around this issue.
Basically, We're following the standard practices to register this schema the way @nrellanti has shared two schema files.
We're using TopicNaming Strategy to create topics and schema in the confluent cloud.

Example:
Topic name: MESSAGING-UNIFIED-ORDER
Subject name of parent schema: MESSAGING-UNIFIED-ORDER-value
Child schema's subject name: messaging_intra_order.proto (We are importing this schema in the above parent schema as import "messaging_intra_order.proto";)

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.
image

In the same way, we're importing other custom or child schemas into the parent schema.
image

The latest Kloadgen jar is not supporting this use case. Can you please advise on the above scenario?

Thank you,
Vishal

AdrianLagartera added a commit that referenced this issue Mar 8, 2023
AdrianLagartera added a commit that referenced this issue Mar 8, 2023
Apparently the original project was renamed into cmak to avoid break the TOS of kafka having the kafka in the name of unofficial tool
@AdrianLagartera
Copy link
Member

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:

 {
    "schema": "..."
    "schemaType": "PROTOBUF",
    "references": [
    {
      "name": "messaging_intra_order.proto",
      "subject": "messaging_intra_order",
      "version": 1
    }]
}
  • And after that ensure your topic have the same name as the subject of the schema registry, in the example value you give the subject name of the parent not correct if your topic name its: MESSAGING-UNIFIED-ORDER, should be exactly the same name in the subject and the topic

  • And finally check if your plan test have the correct Name Strategybecause in the attached one the strategy was RecordNameStrategy instead of the TopicNameStrategy

Let me know if it has been useful for you, or if you find new issues, and thanks for your patience.

@vishaldhanani
Copy link

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.
{
"schema": "..."
"schemaType": "PROTOBUF",
"references": [
{
"name": "messaging_intra_order.proto",
"subject": "messaging_intra_order.proto",
"version": 1
}]
}

image

Thank you,
Vishal

@alfredo9f
Copy link
Contributor

Hi @vishaldhanani ,

We are taking a look at your last answer, sorry for the delay.
Best regards.

@alfredo9f alfredo9f self-assigned this Mar 21, 2023
@alfredo9f
Copy link
Contributor

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.
Best regards

@vishaldhanani
Copy link

Hi @alfredo9f, I appreciate your reply. We'll check the most recent changes and let you know if there are any problems.

Thank you,
Vishal

@nrellanti
Copy link
Author

Hi @alfredo9f ,
Tested the new code from Branch 332-comsngularkloadgenserializerprotobufserializer-nullpointerexception

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 
io.confluent.kafka.schemaregistry.client.rest.exceptions.RestClientException: Subject 'MESSAGING-UNIFIED-ORDER' not found.; error code: 40401.

Please suggest!

@alfredo9f
Copy link
Contributor

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.

@vishaldhanani
Copy link

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 MESSAGING-UNIFIED-ORDER topic.

image

Please advise!

Thank you,
Vishal

@alfredo9f
Copy link
Contributor

Hi @vishaldhanani ,

We did a small fix so now should works. Please, could you check if now is ok for you?

Thanks in advance!

@nrellanti
Copy link
Author

@alfredo9f ,
Looks like the new fix was working as expected.
I will test few more similar proto files and will confirm.
Thanks for fix !

@alfredo9f
Copy link
Contributor

Hi @nrellanti ,

Thanks to all for the checks. We will wait your confirm :)

@nrellanti
Copy link
Author

nrellanti commented Dec 19, 2023

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 added a commit that referenced this issue Jan 9, 2024
@nrellanti
Copy link
Author

@jemacineiras Thank you!
I will test next week and get back to you the updated result

@nrellanti
Copy link
Author

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'.
com.sngular.kloadgen.exception.KLoadGenException: Unsupported Serializer
at com.sngular.kloadgen.sampler.SamplerUtil.configureKeyGenerator(SamplerUtil.java:427) ~[kloadgen-5.6.14.jar:?]
at com.sngular.kloadgen.sampler.KafkaProducerSampler.setupTest(KafkaProducerSampler.java:73) ~[kloadgen-5.6.14.jar:?]
at org.apache.jmeter.protocol.java.sampler.JavaSampler.sample(JavaSampler.java:194) ~[ApacheJMeter_java.jar:5.6.2]
at org.apache.jmeter.threads.JMeterThread.doSampling(JMeterThread.java:651) ~[ApacheJMeter_core.jar:5.6.2]
at org.apache.jmeter.threads.JMeterThread.executeSamplePackage(JMeterThread.java:570) ~[ApacheJMeter_core.jar:5.6.2]
at org.apache.jmeter.threads.JMeterThread.processSampler(JMeterThread.java:501) [ApacheJMeter_core.jar:5.6.2]
at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:268) [ApacheJMeter_core.jar:5.6.2]
at java.lang.Thread.run(Thread.java:840) [?:?

@nrellanti
Copy link
Author

Hello @jemacineiras , Thank you for Fix, I will test and update the results here.

@nrellanti
Copy link
Author

Hello @jemacineiras ,
Getting below errors

2024-01-23 11:12:34,945 INFO o.a.j.e.StandardJMeterEngine: Running the test!
2024-01-23 11:12:34,946 INFO o.a.j.s.SampleEvent: List of sample_variables: []
2024-01-23 11:12:34,947 INFO o.a.j.p.j.s.JavaSampler: Created class: com.sngular.kloadgen.sampler.KafkaProducerSampler. Uses tearDownTest:
2024-01-23 11:12:34,947 INFO o.a.j.g.u.JMeterMenuBar: setRunning(true, local)
2024-01-23 11:12:34,995 INFO o.a.j.e.StandardJMeterEngine: Starting ThreadGroup: 1 : Thread Group
2024-01-23 11:12:34,996 INFO o.a.j.e.StandardJMeterEngine: Starting 1 threads for group Thread Group.
2024-01-23 11:12:34,996 INFO o.a.j.e.StandardJMeterEngine: Thread will continue on error
2024-01-23 11:12:34,996 INFO o.a.j.t.ThreadGroup: Starting thread group... number=1 threads=1 ramp-up=1 delayedStart=false
2024-01-23 11:12:34,997 INFO o.a.j.t.ThreadGroup: Started thread group number 1
2024-01-23 11:12:34,997 INFO o.a.j.e.StandardJMeterEngine: All thread groups have been started
2024-01-23 11:12:34,997 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-1
2024-01-23 11:12:34,998 ERROR o.a.j.t.JMeterThread: Error while processing sampler: 'Java Request'.
com.sngular.kloadgen.exception.KLoadGenException: Unsupported Serializer
at com.sngular.kloadgen.sampler.SamplerUtil.configureKeyGenerator(SamplerUtil.java:427) ~[kloadgen-5.6.14.jar:?]
at com.sngular.kloadgen.sampler.KafkaProducerSampler.setupTest(KafkaProducerSampler.java:73) ~[kloadgen-5.6.14.jar:?]
at org.apache.jmeter.protocol.java.sampler.JavaSampler.sample(JavaSampler.java:194) ~[ApacheJMeter_java.jar:5.6.2]
at org.apache.jmeter.threads.JMeterThread.doSampling(JMeterThread.java:651) ~[ApacheJMeter_core.jar:5.6.2]
at org.apache.jmeter.threads.JMeterThread.executeSamplePackage(JMeterThread.java:570) ~[ApacheJMeter_core.jar:5.6.2]
at org.apache.jmeter.threads.JMeterThread.processSampler(JMeterThread.java:501) [ApacheJMeter_core.jar:5.6.2]
at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:268) [ApacheJMeter_core.jar:5.6.2]
at java.lang.Thread.run(Thread.java:840) [?:?]
2024-01-23 11:12:34,998 INFO o.a.j.t.JMeterThread: Thread is done: Thread Group 1-1
2024-01-23 11:12:34,999 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-1
2024-01-23 11:12:34,999 INFO o.a.j.e.StandardJMeterEngine: Notifying test listeners of end of test
2024-01-23 11:12:34,999 INFO o.a.j.g.u.JMeterMenuBar: setRunning(false, local)

@jemacineiras
Copy link
Contributor

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.

jemacineiras added a commit that referenced this issue Jan 26, 2024
@nrellanti
Copy link
Author

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!
2024-01-26 09:41:26,456 INFO o.a.j.s.SampleEvent: List of sample_variables: []
2024-01-26 09:41:26,457 INFO o.a.j.p.j.s.JavaSampler: Created class: com.sngular.kloadgen.sampler.KafkaProducerSampler. Uses tearDownTest:
2024-01-26 09:41:26,457 INFO o.a.j.g.u.JMeterMenuBar: setRunning(true, local)
2024-01-26 09:41:26,510 INFO o.a.j.e.StandardJMeterEngine: Starting ThreadGroup: 1 : Thread Group
2024-01-26 09:41:26,510 INFO o.a.j.e.StandardJMeterEngine: Starting 1 threads for group Thread Group.
2024-01-26 09:41:26,510 INFO o.a.j.e.StandardJMeterEngine: Thread will continue on error
2024-01-26 09:41:26,511 INFO o.a.j.t.ThreadGroup: Starting thread group... number=1 threads=1 ramp-up=1 delayedStart=false
2024-01-26 09:41:26,512 INFO o.a.j.t.ThreadGroup: Started thread group number 1
2024-01-26 09:41:26,512 INFO o.a.j.e.StandardJMeterEngine: All thread groups have been started
2024-01-26 09:41:26,512 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-1
2024-01-26 09:41:26,513 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-1
2024-01-26 09:41:26,513 ERROR o.a.j.JMeter: Uncaught exception in thread Thread[Thread Group 1-1,6,main]
java.lang.IncompatibleClassChangeError: Expecting non-static method 'org.apache.jmeter.threads.JMeterVariables org.apache.jmeter.protocol.java.sampler.JavaSamplerContext.getJMeterVariables()'
at com.sngular.kloadgen.sampler.KafkaProducerSampler.setupTest(KafkaProducerSampler.java:72) ~[kloadgen-5.6.14.jar:?]
at org.apache.jmeter.protocol.java.sampler.JavaSampler.sample(JavaSampler.java:194) ~[ApacheJMeter_java.jar:5.6.2]
at org.apache.jmeter.threads.JMeterThread.doSampling(JMeterThread.java:651) ~[ApacheJMeter_core.jar:5.6.2]
at org.apache.jmeter.threads.JMeterThread.executeSamplePackage(JMeterThread.java:570) ~[ApacheJMeter_core.jar:5.6.2]
at org.apache.jmeter.threads.JMeterThread.processSampler(JMeterThread.java:501) ~[ApacheJMeter_core.jar:5.6.2]
at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:268) ~[ApacheJMeter_core.jar:5.6.2]
at java.lang.Thread.run(Thread.java:840) [?:?]
2024-01-26 09:41:26,514 INFO o.a.j.e.StandardJMeterEngine: Notifying test listeners of end of test
2024-01-26 09:41:26,514 INFO o.a.j.g.u.JMeterMenuBar: setRunning(false, local)

@jemacineiras
Copy link
Contributor

Hi @nrellanti,

This error is with the code I just pushed today ?
Its happening with the JMeter 5.6.3 version. Is this the one you are using?

Cheers

@nrellanti
Copy link
Author

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.
Thanks

@jemacineiras
Copy link
Contributor

Hi @nrellanti,
Ok I´ll took a look and back asap.

Cheers

@nrellanti
Copy link
Author

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'.
com.sngular.kloadgen.exception.KLoadGenException: Unsupported Serializer
at com.sngular.kloadgen.sampler.SamplerUtil.configureKeyGenerator(SamplerUtil.java:427) ~[kloadgen-5.6.14.jar:?]
at com.sngular.kloadgen.sampler.KafkaProducerSampler.setupTest(KafkaProducerSampler.java:73) ~[kloadgen-5.6.14.jar:?]
at org.apache.jmeter.protocol.java.sampler.JavaSampler.sample(JavaSampler.java:194) ~[ApacheJMeter_java.jar:5.6.3]
at org.apache.jmeter.threads.JMeterThread.doSampling(JMeterThread.java:651) ~[ApacheJMeter_core.jar:5.6.3]
at org.apache.jmeter.threads.JMeterThread.executeSamplePackage(JMeterThread.java:570) ~[ApacheJMeter_core.jar:5.6.3]
at org.apache.jmeter.threads.JMeterThread.processSampler(JMeterThread.java:501) ~[ApacheJMeter_core.jar:5.6.3]
at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:268) ~[ApacheJMeter_core.jar:5.6.3]
at java.base/java.lang.Thread.run(Thread.java:1583) [?:?]

jemacineiras added a commit that referenced this issue Jan 26, 2024
@jemacineiras
Copy link
Contributor

HI @nrellanti
right, this last one.. need the JMX to see the flow
Cheers

@nrellanti
Copy link
Author

@jemacineiras ,
please see the jmx file in txt format
KLG - Value Schema Serializer Config.txt

jemacineiras added a commit that referenced this issue Jan 26, 2024
@jemacineiras
Copy link
Contributor

Hi @nrellanti
Just uploaded a quick fix, can you try if that works with you in your systems?
Cheers

@nrellanti
Copy link
Author

Hi @jemacineiras,

Please see the logs on JMeter 5.6.2 and JMeter 5.6.3 with your quick fix code.

Jmeter-5.6.3-logs.txt
Jmeter-5.6.2-logs.txt

jemacineiras added a commit that referenced this issue Jan 26, 2024
jemacineiras added a commit that referenced this issue Jan 26, 2024
jemacineiras added a commit that referenced this issue Jan 29, 2024
@nrellanti
Copy link
Author

Hi @jemacineiras ,

Please see the logs executed on #332 Fix generator creation build on Mon 29, 2024.
Jmeter-5.6.2-log_01292024.txt
Still getting more errors.

@jemacineiras
Copy link
Contributor

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.

@vishaldhanani
Copy link

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!

jemacineiras added a commit that referenced this issue Feb 29, 2024
jemacineiras added a commit that referenced this issue Feb 29, 2024
@nrellanti
Copy link
Author

Hello @jemacineiras , Tested your changes in the 332 branch
getting the below errors during build the project

java: cannot find symbol
symbol: method getExtendDeclarations()
location: variable field of type com.squareup.wire.schema.internal.parser.MessageElement

davidgayoso pushed a commit that referenced this issue May 3, 2024
…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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants