When the project is deployed to atat6.0 and started successfully, the error 500 is displayed on the access page. Solution: tomcat6.0500

When the project is deployed to atat6.0 and started successfully, the error 500 is displayed on the access page. Solution: tomcat6.0500

Example: when the project is deployed to tomcat6.0 and started successfully, the 500 error is reported on the access page. The solution is amazing. There is no problem at startup, but the 500 error is reported after the access address is entered, on the eve of the National Day holiday last year, I finally solved the problem for a long time. Today I met it again. At first glance, I couldn't help it. I thought about it later and quickly solved the problem.

Cause: the jar in the project and the jar in the lib in tomcat are repeated.

Solution:

1. If you change the version of Tomcat 7 or later, the problem will not occur in the later version.

2. Remove the WEB-INF and jsp-api.jar from the webapps \ Project name \ servlet-api-2.4.jar \ lib of tomcat after deployment