Jboss warning(No appenders could be found for logger) during

[alkarim]

Hi all
I have installed jboss-4.0.2 on my desktop. I am using win xp and have java sdk 1.5. I am getting the following error when I startup jboss. Can somebody guide me on this ?
Thanks
Al



C:\jboss-4.0.2\bin>run
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: C:\jboss-4.0.2\bin\\..
JAVA: c:\jdk1.5.0_04\bin\java
JAVA_OPTS: -Dprogram.name=run.bat -Xms128m -Xmx512m
CLASSPATH: c:\jdk1.5.0_04\lib\tools.jar;C:\jboss-4.0.2\bin\\run.jar
===============================================================================
log4j:WARN No appenders could be found for logger (org.jboss.system.server.Serve
r).
log4j:WARN Please initialize the log4j system properly.

[jaikiran]

You will have to place log4j.xml or log4j.properties in your classpath

[vlokesh]

Make sure that you have log4j.xml file under your <JBOSS_HOME>/server//conf folder.

can be a) all b) default or c) minimal which is according to your configuration.

Regards.

Lokesh.

[alkarim]

Thanks for replying. I tried to specify the path in classpath environment variable, but am getting the same error message . Also log4j.xml is in all 3 subdirectories. Please let me know if you have other suggestions. I have seen JBOSS_HOME is being set in run.bat. I do not know if setting the path in the batch file will help?

Thanks

Alkarim

[jaikiran]

Can you post the contents of jboss-service.xml present in server/default/conf directory

[alkarim]

Hello JaiKiran

The following is the contents of jboss-service.xml file.

Thanks

<?xml version="1.0" encoding="UTF-8"?>
<!-- $Id: jboss-service.xml,v 1.117.2.9 2005/04/01 13:50:43 andd Exp $ -->

<!-- ===================================================================== -->
<!-- JBoss Server Configuration -->
<!-- ===================================================================== -->



<!-- Load all jars from the JBOSS_DIST/server//lib directory. This
can be restricted to specific jars by specifying them in the archives
attribute.
-->



<!-- ==================================================================== -->
<!-- JSR-77 Single JBoss Server Management Domain -->
<!-- ==================================================================== -->

jboss.system:service=MainDeployer
jboss.system:service=ServiceDeployer
jboss.j2ee:service=EARDeployer
jboss.ejb:service=EJBDeployer
jboss.jca:service=RARDeployer
jboss.jca:service=ConnectionFactoryDeployer
jboss.web:service=WebServer
jboss:service=Mail
jboss.mq:service=DestinationManager
jboss:service=Naming
jboss:service=TransactionManager
jboss:service=ClientUserTransaction
jboss:service=CorbaORB


<!-- ==================================================================== -->
<!-- XMBean Persistence -->
<!-- ==================================================================== -->
<mbean code="org.jboss.system.pm.AttributePersistenceService"
name="jboss:service=AttributePersistenceService"
xmbean-dd="resource:xmdesc/AttributePersistenceService-xmbean.xml">
<!-- the AttributePersistenceService is persistent, itself -->

<!--
org.jboss.system.pm.XMLAttributePersistenceManager

<data-directory>data/xmbean-attrs</data-directory>

false

-->


<!-- A Thread pool service -->

JBoss System Threads
System Threads
<!-- How long a thread will live without any tasks in MS -->
60000
<!-- The max number of threads in the pool -->
10
<!-- The max number of tasks before the queue is full -->
1000
<!-- The behavior of the pool when a task is added and the queue is full.
abort - a RuntimeException is thrown
run - the calling thread executes the task
wait - the calling thread blocks until the queue has room
discard - the task is silently discarded without being run
discardOldest - check to see if a task is about to complete and enque
the new task if possible, else run the task in the calling thread
-->
run


<!-- Preload all custom editors for VMs that don't use the thread
context class loader when searching for PropertyEditors. Uncomment
if your JDK 1.3.0 VM fails to find JBoss PropertyEditors.


