I tested my jsp codes in my local machine and it works great.
I then deploy the code to a linux server and encounter the error below. I'm not sure how to approach this situation. I gave the permission for user, group, and others to be rwx for myFile.jsp also for the directories where the file kept.
It sounds like Tomcat was installed by one user and is now being run under another username.
You could either: Start tomcat from the same login under which it was installed or ease the permissions for the tomcat/work directory. Tomcat must be able to read and write to the directories under the work directory and the logs directory. It only needs read permissions for the rest.
Odds are that root installed and you're testing under your own user account. I've been bitten by this myself.
The best way to test Tomcat under linux seems to be just unpacking your your own personal tomcat (e.g. under your home directory) and using that one.
For system (production server) use, I prefer to create a user/group named tomcat and "chown tomcat:tomcat --recursive /usr/local/tomcat" so that Tomcat won't have to run as root. In my case, my tomcat init scripts su to be the tomcat user before starting the production server.
Sometimes the only way things ever got fixed is because people became uncomfortable.
Subsequent hits go straight to the last step. If you change the JSP file, the process starts over again. In Tomcat the source and class files get written to directories under the tomcat/work directory.
If, for whatever reason, tomcat can't write to or read from that directory, you're going to see the above exception. One way or another, you will need to insure that the user under which Tomcat is running can read and write to that directory structure. It will also need to be able to write to the tomcat/logs directory.