submissions time out but still work

Graham Faulkner

unread,

Sep 25, 2017, 11:17:05 AM9/25/17

to dspac...@googlegroups.com

Hi all,

Starting around last Tuesday users have been experiencing problems with submitting their theses to our DSpace (v5.5, PostgreSQL, Ubuntu 14.04 with DS 5.6 and 5.7 patches). What happens is they complete the submission information (name, abstract, file upload, license agreement, etc.) but when they press the final submit button after the last step it takes 1-2 minutes to either submit successfully or, most frequently, to get a 500 error.

We haven’t touched the source code in the last month, so we’re not sure what happened as of last week. Looking at the logs, I have noticed a few things:

- We are/were getting lots of traffic from Google, Bing and Baidu spiders – I have since implemented the Crawler Session Manager Valve in Tomcat7, which was mentioned by Alan Orth at https://wiki.duraspace.org/display/cmtygp/DCAT+Meeting+April+2017. We are now getting fewer sessions reported in Tomcat, but the upload/submission problem persists.

- In /dspace/log/dspace.log.<date> we are getting lots of “Failed DNS Lookup for IP:<IP address>”.

- In /dspace/log/dspace.log.<date> were are getting lots of “ERROR org.dspace.app.xmlui.cocoon.DSpaceCocoonServletFilter @ Client closed the connection before file download was complete”

- In /dspace/log/cocoon.log.<date> we are getting lots of errors like “Caused by: org.xml.sax.SAXException: An error was encountered while processing the 'aspect.general.PageNotFoundTransformer' Wing based component: org.dspace.app.xmlui.aspect.general.PageNotFoundTransformer”

The odd thing is that the user’s submission usually does go through successfully, even if the “Internal Server Error” page comes up. If they return to the home page, logout and login and go to their submissions they will set it there. Unfortunately, most people don’t know to do that and keep resubmitting their thesis.

Any pointers in the right direction are greatly appreciated!

Cheers,

Graham

-----------------------------------------

Graham Faulkner

Information Technology Specialist/Developer

Digital Initiatives, Library

University of Waterloo

Waterloo, Ontario N2L 3G1 CANADA

519-888-4567 x32461

graham....@uwaterloo.ca

Graham Faulkner

unread,

Oct 2, 2017, 4:32:35 PM10/2/17

to Graham Faulkner, dspac...@googlegroups.com

Hello again,

I wanted to provide a follow-up to this issue in case anyone has further insight. In order to address the issues outlined below, we ended up doing a full upgrade from our 5.5 code base (with 5.6 and 5.7 security patches) to 5.8. After the rebuild everything seemed to work as expected, and the timeouts during submissions didn’t occur.

However, the day after, my colleague realized that new items are not showing up in author browse. The new author(s) information is indeed available in Solr, but when you try to browse by author in DSpace, nothing comes up. Authors that were available before the upgrade are still viewable via author browse.

Any idea as to what is causing the problem, in the migration from 5.5 to 5.8? I notice a lot of “context.turnOffAuthorisationSystem()” and “context.restoreAuthSystemState()” calls in 5.8 – are they possibly related?

Again, any pointers in the right direction are greatly appreciated!

--
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech...@googlegroups.com.
To post to this group, send email to dspac...@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Tim Donohue

unread,

Oct 3, 2017, 10:33:09 AM10/3/17

to Graham Faulkner, dspac...@googlegroups.com

Hi Graham,

I'd recommend checking your log files for any errors that may occur when you add a new item. It's possible your Apache Solr webapp is not responding properly or an error occurs when it attempts to index the new author. Solr is where all browse/search indexes are stored, and it sounds like your index is not being updated properly when you add new items. (As a sidenote, those "context.turnOffAuthorizationSystem()" and similar calls are likely unrelated to your issue...they exist in the Java code to perform administrative backend functions)

Please, take a look at our guide on Troubleshooting Errors, which provides useful information about where to find error messages, where to search for answers, and what to send along to mailing lists for help: https://wiki.duraspace.org/display/DSPACE/Troubleshoot+an+error

- Tim

--

Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

Graham Faulkner

unread,

Oct 4, 2017, 11:46:10 AM10/4/17

to Tim Donohue, dspac...@googlegroups.com

Hi Tim,

Thanks for the info. FYI, we are running DSpace 5.8 on Ubuntu 14.04 LTS and PostgreSQL. We run Apache and Tomcat7.

I tried to view the logs while my colleague did a deposit through the UI. The /dspace/log/solr.log file didn’t show any errors.

However, I did notice some errors/warnings in our /dspace/log/cocoon.log.2017-10-04 during the time frame of the deposit.

2017-10-04 10:39:32,176 WARN cocoon.access - org.apache.cocoon.ConnectionResetException: Connection reset by peer

at <map:select type="browser"> - jndi:/localhost/sitemap.xmap:256:68

at <map:match type="request-parameter"> - jndi:/localhost/sitemap.xmap:255:88

at <map:match> - jndi:/localhost/sitemap.xmap:254:70

2017-10-04 10:39:38,951 ERROR cocoon.handled - Could not read resource cocoon://DRI/1/handle/10012/9972/workflow

at <map:serialize type="xml"> - jndi:/localhost/aspects/aspects.xmap:85:34

at <map:transform type="PageNotFound"> - jndi:/localhost/aspects/aspects.xmap:84:43

at <map:generate> - jndi:/localhost/aspects/aspects.xmap:83:22

at <map:serialize type="html-no-doctype"> - jndi:/localhost/themes/Mirage2/sitemap.xmap:198:56

at <map:transform type="strip-namespaces"> - jndi:/localhost/themes/Mirage2/sitemap.xmap:108:54

at <map:transform type="i18n"> - jndi:/localhost/themes/Mirage2/sitemap.xmap:102:44

at <map:transform> - jndi:/localhost/themes/Mirage2/sitemap.xmap:98:49

at <map:transform type="IncludePageMeta"> - jndi:/localhost/themes/Mirage2/sitemap.xmap:85:51

at <map:transform> - jndi:/localhost/themes/Mirage2/sitemap.xmap:82:54

at <map:generate type="file"> - jndi:/localhost/themes/Mirage2/sitemap.xmap:190:67

at <map:match> - jndi:/localhost/themes/Mirage2/sitemap.xmap:185:37

org.apache.cocoon.ProcessingException: Could not read resource cocoon://DRI/1/handle/10012/9972/workflow