Hi, Unfortunately it is not intermittent. However, I suspect it is something specific to our setup.
I checked with the python client and the same problem happens with that, however, both clients work fine with a clean docker instance of dspace run outside our network (the one I tested uses tomcat 8) - so it must be our network/machine. I'll keep digging. Thanks, Robin On Saturday, April 2, 2016 at 3:14:25 PM UTC+11, Robin Harper wrote: > > Hi, > > I am having trouble depositing larger files (> about 128k) using the java > Swordv2 Client into dspace - if I am using tomcat 7 or 8 (works fine in > tomcat 6) > > I have tried setting the following in the connector (server.xml) > maxSwallowSize="-1" maxPostSize="-1" but the size of the files causing > errors are wrong in any event (it should default to 2MB) > > There are no error messages in the tomcat files (even with fine), no > reported problems other than > > INFO [main] (HttpMethodDirector.java:439) - I/O exception > (java.net.ConnectException) caught when processing request: Connection > refused > > INFO [main] (HttpMethodDirector.java:445) - Retrying request > > x 3 > > > from the sword client. I am running out of ideas. I am communicating > directly with tomcat on port 8080. > > > I can always shift back to tomcat 6 when I need to use sword (its > intermittent) but that is a pain. > > > I was wondering if anyone had seen this problem - or had any thoughts as > to where I should look? > > > Thanks > > > Robin > > > -- 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.
