--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse-community@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/9903d7a6-0749-4908-9e00-81f94a8032c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hello,On the Glassfish side: Odum has submitted two pull requests to address file descriptor leaks in Dataverse 4.8.6 (and have a patched warfile we're happy to share with you).andYour problems may be solr-specific; there is updated documentation on setting ulimit values atI hope this helps,Donald
On Wed, Jun 6, 2018 at 8:00 AM, <boo...@gmail.com> wrote:
We are running version 4.8.6. for a week now and this morning we had a problem that was new to us:org.apache.solr.client.solrj.SolrServerException: IOException occured when talking to server at: http://localhost:8983/solr java.net.SocketException java.net.SocketException: Too many open files ]]And Solr request are done for almost everything in the UI, therefore our Dataverse wasn't operational anymore. I had to restart glassfish to get things working.Somewhere in the code the sockets are not being closed.Anyone experienced similar problems with 4.8.6?
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.
Thanks,The file descriptor leaks are a very likely cause, because after upgrading I did a 'reExportAll' and these leaks are in the export code.Because we run a fork of I should incorporate these fixes in our code, or just wait for the next upgrade and incorporate it then.
Op woensdag 6 juni 2018 14:34:05 UTC+2 schreef Donald Sizemore II:
Hello,On the Glassfish side: Odum has submitted two pull requests to address file descriptor leaks in Dataverse 4.8.6 (and have a patched warfile we're happy to share with you).andYour problems may be solr-specific; there is updated documentation on setting ulimit values atI hope this helps,Donald
On Wed, Jun 6, 2018 at 8:00 AM, <boo...@gmail.com> wrote:
We are running version 4.8.6. for a week now and this morning we had a problem that was new to us:org.apache.solr.client.solrj.SolrServerException: IOException occured when talking to server at: http://localhost:8983/solr java.net.SocketException java.net.SocketException: Too many open files ]]And Solr request are done for almost everything in the UI, therefore our Dataverse wasn't operational anymore. I had to restart glassfish to get things working.Somewhere in the code the sockets are not being closed.Anyone experienced similar problems with 4.8.6?
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsubscribe...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/9903d7a6-0749-4908-9e00-81f94a8032c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse-community@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/8935c5c6-53e0-41e9-ba2b-17cbf90f106d%40googlegroups.com.