SEVERE: Error getConfigured / ExtensionValidator error?

[benethridge]

This is a continuation of my attempt to get a simple Spring MVC up and running. See other thread for that history, if you wish:

http://forum.springframework.org/showthread.php?t=28199

Note that I have the rapidjava "timex" sample running from the book "Agile Java Development with Spring, Hibernate and Eclipse", so I think understand the basics of how this is supposed to hang together.


This time, instead of using spring.jar (2.0-rc3) plus the dependent libs from the rapidjava (remember, this was working kinda, with its spring.jar 2.0-m2), I used ALL the dependent jars included with 2.0-rc3. So, theoretically, I'm using the latest/greatest spring 2.0 with ALL its downloaded (and supposedly tested) dependencies. With that all in place in my classpath, tomcat shows this "error" in the log. I say "error" because, as you can see below, Spring doesn't think there's an error. It's just spitting out INFO messages, including the "Failure to find 3 required extension(s)". Tomcat (I assume) is spitting out the "SEVERE: Error getConfigured":

INFO: Deploying web application archive TestSpringMVC.war
Aug 18, 2006 10:21:13 AM org.apache.catalina.util.ExtensionValidator validateManifestResources
INFO: ExtensionValidator[/TestSpringMVC][commons-attributes-api.jar]: Required extension "ant" not found.
Aug 18, 2006 10:21:13 AM org.apache.catalina.util.ExtensionValidator validateManifestResources
INFO: ExtensionValidator[/TestSpringMVC][commons-attributes-compiler.jar]: Required extension "ant" not found.
Aug 18, 2006 10:21:13 AM org.apache.catalina.util.ExtensionValidator validateManifestResources
INFO: ExtensionValidator[/TestSpringMVC][commons-attributes-compiler.jar]: Required extension "javadoc" not found.
Aug 18, 2006 10:21:13 AM org.apache.catalina.util.ExtensionValidator validateManifestResources
INFO: ExtensionValidator[/TestSpringMVC]: Failure to find 3 required extension(s).
Aug 18, 2006 10:21:13 AM org.apache.catalina.core.StandardContext start
SEVERE: Error getConfigured
Aug 18, 2006 10:21:13 AM org.apache.catalina.core.StandardContext start
SEVERE: Context [/TestSpringMVC] startup failed due to previous errors
Aug 18, 2006 10:21:13 AM org.apache.catalina.core.StandardContext stop
INFO: Container org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/TestSpringMVC] has not been started

I've googled around on this, but can't find anything signif.

Anyone know why this is erroring?

Again, same as my other forum thread, if I revert back to the rapidjava/lib jars (from the book code), tomcat deploys the app without error, and it mostly runs, so this is probably about lib setup, not my app per se... or maybe some subtle inter-relationship between my app and the lib setup.

Ben

[Jelmer]

Try enabling log4j debugging. Right now you cannot see the errors

[sylvestris]

I have got exactly the same problem, and I can't find out how to solve it. It looks like web.xml is not getting processed, therefore log4j doesn't have time to start up and tell me what is going wrong. I'm trying to run PetClinic on Tomcat 5.5. I do have other Spring applications running on this Tomcat. I'm attempting to run everything inside Eclipse 3.2. Any ideas ?

[benethridge]

Welcome to jar hell (aka dll hell in the Microsoft world), and the biggest problem in the java world today, in my opinion.

