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

Verticle getting deployed in Event Model when its setup for Worker Model using Deployment Options. #5111

Closed
denis-mirchandani opened this issue Feb 8, 2024 · 2 comments
Labels

Comments

@denis-mirchandani
Copy link

Use Case:

We are using Deployment Options to create Worker Model specific options.
We are using Vertx Runner to bootstrap the MainVerticle which uses Vertx Run Command to do so.
The issue is the following : the RunCommand uses setWorker(boolean) [see below] to try to setup the worker model, but in the deployment options method the check seems to be incorrect as it is comparing the boolean (worker) parameter to thread model enum value which will always be false and hence result in Event Model being chosen.

I can see this has been removed from the Master.

I am currently using 4.5.3 version but the same issue is also in 4.5.1.

Please can you have a look.

Thank you

Code reference (branch 4.5.3) :

https://github.com/eclipse-vertx/vert.x/blob/ce654726ce4c7642143258c78b3f8992be99e3c7/src/main/java/io/vertx/core/DeploymentOptions.java#L165C10-L165C25

https://github.com/eclipse-vertx/vert.x/blob/ce654726ce4c7642143258c78b3f8992be99e3c7/src/main/java/io/vertx/core/impl/launcher/commands/RunCommand.java#L258C51-L258C57

@vietj vietj added this to the 4.5.4 milestone Feb 8, 2024
@vietj vietj added the bug label Feb 8, 2024
@tsegismont tsegismont self-assigned this Feb 9, 2024
@tsegismont
Copy link
Contributor

Can you provide a small reproducer please?

@vietj vietj modified the milestones: 4.5.4, 4.5.5 Feb 22, 2024
@tsegismont tsegismont added invalid and removed bug labels Mar 14, 2024
@tsegismont tsegismont removed their assignment Mar 14, 2024
@tsegismont tsegismont removed this from the 4.5.5 milestone Mar 14, 2024
@tsegismont
Copy link
Contributor

Closing, please reopen if you can provide a reproducer

@tsegismont tsegismont closed this as not planned Won't fix, can't repro, duplicate, stale Mar 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants