Why starting with run.sh results in "[Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml"

Solution Verified - Updated -

Issue

Symptoms

  • When I start the server running run.sh from jbosshome/jboss-as/bin i don't get "server started" notification but server is started fine.

    INFO  [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
  • When starting JBoss with the "production" profile JBoss does not see to start up completely. However the "default" and "all" profiles do.

Environment

  • JBoss Enterprise Application Platform (EAP) 4.3

  • JBoss Enterprise Application Platform (EAP) 5.0.x

Resolution

  • This is defined in the Getting Started Guide: http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/4.3.0.cp06/html-single/Getting_Started/index.html#Starting_and_Stopping_the_Server-Start_the_Server

Root Cause

  • This is the default behavior when starting the server with run.sh as a server configuraiton has not been defined and the script picks the "production" profile which is optimized with verbose logging.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content