Terracotta Discussion Forums

Thanks for the suggestion hhuynh, however, I'm not using any of "my own" jars. Just ehcache-server war distribution out of the box.

I'm all for removing lib files that conflict, but the question is, which lib files?

Just looking for the standard JBOSS 4 or 5 solution as it appears to work with Weblogic.

If you see another post, you can see that the stand alone server has issues as well.

Thanks.

You also have to remove
slf4j-api-1.5.8.jar

However, I believe you need to keep resolver in there, or else you get a missing class exception (com/sun/org/apache/xml/internal/resolver/CatalogManager).

Leaving the resolver in there, and gave this a try, however, had the following XML Qname error:

11:38:05,198 SEVERE [http] WSSERVLET11: failed to parse runtime descriptor: java.lang.LinkageError: loader constraints violated when linking javax/xml/namespace/QName class java.lang.LinkageError: loader constraints violated when linking javax/xml/namespace/QName class

Out of the box, on Windows XP, the 1.0.0 standalone server does not startup.

There is a large amout of errors spit out. Glassfish does actually start up, but not of the advertised RESTFul ehcache server starts up.

Full log attached.

Starts with a jasper exception:
org.apache.jasper.JasperException: PWC6177: XML parsing error on file file:/Z:/p
rograms/ehcache-standalone-server-1.0.0/war/WEB-INF/lib/jersey-server-1.1.5.jar
at org.apache.jasper.xmlparser.ParserUtils.parseXMLDocument(ParserUtils.
java:325)

Then nothing starts up after that:

SEVERE: PWC1306: Startup of context /ehcache failed due to previous errors
Sep 2, 2011 4:11:38 PM org.apache.catalina.core.StandardContext start
SEVERE: PWC1305: Exception during cleanup after start failed
org.apache.catalina.LifecycleException: PWC2769: Manager has not yet been started

Environment: XP
Standard JBOSS AS 5.1.0

The initial problem I saw was that jaxb-api-2.0.jar was found, but that actually 2.1.jar was needed, but puting the different jar just lead to Class mismatch errors.

I tried a number of things, but they all ended up failing with different types of errors:
-Removing all the jaxb .jar from the WEB-INF/lib folder (relying on JBOSS's version)
-Added 2.1 api and jaxb-api-2.1.9 api

Also, there was a similar problem with slf4j-api-1.6.jar saying that the Class did not match the interface. Removing the jar from the lib directory solved the problem.

We need some official commentary about how to get it working with JBOSS 5.1.0, similar to how there was a commentary on how to get it working with WebLogic. What jar's do we remove, what do we add etc.

Do we have to change the endorsed jaxb files of JBOSS? That would hurt portability.