-
Notifications
You must be signed in to change notification settings - Fork 167
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
From 24.5, hotswap is generating a lot of error messages #20389
Comments
It looks like Hotswap is notifying Flow about classes that are not available in its class loader. I don't have idea where the agent is getting information about that classes, but at least you can restrict the Vaadin plugin to only react to changes in application classes by setting the |
Anyway, such errors do not affect the application or the hotswap capabilities. |
Documentation for |
Indeed, setting |
I wonder where the javax artifact comes from |
It's continuously logging the stacktrace but only for below 4 classes:
None of these are a dependency in my project so it's really strange. |
Could you please provide the dependency tree of your project? |
Maybe the hotswap agent itself has these dependencies via the plugin mechanism ?
|
I am having the same issue when upgrading from 24.4 to 24.5 Vaadin 24.5.4 Jetbrains JDK 21 with Hotswap installed
|
Is the application executed as a fat-jar? At least, Vaadin does not have any dependency on Edit: did not notice the tree was already provided |
What makes me wonder is that if |
Anyway, it would be good to log the name of the class that cannot be resolved in |
As far as i can see, putting a breakpoint in
It was difficult to see which ones exactly are generating the stacktraces, but packages already seem similar (except for the |
That's weird. If |
To be honest, I don't know why agent classes are redefined. Also |
Note that in order to trigger the stacktraces again and see which classes are causing it, I had to remove the Environment is latest spring-boot with embedded tomcat. |
Description of the bug
Since upgrading to 24.5, when starting the application in debug mode with hotswap i get an endless stream of below log messages for various classes. On 24.4.x this is not happening. Is this a matter of silencing a log category or is this actually an issue? Using hotswap agent 2.0.0.
Expected behavior
No error messages
Minimal reproducible example
Use latest hotswap agent and start project in debug mode like usual.
Versions
Vaadin 24.5.2
The text was updated successfully, but these errors were encountered: