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

Check dataunit releasing in frontend #267

Closed
tomas-knap opened this issue Jan 2, 2015 · 3 comments
Closed

Check dataunit releasing in frontend #267

tomas-knap opened this issue Jan 2, 2015 · 3 comments

Comments

@tomas-knap
Copy link

As described in https://team.eea.sk/jira/browse/COMSODE-200:

RDFQueryView.java:281
RDFQueryView.java:149
ManagableRdfDataUnit is created but never released.
It is mandatory to call .release() after work is done (especially problem for virtuoso data units).

Please check whether this is still relevant (w.r.t. to the currently prepared Virtuoso branch). If not, close with won't fix.

Should be assigned to Petr Skoda.

@skrchnavy
Copy link

@skodape : ist this issue still relevant? it could be related to virtuoso support.

@skodapetr
Copy link
Member

It should be quick-solved by:
2be7174
ab6f76b

Problem is, that there is no space reliable enough to close the repository, also close and open too much will cause performance issue. For this reason the repository is auto closed after some inactivity (frost commit).
Other problem was during redeploy - where repositories had not been closed and the lock prevented from browsing until full tomcat restart. I hope that this is solved by the second commit.

@tomas-knap
Copy link
Author

There is a checker, which closes open connections, solves the problem with RDFQueryView

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

No branches or pull requests

3 participants