it seems that increasing the connection pool in dspace.cfg resolves the problem (keeping the ResultTTL=0):
i've increased the "db.maxconnection = 30" to "db.maxconnection = 500" and it seems working fine. I do not know how much this will affect the server! I can't really troubleshoot the problem but it seems that even with ResultTTL = 0 the connection pool is not freed right away, and if the connection pool is small it finishes its resources, does that make sense? I've tried also with db.maxconnection = 500 and resultTTL=300: after 20 queries or so (2 queries per sec) i get the 404. from the last troubleshoot (db.maxconnection = 500 and resultTTL=300) it seems that the 2 parameters are just a secondary factor, it doesn't make much sense to me. again i dont know the infrastructure/implementation to understand it, how do you see it? Kocisky On 29 March 2011 11:25, LeVan,Ralph <le...@oclc.org> wrote: > Have you been able to make any progress on this? > > > > Ralph > > > > *From:* LeVan,Ralph > *Sent:* Thursday, March 24, 2011 4:42 PM > *To:* Kocisky > *Cc:* dspace-tech@lists.sourceforge.net > > *Subject:* RE: [Dspace-tech] SRW Dspace 1.7 Cannot get a connection > pool(resultSetTTL) > > > > With the resultSetTTL set to zero, how many requests can you make before > you get an error? How long do you have to wait until you can continue > searching? > > > > Everyone else using the SRW interface has the same issues and you’re the > first to report a problem. You might try increasing the size of your > connection pool. > > > > Ralph > > > > *From:* Kocisky [mailto:koci...@autistici.org] > *Sent:* Thursday, March 24, 2011 4:33 PM > *To:* LeVan,Ralph > *Cc:* dspace-tech@lists.sourceforge.net > *Subject:* Re: [Dspace-tech] SRW Dspace 1.7 Cannot get a connection > pool(resultSetTTL) > > > > Ralph, > > the problem reported in my last email was generated by this URL: > > > http://10.0.102.11:8280/SRW/search/DSpace?query=dc.creator+%3D+%22smith%22&version=1.1&operation=searchRetrieve&recordSchema=info%3Asrw%2Fschema%2F1%2Fdc-v1.1&maximumRecords=10&startRecord=1&resultSetTTL=0&recordPacking=xml&recordXPath=&sortKeys= > > this is another example: > > Links:<< Back to Search <http://10.0.102.11:8280/SRW/search/DSpace?> > Results for Search: dc.creator = "smith" > > Records found: 3 > Record: 1 of 3 > > Schema: Dublin Core > Record: 2 of 3 > > Schema: Dublin Core > Record: 3 of 3 > > Schema: Dublin Core > > I have to say that with resultSetTTL=0 it happens less frequently, but if > you make a request each second i think you will definitely experience the > problem. > I was thinking to use SRW for making the queries from a client web > application to a dspace instance. > > I guess that you aren't experiencing this issue, can i ask you what is your > environment? > thank you! > > Kociscky > > > > On 22 March 2011 14:17, LeVan,Ralph <le...@oclc.org> wrote: > > The more I think about this, the more I am convinced that the problem is > confusion at your end. The fact that the searching problem clears up > after 3 minutes is pretty much proof that the cache is being cleared > appropriately. The issue is how to get it cleared out more quickly. > > I think the root problem is the resultSetTTL parameter in your request. > Through it, you are explicitly asking the server to keep the result set > for 300 seconds. No matter what you set the default value to, your > explicit request will override that. You need to omit that parameter > for the default to take effect. Better yet, you should explicitly > specify a resultSetTTL=0 to let the server know you do not want any > caching of results. > > Let me know if this helps. > > Ralph > > > > -----Original Message----- > > From: LeVan,Ralph > > Sent: Tuesday, March 22, 2011 11:42 AM > > To: 'Kocisky'; dspace-tech@lists.sourceforge.net > > Subject: RE: [Dspace-tech] SRW Dspace 1.7 Cannot get a connection > > pool(resultSetTTL) > > > > Kocisky, does that search actually return records when it doesn't > return the 404 > > response? > > > > The root problem is that the search opens a connection to the DSpace > database > > and SRU caches that connection for the life of the search result. > Typically, > > those result sets are cleared from the cache after a configurable > period of > > idleness. That configuration happen through the specification of a > default value > > in the database configuration file, but can be overridden in the > request through > > the resultSetTTL parameter (which I note you still have set to 300 > seconds in the > > request you have shared.) > > > > I have spotted a path in my code where the result set would not be > freed if no > > records had be found as the result of the query. > > > > So, does that search for creator=smith actually find documents? > > > > Ralph > > > > > -----Original Message----- > > > From: Kocisky [mailto:koci...@autistici.org] > > > Sent: Monday, March 21, 2011 4:04 PM > > > To: dspace-tech@lists.sourceforge.net > > > > Subject: [Dspace-tech] SRW Dspace 1.7 Cannot get a connection > > > pool(resultSetTTL) > > > > > > Hi all, > > > > > > I've been trying the SRW module > > > (http://code.google.com/p/oclcsrwdspacelucene/) with dspace 1.7 and > > > i've being facing a problem when I repetitively make the same query: > > > > > > > > http://10.0.102.1:8080/SRW/search/?query=dc.creator+%3D+%22smith%22&ve > > > > > rsion=1.1&operation=searchRetrieve&recordSchema=info%3Asrw%2Fschema > > > %2F1%2Fdc- > > > > > v1.1&maximumRecords=10&startRecord=1&resultSetTTL=300&recordPacking= > > > xml&recordXPath=&sortKeys= > > > > > > i will get: > > > > > > 404: Document not found (No searchRetrieveResponse) > > > OCLC SRW/SRU Server > > > > > > after 3 minutes or so it will restart working. With some extra > > > debugging (thanks to Ralph): > > > > > > ORG.oclc.os.SRW.HouseKeeping=DEBUG > > > ORG.oclc.os.SRW.DSpaceLucene.LuceneQueryResult=DEBUG > > > > > > log4j.logger.ORG.oclc.os.SRW.HouseKeeping=DEBUG > > > log4j.logger.ORG.oclc.os.SRW.DSpaceLucene.LuceneQueryResult=DEBUG > > > > > > i will get the following exception in dspace.cfg: > > > > > > 2011-03-10 16:15:33,978 DEBUG ORG.oclc.os.SRW.SRWServlet @ exit > > > processMethodRequest > > > 2011-03-10 16:15:33,978 DEBUG ORG.oclc.os.SRW.SRWServlet @ Exit: > > > doGet() > > > 2011-03-10 16:15:34,318 ERROR > > > ORG.oclc.os.SRW.DSpaceLucene.SRWLuceneDatabase @ > > > java.lang.InstantiationException: Cannot get a connection, pool > error > > > Timeout waiting for idle object > > > java.lang.InstantiationException: Cannot get a connection, pool > error > > > Timeout waiting for idle object > > > at > > > > > ORG.oclc.os.SRW.DSpaceLucene.LuceneQueryResult.<init>(LuceneQueryRes > > > ult.java:113) > > > at > > > > > ORG.oclc.os.SRW.DSpaceLucene.SRWLuceneDatabase.getQueryResult(SRW > > > LuceneDatabase.java:209) > > > at ORG.oclc.os.SRW.SRWDatabase.doRequest(SRWDatabase.java:598) > > > at > > > > > > gov.loc.www.zing.srw.srw_bindings.SRWSoapBindingImpl.searchRetrieveOpera > > > tion(SRWSoapBindingImpl.java:138) > > > at > > > > > > gov.loc.www.zing.srw.srw_bindings.SRWSoapBindingSkeleton.searchRetrieveO > > > peration(SRWSoapBindingSkeleton.java:68) > > > at sun.reflect.GeneratedMethodAccessor71.invoke(Unknown Source) > > > at > > > > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor > I > > > mpl.java:25) > > > at java.lang.reflect.Method.invoke(Method.java:597) > > > at > > > > > > org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java > :3 > > > 97) > > > at > > > > > > org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.ja > v > > > a:186) > > > at > > > org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323 > ) > > > > > > i've been suggested to try with resultSetTTL=0 in the URL and the > > > configuration, but i didn't see any improvements, does anybody > > > faced/resolved the same issue? > > > thanks > > > > > > Kocisky > > > > > > > > ------------------------------------------------------------------------ > ------ > > > Colocation vs. Managed Hosting > > > A question and answer guide to determining the best fit > > > for your organization - today and in the future. > > > http://p.sf.net/sfu/internap-sfd2d > > > _______________________________________________ > > > DSpace-tech mailing list > > > DSpace-tech@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/dspace-tech > > >
------------------------------------------------------------------------------ Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
_______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech