[Archivesspace_Users_Group] Database connection error in ArchivesSpace 2.8 PUI

[Cory Nimer]

Looking at the record, there are 604 top containers associated with the resource record. Overall, the collection has 632 top container records.

Cory

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Joshua D. Shaw
Sent: Wednesday, September 30, 2020 11:18 AM
To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org) <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Database connection error in ArchivesSpace 2.8 PUI

Just a guess, but are there more than 1024 top containers that you are trying to retrieve? The maxBooleanClauses setting in https://github.com/archivesspace/archivesspace/blob/master/solr/solrconfig.xml#L69 limits the max number of booleans to 1024.

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Cory Nimer <cory_nimer at byu.edu<mailto:cory_nimer at byu.edu>>
Sent: Wednesday, September 30, 2020 12:09 PM
To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>) <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Database connection error in ArchivesSpace 2.8 PUI


Colleagues,



While testing ArchivesSpace 2.8, we have run into occasional problems loading some records in the PUI, receiving the message "Unable to Connect to Database". Looking at the log files, it reports that the Solr search failed, caused by "too many boolean clauses". A copy of the relevant portion of the log file is attached.



We had experienced similar issues in 2.5.1 as well, but hoped that this would be resolved by the 2.8 release. Reviewing GitHub, the only similar references that we found were pull requests 1155 (https://github.com/archivesspace/archivesspace/pull/1155<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Farchivesspace%2Farchivesspace%2Fpull%2F1155&data=02%7C01%7Cjoshua.d.shaw%40dartmouth.edu%7Cb964b77d8c734c505dac08d8655b4804%7C995b093648d640e5a31ebf689ec9446f%7C0%7C1%7C637370790074461570&sdata=luMVoRgj245fXpohvHhuuUYglynRRPUIjaTG2pxqEqI%3D&reserved=0>) and 1257 (https://github.com/archivesspace/archivesspace/issues/1257<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Farchivesspace%2Farchivesspace%2Fissues%2F1257&data=02%7C01%7Cjoshua.d.shaw%40dartmouth.edu%7Cb964b77d8c734c505dac08d8655b4804%7C995b093648d640e5a31ebf689ec9446f%7C0%7C1%7C637370790074471523&sdata=2%2BGYq9uEXpPP%2FtTLlhJ0zFhHlFxLKlYHPhj4sSQNxG4%3D&reserved=0>), though these were back in the 2.3.1 release.



Have others encountered similar issues, and if so how were they resolved?



Thank you for your help,



Cory Nimer

University Archivist

Brigham Young University

801-422-6091


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200930/e17bd6ad/attachment.html>