47

I have downloaded Eclipse and tried to create a sample servlet program but I got following error

The type java.io.ObjectInputStream cannot be resolved. It is indirectly referenced from required .class files

I have configured build path correctly. I am using Java 8 and Apache Tomcat 7 and libraries for both are referenced correctly.

Problem is specifically for Java EE only. Ordinarily Java SE projects are running fine.

Improve this question
8
  • What specific Java 8 version is this about? Commented May 2, 2016 at 11:06
  • 2
    I am getting the same exception with both jdk and jre Version 8 Update 91. Commented May 2, 2016 at 11:40
  • 1
    Red Hat issue related to this : access.redhat.com/solutions/2294701 Commented May 3, 2016 at 10:57
  • @İbrahimGürses I can't access it due to login restrictions. It would be kind if you could post the conclusion or solution if there is any. Commented May 3, 2016 at 12:08
  • @flob: The suggested resolution is "Consider precompiling JSPs as a workaround". There is also a link to a reopened bug report (1223609) and note that says "ecj is an older version that does not support java 8". I don't know what to make of that. There was no problem with Java 8 Update 77 AFAIK. Commented May 9, 2016 at 5:55

11 Answers 11

Reset to default
42

Something happened in Java 8 Update 91 that broke existing JSP code. That seems pretty clear. Here is a sample of similar questions and bug reports:

All these are about problems with Java 8 Update 91 (or later) that are not present when using earlier JRE/JDK versions.

The following OpenJDK changeset from 22 January 2016 appears to be related: http://hg.openjdk.java.net/jdk8u/jdk8u/jdk/rev/32f64c19b5fb (commit message "8144430: Improve JMX connections"). The changeset seems to be related to this vulnerability, https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3427, which is mentioned in a comment to this Red Hat bug report, https://bugzilla.redhat.com/show_bug.cgi?id=1336481.

The Update 91 release notes document mentions JDK-8144430 (non-public ticket): http://www.oracle.com/technetwork/java/javase/8u91-relnotes-2949462.html.

In "Oracle Critical Patch Update Advisory - April 2016", the CVE-2016-3427 vulnerability is mentioned: http://www.oracle.com/technetwork/security-advisory/cpuapr2016v3-2985753.html.

Improve this answer
Sign up to request clarification or add additional context in comments.

2 Comments

facing the same issue but once I move to tomcat 7 things are working fine..using jdk8_121
@dom, in the question it says "I am using Java 8 and Apache Tomcat 7". So what do you mean by "once I move to tomcat 7"?
8

You simply need to upgrade your Tomcat version, to Tomcat 8.0.xx. Java8 <-> Tomcat8

This is the configuration that I have been using and it has always worked out well JDK version Tomcat versions

Improve this answer

6 Comments

To me it seems like a bug in Java 8 Update 91. I doubt that upgrading Tomcat will fix the issue for everyone. See stackoverflow.com/questions/36981733/….
@user3891270: Does this answer help? Does it work if you upgrade to Tomcat 8?
Runtime Environments->Add->Apache->till 7 version i could find but 8th version of apache is not shown.How to add it externally.Please help me bro
@GaneshChowdharySadanala what version of Eclipse are you using? I suggest you to use new versions; they are faster, they still support old versions of java and more stable. You should find Apache 7 from version Kepler (4.3) on. eclipse.org/downloads
@IsmaelSarmento yeah I just resolved it by installing new version of eclipse jee
|
3

Reason : Old versions of Tomcat 6 JSP compiler don't seem to be aware of JDK 8 constant pool enhancements - eg. method handles. New code in JDK 8u is using a method handle instead of creating an anonymous class. This will cause the method handle to be listed in the constant pool and the eclipse compiler will choke on this - https://bz.apache.org/bugzilla/show_bug.cgi?id=56613

Improve this answer

Comments

2

same problem with me. This is not a solution but a workaround, which worked for me: Buildpath->Configure buildpath->Libraries-> Here remove the JRE system library pointing to JRE8 and add JRE system library for JRE7.

Improve this answer

Comments

2

Using the latest 7.x Tomcat (currently 7.0.69) solved the problem for me.

We did also try a workaround in a old eclipse bug, maybe that did it's part to solve the problem, too?

https://bugs.eclipse.org/bugs/show_bug.cgi?id=67414

Workaround:

  • Window->Preferences->Java->Installed JREs
  • Uncheck selected JRE
  • Click OK (this step may be optional?)
  • Check JRE again
Improve this answer

1 Comment

I am upgrading to tomcat-7.0.70, and i am seeing the problem in some cases. I use SUSE Linux version 12 and all is copacetic, but i have an older machine on version 11 SP 3, and that one still has the error with JDK_1.8.0_91.
2

Okay, this question was a year ago but I recently got this problem as well.

So what I did :

  1. Update tomcat 7 to tomcat 8.
  2. Update to the latest java (java 1.8.0_141).
  3. Update the JRE System Library in Project > Properties > Java Build Path. Make sure it has the latest version which in my case is jre1.8.0_141 (before it was the previous version jre1.8.0_111)

When I did the first two steps it still doesn't remove the error so the last step is important. It didn't automatically change the build path for jre.

Improve this answer

Comments

1

Workaround:

Window -> Preferences -> Java -> Installed JREs, select a different JRE

maybe this JDK edition is not suitable:

enter image description here

So try this one instead:

enter image description here

Problem solved!

Improve this answer

1 Comment

Exercise caution when downgrading -- it's worth noting that there are many known security vulnerabilities in prior versions of Java.
1

Upgrading to tomcat 7.0.70 resolved the issue for me

Improve this answer

1 Comment

Change the Tomcat server, I upgraded to Tomcat 8
1

I am using Google appengine java sdk and was facing similar issue. I had to add

<runtime>java8</runtime>

in appengine-web.xml file to make it work.

Improve this answer

Comments

0

I was also facing same issue. I had Jdk1.7.0.79. Then I updated it with Jdk8.0.120. Then the problem solved. After successful completion of upgraded jdk. Go to project->clean. It will rebuild the project and all red alert will be eliminated.

Improve this answer

Comments

0

If anyone trying to get an old Java EE Application Server onto Java 8 just for extended support (while of course upgrading the app server, because even Java 8's time is running out), I may have an answer for you.

Your mileage may vary, but by adding ecj-4.5.1.jar to the classpath of my server, this error goes away. I found this artifact in Maven Central here.

In my particular case, this was getting JBoss 5 running on Java 8, and this error appeared when opening the jmx-console, which is heavily used by us.

If like us and you're trying to run old JSP applications, you may also find that you need to update your jaxb-impl.jar to version 2.2.5. This can also be found here.

I'll mention it again that this is a short term fix and you need to prioritize getting off old versions of application servers; this only buys you a little bit of time. Make migration to modern Java technologies a priority.

Improve this answer

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.