Bug 804856 - Feature request - provide an easy to find server.log message to enable users to identify that their server startup is successful
Feature request - provide an easy to find server.log message to enable users ...
Status: NEW
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Distribution (Show other bugs)
5.3.0 GA
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Default User
: FutureFeature
Depends On: 804819
Blocks:
  Show dependency treegraph
 
Reported: 2012-03-19 20:32 EDT by Len DiMaggio
Modified: 2012-07-31 01:58 EDT (History)
3 users (show)

See Also:
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: ---


Attachments (Terms of Use)

  None (edit)
Description Len DiMaggio 2012-03-19 20:32:04 EDT
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-19 22:05:51 EDT
This is a very good idea.

Note You need to log in before you can comment on or make changes to this bug.