Changes between Version 4 and Version 5 of StartupErrorsDatabaseConnections


Ignore:
Timestamp:
Feb 15, 2011, 1:01:55 AM (13 years ago)
Author:
simonp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • StartupErrorsDatabaseConnections

    v4 v5  
    1818
    1919 * detect and collect any exception information from the servlet initialization (as well as continuing to log it) in jeeves/server/JeevesEngine.java
    20  * if an exception occurs then this info will be shown to any user that makes a request after the servlet has finished initialization by directing all requests to a !GeoNetwork error service (main.error), configured in web/geonetwork/WEB-INF/config.xml
     20 * if an exception occurs then this info will be shown to any user that makes a request after the servlet has finished initialization by directing all requests (because we can't assume the user will come to the page through a particular service and what use is the webapp when the initialization has failed?) to a !GeoNetwork error service (main.error), configured in web/geonetwork/WEB-INF/config.xml
    2121
    22 
     22[[Image(screenshot-initialization-exception.png)]]
    2323
    2424Finally, related to this problem is the need to display database status (at least: has the connection been successful, jdbc url, number of active connections in pool, number of available (idle) connections in pool, maximum number of active connections). This info can be obtained from the Apache Commons Database Connection Pool !ResourceProvider that replaces the old Jeeves !DbmsPool and can be displayed in Francois' new System Information screen in the Administration menu.