On Mon, Nov 5, 2012 at 3:36 AM, Vlastimil Krejcir <krej...@ics.muni.cz> wrote:
>   Hi,
>
>   it's again and again - try to search dspace-tech archives, it has been
> already discussed. And don't be sad, this is probably not your fault and
> you're not alone who observer this behaviour. The solution is to have a
> "guard" testing periodically if Tomcat is running. In case Tomcat doesn't
> respond you need to restart it.
>
>   Have a nice day

Thanks. Since my monitor reports an average of every 20 or so minutes
I felt pretty sure it was something about my settings.

regards,
./fxk



>
>   Vlastik
>
> ----------------------------------------------------------------------------
> Vlastimil Krejčíř
> Library and Information Centre, Institute of Computer Science
> Masaryk University, Brno, Czech Republic
> Email: krejcir (at) ics (dot) muni (dot) cz
> Phone: +420 549 49 3872
> ICQ: 163963217
> Jabber: kre...@jabber.org
> ----------------------------------------------------------------------------
>
>
> On Sun, 4 Nov 2012, Francis Kayiwa wrote:
>
>> Hey all
>>
>> I am wondering if anyone can help shed light on this. We have
>>
>> Red Hat Enterprise Linux Server release 6.3
>> Apache 2.2.15 (Red Hat package)
>> Tomcat (Apache Tomcat Version 6.0.36)
>> Apache forwards request via AJP
>>
>> We seem to encounter frequent crashes that remain unpredictable to me
>> at the moment. As best as I can determine Tomcat is not processing
>> these `fast enough` based on the errors in the Apache logs
>>
>> We keep seeing these errors
>>
>> [Sun Nov 04 03:16:09 2012] [error] proxy: AJP: failed to make
>> connection to backend: localhost
>> [Sun Nov 04 03:16:16 2012] [error] (111)Connection refused: proxy:
>> AJP: attempt to connect to 127.0.0.1:8009 (localhost) failed
>> [Sun Nov 04 03:16:16 2012] [error] ap_proxy_connect_backend disabling
>> worker for (localhost)
>> [Sun Nov 04 03:16:16 2012] [error] proxy: AJP: failed to make
>> connection to backend: localhost
>>
>> Below are what I think are the pertinent parts of the config files
>> which I will gladly share on request.
>>
>> <IfModule prefork.c>
>> StartServers       8
>> MinSpareServers    5
>> MaxSpareServers   20
>> ServerLimit      256
>> MaxClients       256
>> MaxRequestsPerChild  4000
>> </IfModule>
>>
>> <VirtualHost *:80>
>>        ServerName tld.domain.name
>>        DocumentRoot /path/to/home
>>        ErrorLog /var/log/httpd/error.log
>>        CustomLog /var/log/httpd/access.log combined
>>
>>        ProxyRequests Off
>>
>>        ProxyPass  /Shibboleth.sso !
>>        ProxyPass / ajp://localhost:8009/ max=256 retry=60
>>        ProxyPassReverse / ajp://localhost:8009/
>> </VirtualHost>
>>
>> <Connector port="8009" protocol="AJP/1.3" redirectPort="8443"
>> UIEncoding="UTF-8" tomcatAuthentication="false" enableLookups="false"
>> connectionTimeout="120000" packetSize="22528" maxThreads="256" />
>>
>> Is there anything there that looks unreasonable? Any recommendations?
>> My (mis?)reading of the dspace documentation is that mod_proxy_ajp has
>> the most reliable results. It certainly is that way on all our dev
>> machines.
>>
>> regards,
>> ./fxk
>>
>> --
>> "Beer busts, beer blasts, keggers, stein hoists, A.A. meetings, beer
>> nights..." --Homer Simpson
>>
>>
>> ------------------------------------------------------------------------------
>> LogMeIn Central: Instant, anywhere, Remote PC access and management.
>> Stay in control, update software, and manage PCs from one command center
>> Diagnose problems and improve visibility into emerging IT issues
>> Automate, monitor and manage. Do more in less time with Central
>> http://p.sf.net/sfu/logmein12331_d2d
>> _______________________________________________
>> DSpace-tech mailing list
>> DSpace-tech@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>>
>



--
"Beer busts, beer blasts, keggers, stein hoists, A.A. meetings, beer
nights..." --Homer Simpson

------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to