VIVO v1.6.2 Release Notes

What is this document?

The VIVO 1.6.2 Release contains no new features - only a fix for a memory leak. This memory leak causes a VIVO installation to crash after several hours of use. Sites that are using VIVO 1.6 or VIVO 1.6.1 are strongly urged to upgrade to VIVO 1.6.2

Significant bugs

VIVO-783 Fix memory leak

After converting from VIVO 1.5.1 to VIVO 1.6.1, Cornell's VIVO site began crashing 2 or 3 times every day. This was found to be the result of a memory leak.

In release 1.6, there was a change in how RDF models were accessed -- the ModelAccess class was created to standardize access. However, the request-specific instance of ModelAccess did not close the WebappDaoFactory assigned to it. Some DAOs rely on that close() signal to release resources.

Adding a close() method to ModelAccess, and calling that from RequestModelsPrep solved the problem.

More details

These issues are explained in greater detail in JIRA, our issue-tracking system. To see an issue in JIRA, go to and search for the issue key. The key is in the form "VIVO-999".

  • No labels