If the release value in the release table is greater than the starting Liferay version, shut down and change no data

• Type: Bug
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: 6.0.12 EE
• Fix Version/s: --Sprint 12/11, 6.1.0 CE RC1, 6.0.X EE
• Component/s: Upgrades
• Labels: None
• Branch Version/s:
  6.0.x
• Backported to Branch:
  Committed
• Similar Issues: Show 4 results ; ;

  LPS-28957	OpenSocial memory leaks when shutting down liferay
  LPS-27496	Possible memory leak when shutting down Liferay + SAML
  LPS-15412	release_.buildNumber changes if an older version of the portal connects to the database
  LPS-18925	OpenSocial plugin stack trace error and deployment failure after shutting down and restarting Liferay

Currently, if you have a DB filled with Liferay 6.0EE SP2 data and start Liferay 6 against it (accidentally), it tries to run an upgrade and verify. This results in a bad DB. If the value in the release_ table is greater that the running Liferay (release says 6012 and the running Liferay is 6010) shut down immediately. Do not run upgrade, do not run verify. Output a message in the log stating that the database is setup for Liferay (6012 or whatever version) but you are trying to start (6010 or whatever version). Shutting down to save data.

[Vicki Tsang]

This is being bulk closed in preparation for the new workflow.