Production package in the development environment reported a path can not find the error, modify the configuration of course to solve the problem, but if each online change is involved in the path of the matter will be annoying it? Or do you just put up with it?
Here's the solution:
For production safety, do not modify the configuration for good. The idea is to manually create the directory that the development environment needs to run the program.
For example, the development environment Tomcat is installed on the C: disk (This is not important at this point in which subdirectory is specifically installed)
View production configuration such as:/one/two/three/four/websphere/logs/myapp/logs/rootlog.log
Create/one/two/three/four/websphere/logs/myapp/logs in development environment C: disk
Well, the world is quiet.
[solve other similar problems]
1 Try the bin directory in the Tomcat installation directory if the directory is built on the root path (for example, C:).
For example: C:\Program Files (x86) \apache Software Foundation\tomcat 5.0\bin
2 If you find that it is not a problem to start Tomcat manually by using Tomcatmonitor, you can set "Working Path" On the Startup tab, for example, if you created those directories in C disk, this is set to C: The disk is OK.
[Possible interference]
1 tomcat off reboot the wood there? (Tomcat and Apache don't seem to be the same thing)
2 in Eclipse can start Tomcat, sometimes do not start, looks a bit unstable, may wish to check the Hosts file under C:\Windows\System32\drivers\etc, add a line:
127.0.0.1 localhost.localdomain localhost