RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1338903 - java-1.8.0-openjdk problem with tomcat6
Summary: java-1.8.0-openjdk problem with tomcat6
Keywords:
Status: CLOSED DUPLICATE of bug 1223609
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: java-1.8.0-openjdk
Version: 6.8
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Elliott Baron
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-23 15:29 UTC by Martin Juricek
Modified: 2016-08-16 21:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-16 21:53:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1336481 0 high CLOSED Rebase: Upgrade ECJ to at least 4.4 2021-02-22 00:41:40 UTC

Internal Links: 1336481

Description Martin Juricek 2016-05-23 15:29:58 UTC 
Description of problem:
java-1.8.0-openjdk-1.8.0.91-1.b14.el6 doesn't work properly with tomcat6 server. jsp pages fail to display, exception is thrown instead.
Older version (java-1.8.0-openjdk-1.8.0.45-35.b13.el6 from rhel-6.7 seems to work fine).


Version-Release number of selected component (if applicable):
java-1.8.0-openjdk-1.8.0.91-1.b14.el6.x86_64
tomcat6-6.0.24-95.el6.noarch
tomcat6-webapps-6.0.24-95.el6.noarch


How reproducible:
100%

Steps to Reproduce:
1. Install and start tomcat6 
2. Try to access a .jsp page on the tomcat6


Actual results:
HTTP Status 500, exception stacktrace is thrown

Expected results:
Page correctly displayed


Additional info:

### tomcat6 is running: 
[root@virt-242 ~]# service tomcat6 status
tomcat6 (pid 2842) is running...[  OK  ]

[root@virt-242 ~]# ps aux | grep tomcat
tomcat    2842  0.5  9.5 2280348 97132 ?       Sl   16:39   0:13 /usr/lib/jvm/jre/bin/java -Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory -classpath :/usr/share/tomcat6/bin/bootstrap.jar:/usr/share/tomcat6/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar -Dcatalina.base=/usr/share/tomcat6 -Dcatalina.home=/usr/share/tomcat6 -Djava.endorsed.dirs= -Djava.io.tmpdir=/var/cache/tomcat6/temp -Djava.util.logging.config.file=/usr/share/tomcat6/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager org.apache.catalina.startup.Bootstrap start


### getting of index.jsp page fails:

# curl http://virt-242.cluster-qe.lab.eng.brq.redhat.com:8080/index.jsp

<html><head><title>Apache Tomcat/6.0.24 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 500 - </h1><HR size="1" noshade="noshade"><p><b>type</b> Exception report</p><p><b>message</b> <u></u></p><p><b>description</b> <u>The server encountered an internal error () that prevented it from fulfilling this request.</u></p><p><b>exception</b> <pre>org.apache.jasper.JasperException: Unable to compile class for JSP: 

An error occurred at line: 1 in the generated java file
The type java.io.ObjectInputStream cannot be resolved. It is indirectly referenced from required .class files

Stacktrace:
        org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:92)
        org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:330)
        org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:439)
        org.apache.jasper.compiler.Compiler.compile(Compiler.java:334)
        org.apache.jasper.compiler.Compiler.compile(Compiler.java:312)
        org.apache.jasper.compiler.Compiler.compile(Compiler.java:299)
        org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:589)
        org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:317)
        org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
        org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:723)
Comment 5 Elliott Baron 2016-08-16 21:53:38 UTC 
This appears to be a known issue with JSP compilation with Tomcat on RHEL 6. The current version of ECJ in RHEL 6, which is used by Tomcat to compile JSPs, does not properly support Java 8. We are attempting to upgrade ECJ to a newer version that fully supports Java 8 and should resolve these JSP compilation failures [1].

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1336481

*** This bug has been marked as a duplicate of bug 1223609 ***
Note You need to log in before you can comment on or make changes to this bug.