java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "org.terracotta.modules.ehcache.xa.EhcacheXAStoreClusteredImpl.isValid(Lnet/sf/ehcache/transaction/xa/VersionAwareCommand;Ljavax/transaction /xa/Xid;)Z" the class loader (instance of org/terracotta/express/ClusteredStateLoader) of the current class, org/terracotta/modules/ehcache /xa/EhcacheXAStoreClusteredImpl, and the class loader (instance of org/mortbay/jetty/webapp/WebAppClassLoader) for interface net/sf/ehcache /transaction/xa/EhcacheXAStore have different Class objects for the type javax/transaction/xa/Xid used in the signature

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Terracotta Project Issue Tracker by Himadri Singh, 1 year ago
loader (instance of org/terracotta/express/ClusteredStateLoader) of the current class, org/terracotta/modules/ehcache /xa/EhcacheXAStoreClusteredImpl, and the class loader (instance of org/mortbay/jetty/webapp/WebAppClassLoader) for interface net/sf/ehcache /transaction/xa/EhcacheXAStore have different Class objects for the type javax/transaction/xa/Xid used in the signature
via Terracotta Project Issue Tracker by Himadri Singh, 1 year ago
loader (instance of org/terracotta/express/ClusteredStateLoader) of the current class, org/terracotta/modules/ehcache /xa/EhcacheXAStoreClusteredImpl, and the class loader (instance of org/mortbay/jetty/webapp/WebAppClassLoader) for interface net/sf/ehcache /transaction/xa/EhcacheXAStore have different Class objects for the type javax/transaction/xa/Xid used in the signature
via terracotta.org by Unknown author, 2 years ago
(instance of org/terracotta/express/ClusteredStateLoader) of the current class, org/terracotta/modules/ehcache /xa/EhcacheXAStoreClusteredImpl, and the class loader (instance of org/mortbay/jetty/webapp/WebAppClassLoader) net/sf/ehcache /transaction/xa/EhcacheXAStore have different objects the type javax/transaction/xa/Xid used in the signature
java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "org.terracotta.modules.ehcache.xa.EhcacheXAStoreClusteredImpl.isValid(Lnet/sf/ehcache/transaction/xa/VersionAwareCommand;Ljavax/transaction /xa/Xid;)Z" the class loader (instance of org/terracotta/express/ClusteredStateLoader) of the current class, org/terracotta/modules/ehcache /xa/EhcacheXAStoreClusteredImpl, and the class loader (instance of org/mortbay/jetty/webapp/WebAppClassLoader) for interface net/sf/ehcache /transaction/xa/EhcacheXAStore have different Class objects for the type javax/transaction/xa/Xid used in the signature
at org.terracotta.modules.ehcache.store.TerracottaClusteredInstanceFactory.getOrCreateXAStore(TerracottaClusteredInstanceFactory.java:194)
at org.terracotta.modules.ehcache.store.TerracottaClusteredInstanceFactory.createXAStore(TerracottaClusteredInstanceFactory.java:125)
at net.sf.ehcache.terracotta.StandaloneTerracottaClusteredInstanceFactory.createXAStore(StandaloneTerracottaClusteredInstanceFactory.java:60)
at net.sf.ehcache.CacheManager.createEhcacheXAStore(CacheManager.java:427)
at net.sf.ehcache.Cache.initialise(Cache.java:1038)
at net.sf.ehcache.CacheManager.addCacheNoCheck(CacheManager.java:1010)
at net.sf.ehcache.CacheManager.addCache(CacheManager.java:938)
at net.sf.ehcache.CacheManager.addCache(CacheManager.java:916)
at org.terracotta.ehcache.TMLookup.init(TMLookup.java:68)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:440)
at org.mortbay.jetty.servlet.ServletHolder.getServlet(ServletHolder.java:339)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)

Users with the same issue

You are the first who have seen this exception.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.