Closed ndrake closed 1 year ago
@ndrake this doesn't seem like a Gretty issue. But the multiple Bouncy Castle JARs could definitely cause problems. Why are you having troubles excluding them? Do you use Gradle or Maven?
Closing this now, as it seems Gretty 3.1.0 has resolved the StackOverflowError we had previously.
We're in the process of upgrading a project from using Gradle 5.1/Gretty 3.0.3 to Gradle 7.5.1. As part of that work, we updated to Gretty 3.0.8. When using
./gradlew appRun
most of the time Tomcat startup fails with the following stacktrace:This doesn't happen ALL the time, but most of the time. Also, when this failure happens, we need to do
./gradlew --stop
before tryingappRun
again our we get "Port in use" errors.We didn't update any of our application dependencies as part of this work, so I'm not sure why we're running into this now. Running
./gradlew :dependencies
shows the same set of Bouncy Castle JARs pre and post Gradle/Gretty upgrade.My various attempts to exclude different Bouncy Castle JARs hasn't helped. Has anyone run into this situation? We aren't using Gretty 4.x yet, as we still require Tomcat 9 support at this time.
Our Gretty config looks like this: