Closed markwoodward86 closed 1 year ago
Closing this out as I was able to figure it out after a nights rest away from my computer!
@markwoodward86 would you be willing to share what you figured out here? I just ran into the same issue, trying to run the batch process for the first time
Yeesh, this was a while back. I'll try and rack my brain and let you know if I am able to recall. I should have known better and documented my findings.
@smoores-dev please feel free to open a new issue with your full stack trace (although you probably want to redact your access tokens) and I can take a look. The trace posted here only has the top level error, which is a very generic "application failed to start" and doesn't dig into why it failed to start.
Also if you're feeling feisty you can do what I do and trace the exception chain down to the lowest "caused by," which in this case I would guess is probably a missing parameter in the configuration file.
I am pretty sure it was a missing parameter in the config that I traced it back to when i originally got this too so that checks out.
Hey, thanks folks! Yeah this was a bit silly, I had been mounting my application.yaml to the wrong path in the container. It's been a while since I've worked with the JVM; always takes me a minute to remember to look at the Caused by!
I'm sorry, ive tried investigating this for a while now and i cant seem to get my polling docker file to run. This is the log. Hopefully this is something simple that I am overlooking on my part.