问题

问题

症状

  • 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.

环境

  • JBoss企业应用平台(EAP)4.3

  • JBoss企业应用平台(EAP)5.0.x

分辨率

  • 这是在"入门指南"中定义的: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 < / li>

根本原因

  • 这是在使用run.sh启动服务器时的默认行为,因为服务器配置尚未定义,脚本将选择通过详细日志记录优化的"生产"配置文件.

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.


解决方法

请关注DeveloperQ公众号以获得问题解决方法 DeveloperQ公众号




相关问题推荐