The production package reports a path error that cannot be found in the development environment. Modifying the configuration can solve the problem, but will it be annoying if path is involved in every online change? Or, how can this be tolerated?
The solution is as follows:
For production security, it is better not to modify the configuration. The idea is to manually create the directory required to run the program in the development environment.
For example, if tomcat is installed in C in the development environment: the subdirectory where the disk is installed is not important)
View the production configuration, for example,/one/two/three/four/WebSphere/logs/myapp/logs/rootLog. log.
In the development environment C: Create a disk/one/two/three/four/WebSphere/logs/myapp/logs
Well, the world is quiet.
[Solve other similar problems]
1) if the directory is not used in the root path such as C :), try the bin directory under the Tomcat installation directory.
Example: C: \ Program Files (x86) \ Apache Software Foundation \ Tomcat 5.0 \ bin
2) if you find that it is okay to manually execute batch processing to start Tomcat, you can set "Working Path" on the Startup tab, for example, creating those directories on disk C, set it to C: the disk is ready.
[Possible interference]
1) What if I shut down Tomcat and restarted wood? Tomcat and Apache do not seem to be the same thing)
2) In eclipse, tomcat can be started and sometimes cannot be started. It looks a little unstable. Check the hosts file under C: \ Windows \ System32 \ drivers \ etc and add a line:
- 127.0.0.1 localhost.localdomain localhost
This article is from the iData blog, please be sure to keep this source http://idata.blog.51cto.com/4581576/1163400