Bug 804856

Summary: Feature request - provide an easy to find server.log message to enable users to identify that their server startup is successful
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Len DiMaggio <ldimaggi>
Component: DistributionAssignee: Nobody <nobody>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.3.0 GACC: kejohnso, soa-p-jira
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 804819    
Bug Blocks:    

Description Len DiMaggio 2012-03-20 00:32:04 UTC
Description of problem:
With the removal of the server "started in NNN seconds" server.log message, it's difficult easily identify for the user a single server.log message that confirms that the server was successfully started.

As of 5.2.GA, the last messages written to the server.log after startup are:

2012-03-19 16:15:46,432 INFO  [org.hibernate.cfg.SettingsFactory] (Thread-32) Generate SQL with comments: disabled
2012-03-19 16:15:46,432 INFO  [org.hibernate.cfg.SettingsFactory] (Thread-32) Order SQL updates by primary key: disabled
2012-03-19 16:15:46,432 INFO  [org.hibernate.cfg.SettingsFactory] (Thread-32) Order SQL inserts for batching: disabled
2012-03-19 16:15:46,432 INFO  [org.hibernate.cfg.SettingsFactory] (Thread-32) Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory
2012-03-19 16:15:46,432 INFO  [org.hibernate.hql.ast.ASTQueryTranslatorFactory] (Thread-32) Using ASTQueryTranslatorFactory
2012-03-19 16:15:46,433 INFO  [org.hibernate.cfg.SettingsFactory] (Thread-32) Query language substitutions: {}
2012-03-19 16:15:46,433 INFO  [org.hibernate.cfg.SettingsFactory] (Thread-32) JPA-QL strict compliance: disabled
2012-03-19 16:15:46,433 INFO  [org.hibernate.cfg.SettingsFactory] (Thread-32) Second-level cache: enabled
2012-03-19 16:15:46,433 INFO  [org.hibernate.cfg.SettingsFactory] (Thread-32) Query cache: disabled
2012-03-19 16:15:46,434 INFO  [org.hibernate.cfg.SettingsFactory] (Thread-32) Cache region factory : org.hibernate.cache.impl.bridge.RegionFactoryCacheProviderBridge
2012-03-19 16:15:46,440 INFO  [org.hibernate.cache.impl.bridge.RegionFactoryCacheProviderBridge] (Thread-32) Cache provider: org.hibernate.cache.HashtableCacheProvider
2012-03-19 16:15:46,442 INFO  [org.hibernate.cfg.SettingsFactory] (Thread-32) Optimize cache for minimal puts: disabled
2012-03-19 16:15:46,442 INFO  [org.hibernate.cfg.SettingsFactory] (Thread-32) Structured second-level cache entries: disabled
2012-03-19 16:15:46,442 INFO  [org.hibernate.cfg.SettingsFactory] (Thread-32) Statistics: disabled
2012-03-19 16:15:46,442 INFO  [org.hibernate.cfg.SettingsFactory] (Thread-32) Deleted entity synthetic identifier rollback: disabled
2012-03-19 16:15:46,442 INFO  [org.hibernate.cfg.SettingsFactory] (Thread-32) Default entity-mode: pojo
2012-03-19 16:15:46,442 INFO  [org.hibernate.cfg.SettingsFactory] (Thread-32) Named query checking : enabled
2012-03-19 16:15:46,448 INFO  [org.hibernate.impl.SessionFactoryImpl] (Thread-32) building session factory
2012-03-19 16:15:46,962 INFO  [org.hibernate.impl.SessionFactoryObjectFactory] (Thread-32) Not binding factory to JNDI, no JNDI name configured
2012-03-19 16:15:46,963 INFO  [org.hibernate.util.NamingHelper] (Thread-32) JNDI InitialContext properties:{}


Version-Release number of selected component (if applicable):
5.2, 5.3

How reproducible:
Start the server

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Ken Johnson 2012-03-20 02:05:51 UTC
This is a very good idea.