On 07/06/2019 15:35, Alex O'Ree wrote:
> HTTP Status 500 – Internal Server Error
> Type Exception Report
> 
> Message Unable to compile class for JSP
> 
> Description The server encountered an unexpected condition that
> prevented it from fulfilling the request.

Not as helpful as I had hoped.

Given that the issue is random and that immediately retrying usually
works that tends to rule out permission issues.

Where is the work directory located? If it is anywhere other than local
disk that might be the source of the problem.

I'll look into improving those error messages a little (at least provide
source and destination file names).

Mark


> 
> Exception
> 
> org.apache.jasper.JasperException: Unable to compile class for JSP
>       
> org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:610)
>       
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:399)
>       org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:386)
>       org.apache.jasper.servlet.JspServlet.service(JspServlet.java:330)
>       javax.servlet.http.HttpServlet.service(HttpServlet.java:742)
>       org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>       
> org.apache.logging.log4j.web.Log4jServletFilter.doFilter(Log4jServletFilter.java:71)
> Root Cause
> 
> java.io.IOException: tmpFile.renameTo(classFile) failed
>       
> org.apache.jasper.compiler.SmapUtil$SDEInstaller.install(SmapUtil.java:204)
>       org.apache.jasper.compiler.SmapUtil.installSmap(SmapUtil.java:163)
>       
> org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:564)
>       org.apache.jasper.compiler.Compiler.compile(Compiler.java:378)
>       org.apache.jasper.compiler.Compiler.compile(Compiler.java:350)
>       org.apache.jasper.compiler.Compiler.compile(Compiler.java:334)
>       
> org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:595)
>       
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:399)
>       org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:386)
>       org.apache.jasper.servlet.JspServlet.service(JspServlet.java:330)
>       javax.servlet.http.HttpServlet.service(HttpServlet.java:742)
>       org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>       
> org.apache.logging.log4j.web.Log4jServletFilter.doFilter(Log4jServletFilter.java:71)
> Note The full stack trace of the root cause is available in the server logs.
> 
> 
> 
> 
> On Fri, Jun 7, 2019 at 4:58 AM Mark Thomas <ma...@apache.org> wrote:
> 
>> On 06/06/2019 20:38, Alex O'Ree wrote:
>>> I've upgraded from .34 to .40 somewhat recently (on windows) and have
>> been
>>> getting random errors rendering jsp pages recently. The trace is always
>>> related to jasper failing to rename a file. I'm not really sure what the
>>> issue is. Has anyone seen this or something similar?
>>>
>>> Usually retrying the request resolves the issue immediately but something
>>> seems fishy. This worked fine on previous versions.
>>
>> Can you provide a stack trace please.
>>
>> Thanks,
>>
>> Mark
>>
>> ---------------------------------------------------------------------
>> 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

Reply via email to