-
1. JBoss 5.1 - Multiple deployments in error
nickarls Feb 2, 2011 3:45 PM (in response to hicsuntleones)try unsetting JBOSS_HOME and attach the complete log with stacktaces
-
2. Re: JBoss 5.1 - Multiple deployments in error
hicsuntleones Feb 2, 2011 4:12 PM (in response to nickarls)Hi Nicklas,
thanks for your kind reply.
I've unset the JBOSS_HOME variable and run Jboss.
Attached you can find the complete log/server.txt and log/boot.txt files
I'm on Win Server 64 bit.
Do you see anything else wrong in the logs?
Thanks, regards
Vincenzo
-
log_boot.txt.zip 32.7 KB
-
log_server.txt.zip 93.4 KB
-
-
3. Re: JBoss 5.1 - Multiple deployments in error
nickarls Feb 3, 2011 1:42 AM (in response to hicsuntleones)The "ClassLoader has not been set" in a bit omnious. Tried using a different dir than "Program Files". I think it can barf on that.
-
4. JBoss 5.1 - Multiple deployments in error
wdfink Feb 3, 2011 2:37 AM (in response to hicsuntleones)Problems with whitespaces in path or filenames are often a problem.
Install JBoss and Java JDK in directories without it!
-
5. JBoss 5.1 - Multiple deployments in error
hicsuntleones Feb 3, 2011 9:48 AM (in response to wdfink)Hi Nicklas and Wolf-Dieter,
thanks for your replies. I will try asap your suggestion and provide feedback.
Regards
Vincenzo
-
6. Re: JBoss 5.1 - Multiple deployments in error
hicsuntleones Feb 6, 2011 6:43 AM (in response to nickarls)Hi I have tried to install JBoss and Jdk in paths without spaces but the result is still the same.
In addition I have found a wiki entry (http://community.jboss.org/wiki/ClassLoaderhasnotbeensetexceptioninbootlog) where it is explained that the "ClassLoader has not been set" is just a debug info.
I have attached the newly generated logs, but they seem identical to the previous ones.
Is there any other attempt that I might make?
Thanks, regards
Vincenoz
-
log_server.txt.zip 93.1 KB
-
log_boot.txt.zip 32.3 KB
-
-
7. Re: JBoss 5.1 - Multiple deployments in error
hicsuntleones Feb 6, 2011 4:29 PM (in response to hicsuntleones)Hi all,
it was all a matter of starting the default configuration.
In fact, using all/standard/... the error disappeared
Thanks for your support
Vincenzo