Two class loaders have to be loading the javax/transaction/xa/XAResource class. If its really not in more than one jar, then perhaps a jar has a manifest reference to the containg jar which is the same thing. There was a fix for the LinkageError issue added to the 3.0 branch over the weekend. Try that or followow the 3.2beta2 release notes to generate a class loading trace and submit a bug report if either you can't try the 3.0 branch code or it still exhibits a problem.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Brian Topping" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, December 09, 2002 1:43 PM Subject: [JBoss-user] java.lang.LinkageError -- help! Hi all, I'm stumped on a problem that I wondered if anyone recognizes. I've set up Quartz (http://www.part.net/quartz.html) as a SAR and have no problem repeatedly launching JBoss 3.0.4/Tomcat 4.1.x with it installed. Then I have a session bean that calls Quartz, into the SAR, through an InitialContext.lookup(). Everything works fine the first time that I install the EJB jar file in the deployment directory, and I can call it as many times as I want. But if I do a clean shutdown of JBoss, then immediately restart it, I get the following in the startup, while loading the EJB JAR: ###### java.lang.LinkageError: Class javax/transaction/xa/XAResource violates loader constraints at org.jboss.mq.SpyXAConnection.createXATopicSession(SpyXAConnection.java:96) at org.jboss.jms.asf.StdServerSessionPool.create(StdServerSessionPool.java:354) at org.jboss.jms.asf.StdServerSessionPool.<init>(StdServerSessionPool.java:168) at org.jboss.jms.asf.StdServerSessionPoolFactory.getServerSessionPool(StdServerS essionPoolFactory.java:101) at org.jboss.ejb.plugins.jms.JMSContainerInvoker.createSessionPool(JMSContainerI nvoker.java:538) .... ###### This problem is consistent, *unless* I blow away all the temp directories in JBoss. Then it loads fine. But only once, and I have to blow away the temp directories again before it will work again. I've confirmed that there are no overlapping classes between SAR, JAR and WAR files and all three files were built from a clean build and in sync with each other. Any ideas how I can make the environment stable across multiple launches? Thanks a bunch! Brian ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
