top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Tomcat class loading with index.list - invalid jar index exception

+1 vote

I am facing an invalid jar index exception in both tomcat 5.5.x and 7.0.39 . After some investigation , we figured out this is because of class loading in tomcat which uses index.list file in jar files. I have two jars with same package names but classes in those package are different. Since the package name are defined or mentioned in the index.list file of every jar for some reason tomcat is showing me an invalid jar index exception even if try to load a simple index.jsp.

posted Sep 5, 2013 by Amit Parthsarthi

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote

Your jar indexes are broken. They need to be re-generated for all the JAR files in in one go so that the package mappings are correct.

The error you are seeing is from the JRE code, not from Tomcat.

answer Sep 5, 2013 by Kumar Mitrasen
Thanks for the response. The issue we were facing is when we are tying to access a simple index.jsp file which is deployed on tomcat.

I am sure java handles the libraries properly since tomcat is a component in our system and all other  components are working fine. This issue is very particular to tomcat where it detects a duplicate package name across jar files and throws an invalid jar index exception. And also as you have mentioned I regenerate all the jar files using maven/jenkins build before deploying.
Similar Questions
+2 votes

While doing some testing out of the blue seeing a string of SEVERE messages in catalina.out. Apache is not running and in fact has been uninstalled. The proxyPort directive has been removed from the Tomcat server.xml connector config, and Tomcat has been rebooted. I was using http not ajp.

org.apache.coyote.ajp.AjpMessage processHeader
SEVERE: Invalid message received with signature xxxx

Any pointer?

+1 vote

I'm trying to use the Tomcat8 jsr client functionality in a standalone java client. I'm trying to use the minimal number of jars, so I gabbed websocket-api.jar ONLY. When I call ContainerProvider.getWebSocketContainer(), it returns null. Do I need another jar to resolve this on the client?