Thank you very much Tim & Kim There's nothing (for the time being) in front of both instances, Tomcat only. The client returns
2018-02-05 03:55:59,020 ERROR org.dspace.app.xmlui.aspect.swordclient.DepositAction @ SWORDClientException encountered Connection reset org.purl.sword.client.SWORDClientException: Connection reset at org.purl.sword.client.Client.postFile(Client.java:460) at org.dspace.sword.client.DSpaceSwordClient.sendMessage(DSpaceSwordClient.java:262) at org.dspace.sword.client.DSpaceSwordClient.deposit(DSpaceSwordClient.java:194) The server says 2018-02-05 18:40:24,003 INFO org.dspace.sword.SWORDAuthenticator @ anonymous:session_id=0:ip_addr=192.168.56.102:sword_authenticate:username= [email protected],on_behalf_of=null 2018-02-05 18:40:24,010 INFO org.dspace.authenticate.PasswordAuthentication @ anonymous:session_id=0:ip_addr=192.168.56.102:authenticate:attempting password auth of [email protected] 2018-02-05 18:40:24,096 INFO org.dspace.authenticate.PasswordAuthentication @ [email protected]: session_id=0:ip_addr=192.168.56.102:authenticate:type=PasswordAuthentication 2018-02-05 18:40:24,097 INFO org.dspace.eperson.EPersonServiceImpl @ [email protected]:session_id=0:ip_addr=192.168.56.102: update_eperson:eperson_id=cef96e76-7b76-4820-ba05-ec0034418b93 2018-02-05 18:40:24,103 INFO org.dspace.sword.DSpaceSWORDServer @ [email protected]:session_id=0:ip_addr=192.168.56.102: sword_service_document_request:[email protected] ,on_behalf_of=null 2018-02-05 18:40:34,693 INFO org.dspace.sword.SWORDAuthenticator @ anonymous:session_id=0:ip_addr=192.168.56.102:sword_authenticate:username= [email protected],on_behalf_of=null 2018-02-05 18:40:34,693 INFO org.dspace.authenticate.PasswordAuthentication @ anonymous:session_id=0:ip_addr=192.168.56.102:authenticate:attempting password auth of [email protected] 2018-02-05 18:40:34,699 INFO org.dspace.authenticate.PasswordAuthentication @ [email protected]: session_id=0:ip_addr=192.168.56.102:authenticate:type=PasswordAuthentication 2018-02-05 18:40:34,699 INFO org.dspace.eperson.EPersonServiceImpl @ [email protected]:session_id=0:ip_addr=192.168.56.102: update_eperson:eperson_id=cef96e76-7b76-4820-ba05-ec0034418b93 2018-02-05 18:40:34,700 INFO org.dspace.sword.DSpaceSWORDServer @ [email protected]:session_id=0:ip_addr=192.168.56.102: sword_service_document_request:[email protected] ,on_behalf_of=null 2018-02-05 18:40:35,245 INFO org.purl.sword.server.DepositServlet @ Using org.dspace.sword.DSpaceSWORDServer as the SWORDServer 2018-02-05 18:40:35,246 INFO org.purl.sword.server.DepositServlet @ Authentication type set to: Basic 2018-02-05 18:40:35,246 WARN org.purl.sword.server.DepositServlet @ No maxUploadSize set, so setting max file upload size to unlimited. 2018-02-05 18:40:35,246 INFO org.purl.sword.server.DepositServlet @ Upload temporary directory set to: /services/tomcat-test/temp And in success cases (files <=4 Mb) 2018-02-05 18:44:18,266 INFO org.dspace.sword.SWORDService @ [2018-02-05 18:44:18.266] Workflow process started; 2018-02-05 18:44:18,270 INFO org.dspace.sword.SWORDService @ [2018-02-05 18:44:18.270] Updated date added to response from item metadata where available; 2018-02-05 18:44:18,270 INFO org.dspace.content.Item @ [email protected]:session_id=0:ip_addr=192.168.56.102: update_item:item_id=c575bef8-c2aa-4843-aad4-9c715b8870d2 2018-02-05 18:44:18,274 INFO org.dspace.sword.SWORDService @ [2018-02-05 18:44:18.274] Ingest successful; 2018-02-05 18:44:18,274 INFO org.dspace.sword.SWORDService @ [2018-02-05 18:44:18.274] Item created with internal identifier: c575bef8-c2aa-4843-aad4-9c715b8870d2; 2018-02-05 18:44:18,277 INFO org.dspace.sword.SWORDService @ [2018-02-05 18:44:18.274] No external identifier available at this stage (item in workflow); 2018-02-05 18:44:18,277 INFO org.dspace.sword.SWORDService @ [2018-02-05 18:44:18.277] Archive ingest completed successfully; 2018-02-05 18:44:18,280 INFO org.dspace.sword.SWORDService @ [2018-02-05 18:44:18.280] Initialising ATOM entry generator for an Item; 2018-02-05 18:44:18,284 INFO org.dspace.sword.SWORDService @ [2018-02-05 18:44:18.284] Total time for deposit processing: 852 ms; 2018-02-05 18:44:18,298 INFO org.purl.sword.base.DepositResponse @ <?xml version="1.0" encoding="UTF-8"?> <atom:entry xmlns:atom="http://www.w3.org/2005/Atom"; xmlns:sword=" http://purl.org/net/sword/";> <atom:id>http://10.63.1.77/dspace</atom:id> <atom:author> <atom:name>[email protected]</atom:name> </atom:author> <atom:generator uri="http://www.dspace.org/ns/sword/1.3.1"; version="1.3"/> <atom:published>1999</atom:published> The sword server log shows the atom entry. I've tried several settings of Tomcat as maxPostSize, others related to uploads, tried with Tomcat 8 and 7 and same results. The stranger thing is that I've tried with a 6.3 instance installed in an old CentOS server (kernel 2.x) and the same client can put files <4Mb and >4Mb Debian/ubuntu distribution seems to have some limit that I can't find. Regards and thank you for your interest German 2018-02-05 17:42 GMT-03:00 Kim Shepherd <[email protected]>: > Hi Germán, > > There could be a few reasons for this -- perhaps a timeout somewhere > during the upload (ie. the larger files aren't causing an issue directly, > but take longer and so trigger a timeout) though that typically wouldn't be > a "connection reset" error... another option could be that the POSTed > header is too large... are there any differences other than file size in > the submissions that are not working? > > Does the DSpace server run Tomcat (or another java container) directly, or > is there something like Apache or nginx in front? It will be useful to know > exactly where the connection reset issue is being triggered. > > I'm CC'ing this message to the dspace-tech list as that's usually a better > place for tech support help > > Cheers! > > Kim > > > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > Virus-free. > www.avg.com > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > <#m_-7842166648088780151_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > M: [email protected] > T: @kimshepherd > P: +6421883635 > W: www.shepherd.nz <http://shepherd.nz> > > 0CCB D957 0C35 F5C1 497E CDCF FC4B ABA3 2A1A FAEC > > On 6 February 2018 at 02:17, Germán Biozzoli <[email protected]> > wrote: > >> Hi >> >> Somebody has experienced problems copying items between instances of >> DSpace using SWORD client & sever? It looks like working OK for attachments >> less than 4Mb, for attachments greater than this size, the server returns >> connection reset. I've checked that >> >> sword-server.max-upload-size = 0 >> >> is set for the server. Could it be a default limit of modern linux >> distros? I'm almost sure it was working ok some years ago. >> >> DSpace 6.2 >> PostgreSQL 9.6.6 >> Debian 9 >> >> both instances >> >> Regards & thanks in advance >> German >> >> -- >> You received this message because you are subscribed to the Google Groups >> "DSpace Community" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at https://groups.google.com/group/dspace-community. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
