Forum LAMS for Tech-Heads - General Forum: Oh my god~~~ suddenly error occur

By: leo luo

[ Reply | Forward ]

when I start my lams server today,I havn't do any uncorrect operation,but suddenly error occur
I post the jboss server.log error message here:


2010-11-24 14:44:43,783 INFO [com.tacitknowledge.util.migration.jdbc.AutoPatchService] Applying patches....
2010-11-24 14:44:43,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] Waiting for migration lock for system "laqa11"
2010-11-24 14:44:43,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] If this isn't from a long-running patch, but a stale lock, either:
2010-11-24 14:44:43,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] 1) run MigrationTableUnlock (probably 'ant patch.unlock')
2010-11-24 14:44:43,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] 2) set the lockPollRetries property so the lock times out
2010-11-24 14:44:43,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] (this is dangerous in combination with long-running patches)
2010-11-24 14:44:43,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] 3) set the 'patch_in_progress' in the patches table to 'F'
2010-11-24 14:44:58,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] Waiting for migration lock for system "laqa11"
2010-11-24 14:44:58,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] If this isn't from a long-running patch, but a stale lock, either:
2010-11-24 14:44:58,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] 1) run MigrationTableUnlock (probably 'ant patch.unlock')
2010-11-24 14:44:58,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] 2) set the lockPollRetries property so the lock times out
2010-11-24 14:44:58,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] (this is dangerous in combination with long-running patches)
2010-11-24 14:44:58,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] 3) set the 'patch_in_progress' in the patches table to 'F'
2010-11-24 14:45:13,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] Waiting for migration lock for system "laqa11"
2010-11-24 14:45:13,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] If this isn't from a long-running patch, but a stale lock, either:
2010-11-24 14:45:13,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] 1) run MigrationTableUnlock (probably 'ant patch.unlock')
2010-11-24 14:45:13,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] 2) set the lockPollRetries property so the lock times out
2010-11-24 14:45:13,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] (this is dangerous in combination with long-running patches)
2010-11-24 14:45:13,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] 3) set the 'patch_in_progress' in the patches table to 'F'
2010-11-24 14:45:28,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] Waiting for migration lock for system "laqa11"
2010-11-24 14:45:28,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] If this isn't from a long-running patch, but a stale lock, either:
2010-11-24 14:45:28,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] 1) run MigrationTableUnlock (probably 'ant patch.unlock')
2010-11-24 14:45:28,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] 2) set the lockPollRetries property so the lock times out
2010-11-24 14:45:28,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] (this is dangerous in combination with long-running patches)
2010-11-24 14:45:28,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] 3) set the 'patch_in_progress' in the patches table to 'F'
2010-11-24 14:45:43,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] Waiting for migration lock for system "laqa11"
2010-11-24 14:45:43,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] If this isn't from a long-running patch, but a stale lock, either:
2010-11-24 14:45:43,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] 1) run MigrationTableUnlock (probably 'ant patch.unlock')
2010-11-24 14:45:43,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] 2) set the lockPollRetries property so the lock times out
2010-11-24 14:45:43,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] (this is dangerous in combination with long-running patches)
2010-11-24 14:45:43,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] 3) set the 'patch_in_progress' in the patches table to 'F'
2010-11-24 14:45:58,783 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] Waiting for migration lock for system "laqa11"
2010-11-24 14:45:58,799 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] If this isn't from a long-running patch, but a stale lock, either:
2010-11-24 14:45:58,799 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] 1) run MigrationTableUnlock (probably 'ant patch.unlock')
2010-11-24 14:45:58,799 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] 2) set the lockPollRetries property so the lock times out
2010-11-24 14:45:58,799 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] (this is dangerous in combination with long-running patches)
2010-11-24 14:45:58,799 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] 3) set the 'patch_in_progress' in the patches table to 'F'
2010-11-24 14:46:13,799 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] Waiting for migration lock for system "laqa11"
2010-11-24 14:46:13,799 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] If this isn't from a long-running patch, but a stale lock, either:
2010-11-24 14:46:13,799 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] 1) run MigrationTableUnlock (probably 'ant patch.unlock')
2010-11-24 14:46:13,799 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] 2) set the lockPollRetries property so the lock times out
2010-11-24 14:46:13,799 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] (this is dangerous in combination with long-running patches)
2010-11-24 14:46:13,799 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] 3) set the 'patch_in_progress' in the patches table to 'F'
2010-11-24 14:46:28,799 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] Waiting for migration lock for system "laqa11"
2010-11-24 14:46:28,799 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] If this isn't from a long-running patch, but a stale lock, either:
2010-11-24 14:46:28,799 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] 1) run MigrationTableUnlock (probably 'ant patch.unlock')
2010-11-24 14:46:28,799 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] 2) set the lockPollRetries property so the lock times out
2010-11-24 14:46:28,799 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] (this is dangerous in combination with long-running patches)
2010-11-24 14:46:28,799 INFO [com.tacitknowledge.util.migration.jdbc.JdbcMigrationLauncher] 3) set the 'patch_in_progress' in the patches table to 'F'


Now I can't start lams server again ~~
how can I fix it?...
thank you

Posted by leo luo