Right, you are referring to those errors that trigger emails *during *the
database downtime.
As far as I know, there are no email digest features in DSpace out of the
box, so this would require customization.
You might be able to circumvent this by having a more selective number of
recipients in the alert.recipient config variable, and have the recipients
use something like Gmail's inbox filters to ensure that a flood of errors
doesn't clutter up the recipients inbox.
best,
Bram Luyten
--
[image: logo]
*Bram Luyten* *@mire*
*2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010*
*Esperantolaan 4, Heverlee 3001, Belgium*
www.atmire.com<http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=braml>
On Tue, Apr 23, 2013 at 5:06 PM, Kirti Bodhmage <[email protected]>wrote:
> HI,****
>
> ** **
>
> The database is on a flaky hardware. We had few incidences of Dspace
> database going down over the weekend and then DSpace sending loads of
> alert messages.****
>
> ** **
>
> Here is the email generated:****
>
> ** **
>
> *************************
>
> An internal server error occurred on http://qmro.qmul.ac.uk/jspui:****
>
> Date: 4/23/13 2:07 AM****
>
> Session ID: C9917768F7057707AEA026A3DF7BFDF2****
>
> User: Anonymous****
>
> IP address: 138.37.31.252****
>
> -- URL Was:
> http://qmro.qmul.ac.uk/jspui/bitstream/123456789/1674/1/SODIPOPiracyAnd1995.pdf
> ****
>
> -- Method: GET****
>
> -- Parameters were:****
>
> Exception:****
>
> java.sql.SQLRecoverableException: IO Error: The Network Adapter could not
> establish the connection****
>
> at
> oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:478)****
>
> at
> oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:547)*
> ***
>
> at
> oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:225)****
>
> at
> oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:29)
> ****
>
> at
> oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:556)****
>
> at
> java.sql.DriverManager.getConnection(DriverManager.java:582)****
>
> at
> java.sql.DriverManager.getConnection(DriverManager.java:185)****
>
> at
> org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:75)
> ****
>
> at
> org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
> ****
>
> at
> org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:974)
> ****
>
> at
> org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)
> ****
>
> at
> org.dspace.storage.rdbms.DatabaseManager.getConnection(DatabaseManager.java:588)
> ****
>
> at org.dspace.core.Context.<init>(Context.java:95)****
>
> at
> org.dspace.app.webui.util.UIUtil.obtainContext(UIUtil.java:98)****
>
> at
> org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:100)
> ****
>
> at
> org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:67)***
> *
>
> at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:617)****
>
> at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:717)****
>
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> ****
>
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> ****
>
> at
> org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78)
> ****
>
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> ****
>
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> ****
>
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> ****
>
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> ****
>
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> ****
>
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> ****
>
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> ****
>
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> ****
>
> at
> org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)****
>
> at
> org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)****
>
> at
> org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:774)****
>
> at
> org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:703)
> ****
>
> at
> org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:896)
> ****
>
> at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
> ****
>
> at java.lang.Thread.run(Thread.java:619)****
>
> Caused by: oracle.net.ns.NetException: The Network Adapter could not
> establish the connection****
>
> ** **
>
> ** **
>
> ******************************************
>
> ** **
>
> *From:* [email protected] [mailto:[email protected]] *On Behalf Of *Bram
> Luyten
> *Sent:* 23 April 2013 11:40
> *To:* Kirti Bodhmage
> *Cc:* [email protected]
> *Subject:* Re: [Dspace-tech] Dspace sending too many alert emails****
>
> ** **
>
> Hi Kirti,****
>
> ** **
>
> can you copy a typical log entry for such a database error?****
>
> ** **
>
> best regards,****
>
> ** **
>
> Bram****
>
>
> ****
>
>
> -- ****
>
> [image: logo] ****
>
> *Bram Luyten* *@mire*
> *2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010*
> *Esperantolaan 4, Heverlee 3001, Belgium*
> www.atmire.com<http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=braml>
> ****
>
> ** **
>
> On Tue, Apr 23, 2013 at 10:36 AM, Kirti Bodhmage <[email protected]>
> wrote:****
>
> Hi,****
>
> ****
>
> We had couple of occasions when our dspace database went down and that has
> triggered DSpace sending alert messages to the mailing list with****
>
> subject line ‘DSpace: Internal Server Error’.****
>
> ****
>
> The frequency of these messages are 2 or 3 messages per minute, within few
> hours we usually get hundreds of alert emails.****
>
> ****
>
> We do not want Dspace to send loads of alert messages when something goes
> wrong.****
>
> Is there any way to reduce the frequency of these emails ?****
>
> ****
>
> Regards****
>
> Kirti Bodhmage****
>
> ****
>
>
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
> _______________________________________________
> DSpace-tech mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
> List Etiquette:
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette****
>
> ** **
>
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
