Details
-
Suggestion
-
Resolution: Fixed
Description
Its not clear when looking at the logs when JIRA is "starting" to start and when its "finished" starting. For example see below. When did JIRA restart?
2008-01-25 03:33:29,604 http-8090-Processor2 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 258 2008-01-25 03:33:29,609 http-8090-Processor2 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Populates the JIRA System Administrator global permission with all groups associated with the JIRA Administrators global permission. 2008-01-25 03:33:29,609 http-8090-Processor2 INFO [jira.upgrade.tasks.UpgradeTask_Build296] Creating a JIRA System Administrators permission entry for group 'jira-administrators'. 2008-01-25 03:33:29,617 http-8090-Processor2 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Populates the JIRA System Administrator global permission with all groups associated with the JIRA Administrators global permission.' succeeded 2008-01-25 03:33:29,617 http-8090-Processor2 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 296 2008-01-25 03:33:29,619 http-8090-Processor2 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2008-01-25 03:33:29,626 http-8090-Processor2 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2008-01-25 03:33:29,626 http-8090-Processor2 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2008-01-25 03:33:29,628 http-8090-Processor2 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade completed without error. 2008-01-25 03:33:29,628 http-8090-Processor2 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number to: 319 2008-01-25 03:33:48,153 http-8090-Processor2 [webwork.dispatcher.ServletDispatcher] Could not execute action java.lang.IllegalArgumentException: Action 'DashboardX' not found or could not be initialized: java.lang.ClassNotFoundException: DashboardX at webwork.action.factory.JavaActionFactory.getActionImpl(JavaActionFactory.java:64) at webwork.action.factory.ScriptActionFactoryProxy.getActionImpl(ScriptActionFactoryProxy.java:54) at webwork.action.factory.XMLActionFactoryProxy.getActionImpl(XMLActionFactoryProxy.java:54) at webwork.action.factory.PrefixActionFactoryProxy.getActionImpl(PrefixActionFactoryProxy.java:102) at webwork.action.factory.JspActionFactoryProxy.getActionImpl(JspActionFactoryProxy.java:53) 2008-01-25 03:29:28,548 main [core.entity.jdbc.DatabaseUtil] Entity "Action" has no table in the database 2008-01-25 03:29:28,622 main [core.entity.jdbc.DatabaseUtil] Entity "ChangeGroup" has no table in the database 2008-01-25 03:29:28,650 main [core.entity.jdbc.DatabaseUtil] Entity "ChangeItem" has no table in the database 2008-01-25 03:29:28,655 main [core.entity.jdbc.DatabaseUtil] Entity "ColumnLayout" has no table in the database 2008-01-25 03:29:32,538 main INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] Starting JIRA Enterprise Edition, Version: 4.0-SNAPSHOT-#319 2008-01-25 03:29:32,538 main INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] Configured to use database: postgres72 2008-01-25 03:29:32,541 main INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] Could not find Issue Cache Listener, adding. 2008-01-25 03:29:33,560 main INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] Could not find Mail Listener, adding. 2008-01-25 03:29:33,566 main INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] Could not find Mail Queue Service, adding. 2008-01-25 03:29:33,601 main INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] Input Language has not been set. Setting to 'English' 2008-01-25 03:29:33,618 main INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] ************************************************************************************************************ JIRA 4.0-SNAPSHOT build: 319 (Enterprise Edition) started. You can now access JIRA through your web browser. ************************************************************************************************************
What I would like to see is a clear "we are starting" followed by a "we are started". Maybe something like this
2008-01-25 03:33:29,628 http-8090-Processor2 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number to: 319 2008-01-25 03:33:48,153 http-8090-Processor2 [webwork.dispatcher.ServletDispatcher] Could not execute action java.lang.IllegalArgumentException: Action 'DashboardX' not found or could not be initialized: java.lang.ClassNotFoundException: DashboardX at webwork.action.factory.JavaActionFactory.getActionImpl(JavaActionFactory.java:64) at webwork.action.factory.ScriptActionFactoryProxy.getActionImpl(ScriptActionFactoryProxy.java:54) at webwork.action.factory.XMLActionFactoryProxy.getActionImpl(XMLActionFactoryProxy.java:54) at webwork.action.factory.PrefixActionFactoryProxy.getActionImpl(PrefixActionFactoryProxy.java:102) at webwork.action.factory.JspActionFactoryProxy.getActionImpl(JspActionFactoryProxy.java:53) 2008-01-25 03:29:33,618 main INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] ************************************************************************************************************ JIRA 4.0-SNAPSHOT build: 319 (Enterprise Edition) starting. ************************************************************************************************************ 2008-01-25 03:29:28,548 main [atlassian.jira.startup] Checking database 'jdbc:db2:wrongscheme:jiradb' using entity scheme 'postgres72' 2008-01-25 03:29:28,548 main [core.entity.jdbc.DatabaseUtil] Entity "Action" has no table in the database 2008-01-25 03:29:28,622 main [core.entity.jdbc.DatabaseUtil] Entity "ChangeGroup" has no table in the database 2008-01-25 03:29:28,650 main [core.entity.jdbc.DatabaseUtil] Entity "ChangeItem" has no table in the database 2008-01-25 03:29:28,655 main [core.entity.jdbc.DatabaseUtil] Entity "ColumnLayout" has no table in the database 2008-01-25 03:29:32,538 main INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] Starting JIRA Enterprise Edition, Version: 4.0-SNAPSHOT-#319 2008-01-25 03:29:32,538 main INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] Configured to use database: postgres72 2008-01-25 03:29:32,541 main INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] Could not find Issue Cache Listener, adding. 2008-01-25 03:29:33,560 main INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] Could not find Mail Listener, adding. 2008-01-25 03:29:33,566 main INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] Could not find Mail Queue Service, adding. 2008-01-25 03:29:33,601 main INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] Input Language has not been set. Setting to 'English' 2008-01-25 03:29:33,618 main INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] ************************************************************************************************************ JIRA 4.0-SNAPSHOT build: 319 (Enterprise Edition) started. You can now access JIRA through your web browser. ************************************************************************************************************
Then if anything fails in database consistency check we can see more easily. Plus we have all the system properties that may affect users setup.
Also you would see entity engine to JDBC/entity engine drivers screws ups just that little more easily. Not guaranteed but a little more easily.
Also when doing support you often have you head buried in logs and dont want t swithc back to the SAC ewb page to find out what the system info is. This would help support a lot.
Attachments
Issue Links
- is related to
-
- Closed