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
We recently stepped up to a newer version of both OpenGrok and Tomcat, and have noticed a not-so-desirable effect. We restart our tomcat instance every so often to combat server/process instability. With the newer versions, we've noticed that we are unable to do OpenGrok searches once tomcat is restarted. It reports 'You must select a project!' despite no project being available. The search works fine, and there are projects available prior to the restart. The only way we've discovered to get around this was to completely re-index very app we had. This was not a problem with the older versions we were using. This is problematic because we have about 15 or so projects we like to index, and some take several hours to index. If we need to regenerate all of these every time tomcat restarts, that's going to be an issue.
The text was updated successfully, but these errors were encountered:
I have found that manually invoking the REST API calls to mark each project as 'indexed' will refresh the GUI and allow us to search again - but I wouldn't expect that to be the correct answer here.
We recently stepped up to a newer version of both OpenGrok and Tomcat, and have noticed a not-so-desirable effect. We restart our tomcat instance every so often to combat server/process instability. With the newer versions, we've noticed that we are unable to do OpenGrok searches once tomcat is restarted. It reports 'You must select a project!' despite no project being available. The search works fine, and there are projects available prior to the restart. The only way we've discovered to get around this was to completely re-index very app we had. This was not a problem with the older versions we were using. This is problematic because we have about 15 or so projects we like to index, and some take several hours to index. If we need to regenerate all of these every time tomcat restarts, that's going to be an issue.
The text was updated successfully, but these errors were encountered: