Re: Tomcat 7.0.54 gives zero-byte .java and .class files for jsp in work directory that cause truncated class error

2016-08-09 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 David, On 8/4/16 9:19 PM, David Kerber wrote: > On 8/4/2016 3:18 AM, Rahul Singh wrote: >> Dear Christopher, >> >> >> Thanks you very much for your response !! >> >> >>> Filesystem quota? >> >> Filesystem Quota is not enabled for this disk

Re: Tomcat 7.0.54 gives zero-byte .java and .class files for jsp in work directory that cause truncated class error

2016-08-04 Thread David Kerber
On 8/4/2016 3:18 AM, Rahul Singh wrote: Dear Christopher, Thanks you very much for your response !! Filesystem quota? Filesystem Quota is not enabled for this disk partition so there is no restrictions on disk usage. Look at the timestamps on the zero-byte files, then find that same

Re: Tomcat 7.0.54 gives zero-byte .java and .class files for jsp in work directory that cause truncated class error

2016-08-04 Thread Rahul Singh
Dear Christopher, Thanks you very much for your response !! >Filesystem quota? Filesystem Quota is not enabled for this disk partition so there is no restrictions on disk usage. >Look at the timestamps on the zero-byte files, then find that same >place in catalina.out or one of the other

Re: Tomcat 7.0.54 gives zero-byte .java and .class files for jsp in work directory that cause truncated class error

2016-07-31 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rahul, On 7/28/16 1:50 AM, Rahul Singh wrote: > Hi tomcat team, Thanks for your continued support and help. > > I am facing the a peculiar problem in Tomcat 7.0.54. Any chance for a Tomcat upgrade? Also, Java 7 has reached End-of-Life. >

Tomcat 7.0.54 gives zero-byte .java and .class files for jsp in work directory that cause truncated class error

2016-07-27 Thread Rahul Singh
Hi tomcat team, Thanks for your continued support and help. I am facing the a peculiar problem in Tomcat 7.0.54. Configurations: OS: RHEL Tomcat:7.0.54 Java:1.7.79 A jsp that was running properly gave the following exception after graceful tomcat restart