We ended up "solving" this problem, by switching jars and tinkering with the classpath order until we found a combination that works. (Lots of fun, coz the problems problems often don't show up until statement execution time. )

I'm hoping that Spring team will give us (a) the main jars we need from them, (b) the third-party "dependent" jars they used in testing, and (c) the all-important classpath order of the jars they used in TESTING, so that we can avoid this hell in the future.

Of course, they give us (a) by definition, and I believe they give us (b) already, yes?

Maybe they have (c) in the release doc, and I just didn't see it?

Ben

[draconis-cs]

Just for documentation sake, I came across this when I added the jars from lib/jakarta-commons to my build. As soon as I took that directory out, it solved this message.

[dcoleman17]

I had the same problem after adding all the jar files from spring-framework-2.0.2/lib/jakarta-commons directory into my project. I fixed it by removing from my project:

commons-validator.jar
commons-digester.jar
commons-codec.jar
commons-attributes-compiler.jar

I don't know which one of these it was, I started by removing these 4 and then it worked.

[sornet]

I think the problem is located in the commons-attributes-*.jar build process.

Check META-INF/MANIFEST.MF in both "commons-attributes-api.jar" and "commons-attributes-compiler.jar".

Every extension Implementation URL contains blank spaces and carry returns!

Manifest-Version: 1.0
Ant-Version: Apache Ant 1.5.3 
Created-By: Apache Maven
Built-By: hen
Package: org.apache.commons.attributes
Build-Jdk: 1.4.2_05
Extension-Name: commons-attributes-api
Specification-Title: Client API for Jakarta Commons Attributes.
Specification-Vendor: The Apache Software Foundation
Implementation-Title: org.apache.commons.attributes
Implementation-Vendor: The Apache Software Foundation
Implementation-Version: 2.2
Extension-List: ant qdox
ant-Extension-Name: ant
ant-Implementation-Version: 1.5
ant-Implementation-URL: http://www.ibiblio.org/maven/ant/jars/ant-1.5.
 jar
qdox-Extension-Name: qdox
qdox-Implementation-Version: 1.5
qdox-Implementation-URL: http://www.ibiblio.org/maven/qdox/jars/qdox-1
 .5.jar
Implementation-Vendor-Id: org.apache
X-Compile-Source-JDK: 1.4
X-Compile-Target-JDK: 1.4

Edit the manifest files removing those characters so the implementation URLs are just in one line. It might looks like this:

Manifest-Version: 1.0
Ant-Version: Apache Ant 1.5.3 
Created-By: Apache Maven
Built-By: hen
Package: org.apache.commons.attributes
Build-Jdk: 1.4.2_05
Extension-Name: commons-attributes-api
Specification-Title: Client API for Jakarta Commons Attributes.
Specification-Vendor: The Apache Software Foundation
Implementation-Title: org.apache.commons.attributes
Implementation-Vendor: The Apache Software Foundation
Implementation-Version: 2.2
Extension-List: ant qdox
ant-Extension-Name: ant
ant-Implementation-Version: 1.5
ant-Implementation-URL: http://www.ibiblio.org/maven/ant/jars/ant-1.5.jar
qdox-Extension-Name: qdox
qdox-Implementation-Version: 1.5
qdox-Implementation-URL: http://www.ibiblio.org/maven/qdox/jars/qdox-1.5.jar
Implementation-Vendor-Id: org.apache
X-Compile-Source-JDK: 1.4
X-Compile-Target-JDK: 1.4

It worked fine for me.

[infernalproteus]

I'm afraid I still have an issue around commons-attributes-compiler.jar

1) I tried correcting the MANIFEST.MF file as suggested above, but this did not help at all. I still see all the "extension not found" messages mentioned in the first comment. In addition, I also see this message for commons-attributes-api.jar (so 4 extensions not found in all).
Further investigation indicates that the MANIFEST.MF file is not invalid, it is simply following line length limitations, as a mentioned in this post: http://forum.springframework.org/sho...07&postcount=9, I also saw some generic posts covering MANIFEST.MF files which mentioned this.

2) I was able to remove the qdox extension error by adding qdox-1.5.jar which is part of the spring distribution to my web applications "lib" folder. OK.
However, try as I might, I cannot fix the other extension errors (with and without the MANIFEST.MF changes specified).
For example, I do have commons-attributes-api.jar in my lib folder and it's implementation-version is 2.2, which satisfies the requirement imposed by the manifest in commons-attributes-compiler.jar. I still see the missing extension error.

I later tried dumping all the JARs in the spring distribution into my lib folder to no effect.

3) The spring readme mentioned that commons-attributes-api.jar has a patched manifest with the qdox and the ant requirement removed. It follows that I should be able to remove these extensions dependencies from commons-attributes-compiler.jar as well. Will Spring's common attribute support be affected? I would like to think not, but can someone from the Spring team please shed some light on this?

I will point out that earlier versions of the commons-attributes libraries did not have any extensions listed in their manifests. This is also the reason why some users had broken deployments when they shifted from Spring 2 RC2 to RC3, the commons-attributes libraries were upgraded from version 2.1 to 2.2 and only the latter had the extensions listed in the manifest.


Following up with some details, I have a simple empty web application to which I have added the Spring core JAR and it's other dependent JARs. Later, I added all the JARs distributed with Spring as a "kitchen sink" test. I'm deploying this to Tomcat 6.

Any suggestions appreciated,
Brian.

[cwilkes]

Any suggestions appreciated,

Use maven and it takes care of all the jars you need in the WEB-INF/lib directory for you

[infernalproteus]

cwilkes, thanks for the input. Unfortunately maven is not an option - I do not wish to change my build/deploy infrastructure to combat this issue; at this point I'm not even sure if it has to do with missing JAR files.

Any other ideas?