[Dspace-devel] [DuraSpace JIRA] (DS-1986) REST API holds on to context for too long, should use DB pool
Title: Message Title Graham Triggs updated an issue DSpace / DS-1986 REST API holds on to context for too long, should use DB pool Change By: Graham Triggs Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v6.1.7#6163-sha1:94d557d) -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1986) REST API holds on to context for too long, should use DB pool
Title: Message Title Graham Triggs commented on an issue Re: REST API holds on to context for too long, should use DB pool The context is being stored in a private STATIC member variable in the ItemsResource class (and probably the others too - I haven't checked). This means that it will create it once, and never let it go. Even removing the STATIC probably won't help - it's being wired through Spring, which typically only creates a single instance of the object when processing the configuration. Which puts it in the same class as webapp servlets - also, only a single instance is ever constructed for those too. These objects/methods really should be re-entrant. So no member variables - apart from static instances to loggers and other things that you deliberately know need to persist over multiple calls. Everything should be passed as parameters. This is particularly true for contexts / transactions that demarcate units of work. Apart from rare circumstances, these should always be passed in to method calls. Add Comment DSpace / DS-1986 REST API holds on to context for too long, should use DB pool REST API (Jersey), grabs a context, and never frees/returns/releases it. I don't know exactly what is going on, but it causes the REST API to not be able to reflect real-time updates to content. To repeat. Load a DSpace-REST result for some endpoint. Edit the title/name of the first object returned in that result. Reload the REST endpoint. For me, the... This message was sent by Atlassian JIRA (v6.1.7#6163-sha1:94d557d)
[Dspace-devel] [DuraSpace JIRA] (DS-626) API for exchange of Usage Data over OAI-PMH or SUSHI
[ https://jira.duraspace.org/browse/DS-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=28141#comment-28141 ] Graham Triggs commented on DS-626: -- I'll add to this that the COUNTER Code of Practice 4 calls for the use of SUSHI: http://www.projectcounter.org/r4/COPR4.pdf COUNTER usage reports must also be provided in XML format in accordance with the COUNTER XML schema that is specified by SUSHI ... COUNTER reports in XML must be downloadable using the SUSHI protocol API for exchange of Usage Data over OAI-PMH or SUSHI Key: DS-626 URL: https://jira.duraspace.org/browse/DS-626 Project: DSpace Issue Type: New Feature Components: DSpace API Affects Versions: 1.7.0 Reporter: Bram Luyten (@mire) Priority: Major Exchange of usage statistics from a repository to a central server using OpenURL Context Objects via OAI-PMH or SUSHI http://wiki.surffoundation.nl/display/standards/KE+Usage+Statistics+Guidelines http://wiki.surffoundation.nl/display/standards/info-eu-repo The big stakeholders (OA Statistik, PIRUS, SURF, ...) agreed on a standard for exchange of usage data. This could be a very relevant standard to integrate. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Try New Relic Now We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1245) European Cookie Law Compliance
[ https://jira.duraspace.org/browse/DS-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=27685#comment-27685 ] Graham Triggs commented on DS-1245: --- There is an exception to the requirement to provide information about cookies and obtain consent where the use of the cookie is: (a) for the sole purpose of carrying out the transmission of a communication over an electronic communications network; or (b) where such storage or access is strictly necessary for the provision of an information society service requested by the subscriber or user. Which clears the use of JSESSIONID. With regards to analytics (just a brief snippet): This is especially important with regard to commonly used features such as web analytics. It is clearly the case that the majority of websites undertake some form of analytics activity and most of those will use cookies to facilitate some if not all of that activity. The Information Commissioner recognises that gaining explicit opt-in consent for analytics cookies is difficult and that implied consent might be the most practical and user-friendly option. Overall, the advice seems to be to provide information about the analytics cookies, but not necessarily ask consent. European Cookie Law Compliance -- Key: DS-1245 URL: https://jira.duraspace.org/browse/DS-1245 Project: DSpace Issue Type: New Feature Reporter: Bram Luyten (@mire) Due to e-Privacy regulations in Europe, many websites are now taking measures by means of notifying users and in some cases even requesting acceptance for storing information in cookies. Apart from the session cookie described here https://wiki.duraspace.org/display/DSPACE/SecuringDspace I am not aware of which information DSpace stores and uses in cookies. So in order to deal with this it should be clear what is stored, and based on what is stored, which kinds of notifications are required. more information: http://www.ico.gov.uk/news/blog/2012/updated-ico-advice-guidance-e-privacy-directive-eu-cookie-law.aspx http://econsultancy.com/be/blog/9990-the-bbc-unveils-its-eu-cookie-law-solution -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1482) Add a way for harvesters to find recently added items (request from Google)
[ https://jira.duraspace.org/browse/DS-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=27677#comment-27677 ] Graham Triggs commented on DS-1482: --- I thought this is why we have the sitemaps? If you look at a sitemap, for every item we give the lastmod date as part of the sitemap entry (but not collection / community, as we don't have that information). Retrieving those sitemaps are fast (pre-generated), and it's pretty trivial to either work out from the lastmod date is newer than the last indexed date - or even if it is more recent that the previous time the sitemap was accessed (new item). Add a way for harvesters to find recently added items (request from Google) --- Key: DS-1482 URL: https://jira.duraspace.org/browse/DS-1482 Project: DSpace Issue Type: New Feature Reporter: Tim Donohue This request came out of a discussion I had with Anurag Acharya and Darcy Darpa at Google / Google Scholar. Anurag mentioned that often the Google harvesters seem to need to do a lot of paging / clicking in order to find new items in a DSpace instance. This can cause both a performance hit in DSpace (as the crawler keeps requesting pages), and also can result in delays where items may not appear in Google for some time (if the crawler gives up or moves on before it ever finds the item). Anurag mentioned that it'd be much easier (both on DSpace performance and on the Google crawlers), if DSpace provided some way to easily locate recently added items. This could be something like a Browse Recently Added Items (i.e. browse by dc.date.accessioned), or similar. It was noted that EPrints has such a feature (called Latest Additions). For example, see their demo site: http://demoprints.eprints.org/cgi/latest It's also worth noting this could just be as simple as adding a More Option to our existing Recently Added list (of 5 items), so that you can see other recently added items. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1245) European Cookie Law Compliance
[ https://jira.duraspace.org/browse/DS-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=27678#comment-27678 ] Graham Triggs commented on DS-1245: --- As far as I'm aware, the cookies listed by Tim are the only ones that DSpace uses - and that these are specifically listed as exempt in the ICO advice. However, it doesn't hurt to have an option that can be enabled to display a warning. European Cookie Law Compliance -- Key: DS-1245 URL: https://jira.duraspace.org/browse/DS-1245 Project: DSpace Issue Type: New Feature Reporter: Bram Luyten (@mire) Due to e-Privacy regulations in Europe, many websites are now taking measures by means of notifying users and in some cases even requesting acceptance for storing information in cookies. Apart from the session cookie described here https://wiki.duraspace.org/display/DSPACE/SecuringDspace I am not aware of which information DSpace stores and uses in cookies. So in order to deal with this it should be clear what is stored, and based on what is stored, which kinds of notifications are required. more information: http://www.ico.gov.uk/news/blog/2012/updated-ico-advice-guidance-e-privacy-directive-eu-cookie-law.aspx http://econsultancy.com/be/blog/9990-the-bbc-unveils-its-eu-cookie-law-solution -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1396) Very slow startup on Linux Platforms
[ https://jira.duraspace.org/browse/DS-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=26977#comment-26977 ] Graham Triggs commented on DS-1396: --- Ian, Can you isolate the apps? Does the problem occur when there is only one webapp being loaded, and if so which one? Or does it require a combination (again, what is the minimal combination)? Also, are you judging this by the startup logging from Tomcat, or the first response of the application to requests? The Solr app alone clearly isn't going to be affected by EPerson changes / Bouncy Castle, although it does have significant startup overhead of it's own. Xmlui as well has quite a bit to load. I wouldn't have expected Bouncy Castle to be getting involved during application startup - only when a page is accessed - but I haven't looked over it or traced the execution in quite a while. G Very slow startup on Linux Platforms Key: DS-1396 URL: https://jira.duraspace.org/browse/DS-1396 Project: DSpace Issue Type: Bug Affects Versions: 3.0 Environment: Linux version 2.6.32-38-server (buildd@allspice) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) /usr/lib/jvm/java-6-sun/bin/java -Djava.util.logging.config.file=/usr/local/tomcat7/conf/logging.properties -Djava.awt.headless=true -Djava.security.egd=file:/dev/./urandom -Xms256m -Xmx800m -XX:PermSize=256m -XX:NewSize=64m -server -XX:+UseConcMarkSweepGC -Djava.net.preferIPv4Stack=true -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.endorsed.dirs=/usr/local/tomcat7/endorsed -classpath /usr/local/tomcat7/bin/bootstrap.jar:/usr/local/tomcat7/bin/tomcat-juli.jar -Dcatalina.base=/usr/local/tomcat7 -Dcatalina.home=/usr/local/tomcat7 -Djava.io.tmpdir=/tmp/tomcat7-tmp org.apache.catalina.startup.Bootstrap start Reporter: Ian Boston Priority: Critical I am experiencing extremely slow startup times for DS3-rc3 on Linux with the stock sun JVM, and I have experienced total hangs 11:19-15:09 of the JVM with perfect operation after the end of the period (no restart of any form was required). By slow startup I mean just bringing up solr, xmlui and jspui can take 60 minutes. I think this is due to /dev/ramdom on the OS not getting sufficient entropy, probably caused by the Bouncy Castle crypto APIs or the new SecureRandom() in Eperson. performing a find / as root appears to unstick the JVM on startup, pointing to an entropy issue (find / will cause disk I/O not from cache generating low level device driver entropy) Has anyone else seen these issues ? Is there a known fix (other than performing a find) I have already tried -Djava.security.egd=file:/dev/./urandom -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1222) Alternative Metrics - Integration of AltMetrics
Graham Triggs created DS-1222: - Summary: Alternative Metrics - Integration of AltMetrics Key: DS-1222 URL: https://jira.duraspace.org/browse/DS-1222 Project: DSpace Issue Type: New Feature Reporter: Graham Triggs Relates to DS-1206 (as in inspired by) AltMetrics is a service that gathers metrics from different services and offers an API to display these metrics back in your system. API docs are available here: http://api.altmetric.com/ Note that whilst there are pricing plans, it does state that it is free for non-commercial use. Given that altmetrics are gaining more popularity, it might be a nice feature in DSpace to support this integration out of the box. To be addressed: - would a repository manager want to enable this for all items in the repository, only for certain ones that have a specific identifier (a DOI for example) or even would want to manually enabling or disabling this integration on a per item basis? - How will inclusion of these scripts affect performance (it should not delay pageloads)? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.duraspace.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-924) ItemImport should allow you to import to a workspace
ItemImport should allow you to import to a workspace Key: DS-924 URL: https://jira.duraspace.org/browse/DS-924 Project: DSpace Issue Type: Improvement Reporter: Graham Triggs Assignee: Graham Triggs Currently, ItemImport can import items directly into the archive, or push them through a workflow. It would be useful if you could import into a user's workspace but not push through to the workflow allowing for final modifications before granting the license. This is a tiny change to the importer - I already have the modifications, just need a little bit of work before applying them to trunk. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-925) ItemImport does not delete items that weren't placed into the archive
ItemImport does not delete items that weren't placed into the archive - Key: DS-925 URL: https://jira.duraspace.org/browse/DS-925 Project: DSpace Issue Type: Bug Reporter: Graham Triggs -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-925) ItemImport does not delete items that weren't placed into the archive
[ https://jira.duraspace.org/browse/DS-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs updated DS-925: - Documentation Status: Not Required (was: Needed) Component/s: DSpace API Description: If you don't import items directly into the archive, then the delete function (when given a map file) does not remove the items from DSpace. The code currently just gets the collections for an item, then deletes the item from all collections. It doesn't take into account the possibility of workspace / workflow wrappers. And whilst it doesn't actually remove any items, it does report as if it had. Affects Version/s: 1.5.0 1.5.1 1.5.2 1.6.0 1.6.1 1.6.2 1.7.0 1.7.1 ItemImport does not delete items that weren't placed into the archive - Key: DS-925 URL: https://jira.duraspace.org/browse/DS-925 Project: DSpace Issue Type: Bug Components: DSpace API Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2, 1.7.0, 1.7.1 Reporter: Graham Triggs If you don't import items directly into the archive, then the delete function (when given a map file) does not remove the items from DSpace. The code currently just gets the collections for an item, then deletes the item from all collections. It doesn't take into account the possibility of workspace / workflow wrappers. And whilst it doesn't actually remove any items, it does report as if it had. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-916) The Decompose Diacritics class doesn't work.
[ https://jira.duraspace.org/browse/DS-916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=20559#action_20559 ] Graham Triggs commented on DS-916: -- This is not a bug. It is by design that this class does not strip diacritics. It decomposes them into base and combining character. Note that there is no mention of 'Strip' in the class name or description. If you wish to remove diacritics from the index, then chain the StripDiacritics class after DecomposeDiacritics (the StripDiacritics class does exactly what you patch does - strips the diacritic modifiers from a string, and effectively depends on DecomposeDiacritics being used first). The Decompose Diacritics class doesn't work. Key: DS-916 URL: https://jira.duraspace.org/browse/DS-916 Project: DSpace Issue Type: Bug Components: DSpace API Reporter: Kevin Van de Velde Priority: Major Attachments: Decompose_Diacritics_bugfix.patch The Decompose Diacritics class which should remove the diacritics from the indexed browse values doesn't work (Simply put it does remove the diacritics). I have attached a patch that will resolve this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-803) 'dspace harvest -g' (ping) doesn't
[ https://jira.duraspace.org/browse/DS-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=20388#action_20388 ] Graham Triggs commented on DS-803: -- The harvester CLI calls various methods on the harvester object (OAIHarvester) for each 'command'. But the 'ping' command only checks the parameters and does nothings else. There is a method on the Harvest object that tests the server, looks like it just needs to call that if the parameters are valid: harvester.verifyOAIharvester(oaiSource, oaiSetID, metadataKey, /* true / false for testing ORE */); 'dspace harvest -g' (ping) doesn't -- Key: DS-803 URL: https://jira.duraspace.org/browse/DS-803 Project: DSpace Issue Type: Bug Components: DSpace API Affects Versions: 1.6.2 Reporter: Mark H. Wood Priority: Major The 'ping' code carefully checks its arguments and then exits without doing anything. http://sourceforge.net/mailarchive/forum.php?thread_name=004201cbb7e3%24bd5d5220%243817f660%24%40caforum_name=dspace-tech -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-796) Adding a Community throws ORA-0001 error
[ https://jira.duraspace.org/browse/DS-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=18619#action_18619 ] Graham Triggs commented on DS-796: -- No, the handle server doesn't manage the assignment or indexing of handles. It simply matches against the contents of the handle table, and the assignment is driven by handle_seq which is internal to DSpace. Simplest way of correcting the problem is to drop the sequence, and recreate it with a STARTING WITH clause greater than any of your existing handle [suffixes]. Adding a Community throws ORA-0001 error Key: DS-796 URL: https://jira.duraspace.org/browse/DS-796 Project: DSpace Issue Type: Bug Affects Versions: 1.6.2 Environment: Red Hat Enterprise 5 Oracle 11g Reporter: Bert Lensch While trying to add a top-level community, or a sub-community to our DSpace community, we received an Internal Server Error. Looking through the logs, I noticed that trying to add a community causes Oracle to throw a ORA-0001 error: 2011-01-07 09:14:32,848 WARN org.dspace.app.webui.servlet.DSpaceServlet @ blen...@georgiasouthern.edu:session_id=1232A007BC7400C3524C38F490C87A6B:ip_addr=141.x.x.x:database_error:java.sql.SQLException\colon; ORA-1\colon; unique constraint (DSPACE_USER.SYS_C007905) violated java.sql.SQLException: ORA-1: unique constraint (DSPACE_USER.SYS_C007905) violated at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288) at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:219) at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:970) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1190) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3370) at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3454) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:102) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:102) at org.dspace.storage.rdbms.DatabaseManager.execute(DatabaseManager.java:1429) at org.dspace.storage.rdbms.DatabaseManager.update(DatabaseManager.java:781) at org.dspace.handle.HandleManager.createHandle(HandleManager.java:172) at org.dspace.content.Community.create(Community.java:205) at org.dspace.content.Community.createSubcommunity(Community.java:845) at org.dspace.app.webui.servlet.admin.EditCommunitiesServlet.processConfirmEditCommunity(EditCommunitiesServlet.java:520) at org.dspace.app.webui.servlet.admin.EditCommunitiesServlet.doDSPost(EditCommunitiesServlet.java:237) at org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:147) at org.dspace.app.webui.servlet.DSpaceServlet.doPost(DSpaceServlet.java:105) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.dspace.app.webui.filter.RegisteredOnlyFilter.doFilter(RegisteredOnlyFilter.java:98) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:112) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) at
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-796) Adding a Community throws ORA-0001 error
[ https://jira.duraspace.org/browse/DS-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=18602#action_18602 ] Graham Triggs commented on DS-796: -- I wouldn't want to contradict your DBA, but that description doesn't make any sense. DSPACE_USER is the login / schema that you are using for the database, and SYS_C007905 is the name of the constraint, which you would need to look up in the data dictionary to see what it is operating on. ie: select UCC.CONSTRAINT_NAME, UCC.COLUMN_NAME, UC.CONSTRAINT_TYPE, UC.SEARCH_CONDITION, UC2.TABLE_NAME as REFERENCES_TABLE from USER_CONS_COLUMNS UCC, USER_CONSTRAINTS UC, USER_CONSTRAINTS UC2 where UCC.CONSTRAINT_NAME = UC.CONSTRAINT_NAME and UC.R_CONSTRAINT_NAME = UC2.CONSTRAINT_NAME(+) and UCC.CONSTRAINT_NAME='SYS_C007905' However, looking at your stack trace, the constraint appears to be violated whilst processing HandleManager.createHandle() - which is assigning a handle (prefix + next value in handle sequence) to the community. This would occur if you already have handles in the handle table, but the sequence is not set to provide the next value as being at least one higher than the largest suffix of your already allocated handles. If you recreate handle_seq to start with a value that avoids collisions, you should get past this error. Adding a Community throws ORA-0001 error Key: DS-796 URL: https://jira.duraspace.org/browse/DS-796 Project: DSpace Issue Type: Bug Affects Versions: 1.6.2 Environment: Red Hat Enterprise 5 Oracle 11g Reporter: Bert Lensch While trying to add a top-level community, or a sub-community to our DSpace community, we received an Internal Server Error. Looking through the logs, I noticed that trying to add a community causes Oracle to throw a ORA-0001 error: 2011-01-07 09:14:32,848 WARN org.dspace.app.webui.servlet.DSpaceServlet @ blen...@georgiasouthern.edu:session_id=1232A007BC7400C3524C38F490C87A6B:ip_addr=141.x.x.x:database_error:java.sql.SQLException\colon; ORA-1\colon; unique constraint (DSPACE_USER.SYS_C007905) violated java.sql.SQLException: ORA-1: unique constraint (DSPACE_USER.SYS_C007905) violated at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288) at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:219) at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:970) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1190) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3370) at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3454) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:102) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:102) at org.dspace.storage.rdbms.DatabaseManager.execute(DatabaseManager.java:1429) at org.dspace.storage.rdbms.DatabaseManager.update(DatabaseManager.java:781) at org.dspace.handle.HandleManager.createHandle(HandleManager.java:172) at org.dspace.content.Community.create(Community.java:205) at org.dspace.content.Community.createSubcommunity(Community.java:845) at org.dspace.app.webui.servlet.admin.EditCommunitiesServlet.processConfirmEditCommunity(EditCommunitiesServlet.java:520) at org.dspace.app.webui.servlet.admin.EditCommunitiesServlet.doDSPost(EditCommunitiesServlet.java:237) at org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:147) at org.dspace.app.webui.servlet.DSpaceServlet.doPost(DSpaceServlet.java:105) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.dspace.app.webui.filter.RegisteredOnlyFilter.doFilter(RegisteredOnlyFilter.java:98) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:112) at
[Dspace-devel] [DuraSpace JIRA] Created: (DS-773) Reduce pressure on memory by ensuring that classes with a finalize method make their fields available for garbage collection at earliest possible oppo
Reduce pressure on memory by ensuring that classes with a finalize method make their fields available for garbage collection at earliest possible opportunity - Key: DS-773 URL: https://jira.duraspace.org/browse/DS-773 Project: DSpace Issue Type: Improvement Components: DSpace API Reporter: Graham Triggs Assignee: Graham Triggs Priority: Major Fix For: 1.7.0 There are a couple of classes in DSpace that have a finalize() method - most notably Context(). When those objects are discarded, any objects referenced by their fields can not be garbage collected until the finalizer queue has processed it. By reducing the amount of values retained where possible (ie. by cleaning the Context cache on a complete or abort), we can reduce the pressure on the memory by allowing the objects to be garbage collected before the finalizer thread has processed the referencing objects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Increase Visibility of Your 3D Game App Earn a Chance To Win $500! Tap into the largest installed PC base get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-773) Reduce pressure on memory by ensuring that classes with a finalize method make their fields available for garbage collection at earliest possible opp
[ https://jira.duraspace.org/browse/DS-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs resolved DS-773. -- Resolution: Fixed Reduce pressure on memory by ensuring that classes with a finalize method make their fields available for garbage collection at earliest possible opportunity - Key: DS-773 URL: https://jira.duraspace.org/browse/DS-773 Project: DSpace Issue Type: Improvement Components: DSpace API Reporter: Graham Triggs Assignee: Graham Triggs Priority: Major Fix For: 1.7.0 There are a couple of classes in DSpace that have a finalize() method - most notably Context(). When those objects are discarded, any objects referenced by their fields can not be garbage collected until the finalizer queue has processed it. By reducing the amount of values retained where possible (ie. by cleaning the Context cache on a complete or abort), we can reduce the pressure on the memory by allowing the objects to be garbage collected before the finalizer thread has processed the referencing objects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Increase Visibility of Your 3D Game App Earn a Chance To Win $500! Tap into the largest installed PC base get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-203) Extend the event system to no CRUD actions
[ https://jira.duraspace.org/browse/DS-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=18150#action_18150 ] Graham Triggs commented on DS-203: -- I think this needs to be postponed, given the time it would take to address and test this. We're probably also missing a bit of a trick here - yes, we need to think about the events being fired as being more descriptive, but actually we're too restricted as to what is the object that the event relates to. Why would you get an 'step 1' event on an Item, and not an update on an InprogressSubmission? The event should also carry extended information in it's payload (ie. what start it was transitioning from / to / etc.), rather than having an explosion of event types. Extend the event system to no CRUD actions -- Key: DS-203 URL: https://jira.duraspace.org/browse/DS-203 Project: DSpace Issue Type: Improvement Components: DSpace API Reporter: Andrea Bollini Priority: Major Fix For: 1.7.0 I think that we need to extend the event system to cover also no CRUD actions on content object. I'm thinking to events related to status transactions of an item (or more appropriately of an InProgresSubmission) like these: - installation - start of workflow process - reach of step 1, 2, 3 Also other events could be fired like login / logout of an eperson... Please add here your comments and vote for this issue if you like to see more efforts in this direction -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-470) Batch import times increase drastically as repository size increases; patch to mitigate the problem
[ https://jira.duraspace.org/browse/DS-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=18151#action_18151 ] Graham Triggs commented on DS-470: -- Replaced by DS-696, DS-732 and DS-734 Batch import times increase drastically as repository size increases; patch to mitigate the problem --- Key: DS-470 URL: https://jira.duraspace.org/browse/DS-470 Project: DSpace Issue Type: Improvement Components: DSpace API Affects Versions: 1.6.0 Reporter: Simon Brown Fix For: 1.7.0 Attachments: batch_importer_speedup.patch, prune.patch As mentioned by my colleague Tom De Mulder on dspace-tech and at http://tdm27.wordpress.com/2010/01/19/dspace-1-6-scalability-testing/ As the repository grows, the time taken for batch imports to run also increases. Having profiled the importer in our 1.6.0-RC1 install we determined that most (80%-90%) of the time was spent in calls to IndexBrowse.pruneIndexes(). The reason for this is that IndexBrowse.indexItem() calls pruneIndexes(), so every time an item is indexed, the indexes are pruned. For any batch of size n, where n 1, this is (n - 1) times more than is necessary. Increasing the visibility of pruneIndexes(), removing the call from IndexBrowse.indexItem(), and making a single call at the end of the BrowseConsumer.end() method reduces this to once per event queue run. However, the batch importer calls Context.commit() after each item is imported. Context.commit() runs the event queue, thus causing one event queue run per imported item. This patch addresses both of these issues in a way which has a minimal effect on the rest of the code base; I don't necessarily consider it to be the best way, but I wanted to keep the patch small so it could be put out. What it does is: 1. create an IndexBrowse.indexItemNoPrune() method, which is called from the BrowseConsumer class instead of indexItem(). Other calls to indexItem() are not affected. 2. Call pruneIndexes() from BrowseConsumer.end() 3. Change the call in the batch importer from Context.commit() to Context.getDBConnection.commit(). The only effective difference between the two is that the event queue is not run; I think that a better solution might be to move the code to run the event queue from the Context.commit() method to the Context.complete() method, but I don't know what effect that will have on the rest of the code. As noted in Tom's blog post linked above, these changes, on a repository with in excess of 120,000 items, brought import time from 4.7 seconds/item down to 4.9 items/second. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-470) Batch import times increase drastically as repository size increases; patch to mitigate the problem
[ https://jira.duraspace.org/browse/DS-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs resolved DS-470. -- Resolution: Duplicate Batch import times increase drastically as repository size increases; patch to mitigate the problem --- Key: DS-470 URL: https://jira.duraspace.org/browse/DS-470 Project: DSpace Issue Type: Improvement Components: DSpace API Affects Versions: 1.6.0 Reporter: Simon Brown Fix For: 1.7.0 Attachments: batch_importer_speedup.patch, prune.patch As mentioned by my colleague Tom De Mulder on dspace-tech and at http://tdm27.wordpress.com/2010/01/19/dspace-1-6-scalability-testing/ As the repository grows, the time taken for batch imports to run also increases. Having profiled the importer in our 1.6.0-RC1 install we determined that most (80%-90%) of the time was spent in calls to IndexBrowse.pruneIndexes(). The reason for this is that IndexBrowse.indexItem() calls pruneIndexes(), so every time an item is indexed, the indexes are pruned. For any batch of size n, where n 1, this is (n - 1) times more than is necessary. Increasing the visibility of pruneIndexes(), removing the call from IndexBrowse.indexItem(), and making a single call at the end of the BrowseConsumer.end() method reduces this to once per event queue run. However, the batch importer calls Context.commit() after each item is imported. Context.commit() runs the event queue, thus causing one event queue run per imported item. This patch addresses both of these issues in a way which has a minimal effect on the rest of the code base; I don't necessarily consider it to be the best way, but I wanted to keep the patch small so it could be put out. What it does is: 1. create an IndexBrowse.indexItemNoPrune() method, which is called from the BrowseConsumer class instead of indexItem(). Other calls to indexItem() are not affected. 2. Call pruneIndexes() from BrowseConsumer.end() 3. Change the call in the batch importer from Context.commit() to Context.getDBConnection.commit(). The only effective difference between the two is that the event queue is not run; I think that a better solution might be to move the code to run the event queue from the Context.commit() method to the Context.complete() method, but I don't know what effect that will have on the rest of the code. As noted in Tom's blog post linked above, these changes, on a repository with in excess of 120,000 items, brought import time from 4.7 seconds/item down to 4.9 items/second. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-707) Fix/improve DSpace through static code inspections
[ https://jira.duraspace.org/browse/DS-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs resolved DS-707. -- Resolution: Fixed Done about as much as we can for 1.7.0 - however, it's an ongoing task to ensure that we maintain quality. Fix/improve DSpace through static code inspections -- Key: DS-707 URL: https://jira.duraspace.org/browse/DS-707 Project: DSpace Issue Type: Improvement Reporter: Graham Triggs Fix For: 1.7.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-640) Interal System Error when browsing with wrong argument
[ https://jira.duraspace.org/browse/DS-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=18101#action_18101 ] Graham Triggs commented on DS-640: -- Rather than adding exceptions, can't we use ones that already exist? For instance, why not use ResourceNotFoundException instead of NotFoundException? There is also a case for using a default browse option rather than enforce supplying a parameter - it's more likely that /browse returning an error code will cause a problem than any of the ?type= variants, if any proxy or robot is given cause to process such a url. Interal System Error when browsing with wrong argument -- Key: DS-640 URL: https://jira.duraspace.org/browse/DS-640 Project: DSpace Issue Type: Bug Components: JSPUI, XMLUI Affects Versions: 1.5.2, 1.6.0, 1.6.1, 1.6.2 Reporter: Hardik Mishra Assignee: Kim Shepherd Priority: Major Attachments: browse.patch On Browsing Items: If someone tries to use browse type for which browse index does not exist, like browse=publisher e.g. http://dspace.webinito.com/browse?type OR e.g. http://dspace.webinito.com/browse?type=xyz You will get Internal System Error -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-733) Tools for (load) testing
[ https://jira.duraspace.org/browse/DS-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs resolved DS-733. -- Resolution: Fixed Tools for (load) testing Key: DS-733 URL: https://jira.duraspace.org/browse/DS-733 Project: DSpace Issue Type: New Feature Reporter: Graham Triggs Assignee: Graham Triggs Fix For: 1.7.0 Tools that are useful for testing purposes. Currently, this contains: - a class that will parse a medline.xml file from PubMed (containing multiple records) into DSpace packages (allows for a large number of realistic records to be generated simply) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-733) Tools for (load) testing
[ https://jira.duraspace.org/browse/DS-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs updated DS-733: - Documentation Status: Not Required (was: Needed) Status: Open (was: Received) Tools for (load) testing Key: DS-733 URL: https://jira.duraspace.org/browse/DS-733 Project: DSpace Issue Type: New Feature Reporter: Graham Triggs Assignee: Graham Triggs Fix For: 1.7.0 Tools that are useful for testing purposes. Currently, this contains: - a class that will parse a medline.xml file from PubMed (containing multiple records) into DSpace packages (allows for a large number of realistic records to be generated simply) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-743) ItemImport fails on large batches with OutOfMemory exception
[ https://jira.duraspace.org/browse/DS-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs updated DS-743: - Status: Open (was: Received) ItemImport fails on large batches with OutOfMemory exception Key: DS-743 URL: https://jira.duraspace.org/browse/DS-743 Project: DSpace Issue Type: Bug Reporter: Graham Triggs Priority: Major Fix For: 1.7.0 On large imports, ItemImport will throw an OutOfMemory exception - this is because the context isn't having the cache cleared, so the Item objects that are created are building up in memory. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-743) ItemImport fails on large batches with OutOfMemory exception
[ https://jira.duraspace.org/browse/DS-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs resolved DS-743. -- Resolution: Fixed ItemImport fails on large batches with OutOfMemory exception Key: DS-743 URL: https://jira.duraspace.org/browse/DS-743 Project: DSpace Issue Type: Bug Reporter: Graham Triggs Priority: Major Fix For: 1.7.0 On large imports, ItemImport will throw an OutOfMemory exception - this is because the context isn't having the cache cleared, so the Item objects that are created are building up in memory. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-734) Improve database efficiency
[ https://jira.duraspace.org/browse/DS-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs resolved DS-734. -- Resolution: Fixed Improve database efficiency --- Key: DS-734 URL: https://jira.duraspace.org/browse/DS-734 Project: DSpace Issue Type: Improvement Reporter: Graham Triggs Assignee: Graham Triggs Fix For: 1.7.0 Improve various parts of database access - ie. - PreparedStatement and parameterized access for getnextid() (relatively expensive as a statement / unparameterized) - Where possible, convert DatabaseManager.create() / DatabaseManager.update() to DatabaseManager.row() / DatabaseManager.insert() (delay inserting records until you have the rest of the data for the row, thereby reducing an INSERT / UPDATE sequence to just an INSERT. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-739) Improve performance of Lucene indexing
[ https://jira.duraspace.org/browse/DS-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs resolved DS-739. -- Resolution: Fixed Improve performance of Lucene indexing -- Key: DS-739 URL: https://jira.duraspace.org/browse/DS-739 Project: DSpace Issue Type: Improvement Reporter: Graham Triggs Assignee: Graham Triggs Fix For: 1.7.0 Adds a batch processing mode for Lucene indexes. Can be controlled by calling DSIndexer.setBatchProcessingMode(boolean). NB: If you set batch processing mode to true, ensure that you set it to 'false' at the end of the batch to flush any unwritten documents. The size of the batch can be controlled by setting a numeric value in dspace.cfg for the property: search.batch.documents By default, the size of the batch is 20 documents. Additionally, there is the possibility to create a 'delayed index flusher'. If a web application pushes multiple search requests (ie. a barrage or sword deposits, or multiple quick edits in the ui), then this will combine them into a single index update (up to the limit of the batch defined above). To use the delayed update, set the property 'search.index.delay' in dspace.cfg to the number of milliseconds to wait for an update. eg. search.index.delay = 5000 will hold a Lucene update in a queue for up to 5 seconds. After 5 seconds - or the batch limit above is reached - all waiting updates will be written to the Lucene index. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-732) Improve performance of browse
[ https://jira.duraspace.org/browse/DS-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs resolved DS-732. -- Resolution: Fixed Improve performance of browse - Key: DS-732 URL: https://jira.duraspace.org/browse/DS-732 Project: DSpace Issue Type: Improvement Reporter: Graham Triggs Assignee: Graham Triggs Priority: Major Fix For: 1.7.0 Profile browse and find improvements in performance -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-739) Improve performance of Lucene indexing
[ https://jira.duraspace.org/browse/DS-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=17996#action_17996 ] Graham Triggs commented on DS-739: -- The various tasks - media-filter, indexing, itemimport - put DSIndexer into batchprocessingmode in all cases. It's just a case of what you have set the dspace.cfg property to in order to control the size of the batch (default is 20). For the delayed update for web applications, this defaults to being disabled, but can be enabled by adding the dspace.cfg property. Improve performance of Lucene indexing -- Key: DS-739 URL: https://jira.duraspace.org/browse/DS-739 Project: DSpace Issue Type: Improvement Reporter: Graham Triggs Assignee: Graham Triggs Fix For: 1.7.0 Adds a batch processing mode for Lucene indexes. Can be controlled by calling DSIndexer.setBatchProcessingMode(boolean). NB: If you set batch processing mode to true, ensure that you set it to 'false' at the end of the batch to flush any unwritten documents. The size of the batch can be controlled by setting a numeric value in dspace.cfg for the property: search.batch.documents By default, the size of the batch is 20 documents. Additionally, there is the possibility to create a 'delayed index flusher'. If a web application pushes multiple search requests (ie. a barrage or sword deposits, or multiple quick edits in the ui), then this will combine them into a single index update (up to the limit of the batch defined above). To use the delayed update, set the property 'search.index.delay' in dspace.cfg to the number of milliseconds to wait for an update. eg. search.index.delay = 5000 will hold a Lucene update in a queue for up to 5 seconds. After 5 seconds - or the batch limit above is reached - all waiting updates will be written to the Lucene index. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book Blueprint to a Billion shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-743) ItemImport fails on large batches with OutOfMemory exception
ItemImport fails on large batches with OutOfMemory exception Key: DS-743 URL: https://jira.duraspace.org/browse/DS-743 Project: DSpace Issue Type: Bug Reporter: Graham Triggs Priority: Major Fix For: 1.7.0 On large imports, ItemImport will throw an OutOfMemory exception - this is because the context isn't having the cache cleared, so the Item objects that are created are building up in memory. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book Blueprint to a Billion shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-739) Improve performance of Lucene indexing
Improve performance of Lucene indexing -- Key: DS-739 URL: https://jira.duraspace.org/browse/DS-739 Project: DSpace Issue Type: Improvement Reporter: Graham Triggs Fix For: 1.7.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book Blueprint to a Billion shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Assigned: (DS-739) Improve performance of Lucene indexing
[ https://jira.duraspace.org/browse/DS-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs reassigned DS-739: Assignee: Graham Triggs Improve performance of Lucene indexing -- Key: DS-739 URL: https://jira.duraspace.org/browse/DS-739 Project: DSpace Issue Type: Improvement Reporter: Graham Triggs Assignee: Graham Triggs Fix For: 1.7.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book Blueprint to a Billion shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-739) Improve performance of Lucene indexing
[ https://jira.duraspace.org/browse/DS-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs updated DS-739: - Status: Open (was: Received) Improve performance of Lucene indexing -- Key: DS-739 URL: https://jira.duraspace.org/browse/DS-739 Project: DSpace Issue Type: Improvement Reporter: Graham Triggs Assignee: Graham Triggs Fix For: 1.7.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book Blueprint to a Billion shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-739) Improve performance of Lucene indexing
[ https://jira.duraspace.org/browse/DS-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs updated DS-739: - Description: Adds a batch processing mode for Lucene indexes. Can be controlled by calling DSIndexer.setBatchProcessingMode(boolean). NB: If you set batch processing mode to true, ensure that you set it to 'false' at the end of the batch to flush any unwritten documents. The size of the batch can be controlled by setting a numeric value in dspace.cfg for the property: search.batch.documents By default, the size of the batch is 20 documents. Improve performance of Lucene indexing -- Key: DS-739 URL: https://jira.duraspace.org/browse/DS-739 Project: DSpace Issue Type: Improvement Reporter: Graham Triggs Assignee: Graham Triggs Fix For: 1.7.0 Adds a batch processing mode for Lucene indexes. Can be controlled by calling DSIndexer.setBatchProcessingMode(boolean). NB: If you set batch processing mode to true, ensure that you set it to 'false' at the end of the batch to flush any unwritten documents. The size of the batch can be controlled by setting a numeric value in dspace.cfg for the property: search.batch.documents By default, the size of the batch is 20 documents. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book Blueprint to a Billion shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-739) Improve performance of Lucene indexing
[ https://jira.duraspace.org/browse/DS-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs updated DS-739: - Documentation Status: In Description (was: Not Required) Description: Adds a batch processing mode for Lucene indexes. Can be controlled by calling DSIndexer.setBatchProcessingMode(boolean). NB: If you set batch processing mode to true, ensure that you set it to 'false' at the end of the batch to flush any unwritten documents. The size of the batch can be controlled by setting a numeric value in dspace.cfg for the property: search.batch.documents By default, the size of the batch is 20 documents. Additionally, there is the possibility to create a 'delayed index flusher'. If a web application pushes multiple search requests (ie. a barrage or sword deposits, or multiple quick edits in the ui), then this will combine them into a single index update (up to the limit of the batch defined above). To use the delayed update, set the property 'search.index.delay' in dspace.cfg to the number of milliseconds to wait for an update. eg. search.index.delay = 5000 will hold a Lucene update in a queue for up to 5 seconds. After 5 seconds - or the batch limit above is reached - all waiting updates will be written to the Lucene index. was: Adds a batch processing mode for Lucene indexes. Can be controlled by calling DSIndexer.setBatchProcessingMode(boolean). NB: If you set batch processing mode to true, ensure that you set it to 'false' at the end of the batch to flush any unwritten documents. The size of the batch can be controlled by setting a numeric value in dspace.cfg for the property: search.batch.documents By default, the size of the batch is 20 documents. Improve performance of Lucene indexing -- Key: DS-739 URL: https://jira.duraspace.org/browse/DS-739 Project: DSpace Issue Type: Improvement Reporter: Graham Triggs Assignee: Graham Triggs Fix For: 1.7.0 Adds a batch processing mode for Lucene indexes. Can be controlled by calling DSIndexer.setBatchProcessingMode(boolean). NB: If you set batch processing mode to true, ensure that you set it to 'false' at the end of the batch to flush any unwritten documents. The size of the batch can be controlled by setting a numeric value in dspace.cfg for the property: search.batch.documents By default, the size of the batch is 20 documents. Additionally, there is the possibility to create a 'delayed index flusher'. If a web application pushes multiple search requests (ie. a barrage or sword deposits, or multiple quick edits in the ui), then this will combine them into a single index update (up to the limit of the batch defined above). To use the delayed update, set the property 'search.index.delay' in dspace.cfg to the number of milliseconds to wait for an update. eg. search.index.delay = 5000 will hold a Lucene update in a queue for up to 5 seconds. After 5 seconds - or the batch limit above is reached - all waiting updates will be written to the Lucene index. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book Blueprint to a Billion shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-736) ItemImport - nicer handling of no contents file, and more efficient handling of no handle file
ItemImport - nicer handling of no contents file, and more efficient handling of no handle file -- Key: DS-736 URL: https://jira.duraspace.org/browse/DS-736 Project: DSpace Issue Type: Improvement Reporter: Graham Triggs Assignee: Graham Triggs Fix For: 1.7.0 Improves contents file handling, so that if the contents file is missing, but the directory only contains metadata files, then continue to import the item as a metadata record. If there are any non-metadata (and non-handle) files, then fail to import if the contents file is missing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Achieve Improved Network Security with IP and DNS Reputation. Defend against bad network traffic, including botnets, malware, phishing sites, and compromised hosts - saving your company time, money, and embarrassment. Learn More! http://p.sf.net/sfu/hpdev2dev-nov ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Work started: (DS-736) ItemImport - nicer handling of no contents file, and more efficient handling of no handle file
[ https://jira.duraspace.org/browse/DS-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on DS-736 started by Graham Triggs. ItemImport - nicer handling of no contents file, and more efficient handling of no handle file -- Key: DS-736 URL: https://jira.duraspace.org/browse/DS-736 Project: DSpace Issue Type: Improvement Reporter: Graham Triggs Assignee: Graham Triggs Fix For: 1.7.0 Improves contents file handling, so that if the contents file is missing, but the directory only contains metadata files, then continue to import the item as a metadata record. If there are any non-metadata (and non-handle) files, then fail to import if the contents file is missing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Achieve Improved Network Security with IP and DNS Reputation. Defend against bad network traffic, including botnets, malware, phishing sites, and compromised hosts - saving your company time, money, and embarrassment. Learn More! http://p.sf.net/sfu/hpdev2dev-nov ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Assigned: (DS-734) Improve database efficiency
[ https://jira.duraspace.org/browse/DS-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs reassigned DS-734: Assignee: Graham Triggs Improve database efficiency --- Key: DS-734 URL: https://jira.duraspace.org/browse/DS-734 Project: DSpace Issue Type: Improvement Reporter: Graham Triggs Assignee: Graham Triggs Fix For: 1.7.0 Improve various parts of database access - ie. - PreparedStatement and parameterized access for getnextid() (relatively expensive as a statement / unparameterized) - Where possible, convert DatabaseManager.create() / DatabaseManager.update() to DatabaseManager.row() / DatabaseManager.insert() (delay inserting records until you have the rest of the data for the row, thereby reducing an INSERT / UPDATE sequence to just an INSERT. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-734) Improve database efficiency
[ https://jira.duraspace.org/browse/DS-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs updated DS-734: - Status: Open (was: Received) Improve database efficiency --- Key: DS-734 URL: https://jira.duraspace.org/browse/DS-734 Project: DSpace Issue Type: Improvement Reporter: Graham Triggs Assignee: Graham Triggs Fix For: 1.7.0 Improve various parts of database access - ie. - PreparedStatement and parameterized access for getnextid() (relatively expensive as a statement / unparameterized) - Where possible, convert DatabaseManager.create() / DatabaseManager.update() to DatabaseManager.row() / DatabaseManager.insert() (delay inserting records until you have the rest of the data for the row, thereby reducing an INSERT / UPDATE sequence to just an INSERT. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-732) Improve performance of browse
[ https://jira.duraspace.org/browse/DS-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs updated DS-732: - Status: Open (was: Received) Improve performance of browse - Key: DS-732 URL: https://jira.duraspace.org/browse/DS-732 Project: DSpace Issue Type: Improvement Reporter: Graham Triggs Assignee: Graham Triggs Priority: Major Fix For: 1.7.0 Profile browse and find improvements in performance -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Work started: (DS-732) Improve performance of browse
[ https://jira.duraspace.org/browse/DS-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on DS-732 started by Graham Triggs. Improve performance of browse - Key: DS-732 URL: https://jira.duraspace.org/browse/DS-732 Project: DSpace Issue Type: Improvement Reporter: Graham Triggs Assignee: Graham Triggs Priority: Major Fix For: 1.7.0 Profile browse and find improvements in performance -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-734) Improve database efficiency
Improve database efficiency --- Key: DS-734 URL: https://jira.duraspace.org/browse/DS-734 Project: DSpace Issue Type: Improvement Reporter: Graham Triggs Fix For: 1.7.0 Improve various parts of database access - ie. - PreparedStatement and parameterized access for getnextid() (relatively expensive as a statement / unparameterized) - Where possible, convert DatabaseManager.create() / DatabaseManager.update() to DatabaseManager.row() / DatabaseManager.insert() (delay inserting records until you have the rest of the data for the row, thereby reducing an INSERT / UPDATE sequence to just an INSERT. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-733) Tools for (load) testing
Tools for (load) testing Key: DS-733 URL: https://jira.duraspace.org/browse/DS-733 Project: DSpace Issue Type: New Feature Reporter: Graham Triggs Assignee: Graham Triggs Fix For: 1.7.0 Tools that are useful for testing purposes. Currently, this contains: - a class that will parse a medline.xml file from PubMed (containing multiple records) into DSpace packages (allows for a large number of realistic records to be generated simply) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DSRV-10) Create simplified version of DSpace services that only uses Spring as a service manager
Create simplified version of DSpace services that only uses Spring as a service manager --- Key: DSRV-10 URL: https://jira.duraspace.org/browse/DSRV-10 Project: DSpace Services Module Issue Type: Improvement Reporter: Graham Triggs Assignee: Graham Triggs The current dspace-services code is overly complex to deal with the possibility of using multiple IoC containers. Plus, some of the complex functionality is causing resource leakage. A simplified version has been created that only uses Spring as a service manager, and removes a lot of the now redundant code -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-723) Some Browse code did not take into account the change to Authority values
Some Browse code did not take into account the change to Authority values - Key: DS-723 URL: https://jira.duraspace.org/browse/DS-723 Project: DSpace Issue Type: Bug Affects Versions: 1.6.2, 1.6.1, 1.6.0 Reporter: Graham Triggs There is a potential issue in the obtaining of list values - where the authority code was added, it changed a List of Strings to a List of String arrays ( the value, and the authority). Some of the code that used these methods did not take into account that there was a String[] and would have thrown a classcastexception. This has now been accounted for, but in doing so, it ignores the authority value component of the array. We need to consider if this needs to be updated, or possibly if that method should just be removed (doesn't appear to be used) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-695) Separate DatabaseManager from registering / creating database pool, allow datasource to be retrieved from JNDI
[ https://jira.duraspace.org/browse/DS-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs resolved DS-695. -- Resolution: Fixed Separate DatabaseManager from registering / creating database pool, allow datasource to be retrieved from JNDI -- Key: DS-695 URL: https://jira.duraspace.org/browse/DS-695 Project: DSpace Issue Type: Improvement Reporter: Graham Triggs Assignee: Graham Triggs Priority: Major Fix For: 1.7.0 Attachments: datasource.patch Change DatabaseManager to use a Datasource instead of the DriverManager methods. Separate the registering of the database driver / pool into a separate class that returns a new DataSource (this mainly facilitates removing the -dbcp, -pool and driver jars from the web application in the case that you are retrieving a pre-configured database resource from JNDI. Will fallback when JNDI not detected to manually create a pool from the dspace.cfg (for offline tasks). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-697) Extend supported input formats for thumbnail generation in MediaFilter
[ https://jira.duraspace.org/browse/DS-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs resolved DS-697. -- Resolution: Fixed Extend supported input formats for thumbnail generation in MediaFilter -- Key: DS-697 URL: https://jira.duraspace.org/browse/DS-697 Project: DSpace Issue Type: Improvement Reporter: Graham Triggs Assignee: Graham Triggs Priority: Major Fix For: 1.7.0 Attachments: mediafilter.patch -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
