-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Remote-dev with mutable jar throws connection errors #12497
Comments
Looking at your workflow this is not actually remote, you are running both the remote agent and the mvn quarkus:remote-dev agent in the same directory. You need to either:
previously the agent would just handle sending files, while now it handles local compilation as well, this causes them to both interfere with each other and weirdness results. |
Sorry for responding late. Actually, this was just the reproducer which resulted in the same condition like in the container. In my tests, it also didn't work inside a Docker container. Could you please re-open? From my PoV it's still open. |
I could only reproduce problems with pom.xml changes, that I think should be fixed at #12969 I could not reproduce any problems with normal java files changes. Can you test out the PR and let me know if it helps? |
Describe the bug
Since the change in how the
remote-dev
feature works (was that around1.6
,1.7
?), the remote dev doesn't quite work for me anymore.Before, I've used this approach: https://blog.sebastian-daschner.com/entries/quarkus-remote-dev-in-containers
Now, I've tried the following, with
mutable-jar
andQUARKUS_LAUNCH_DEVMODE=true
on the production side, which basically works, but results in many connection errors, and also reacts much slower than usual, since it involves some restarts (?).To Reproduce
mvn clean package
export QUARKUS_LAUNCH_DEVMODE=true
java -jar target/quarkus-app/quarkus-run.jar
mvn quarkus:remote-dev -Dquarkus.live-reload.url=http://localhost:8080
curl localhost:8080/coffee
When I change some Java code and make another HTTP request, it produces the following errors:
In
mvn
:In
java -jar
:I've used:
1.8.1.Final
Eclipse OpenJ9 VM AdoptOpenJDK (build openj9-0.19.0, JRE 14 Linux amd64-64-Bit Compressed References 20200318_6 (JIT enabled, AOT enabled)
With that experience, I'm blocked to update to the latest version. What is the correct way to run this new remote-dev mode?
The text was updated successfully, but these errors were encountered: