> -----Original Message----- > From: Fernando Padilla [mailto:[EMAIL PROTECTED] > Sent: Monday, December 29, 2003 8:45 PM > > This LinkageError is really annoying, becuase we can't use the Unit > testing to the fullest. Does anybody have any idea what is going > wrong? >
No, unfortunately not. I have been struggling with this problem for quite a few days and found absolutely nothing. > I went and added the maven.pom.dependeies from merlin/kernel/servlet, but > nothing changed. > After reading the JDK api-docs for java.lang.LinkageError: Subclasses of LinkageError indicate that a class has some dependency on another class; however, the latter class has incompatibly changed after the compilation of the former class. I decided on completely rebuilding absolutely everything. I erased my merlin sources, made a fresh CVS checkout, rebuilt and reinstalled. After that, I updated my merlin-related dependencies, cleaned my project's target directory and rebuilt. Same error. Very strange. I am just guessing here, but could it be that on a second merlin startup - if given a custom classloader via InitialContext - a subset of merlin's internal classes is loaded via a classloader different from the classloader used during the first startup? Also, the situation is different from merlin standalone in that the JVM "survives" the shutdown and restart of the kernel. So some of merlin's classes might remain loaded, whereas others might be actively and explicitely reloaded by merlin during restart, ultimately leading to this LinkageError. But then again I know very little about classloading issues and could be completely off track. If it's a classloading issue at all. Cheers, Olaf > > > > On Mon, 29 Dec 2003, Olaf Bergner wrote: > > > Thanks, man. I was starting to believe I was going nuts. > Couldn't believe my > > eyes when I first came across this problem and decided on > refraining from > > reporting it since it seemed to be so far out. I am using a > rewrite of the > > AbstractMerlinTestCase with only some setters added so that it > is easier to > > adapt to my environment. Switched to AMTC just for verification > and got the > > exact same LinkageError. > > > > Cheers, > > > > Olaf > > > > > -----Original Message----- > > > From: Stephen McConnell [mailto:[EMAIL PROTECTED] > > > Sent: Monday, December 29, 2003 12:45 PM > > > To: Avalon framework users > > > Subject: Re: Merlin Dynamic Block Un/Loading > > > > > > > > > > > > > > > Fernando Padilla wrote: > > > > > > > Thank you Stephen for your previous responces! :) But, let's > > > > continue. Below are more things that I would love your comments on. > > > > > > > > > Fernando: > > > > > > I've downloaded your kernel and can confirm your second > problem with the > > > link error - this seems to be some sort of a classloader issue but no > > > immediate idea of what the problem could be. I did some additional > > > tests relative to the merlin unit test case and there are no problems > > > with multiple tests (corresponding to multiple kernel > deployments in the > > > same run). One reason could be that in the merlin case the classloader > > > structure is a lot cleaner than in your case - probably an > area to look > > > into. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
