1 Reply Latest reply on May 29, 2008 10:24 AM by jaikiran

    log4j error during Run, after Deployment

    taicode

      Hi,

      I'm using JBoss 4.2.2 and MyEclipse 6.0. Everything is fine to the Deployment, but after I RUN the JBoss, I get the following Error Message Snippet: Please help. thank you.

      08:00:36,862 ERROR [STDERR] log4j:ERROR A "org.jboss.logging.appender.FileAppender" object is not assignable to a "org.apache.log4j.Appender" variable.
      08:00:36,862 ERROR [STDERR] log4j:ERROR The class "org.apache.log4j.Appender" was loaded by
      08:00:36,862 ERROR [STDERR] log4j:ERROR [WebappClassLoader
       delegate: false
       repositories:
       /WEB-INF/classes/
      ----------> Parent Classloader:
      java.net.FactoryURLClassLoader@82acef
      ] whereas object of type
      08:00:36,862 ERROR [STDERR] log4j:ERROR "org.jboss.logging.appender.FileAppender" was loaded by [org.jboss.system.server.NoAnnotationURLClassLoader@ab95e6].
      08:00:36,862 ERROR [STDERR] log4j:ERROR Could not instantiate appender named "FILE".
      




      the complete Console display is:
      08:00:07,506 INFO [Server] Starting JBoss (MX MicroKernel)...
      08:00:07,506 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)
      08:00:07,506 INFO [Server] Home Dir: C:\jboss-4.2.2.GA-original
      08:00:07,522 INFO [Server] Home URL: file:/C:/jboss-4.2.2.GA-original/
      08:00:07,522 INFO [Server] Patch URL: null
      08:00:07,522 INFO [Server] Server Name: default
      08:00:07,522 INFO [Server] Server Home Dir: C:\jboss-4.2.2.GA-original\server\default
      08:00:07,522 INFO [Server] Server Home URL: file:/C:/jboss-4.2.2.GA-original/server/default/
      08:00:07,522 INFO [Server] Server Log Dir: C:\jboss-4.2.2.GA-original\server\default\log
      08:00:07,522 INFO [Server] Server Temp Dir: C:\jboss-4.2.2.GA-original\server\default\tmp
      08:00:07,522 INFO [Server] Root Deployment Filename: jboss-service.xml
      08:00:07,819 INFO [ServerInfo] Java version: 1.5.0_14,Sun Microsystems Inc.
      08:00:07,819 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_14-b03,Sun Microsystems Inc.
      08:00:07,819 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
      08:00:08,725 INFO [Server] Core system initialized
      08:00:10,834 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
      08:00:10,834 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
      log4j:WARN Continuable parsing error 17 and column 83
      log4j:WARN Attribute "ERROR" must be declared for element type "log4j:configuration".
      08:00:36,862 ERROR [STDERR] log4j:ERROR A "org.jboss.logging.appender.FileAppender" object is not assignable to a "org.apache.log4j.Appender" variable.
      08:00:36,862 ERROR [STDERR] log4j:ERROR The class "org.apache.log4j.Appender" was loaded by
      08:00:36,862 ERROR [STDERR] log4j:ERROR [WebappClassLoader
       delegate: false
       repositories:
       /WEB-INF/classes/
      ----------> Parent Classloader:
      java.net.FactoryURLClassLoader@82acef
      ] whereas object of type
      08:00:36,862 ERROR [STDERR] log4j:ERROR "org.jboss.logging.appender.FileAppender" was loaded by [org.jboss.system.server.NoAnnotationURLClassLoader@ab95e6].
      08:00:36,862 ERROR [STDERR] log4j:ERROR Could not instantiate appender named "FILE".
      08:00:40,221 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
      
      --- MBeans waiting for other MBeans ---
      ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=Invoker
       jboss.web:service=WebServer
      
      ObjectName: jboss.mq.destination:service=Topic,name=testTopic
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
       jboss.mq:service=SecurityManager
      
      ObjectName: jboss.mq.destination:service=Topic,name=securedTopic
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
       jboss.mq:service=SecurityManager
      
      ObjectName: jboss.mq.destination:service=Topic,name=testDurableTopic
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
       jboss.mq:service=SecurityManager
      
      ObjectName: jboss.mq.destination:service=Queue,name=testQueue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
       jboss.mq:service=SecurityManager
      
      ObjectName: jboss.mq.destination:service=Queue,name=A
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:service=Queue,name=B
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:service=Queue,name=C
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:service=Queue,name=D
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:service=Queue,name=ex
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq:service=Invoker
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=TracingInterceptor
       jboss:service=Naming
       Depends On Me:
       jboss.mq:service=InvocationLayer,type=HTTP
       jboss.mq:service=InvocationLayer,type=JVM
       jboss.mq:service=InvocationLayer,type=UIL2
      
      ObjectName: jboss.mq:service=TracingInterceptor
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=SecurityManager
       Depends On Me:
       jboss.mq:service=Invoker
      
      ObjectName: jboss.mq:service=SecurityManager
       State: CONFIGURED
       I Depend On:
       jboss.security:service=JaasSecurityManager
       jboss.mq:service=DestinationManager
       Depends On Me:
       jboss.mq.destination:service=Topic,name=testTopic
       jboss.mq.destination:service=Topic,name=securedTopic
       jboss.mq.destination:service=Topic,name=testDurableTopic
       jboss.mq.destination:service=Queue,name=testQueue
       jboss.mq:service=TracingInterceptor
       jboss.mq.destination:service=Queue,name=DLQ
      
      ObjectName: jboss.mq.destination:service=Queue,name=DLQ
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
       jboss.mq:service=SecurityManager
      
      ObjectName: jboss.mq:service=InvocationLayer,type=JVM
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=Invoker
      
      ObjectName: jboss.mq:service=DestinationManager
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=MessageCache
       jboss.mq:service=PersistenceManager
       jboss.mq:service=StateManager
       Depends On Me:
       jboss.mq.destination:service=Topic,name=testTopic
       jboss.mq.destination:service=Topic,name=securedTopic
       jboss.mq.destination:service=Topic,name=testDurableTopic
       jboss.mq.destination:service=Queue,name=testQueue
       jboss.mq.destination:service=Queue,name=A
       jboss.mq.destination:service=Queue,name=B
       jboss.mq.destination:service=Queue,name=C
       jboss.mq.destination:service=Queue,name=D
       jboss.mq.destination:service=Queue,name=ex
       jboss.mq:service=SecurityManager
       jboss.mq.destination:service=Queue,name=DLQ
      
      ObjectName: jboss.mq:service=PersistenceManager
       State: CONFIGURED
       I Depend On:
       jboss.jca:service=DataSourceBinding,name=OracleDS
       Depends On Me:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq:service=InvocationLayer,type=UIL2
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=Invoker
      
      --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
      ObjectName: jboss.jca:service=DataSourceBinding,name=OracleDS
       State: NOTYETINSTALLED
       Depends On Me:
       jboss.mq:service=PersistenceManager
      


        • 1. Re: log4j error during Run, after Deployment
          jaikiran

          You probably are including log4j.jar as part of your application packaging. The simplest solution is to remove it from your application packaging - JBoss already comes shipped with the log4j jar file in its %JBOSS_HOME%\server\< serverName>\lib folder.