You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Rahul Singh <rk...@hotmail.com> on 2016/08/04 07:18:20 UTC
Re: Tomcat 7.0.54 gives zero-byte .java and .class files for jsp in
work directory that cause truncated class error
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 Tomcat-specific log files.
>See if there's anything in those log files that gives a reason for the
>failure to compile your JSPs.
We have seen the catlina.out and other tomcat logs but no such evidence regarding the compilation of JSP.
during googling in various forums, we have observed that the same problem is occurred to one of the senior engineer of google, and it is unresolved/open yet.
reference: http://stackoverflow.com/questions/8813509/how-does-tomcat-generate-its-work-directory-jsp-java-files-and-what-might-cau
It is very critical problem in our production environments (occurring Many production environments), and it is raised as tomcat specific problem so occurrence condition and root cause may be required from tomcat team.
Regards,
Rahul Kumar Singh
________________________________
From: Christopher Schultz <ch...@christopherschultz.net>
Sent: Sunday, July 31, 2016 5:38:13 PM
To: Tomcat Users List
Subject: Re: Tomcat 7.0.54 gives zero-byte .java and .class files for jsp in work directory that cause truncated class error
-----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.
> Configurations: OS: RHEL Tomcat:7.0.54 Java:1.7.79
If you are using RHEL packages, you may not have an upgrade path. :(
> A jsp that was running properly gave the following exception after
> graceful tomcat restart
>
> ======== javax.servlet.ServletException:
> java.lang.ClassFormatError: Truncated class file at
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:343)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appli
cationFilterChain.java:303)
>
>
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:208)
> at
> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>
>
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:241)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFi
lterChain.java:208)
>
>
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatc
her.java:748)
> at
> org.apache.catalina.core.ApplicationDispatcher.processRequest(Applicat
ionDispatcher.java:486)
>
>
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDisp
atcher.java:411)
> at
> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDisp
atcher.java:338)
>
>
at
org.apache.struts2.dispatcher.ServletDispatcherResult.doExecute(ServletD
ispatcherResult.java:154)
> at
> org.apache.struts2.dispatcher.StrutsResultSupport.execute(StrutsResult
Support.java:186)
>
>
at
com.opensymphony.xwork2.DefaultActionInvocation.executeResult(DefaultAct
ionInvocation.java:362)
> at
> com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionIn
vocation.java:266)
>
> ====
>
> On checking the Tomcat work directory we discovered that the
> corresponding .java and .class files were of zero byte size. In
> other words these files were empty. This was the main reason why
> Tomcat gave truncated class error. Corresponding to this we also
> checked the disk utilization but it was at 54% only. So any
> possibility for disk space are ruled out.
Filesystem quota?
> Also that the same jsp had not been modified and was running
> properly initially. so after reboot of tomcat what happen? why the
> jsp.java and jsp.class size is generated of 0 bytes.
>
> So my question is that what might have caused tomcat to generate
> empty *_jsp.java files in its work directory?
>
> Hope tomcat team will help us to finding root cause.
Look at the timestamps on the zero-byte files, then find that same
place in catalina.out or one of the other Tomcat-specific log files.
See if there's anything in those log files that gives a reason for the
failure to compile your JSPs.
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAled6i0ACgkQ9CaO5/Lv0PB59ACePn8ro2YsATZjgDFh8lTH1dU/
T5YAnjxaL4LZB4BdfL/wTJuPEeBfT4fh
=pvZ5
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 7.0.54 gives zero-byte .java and .class files for jsp in
work directory that cause truncated class error
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----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 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 Tomcat-specific
>>> log files. See if there's anything in those log files that
>>> gives a reason for the failure to compile your JSPs.
>>
>> We have seen the catlina.out and other tomcat logs but no such
>> evidence regarding the compilation of JSP.
>>
>>
>> during googling in various forums, we have observed that the
>> same problem is occurred to one of the senior engineer of google,
>> and it is unresolved/open yet.
>>
>>
>> reference:
>> http://stackoverflow.com/questions/8813509/how-does-tomcat-generate-i
ts-work-directory-jsp-java-files-and-what-might-cau
>>
>>
>>
>>
>>
It is very critical problem in our production environments (occurring
>> Many production environments), and it is raised as tomcat
>> specific problem so occurrence condition and root cause may be
>> required from tomcat team.
>
> Have you verified that the user TC is running under has permissions
> to write to the directories in question?
Tomcat wouldn't be able to write zero-byte files if there were
file-permissions problems.
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJXqgiRAAoJEBzwKT+lPKRYWSgQAMt6CBuAYul5JQpiN2GjTk8b
azl4sV/l10O20US4TmxHHK5s7qhkApQPI/Au+NIkwJ9JzJgGcrvyln9tXoiF5NnB
bkS4ac42/z90nW2XJrMAb5yOr5GT8whSu3jvS2z1uZS2/iOnDzkuJ+fzisZeaWtp
FtG+KXw28+2TqPUusiZzAiJZaE71YThl9EtgLb7Rd3aeUbokcH8pzj149n2XxpJ+
6YdbgePJhw0Kej3MHlDp9IgfRo/heD3ogr2MgXdxiUTj1CooabHlmSQFVyhITN7e
XkRjFK8liqIcXO7YlbX4xDMS479lgYFHY5I2I6dwqZKIF4AjhvVjijLUap9pnwlf
gtDjjILU8YtOCudIhsLc0k6i4VIwuYLeFkvg0wIq6LmTrpLoPmgfWQB1uMBPrJn+
9dfjiIbsJlDqEMwyN/dRjq3XOXEQiljTx6nWuZOJeCd2SQ2fX///GLQfgvbKH6TN
km6wD3SKWV1dW9qn2tf1M3hVvPZq5FO6LCWuFxNUo1skucQrKCcH1UoU3swEpCQu
smWGacd20ahYKF1WAb94TY/wX/K0BI8I2pgO5C6LsktVZpgLCOeFc7Kn+s01Ww6x
24zdBp2xM4PB3hsXT+QpKqLhBSDjRQCYC09yOTh0+BM2ibXg+Fh13fIePzk7rQ/Y
j9ROIfCeqpLo/rc3b5t9
=6zpP
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 7.0.54 gives zero-byte .java and .class files for jsp in
work directory that cause truncated class error
Posted by David Kerber <dc...@verizon.net>.
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
>> place in catalina.out or one of the other Tomcat-specific log files.
>> See if there's anything in those log files that gives a reason for the
>> failure to compile your JSPs.
>
> We have seen the catlina.out and other tomcat logs but no such evidence regarding the compilation of JSP.
>
>
> during googling in various forums, we have observed that the same problem is occurred to one of the senior engineer of google, and it is unresolved/open yet.
>
>
> reference: http://stackoverflow.com/questions/8813509/how-does-tomcat-generate-its-work-directory-jsp-java-files-and-what-might-cau
>
>
> It is very critical problem in our production environments (occurring Many production environments), and it is raised as tomcat specific problem so occurrence condition and root cause may be required from tomcat team.
Have you verified that the user TC is running under has permissions to
write to the directories in question?
>
>
>
> Regards,
>
> Rahul Kumar Singh
>
>
>
>
>
>
> ________________________________
> From: Christopher Schultz <ch...@christopherschultz.net>
> Sent: Sunday, July 31, 2016 5:38:13 PM
> To: Tomcat Users List
> Subject: Re: Tomcat 7.0.54 gives zero-byte .java and .class files for jsp in work directory that cause truncated class error
>
> -----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.
>
>> Configurations: OS: RHEL Tomcat:7.0.54 Java:1.7.79
> If you are using RHEL packages, you may not have an upgrade path. :(
>
>> A jsp that was running properly gave the following exception after
>> graceful tomcat restart
>>
>> ======== javax.servlet.ServletException:
>> java.lang.ClassFormatError: Truncated class file at
>> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:343)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appli
> cationFilterChain.java:303)
>>
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
> erChain.java:208)
>> at
>> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>>
>>
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
> tionFilterChain.java:241)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFi
> lterChain.java:208)
>>
> at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatc
> her.java:748)
>> at
>> org.apache.catalina.core.ApplicationDispatcher.processRequest(Applicat
> ionDispatcher.java:486)
>>
> at
> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDisp
> atcher.java:411)
>> at
>> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDisp
> atcher.java:338)
>>
> at
> org.apache.struts2.dispatcher.ServletDispatcherResult.doExecute(ServletD
> ispatcherResult.java:154)
>> at
>> org.apache.struts2.dispatcher.StrutsResultSupport.execute(StrutsResult
> Support.java:186)
>>
> at
> com.opensymphony.xwork2.DefaultActionInvocation.executeResult(DefaultAct
> ionInvocation.java:362)
>> at
>> com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionIn
> vocation.java:266)
>> ====
>>
>> On checking the Tomcat work directory we discovered that the
>> corresponding .java and .class files were of zero byte size. In
>> other words these files were empty. This was the main reason why
>> Tomcat gave truncated class error. Corresponding to this we also
>> checked the disk utilization but it was at 54% only. So any
>> possibility for disk space are ruled out.
> Filesystem quota?
>
>> Also that the same jsp had not been modified and was running
>> properly initially. so after reboot of tomcat what happen? why the
>> jsp.java and jsp.class size is generated of 0 bytes.
>>
>> So my question is that what might have caused tomcat to generate
>> empty *_jsp.java files in its work directory?
>>
>> Hope tomcat team will help us to finding root cause.
> Look at the timestamps on the zero-byte files, then find that same
> place in catalina.out or one of the other Tomcat-specific log files.
> See if there's anything in those log files that gives a reason for the
> failure to compile your JSPs.
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iEYEARECAAYFAled6i0ACgkQ9CaO5/Lv0PB59ACePn8ro2YsATZjgDFh8lTH1dU/
> T5YAnjxaL4LZB4BdfL/wTJuPEeBfT4fh
> =pvZ5
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org