-
Notifications
You must be signed in to change notification settings - Fork 16
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
Classpath issues in dev mode #22
Comments
Some additional debugging information, gathered via If the
When the same command is run with the aspectj runner in place, there is an attempt to load the resource before the first request, and it doesn't look like the This should provide some additional clues. I'll keep digging. |
Getting more information via IntelliJ debugger. When the config is not specified as a JVM parameter, the
When the config is specified on the command-line the
Note that even if you specify the default config file. e.g. Also note that that in the working case, the thread is an Akka thread (e.g. |
More digging.. The issue is more fundamental than providing config overrides. A config override signals to typesafe-config that the file must be found, or it will fail fast. With no override, it's actually a silent failure and Kamon is not picking up config from The workaround of starting via |
I believe the root cause is the kamon future instrumentation is kicking in before the Play server has started, or more specifically the I verified a few hacks which somewhat alleviate the issue, but none are likely ideal.
Note the comments from jroper about not using Although there's an unfortunate ordering of events. It looks like the new settings aren't in effect until the 2nd request. The incoming context is decoded before
So, lot's of things going on here. There may be a combination of small changes to iron out all the individual cases, or there may be a more fundamental approach such as preventing Kamon from initializing until an appropriate time in the Play dev mode flow. |
I expect to be able to set the play config resource via command-line argument. I have tried several different ways.
sbt -Dconfig.resource=application.local.conf run
Relevant output
Also tried
sbt -Dconfig.file=conf/application.local.conf run
Relevant output
prod mode via
sbt -Dconfig.resource=application.local.conf runProd
does not produce an error at startup, but the configuration setting is not respected, which can be observed by hittinglocalhost:9000
and seeing that b3 headers are propagated, whereas they should not be based on the config file.Repro via https://github.com/jsw/play-2.6-with-kamon/tree/78c5c32e20807477df3d5d675a980d0eb0cd873a
The text was updated successfully, but these errors were encountered: