-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Cannot deploy war file to the Tomcat with Spring Boot 2.2.0.M3 #350
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
Comments
Any one can help? |
What is your application.properties or applicaton.yml ? |
This is my pom.xml
|
Could you provide small reproduce project via GitHub? |
My application.properties
|
Please check the documentation on this property: mybatis.configuration.cacheEnabled Your error is related to this. |
my project urlmyproject @kazuki43zoo |
@thpy Thanks! |
It 's also not work @mallim
|
No solution? |
I will investigating for fix this problem now. I have one question. Is need to get configuration properties via JNDI? If you does not use JNDI, you can prevent this error as adding |
Our production have JNDI for another project. |
OK. The e.g.)
spring.jndi.ignore=true |
I've created spring-projects/spring-boot#17098. |
@thpy Probably, this issue belong the Spring Boot. Please watch the spring-projects/spring-boot#17098. Thanks. |
Ok, It's work when I add that. Thanks @kazuki43zoo
|
Closed because this issue fixed via spring-boot 2.2.0.M4. @thpy Please try again using spring-boot 2.2.0.M4 If you have a time. |
I tried
I tried 2.2.0M4 but seems like issue is still there: |
|
It is not possible to judge the same problem only by the information of the screenshot. |
[SOLVED] I faced the same issue while creating a WAR from spring boot and deploying it to an external tomcat (eg: xampp provided tomcat which had Tomcat version: 7) Was facing issue with the following: I installed a separate Tomcat Server with its latest version (9.0) and deployed the WAR there, which solved the issue for me. |
Spring boot 2.0 is designed for tomcat 9 level (servlet 4 0) so that makes sense. Personally though I wouldn't even use spring boot if just creating a traditional war to run in another container. Just because you can doesnt really mean one should do so. What real value does that provide that way other than possible autocongifuration that spring alone is enough for? I've always found that usage to be a pure novalty at best. You may want to push to run it embedded instead. There is real value there. That is of course my opinion with boot. And only based on the solved answer here. Cheers!
Get Outlook for Android<https://aka.ms/ghei36>
…________________________________
From: u33how <[email protected]>
Sent: Tuesday, January 7, 2020 1:55:26 AM
To: mybatis/spring-boot-starter <[email protected]>
Cc: Subscribed <[email protected]>
Subject: Re: [mybatis/spring-boot-starter] Cannot deploy war file to the Tomcat with Spring Boot 2.2.0.M3 (#350)
[SOLVED]
I faced the same issue while creating a WAR from spring boot and deploying it to an external tomcat (eg: xampp provided tomcat which had Tomcat version: 7)
Was facing issue with the following:
Spring Boot Version: 2
Tomcat Version: 7
I installed a separate Tomcat Server with its latest version (9.0) and deployed the WAR there, which solved the issue for me.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#350?email_source=notifications&email_token=AAHODI23UX5CGEJUYHNNSB3Q4QRN5A5CNFSM4HWTFG22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIH45DQ#issuecomment-571461262>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAHODI52LHVX6PHUPWGLNLTQ4QRN5ANCNFSM4HWTFG2Q>.
|
I can run as spring boot, but I can't run on tomcat, my spring boot is 2.2.0.M3
The text was updated successfully, but these errors were encountered: