Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 356887

Summary: Entering 'Help->Help contents' sometimes causes RCP application to crash
Product: [Eclipse Project] Equinox Reporter: Cesar <luj_ghost83>
Component: Server-SideAssignee: equinox.server-side-inbox <equinox.server-side-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: eclipse, simon_kaegi
Version: 3.7   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug

Description Cesar CLA 2011-09-07 02:46:43 EDT
Build Identifier: 

I am using org.eclipse.help in my RCP. And I have come across a strange issue:

Sometimes when I go to Help->Help Contents, I get a window with this:

HTTP ERROR 500
Problem accessing /help/advanced/help.jsp. Reason: 

    Unable to compile class for JSP

Caused by:
org.apache.jasper.JasperException: Unable to compile class for JSP
      at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:572)
      at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:303)
      at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
      at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
      at org.eclipse.equinox.jsp.jasper.JspServlet.service(JspServlet.java:153)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
      at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180)
      at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
      at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:126)
      at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
……
……

Caused by: java.io.IOException: tmpFile.renameTo(classFile) failed
      at org.apache.jasper.compiler.SmapUtil$SDEInstaller.install(SmapUtil.java:245)
      at org.apache.jasper.compiler.SmapUtil.installSmap(SmapUtil.java:164)
      at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:429)
      at org.apache.jasper.compiler.Compiler.compile(Compiler.java:297)
      at org.apache.jasper.compiler.Compiler.compile(Compiler.java:276)
      at org.apache.jasper.compiler.Compiler.compile(Compiler.java:264)
      at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:563)
      ... 25 more


Note that it does not appears each time. If I refresh or restart the program, the error will not appear.
It seems someone has the same problem: http://www.eclipse.org/forums/index.php/m/624477/#msg_624477
But no one solve this. 

So, Is there anyone who can help me? Any ideas how to fix this? Thanks!



Reproducible: Sometimes
Comment 1 Cesar CLA 2011-09-07 02:51:25 EDT
I used Eclipse 3.7 to develop my RCP application. Operating system is WIN7.
Comment 2 Simon Kaegi CLA 2011-09-07 09:24:43 EDT
Also see https://issues.apache.org/bugzilla/show_bug.cgi?id=38713
Comment 3 Cesar CLA 2011-09-07 22:36:37 EDT
(In reply to comment #2)
> Also see https://issues.apache.org/bugzilla/show_bug.cgi?id=38713

Yes, you got it. I have also read that issue. The exception stack trace are same. 

In the plug-in directory, I have found Eclipse 3.7 are now using Jasper version 5.5.17. Bug 38713 says it is fixed in 5.5.25. So, will Jasper version 5.5.25 or later be used in the next release of Eclipse?
Comment 4 Holger Voormann CLA 2011-12-19 12:22:27 EST
The org.apache.jasper 5.5.17 has been replaced by the new jasper glassfish bundle org.apache.jasper.glassfish 2.2.2 (see bug 362724 comment 9). I assume that jasper.glassfish 2.2.2 is newer than jasper/tomcat 5.5.25 and that this bug is fixed in HEAD/master.

See also bug 367102 which should fix this bug, too.
Comment 5 Eclipse Genie CLA 2019-11-01 02:46:31 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 6 Holger Voormann CLA 2019-11-01 03:41:34 EDT
See my last comment for details.

*** This bug has been marked as a duplicate of bug 362724 ***