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

sls-packaging Default JVM arguments are not applied in launcher scripts #630

Open
mglazer opened this issue Sep 20, 2019 · 0 comments
Open

Comments

@mglazer
Copy link
Contributor

mglazer commented Sep 20, 2019

What happened?

LaunchConfigTask applies a set of sls-packaging defaults to all services:

https://github.com/palantir/sls-packaging/blob/develop/gradle-sls-packaging/src/main/groovy/com/palantir/gradle/dist/service/tasks/LaunchConfigTask.java#L58

This is great, however, it only applies to things invoked via the go-java-launcher. In the case where your service provides some form of CLI based functionality where you would want to invoke:

service/bin/myservice SOME ARGS GO HERE

The DEFAULT_JVM_OPTS environment variable only pulls from what you specify in defaultJvmOpts. The alwaysOnJvmOptions are not merged in.

I believe this is because the JavaServiceDistributionExtension extends from BaseDistributionExtension but does not apply the same set of JVM opts from LaunchConfigTask

What did you want to happen?

The on disk CLI invoker operates the same as what your service sees. Note that go-java-launcher does not work well with CLI invocations because it does not accept CLI args last time I checked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant