Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JSP pages do not work after redeployment of VIVO #4049

Open
litvinovg opened this issue Feb 11, 2025 · 0 comments
Open

JSP pages do not work after redeployment of VIVO #4049

litvinovg opened this issue Feb 11, 2025 · 0 comments

Comments

@litvinovg
Copy link
Member

litvinovg commented Feb 11, 2025

Describe the bug
After some redeployments of VIVO application on the same tomcat instance ontology editor pages do not work anymore.
The pages below that are affected by this issue display blank content:
/ontologyEdit?uri=http%3A%2F%2Fpurl.org%2Fontology%2Fbibo%2F
/vclassEdit?uri=http%3A%2F%2Fvivoweb.org%2Fontology%2Fcore%23AcademicDegree
/propertyEdit?uri=http%3A%2F%2Fpurl.org%2Fontology%2Fbibo%2Fannotates
/datapropEdit?uri=http%3A%2F%2Fpurl.org%2Fontology%2Fbibo%2Fabstract

To summarize all JSP code processing doesn't work in case the issue appears.

Might be related to the memory leak described in #4048
To Reproduce
The issue appears stochastically. It was noticed on multiple servers and local VIVO deployments in different environments with different versions of Tomcat, but always after some redeployments of VIVO application on the same Tomcat.

Workaround
Once issue appear redeployment of VIVO will doesn't help, the only solution is to restart Tomcat application server

Screenshots

Image

Environment:

  • OS: Linux Debian 12
  • Browser Firefox
  • Tomcat version 9.0.67
  • VIVO version 1.15.1-SNAPSHOT (VIVO commit, Vitro commit)
  • Apache Solr

Logs related to the issue

vivo-all.log

localhost.2025-02-11.log

catalina.out.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants