fix: JAVA_OPTS doens't work #405
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current worker config's
JAVA_OPTS
doesn't work. The reason is, the firstarguments
finish with-jar
that assumes, after this argument, jar file name should come. That means, if we specify an option withJAVA_OPTS
it break the configuration. The solution is swap the arguments order. I tested with mesh docker image with/without the option.This work is related Distributed Tracing for Consumption Linux that requires new arguments for the java agent.
Until the release happens, I keep azure-functions-docker-private will copy this
worker.config.json
once this is released, I'll change it to use this commit.