Page History

New

• Memory leak requires restarting Tomcat?
  
  • (Brian L) – looking at what's happening on the VIVO Cornell server
    
    • taking heap dumps to look for objects that are hanging around across garbage collections
  • (Alex) – we restart MWF with data updates so have not had a problem, but will look for messages
  • Other possible approaches:
    
    • Verifying that what is being seen is actual memory usage, not just the size of the JVM as reported by top() – check the gc (garbage collection) logs
      
      • adding a JSP page to force a full garbage collection may verify whether the baseline memory used by Tomcat is in fact increasing
    • Check the possibilities for thread contention that could cause the application to freeze up
    • Make sure your robots.txt blocks access to visualizations and CV generation (if you have that activated, which I think only UF does)
    • What other sites are experiencing this problem? – checking the Cornell VIVO logs this morning
• Any way to batch convert Ontology URIs?
  • (Brian) A hybrid approach might be workable
    
    • could use the existing change namespace tool (designed for changing the namespace of the VIVO) to update all the ontology URIs in the instance data graph, if it's all in the main (KB-2) graph and accessible to that tool in its default configuration
    • then you could export the ontology only, use a text editor to modify the URIs, and load it back in
  • make a JIRA issue

Resolved but worth discussing

• (Mark) Bug in Tomcat 7 for Ubuntu – source of the "There is no <whatever> content in your VIVO" problem from last week
  
  • (Jim) However, it's obvious that we need to make it easier to isolate and diagnose this sort of problem. As a first step, I have started a wiki page with suggestions for troubleshooting this sort of issue.

Still open?

Call-in Information