java.math.BigDecimal=org.jboss.util.propertyeditor.BigDecimalEditor
java.lang.Boolean=org.jboss.util.propertyeditor.BooleanEditor
java.lang.Class=org.jboss.util.propertyeditor.ClassEditor
java.util.Date=org.jboss.util.propertyeditor.DateEditor
java.io.File=org.jboss.util.propertyeditor.FileEditor
java.net.InetAddress=org.jboss.util.propertyeditor.InetAddressEditor
java.lang.Integer=org.jboss.util.propertyeditor.IntegerEditor
javax.management.ObjectName=org.jboss.mx.util.propertyeditor.ObjectNameEditor
java.util.Properties=org.jboss.util.propertyeditor.PropertiesEditor
[Ljava.lang.String;=org.jboss.util.propertyeditor.StringArrayEditor
java.net.URL=org.jboss.util.propertyeditor.URLEditor


-->

<!-- ==================================================================== -->
<!-- Log4j Initialization -->
<!-- ==================================================================== -->

<mbean code="org.jboss.logging.Log4jService"
name="jboss.system:type=Log4jService,service=Logging"
xmbean-dd="resource:xmdesc/Log4jService-xmbean.xml">
resource:log4j.xml
<!-- Set the org.apache.log4j.helpers.LogLog.setQuiteMode. As of log4j1.2.8
this needs to be set to avoid a possible deadlock on exception at the
appender level. See bug#696819.
-->
true
<!-- How frequently in seconds the ConfigurationURL is checked for changes -->
60


<!-- ==================================================================== -->
<!-- JBoss RMI Classloader - only install when available -->
<!-- ==================================================================== -->

java.rmi.server.RMIClassLoaderSpi
org.jboss.system.JBossRMIClassLoader


<!-- ==================================================================== -->
<!-- Service Binding -->
<!-- ==================================================================== -->

<!-- Automatically activated when generatting the clustering environment -->
<!-- @TESTSUITE_CLUSTER_CONFIG@ -->

<!--
| Binding service manager for port/host mapping. This is a sample
| config that demonstrates a JBoss instances with a server name 'ports-01'
| loading its bindings from an XML file using the ServicesStoreFactory
| implementation returned by the XMLServicesStoreFactory.
|
| ServerName: The unique name assigned to a JBoss server instance for
| lookup purposes. This allows a single ServicesStore to handle mulitiple
| JBoss servers.
|
| StoreURL: The URL string passed to org.jboss.services.binding.ServicesStore
| during initialization that specifies how to connect to the bindings store.
| StoreFactory: The org.jboss.services.binding.ServicesStoreFactory interface
| implementation to create to obtain the ServicesStore instance.


ports-01
${jboss.home.url}/docs/examples/binding-manager/sample-bindings.xml

org.jboss.services.binding.XMLServicesStoreFactory



-->


<!-- ==================================================================== -->
<!-- Class Loading -->
<!-- ==================================================================== -->


8083
<!-- Should resources and non-EJB classes be downloadable -->
true
${jboss.bind.address}
${jboss.bind.address}


<!-- ==================================================================== -->
<!-- JNDI -->
<!-- ==================================================================== -->

<mbean code="org.jboss.naming.NamingService"
name="jboss:service=Naming"
xmbean-dd="resource:xmdesc/NamingService-xmbean.xml">
<!-- The call by value mode. true if all lookups are unmarshalled using
the caller's TCL, false if in VM lookups return the value by reference.
-->
false
<!-- The listening port for the bootstrap JNP service. Set this to -1
to run the NamingService without the JNP invoker listening port.
-->
1099
<!-- The bootstrap JNP server bind address. This also sets the default
RMI service bind address. Empty == all addresses
-->
${jboss.bind.address}
<!-- The port of the RMI naming service, 0 == anonymous -->
1098
<!-- The RMI service bind address. Empty == all addresses
-->
${jboss.bind.address}
<!-- The thread pool service used to control the bootstrap lookups -->
<depends optional-attribute-name="LookupPool"
proxy-type="attribute">jboss.system:service=ThreadPool


<mbean code="org.jboss.naming.JNDIView"
name="jboss:service=JNDIView"
xmbean-dd="resource:xmdesc/JNDIView-xmbean.xml">


<!-- ==================================================================== -->
<!-- Security -->
<!-- ==================================================================== -->


jboss.security:service=XMLLoginConfig


login-config.xml


<!-- JAAS security manager and realm mapping -->

org.jboss.security.plugins.JaasSecurityManager
anonymous
<!-- DefaultCacheTimeout: Specifies the default timed cache policy timeout
in seconds.
If you want to disable caching of security credentials, set this to 0 to
force authentication to occur every time. This has no affect if the
AuthenticationCacheJndiName has been changed from the default value.
-->
1800
<!-- DefaultCacheResolution: Specifies the default timed cache policy
resolution in seconds. This controls the interval at which the cache
current timestamp is updated and should be less than the DefaultCacheTimeout
in order for the timeout to be meaningful. This has no affect if the
AuthenticationCacheJndiName has been changed from the default value.
-->
60


<!-- ==================================================================== -->
<!-- Transactions -->
<!-- ==================================================================== -->
<!-- The configurable Xid factory. For use with Oracle, set pad to true -->

<!--attribute name="Pad">true</attribute-->


<!--
| The fast in-memory transaction manager.
-->
<mbean code="org.jboss.tm.TransactionManagerService"
name="jboss:service=TransactionManager"
xmbean-dd="resource:xmdesc/TransactionManagerService-xmbean.xml">
300
<!-- set to false to disable transaction demarcation over IIOP -->
true
<depends optional-attribute-name="XidFactory">jboss:service=XidFactory

<!--
| UserTransaction support.
-->
<mbean code="org.jboss.tm.usertx.server.ClientUserTransactionService"
name="jboss:service=ClientUserTransaction"
xmbean-dd="resource:xmdesc/ClientUserTransaction-xmbean.xml">


jboss:service=invoker,type=jrmp
jboss:service=ClientUserTransaction
UserTransactionSessionFactory
org.jboss.tm.usertx.interfaces.UserTransactionSessionFactory


org.jboss.proxy.ClientMethodInterceptor
org.jboss.invocation.InvokerInterceptor


jboss:service=invoker,type=jrmp


<depends optional-attribute-name="TxProxyName">

jboss:service=invoker,type=jrmp
jboss:service=ClientUserTransaction

org.jboss.tm.usertx.interfaces.UserTransactionSession


org.jboss.proxy.ClientMethodInterceptor
org.jboss.invocation.InvokerInterceptor


jboss:service=invoker,type=jrmp




<!-- ==================================================================== -->
<!-- Invokers to the JMX node -->
<!-- ==================================================================== -->

<!-- RMI/JRMP invoker -->

4444
${jboss.bind.address}
<!--
custom
custom
custom
ssl-domain-name
-->
jboss:service=TransactionManager




jboss:service=TransactionManager



1
300
300
60000
${jboss.bind.address}
4445
${jboss.bind.address}
0
false

<depends optional-attribute-name="TransactionManagerService">jboss:service=TransactionManager


<!-- ==================================================================== -->
<!-- Monitoring and Management -->
<!-- ==================================================================== -->

<!-- Uncomment to enable JMX monitoring of the bean cache

-->

<!-- Uncomment to enable JMX monitoring of the entity bean locking

-->

<!-- ==================================================================== -->
<!-- An MBean that is a registry for JDBC type-mapping metadata -->
<!-- ==================================================================== -->



<!-- ==================================================================== -->
<!-- Deployment Scanning -->
<!-- ==================================================================== -->

<!-- An mbean for hot deployment/undeployment of archives.
-->


<!-- Uncomment (and comment/remove version below) to enable usage of the
DeploymentCache
<depends optional-attribute-name="Deployer">jboss.deployment:type=DeploymentCache
-->
<depends optional-attribute-name="Deployer">jboss.system:service=MainDeployer

<!-- The URLComparator can be used to specify a deployment ordering
for deployments found in a scanned directory. The class specified
must be an implementation of java.util.Comparator, it must be able
to compare two URL objects, and it must have a no-arg constructor.
Two deployment comparators are shipped with JBoss:
- org.jboss.deployment.DeploymentSorter
Sorts by file extension, as follows:
"sar", "service.xml", "rar", "jar", "war", "wsr", "ear", "zip",
"*"
- org.jboss.deployment.scanner.PrefixDeploymentSorter
If the name portion of the url begins with 1 or more digits, those
digits are converted to an int (ignoring leading zeroes), and
files are deployed in that order. Files that do not start with
any digits will be deployed first, and they will be sorted by
extension as above with DeploymentSorter.
-->
org.jboss.deployment.DeploymentSorter
<!--
org.jboss.deployment.scanner.PrefixDeploymentSorter
-->

<!-- The FilterInstance specifies a URLLister.URLFilter for scanned
directories. This DeploymentFilter is initialized with the given
prefixes, suffixes and matches that define which URLs should be
ignored.
-->

<!-- Files starting with theses strings are ignored -->
#,%,\,,.,_$
<!-- Files ending with theses strings are ignored -->
#,$,%,~,\,v,.BAK,.bak,.old,.orig,.tmp,.rej,.sh
<!-- Files matching with theses strings are ignored -->
.make.state,.nse_depinfo,CVS,CVS.admin,RCS,RCSLOG,SCCS,TAGS,core,tags


<!-- Frequency in milliseconds to rescan the URLs for changes -->
5000
<!-- A flag to disable the scans -->
true

<!-- URLs are comma separated and resolve relative to the server home URL
unless the given path is absolute. If the URL ends in "/" it is
considered a collection and scanned, otherwise it is simply deployed;
this follows RFC2518 convention and allows discrimination between
collections and directories that are simply unpacked archives.

URLs may be local (file:) or remote (http:). Scanning is supported
for remote URLs but unpacked deployment units are not.

Example URLs:
deploy/
scans ${jboss.server.url}/deploy/, which is local or remote
depending on the URL used to boot the server
${jboss.server.home}/deploy/
scans ${jboss.server.home)/deploy, which is always local
file:/var/opt/myapp.ear
deploy myapp.ear from a local location
file:/var/opt/apps/
scans the specified directory
http://www.test.com/netboot/myapp.ear
deploys myapp.ear from a remote location
http://www.test.com/netboot/apps/
scans the specified WebDAV location
-->

deploy/


<!-- Indicates if the scanner should recursively scan directories that
contain no "." in their names. This can be used to group applications
and services that must be deployed and that have the same
logical function in the same directory i.e.
deploy/JMX/
deploy/JMS/
...
-->

True