Hello
I recorded one test successfully in Smartmeter
I start my test and I get an empty response. The server writes the following: WARNING (default task-31) Ignoring RPC call for disabled connector com.vaadin.ui.Button WARNING (default task-31) Ignoring RPC call for disabled connector com.vaadin.ui.Label
server ignores the query because it thinks an object would be disabled? But why? the recording was successful
later i also get the following exception in a response:
Unhandled exception: java.lang.IllegalStateException: Received a legacy variable change for com.vaadin.ui.VerticalSplitPanel (399) which is not a VariableOwner. The client-side connector sent these legacy variables: [clickedId]
can’t it find an object under this id. But does not Jmeter work with dynamic variables?
what am I doing wrong?I thank for any helps. Best regards Kourosh
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hi there,
It seems like you’re facing two separate issues with your SmartMeter test:
-
Ignoring RPC calls for disabled connectors: This warning appears when your application is trying to perform RPC calls on disabled components. It’s likely that the component state changed between the recording and the test run, causing this warning. You might want to investigate your application’s state management and ensure the components are enabled when they should be.
-
Received a legacy variable change for a component which is not a VariableOwner: This error is caused by the client sending legacy variables for a component that is not a VariableOwner. It is possible that the component was changed or removed after you recorded the test scenario.
Regarding dynamic variables and JMeter, it does support them. However, you may need to manually adjust your test script to account for any dynamic components or identifiers. You should consider using JMeter’s built-in extractors (e.g., Regular Expression Extractor or JSON Extractor) to extract dynamic values from server responses and use them in subsequent requests.
To resolve these issues, you can try the following:
- Re-record your test scenario to ensure you have the most up-to-date state of your application.
- Manually inspect and update your test script to account for any dynamic components or identifiers, using extractors to handle these values.
Also, make sure that your application’s state is consistent between recording and testing.
Best,
Bobby
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.