You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
Environment:
Logs related to the issue
vivo-all.log
localhost.2025-02-11.log
catalina.out.txt
The text was updated successfully, but these errors were encountered: