responsible for checking if given database is up and working. Filter
SQL query and tests if such query finishes
without any errors. If error appear upon execution of given query then
given action is taken. This filter has few parameters which helps to
customize its behaviour. Every parameter for this filter is set by proper
web.xml file (
Actually filter recognizes following parameters:
jndi.datasource.namedefines source of database being examined. This parameter is
log.categorydefines category for all generated logs. If this parameter is ommited then
pl.aislib.util.web.filters.connection-checkervalue is assumed.
checking.timeoutdefines the delay between each database query. If last check was successful then next database test will occur only after given amount of seconds. If parameter is omited
30 secondperiod will be assumed.
SQLquery executed at every database test. If execution of given query finishes with errors then given action is taken. If this parameter is omitted then filter checks only status of connection with given database. If connection is broken exception is thrown.
error.actiondefines what action is taken when given database is not responding (or given
SQLquery not finished properly). Possible values:
exceptionoccured exception is presented on the screen. This is default action.
redirectif error occured user is redirected to the other page.
dispatchuser is redirected to given page which is relative to the running servlet.
exception.messagedefinies message which is displayed when error occured and value of
exception. Default value for this parameter is
Could not connect to the database server. Please try again later.
URLaddress where user will be redirected after error during database test. This parameter is required when value of
URLaddres where user will be redirected after error during database test. This address is relative to running servlet. This parameter is required when value of