-
Notifications
You must be signed in to change notification settings - Fork 116
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
Exception deploying war in tomcat with version 4.0.0 #268
Comments
We are experiencing the exact same error in our application and are therefore currently not upgrading to the newest version. I did some debugging and I managed to track the difference (with and without database-migration plugin) of the execution to the following lines: Without database-migration plugin, the following initializers are present:
If the database-migration plugin is included, the initializers are the following:
So the culprit seems to be
This also includes grails-shell, which shouldn't belong in an application artifact. I think this might be related to this issue which I opened: |
Can someone tell me which settings work for grails 5.1.2? I am experiencing this issue also. Version 4.0.1-SNAPSHOT is not working, neither does 4.0.0. When I try to go back to version 3.0.4 I get another error (java.lang.NoClassDefFoundError: org/springframework/boot/liquibase/CommonsLoggingLiquibaseLogger). |
@davidkron Please test with the new version (4.1.0) I have the same error. in my case if I do this it works: implementation('org.grails.plugins:database-migration:4.1.0') { |
Tomcat throws an Exception when using new version
NOTE: If I use version 3.1.0 the app is deployed correctly
Exception:
SEVERE [main] org.apache.catalina.startup.HostConfig.deployWAR Error deploying web application archive [E:\apache-tomcat-9.0.33\webapps\prueba.war]
java.lang.IllegalStateException: Error starting child
see logger file for full logger.
Environment Information
Example Application
https://github.com/miguelabautista/database-migration-sample
The text was updated successfully, but these errors were encountered: