Please post the entire console logs. That might give us an idea about what's wrong. Have you deployed any of your applications yet on this installation?
And did you replace/add any jar files in the server, especially any jars related to log4j?
The first problem looks like you are licking up an old version of log4j.
Make sure that your CLASSPATH environment variable is not set. (Yes, I mean *NOT* set.) The run script will set the necessary classpath.
Also, make sure that you do not have any "endorsed" directories in your JVM.
If this doesn't help, add "-verbose:class" to the JVM command line within run.bat. This option causes the JVM to print out the JAR file for every class loaded - that should help you locate the stray log4j jar file.
I deployed session bean in jboss 4.2.3GA . It deployed successfully. But It is giving the exception while running the client.. It is not showing any stack trace on Jboss Console. But showing on client console.
Please help me in this regard.
But showing on client console.
Which means that your client side classpath is having an incorrect version of log4j jar file? What is your classpath pointing to and how do you set the classpath? Are you using an IDE?
Buddy you should perhaps try out giving the following property in your systemVariables:
PATH = "c:\windows\system32"
or alternatively wherever your windows folder exists, give path to system32 directory.