Hi, There are a couple of distinct issues that could be going on:
1) The Tomcat connector may be accepting fewer connections than Apache - so Apache requests have to wait for Tomcat to finish processing some requests. Note - be careful in looking at Tomcat being "idle" - a lack of processor activity is not the same as the threads being idle. They may be sleeping, but allocated to a request. 2) You may be running out of permitted open ports, so Apache can't open another network connection until the OS times out some of the connections, even if Tomcat isn't doing anything. G On Thursday, 17 September 2015 16:47:12 UTC+1, Tyler Danstrom wrote: > > Hi, > > We are having an issue with our DSpace install where Tomcat appears to > idle out during any period of sustained inactivity and then Apache throws a > 503 error the next time any user attempts to connect to our dspace instance. > > Dspace version: 5.1 > UI type: xmlui > OS: Redhat Enterprise Linux release 6.7 > database: oracle > Tomcat version: 7.0.59 > Apache version:2.2.15 > > Tomcat config: > > <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" > > URIEncoding="UTF-8" connectionTimeout="20000"/> > > > > Apache config: > > > ProxyPass /jspui ajp://localhost:8009/jspui/ timeout=10 retry=0 > > ProxyPass /xmlui ajp://localhost:8009/xmlui/ timeout=10 retry=0 > > > We are running Tomcat behind Apache with Shibboleth and accessing dspace > with the following path: > > /xmlui > > after the host name > > The connection is not encrypted over ssl by default. > > Narrative of the problem > > Any time that there is a period of inactivity (inactivity is defined as no > traffic) Tomcat appears to cease to respond to Apache and throws a 503 > error to the end-user. > > The solution to this problem seems to be to upon first receiving the 503 > error immediately reload the page (this may only be required once but has > been witnessed to require three times) within seconds of the unsuccessful > attempt. > > Eventually, the xmlui url resolves correctly and returns a successful > connection to the dspace application and from then on until there is > another sustand period of inactivity everything works fine for one or > multiple simultaneous connections. > > Has anyone else experienced this issue? Does anyone know of a long-term > solution to this problem? > > Any and all help is immensely appreciated. > > Sincerely, > Tyler Danstrom > Programmer/Analyst > University of Chicago Library > -- 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 http://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
