1 Reply Latest reply on Sep 22, 2017 12:58 AM by jaikiran

    Configuring from URL: resource:jboss-log4j.xml



      I am new to jboss so if anyone knows how to solve this issue... please let me know.

      I see a lot of discussion on this topic but no resolution was posted.




      I installed the new server and tried to deploy to the default location.

      It seems to stop at this part; Configuring from URL: resource:jboss-log4j.xml


      13:44:03,490 INFO  [Server] Starting JBoss (MX MicroKernel)...

      13:44:03,490 INFO  [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)

      13:44:03,490 INFO  [Server] Home Dir: C:\JBoss\jboss-4.2.2.GA

      13:44:03,490 INFO  [Server] Home URL: file:/C:/JBoss/jboss-4.2.2.GA/

      13:44:03,490 INFO  [Server] Patch URL: null

      13:44:03,490 INFO  [Server] Server Name: default

      13:44:03,490 INFO  [Server] Server Home Dir: C:\JBoss\jboss-4.2.2.GA\server\default

      13:44:03,490 INFO  [Server] Server Home URL: file:/C:/JBoss/jboss-4.2.2.GA/server/default/

      13:44:03,490 INFO  [Server] Server Log Dir: C:\JBoss\jboss-4.2.2.GA\server\default\log

      13:44:03,490 INFO  [Server] Server Temp Dir: C:\JBoss\jboss-4.2.2.GA\server\default\tmp

      13:44:03,490 INFO  [Server] Root Deployment Filename: jboss-service.xml

      13:44:03,599 INFO  [ServerInfo] Java version: 1.6.0_31,Sun Microsystems Inc.

      13:44:03,599 INFO  [ServerInfo] Java VM: Java HotSpot(TM) Client VM 20.6-b01,Sun Microsystems Inc.

      13:44:03,599 INFO  [ServerInfo] OS-System: Windows 7 6.1,x86

      13:44:03,709 INFO  [Server] Core system initialized

      13:44:04,489 INFO  [WebService] Using RMI server codebase:

      13:44:04,489 INFO  [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml




      Java 1.6 JDK

      JBoss 4.2.2.GA

        • 1. Re: Configuring from URL: resource:jboss-log4j.xml

          It's not stopping. I guess what's happening is that that log4j is configured to _not_ log to the console and hence you see no more logs on the console. The process probably is still running and you can check the process listing to verify it. You can also find the logs in the logs/server.log file for more logs.