CGJ,
> Class.forName() can deliver ugly class references that
> have been wrongly cached inside your VM
An interesting lead... I'll have to look into this further. Could it be
that even though there is only one instance of the class on the classpath,
the JVM thinks there are two, and throws a duplicate class definition error?
> Are you sure that there is no other instance of jboss-net.sar anywhere in
> your distro that might already have been deployed (look at the server log
for
> AxisService to be started)?
I found it in one other place -- ${jboss.root}/server/all . Removing it did
not fix the problem.
> What about putting the sar into the auto-deploy
> directory at startup, does this work?
nope. log file attached for your reference.
> Do you have only problems with your
> copied config or does this appear with the default config, too?
I encountered this problem with the default config, so I decided to make a
copy before changing it -- they are essentially identical.
I'm going to try to find out where the class is loaded -- perhaps this will
provide more clues.
- Matt Munz
-----Original Message-----
From: Jung , Dr. Christoph [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 17, 2002 4:14 AM
To: '[EMAIL PROTECTED]'; [EMAIL PROTECTED]
Cc: '[EMAIL PROTECTED]'
Subject: Hotspot classloading prob and tt-bytecode.jar *was* AW:
JBoss.net deployment stopped by java.lang.LinkageError
Matt,
The longer I look at this stacktrace, the more I am convinced that it is not
a particular tt-bytecode or axis problem, but could be related to the
hotspot
classloading bugs that we were discovering with the jboss-unified
classloaders (e.g., Class.forName() can deliver ugly class references that
have been wrongly cached inside your VM)
I now got a combination of JBoss 3.1 (head rev), JRE 1.4.0_01-b03 and
Jboss.net running on my machine without probs that can even hot-deploy the
whole Axis engine and corresponding web service applications.
Are you sure that there is no other instance of jboss-net.sar anywhere in
your
distro that might already have been deployed (look at the server log for
AxisService to be started)? What about putting the sar into the auto-deploy
directory at startup, does this work? Do you have only problems with your
copied config or does this appear with the default config, too?
I apologize for not having thought of this possibility before the bug has
been filed. Nevertheless it would be interesting to hear what the future of
the tt-bytecode.jar in Axis will be.
Best,
CGJ
-----Ursprüngliche Nachricht-----
Von: Matt Munz [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 16. Juli 2002 22:15
An: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Betreff: JBoss.net deployment stopped by java.lang.LinkageError
Hello Axis Users and Developers,
I have registered a bug #10879 in the bug database regarding a runtime
incompatibility between jre1.4.1 and tt-bytecode.jar, upon which axis is
apparently dependant. I have a couple of questions relating to this.
1) What version of tt-bytecode.jar is this? The manifest says "1.0", but
the File List for the tech trader project
(http://sourceforge.net/project/showfiles.php?group_id=15912) only shows
versions 2.1.1 - 2.1.3.
2) Will Axis be migrating to tt-bytecode's successor, serp, anytime in the
near future?
Thanks for your help. I apologise for "broadcasting" this message to both
mailing lists, but I wasn't sure which was more appropriate. Also, please
cc: mmunz@apelon as I am not a subscriber to either list.
- Matt Munz
[EMAIL PROTECTED]
###########################################
This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/
