Loop in Mark -Yasi
-----Original Message----- From: Yasi Xi (yxi) Sent: Tuesday, February 02, 2016 9:17 AM To: Tomcat Users List <users@tomcat.apache.org> Subject: Empty *jsp_java file after upgrade to Tomcat 8.0.26 Hi, Dear Mark T and all Sorry to resend this mail. I don't quite understand Mark's comment on this problem. ==== WHAT IS THE PROBLEM ==== I'm doing Tomcat upgrade for my J2EE server. When Tomcat is upgraded from 7.0.54 to 8.0.26, 1) I get lots of empty *_jsp.java files in /opt/apache-tomcat_1/work/Catalina/, for example: /opt/apache-tomcat_1/work/Catalina/localhost/cmp0307l/org/apache/jsp/webcomponents/jsp/globalpagenotfound_jsp.java /opt/apache-tomcat_1/work/Catalina/localhost/svc3000/org/apache/jsp/svccomponents/common/jsp/globalerror_jsp.java 2) There're six Tomcat servers working in a round-robin manner. Each of the six Tomcat server has lots of empty *_jsp.java files, but they do not share the same group of empty *_jsp.java files. It appears random regarding which JSP file gets an empty *_jsp.java and in which Tomcat server. 3) When I delete a single empty *_jsp.java file in a Tomcat server and restart Tomcat, the previous empty *_jsp.java is generated and not empty. 4) Before Tomcat upgrade from 7.0.54 to 8.0.26, /opt/apache-tomcat_1 soft link points to /opt/apache-tomcat-7.0.54_1, after the upgrade, it points to /opt/apache-tomcat-8.0.26_1 5) /opt/apache-tomcat-7.0.54_1 and /opt/apache-tomcat-8.0.26_1 are two separate directories. /opt/apache-tomcat-8.0.26_1 does not exist before the upgrade. [root@jm3btc003 opt]# ll /opt/ total 68 lrwxrwxrwx 1 root nobody 22 Dec 23 01:21 apache-tomcat_1 -> apache-tomcat-8.0.26_1 drwx------ 7 nobody nobody 4096 Dec 11 02:23 apache-tomcat-7.0.54_1 drwxr-x--- 9 root nobody 4096 Nov 10 01:51 apache-tomcat-8.0.26_1 ... 6) There are other empty files after upgrading to Tomcat 8.0.26, for example, the following picture files are created by Java process in a separate directory other than Tomcat directories, the picture files are empty: -rw-rw---- 1 nobody nobody 0 Jan 29 07:11 AQ_500/default.jpg -rw-rw---- 1 nobody nobody 0 Jan 28 19:04 BN_500/default.jpg -rw-rw---- 1 nobody nobody 0 Jan 28 21:05 CL_500/default.jpg -rw-rw---- 1 nobody nobody 0 Jan 28 19:00 CP_500/default.jpg -rw-rw---- 1 nobody nobody 0 Jan 28 20:05 DZ_500/default.jpg -rw-rw---- 1 nobody nobody 0 Jan 28 13:11 EG_500/default.jpg 7) We have some tomcat-embed-*.7.0.30.jar files deployed and scanned by Tomcat. Will these tomcat-embed-*.7.0.30.jar impact the *_jsp.java generation under Tomcat 8.0.26? /opt/txs/webapps/TXS/share/tomcat-embed-core-7.0.30.jar /opt/txs/webapps/TXS/share/tomcat-embed-jasper-7.0.30.jar ==== MARK'S COMMENT ==== Do you empty the work directory as part of this upgrade? If not, you should. Mark ==== YASI'S QUESTIONS ==== Sorry, Mark, I don't quite understand 1) Why empty work directory as part of Tomcat upgrade? /opt/apache-tomcat-8.0.26_1 does not exist before the upgrade. Should I empty /opt/apache-tomcat-7.0.54_1/work directory? 2) Is there any change of system IO (e.g. file read/write) in Tomcat 8 which may cause some file to be empty? Really appreciate your help! Regards, -Yasi --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
