Details
-
Bug
-
Resolution: Obsolete
-
Medium
-
4.4
-
JIRA version 4.4-SNAPSHOT#650-r158322 in Studio
-
4.04
-
Description
I am testing some plugins for Studio that use ActiveObjects. When JIRA starts up, the database checker logs a warning for every table that ActiveObjects has created. This pollutes the logs and could confuse an admin or plugin developer trying to diagnose an unrelated issue.
2011-07-26 11:22:22,130 main INFO [jira.config.database.DatabaseConfigurationManagerImpl] Now running Database Checklist Launcher 2011-07-26 11:22:25,838 main WARN [core.entity.jdbc.DatabaseUtil] Table named "PUBLIC.AO_3A3ECC_JIRACOMMENT_MAPPING" exists in the database but has no corresponding entity 2011-07-26 11:22:25,838 main WARN [core.entity.jdbc.DatabaseUtil] Table named "PUBLIC.AO_3A3ECC_JIRAMAPPING_BEAN" exists in the database but has no corresponding entity 2011-07-26 11:22:25,838 main WARN [core.entity.jdbc.DatabaseUtil] Table named "PUBLIC.AO_3A3ECC_JIRAMAPPING_SCHEME" exists in the database but has no corresponding entity 2011-07-26 11:22:25,838 main WARN [core.entity.jdbc.DatabaseUtil] Table named "PUBLIC.AO_3A3ECC_JIRAMAPPING_SET" exists in the database but has no corresponding entity 2011-07-26 11:22:25,838 main WARN [core.entity.jdbc.DatabaseUtil] Table named "PUBLIC.AO_3A3ECC_JIRAPROJECT_MAPPING" exists in the database but has no corresponding entity 2011-07-26 11:22:25,838 main WARN [core.entity.jdbc.DatabaseUtil] Table named "PUBLIC.AO_3A3ECC_REMOTE_IDCF" exists in the database but has no corresponding entity 2011-07-26 11:22:25,838 main WARN [core.entity.jdbc.DatabaseUtil] Table named "PUBLIC.AO_437CB5_AGREEMENT" exists in the database but has no corresponding entity 2011-07-26 11:22:25,839 main WARN [core.entity.jdbc.DatabaseUtil] Table named "PUBLIC.AO_437CB5_COMMENT_LINK" exists in the database but has no corresponding entity 2011-07-26 11:22:25,839 main WARN [core.entity.jdbc.DatabaseUtil] Table named "PUBLIC.AO_437CB5_TICKET_LINK" exists in the database but has no corresponding entity 2011-07-26 11:22:25,839 main WARN [core.entity.jdbc.DatabaseUtil] Table named "PUBLIC.AO_A8A87E_AGREEMENT" exists in the database but has no corresponding entity 2011-07-26 11:22:25,839 main WARN [core.entity.jdbc.DatabaseUtil] Table named "PUBLIC.AO_A8A87E_CONNECTION" exists in the database but has no corresponding entity 2011-07-26 11:22:25,839 main WARN [core.entity.jdbc.DatabaseUtil] Table named "PUBLIC.AO_A8A87E_LICENSE" exists in the database but has no corresponding entity 2011-07-26 11:22:25,839 main WARN [core.entity.jdbc.DatabaseUtil] Table named "PUBLIC.AO_A8A87E_MAPPING_BEAN" exists in the database but has no corresponding entity 2011-07-26 11:22:25,839 main WARN [core.entity.jdbc.DatabaseUtil] Table named "PUBLIC.AO_A8A87E_MAPPING_ENTRY" exists in the database but has no corresponding entity 2011-07-26 11:22:25,839 main WARN [core.entity.jdbc.DatabaseUtil] Table named "PUBLIC.AO_A8A87E_TRANSACTION" exists in the database but has no corresponding entity 2011-07-26 11:22:25,839 main WARN [core.entity.jdbc.DatabaseUtil] Table named "PUBLIC.AO_A8A87E_TRANSACTION_CONTENT" exists in the database but has no corresponding entity 2011-07-26 11:22:25,839 main WARN [core.entity.jdbc.DatabaseUtil] Table named "PUBLIC.AO_A8A87E_TRANSACTION_LOG" exists in the database but has no corresponding entity 2011-07-26 11:22:27,098 main INFO [atlassian.jira.startup.DatabaseChecklistLauncher] JIRA database startup checks completed successfully.