problem of a deployment in tomcat server
-
when i want to deploy my application in tomcat server it can't and this is the error message init: deps-module-jar: deps-ear-jar: deps-jar: library-inclusion-in-archive: library-inclusion-in-manifest: compile: compile-jsps: Undeploying ... undeploy?path=/Mango OK - Application non-déployée pour le chemin de contexte /Mango In-place deployment at D:\PFE\Mango\build\web deploy?config=file%3A%2FC%3A%2FUsers%2FBouali%2FAppData%2FLocal%2FTemp%2Fcontext4268238340729989227.xml&path=/Mango FAIL - Deployed application at context path /Mango but context failed to start D:\PFE\Mango\nbproject\build-impl.xml:847: The module has not been deployed. See the server log for details. BUILD FAILED (total time: 2 seconds) I await your answers in short delays. thank you in advance
-
when i want to deploy my application in tomcat server it can't and this is the error message init: deps-module-jar: deps-ear-jar: deps-jar: library-inclusion-in-archive: library-inclusion-in-manifest: compile: compile-jsps: Undeploying ... undeploy?path=/Mango OK - Application non-déployée pour le chemin de contexte /Mango In-place deployment at D:\PFE\Mango\build\web deploy?config=file%3A%2FC%3A%2FUsers%2FBouali%2FAppData%2FLocal%2FTemp%2Fcontext4268238340729989227.xml&path=/Mango FAIL - Deployed application at context path /Mango but context failed to start D:\PFE\Mango\nbproject\build-impl.xml:847: The module has not been deployed. See the server log for details. BUILD FAILED (total time: 2 seconds) I await your answers in short delays. thank you in advance
The build script is already telling you what you should be doing next. Locate and look into the catalina.out file for more details as to why the web app failed to start. As to where the catalina log files are, that depends greatly on what type of Tomcat install this is. If it's integrated in Netbeans then it's located in the .netbeans/7.1.1/apache-tomcat/logs. If it is a debian / ubuntu based linux its found under /var/log/tomcat In either case the catalina log will show the root cause of the failure to start. But it's most likely something in the web.xml that is wrong.