On Wed, 2002-09-18 at 18:41, Eduard Witteveen wrote:
> Data Source (even pooled one's), i have looked how hard it is to make
> MMBase work with connections retrieved from the application server.
The files:
src/org/mmbas/module/mmbase/database/Naming.java
config/default/modules/jdbc.xml
html/WEB-INF/web.xml
orion/config/data-sources.xml
tomcat/conf/server.xml
--
Eduard Witteveen Systeem Ontwikkelaar
Publieke Omroep, Gateway C Kamer 101
+31(0)356772910 http://www.omroep.nl/
Sed quis custodiet ipsos custodes? : The sixth Satire from Juvenal
/*
This software is OSI Certified Open Source Software.
OSI Certified is a certification mark of the Open Source Initiative.
The license (Mozilla version 1.0) can be read at the MMBase site.
See http://www.MMBase.org/license
*/
package org.mmbase.module.database;
import java.sql.Connection;
import java.sql.SQLException;
import javax.sql.DataSource;
import javax.sql.PooledConnection;
import javax.sql.ConnectionPoolDataSource;
import javax.naming.InitialContext;
import javax.naming.Context;
import org.mmbase.module.*;
import org.mmbase.util.logging.*;
/**
* This class is used to retrieve a connection, which is provided by naming resources.
* With the usage of naming resource, it is possible to configure the database resource
* inside the application server and let the application server do the pooling. Since
* this is a J2EE concept, this class provides support for usage of this.
*
* @author Eduard
* @version $Id: Exp $
*/
public class Naming extends ProcessorModule implements JDBCInterface {
private static Logger log = Logging.getLoggerInstance(Naming.class.getName());
private static String PROPERTY_CONTEXT_NAME = "context";
private static String PROPERTY_DATASOURCE_NAME = "datasource";
private Object datasource = null;
/** our own multi-connection implementation.. arrgg....*/
private class NamingMultiConnection extends MultiConnection {
/** constructor to set the connection which has to be retrieved */
NamingMultiConnection(Connection con) {
super();
// this should take care of everything (we hope)
this.con = con;
state = CON_BUSY;
this.parent = null;
}
//public String getStateString()
//public void setLastSQL(String sql)
//public String getLastSQL()
//public Statement createStatement() throws SQLException
//public PreparedStatement prepareStatement(String sql) throws SQLException
//public CallableStatement prepareCall(String sql) throws SQLException
//public String nativeSQL(String query) throws SQLException
//public void setAutoCommit(boolean enableAutoCommit) throws SQLException
//public boolean getAutoCommit() throws SQLException
//public void commit() throws SQLException
//public void rollback() throws SQLException
/** override the close, since the MultiConnection want to tell the pool that it is closed */
public void close() throws SQLException {
con.close();
}
//public void realclose() throws SQLException
//public boolean isClosed() throws SQLException
//public DatabaseMetaData getMetaData() throws SQLException
//public void setReadOnly(boolean readOnly) throws SQLException
//public boolean isReadOnly() throws SQLException
//public void setCatalog(String catalog) throws SQLException
//public String getCatalog() throws SQLException
//public void setTransactionIsolation(int level) throws SQLException
//public int getTransactionIsolation() throws SQLException
//public SQLWarning getWarnings() throws SQLException
//public void clearWarnings() throws SQLException
//public boolean checkSQLError(Exception e)
/** claim what? */
public void claim() {
}
/** release what? */
public void release() {
}
/** the usage of what? */
public int getUsage() {
return 0;
}
/** the start time of what? */
public int getStartTime() {
return 0;
}
/** the start time of what? */
public long getStartTimeMillis() {
return 0;
}
//public String toString()
//public CallableStatement prepareCall(String sql, int i, int y) throws SQLException
//public void setTypeMap(Map mp) throws SQLException
//public Map getTypeMap() throws SQLException
//public Statement createStatement(int i,int y) throws SQLException
//public PreparedStatement prepareStatement(String sql,int i, int y) throws SQLException
// The 1.4 methods are also skipped..
}
/**
* Init this module. Will check if properties are available and try to get a datasource, to
* test if we can use it.
*/
public void init() {
String context = getInitParameter(PROPERTY_CONTEXT_NAME);
if(context == null) throw new RuntimeException("the property '"+PROPERTY_CONTEXT_NAME+"' was not set");
String source = getInitParameter(PROPERTY_DATASOURCE_NAME);
if(source == null) throw new RuntimeException("the property '"+PROPERTY_CONTEXT_NAME+"' was not set");
// do the naming stuff..
try {
Context initCtx = new InitialContext();
Context envCtx = (Context) initCtx.lookup(context);
datasource = envCtx.lookup(source);
if(datasource == null) {
String msg = "datasource was null for context:" + context + " with source:" + source;
log.error(msg);
throw new RuntimeException(msg);
}
if(datasource instanceof ConnectionPoolDataSource) {
ConnectionPoolDataSource ds = (ConnectionPoolDataSource)datasource;
log.info("Using the interface:" + ConnectionPoolDataSource.class.getName() + "(implemented by:" + ds.getClass().getName() + " to get new database connections(time out: " + ds.getLoginTimeout() + " seconds).");
}
else if(datasource instanceof DataSource) {
log.info("Using the interface:" + DataSource.class.getName() + "(implemented by:" + datasource.getClass().getName() + " to get new database connections.");
}
else {
String msg = "Dont know how to retrieve a connection from datasource:" + datasource.getClass().getName();
log.error(msg);
throw new RuntimeException(msg);
}
// try to get an connection, so we can see if it all works..
Connection con = getConnection();
if(con == null) {
String msg = "Test run of retrieving a test-run failed.";
log.error(msg);
throw new RuntimeException(msg);
}
// closing a connection is very important!
con.close();
}
catch(javax.naming.NamingException ne) {
String msg = "The following error occured while trying to initalise the datasource for context:'" + context + "' datasource:'" + datasource + "' :]\n" + Logging.stackTrace(ne);
log.error(msg);
throw new RuntimeException(msg);
}
catch(java.sql.SQLException se) {
String msg = "The following error occured while trying to retrieve a connection from the datasource for context:'" + context + "' datasource:'" + datasource + "' :]\n" + Logging.stackTrace(se);
log.error(msg);
throw new RuntimeException(msg);
}
}
public void reload() {
init();
}
/**
* retrieves an connection to the database, depending on the class which is used as datasource
* @return Connection A connection to the database
*/
private Connection getConnection() throws java.sql.SQLException {
if(datasource instanceof ConnectionPoolDataSource) {
ConnectionPoolDataSource ds = (ConnectionPoolDataSource) datasource;
PooledConnection pc = ds.getPooledConnection();
return pc.getConnection();
}
else if(datasource instanceof DataSource) {
DataSource ds = (DataSource) datasource;
return ds.getConnection();
}
else {
String msg = "Dont know how to retrieve a connection from datasource:" + datasource.getClass().getName();
log.error(msg);
throw new RuntimeException(msg);
}
}
public MultiConnection getConnection(String url, String name, String password) throws SQLException {
return new NamingMultiConnection(getConnection());
}
public MultiConnection getConnection(String url) throws SQLException {
return new NamingMultiConnection(getConnection());
}
public Connection getDirectConnection(String url) throws SQLException {
return getConnection();
}
public Connection getDirectConnection(String url,String name,String password) throws SQLException {
return getConnection();
}
// below all the things we dont use..
public void unload() {}
public void shutdown() {}
public String makeUrl(){return null;}
public String makeUrl(String dbm) {return null;}
public String makeUrl(String host,String dbm) {return null;}
public String makeUrl(String host,int port,String dbm) {return null;}
public String getUser() {return null;}
public String getPassword() {return null;}
public String getDatabaseName(){return null;}
public void checkTime(){}
}
<?xml version="1.0"?>
<!DOCTYPE data-sources PUBLIC "Orion data-sources" "http://www.orionserver.com/dtds/data-sources.dtd";>
<data-sources>
<!--
An example/default DataSource that uses an ordinary
JDBC-driver (in this case hsql) to create the connections.
This tag creates all the needed kinds
of data-sources, transactional, pooled and EJB-aware sources.
The source generally used in application code is the "EJB"
one - it provides transactional safety and connection pooling.
-->
<data-source
class="com.evermind.sql.DriverManagerDataSource"
name="Hypersonic"
location="jdbc/HypersonicCoreDS"
xa-location="jdbc/xa/HypersonicXADS"
ejb-location="jdbc/HypersonicDS"
connection-driver="org.hsql.jdbcDriver"
username="sa"
password=""
url="jdbc:HypersonicSQL:./database/defaultdb"
inactivity-timeout="30"
/>
<!--
The hsl doesnt work with MMBase, the reason for this is that
getBytes on a String field returns a'?'. This bug was created,
when the general-encoding setting was added to MMBase. A fix for
this would be to add an addition encoding option in the
config/database/datbasetype.xml
-->
<!--
<data-source
class="com.evermind.sql.DriverManagerDataSource"
name="Hypersonic"
location="jdbc/MMBase"
xa-location="jdbc/xa/HypersonicXADS"
ejb-location="jdbc/HypersonicDS"
connection-driver="org.hsql.jdbcDriver"
username="sa"
password=""
url="jdbc:HypersonicSQL:./database/mmbase"
inactivity-timeout="30"
/>
-->
<data-source
class="com.evermind.sql.DriverManagerDataSource"
name="Hypersonic"
location="jdbc/MMBase"
xa-location="jdbc/xa/HypersonicXADS"
ejb-location="jdbc/HypersonicDS"
connection-driver="org.postgresql.Driver"
username="mmbaseuser"
password="secret"
url="jdbc:postgresql://127.0.0.1:5432/mmbase"
inactivity-timeout="30"
/>
</data-sources>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE module PUBLIC "-//MMBase/ DTD module config 1.0//EN" "http://www.mmbase.org/dtd/module_1_0.dtd";>
<module maintainer="mmbase.org" version="0">
<status>active</status>
<classfile>org.mmbase.module.database.Naming</classfile>
<properties>
<property name="context">java:comp/env</property>
<property name="datasource">jdbc/MMBase</property>
</properties>
</module>
<!-- Example Server Configuration File -->
<!-- Note that component elements are nested corresponding to their
parent-child relationships with each other -->
<!-- A "Server" is a singleton element that represents the entire JVM,
which may contain one or more "Service" instances. The Server
listens for a shutdown command on the indicated port.
Note: A "Server" is not itself a "Container", so you may not
define subcomponents such as "Valves" or "Loggers" at this level.
-->
<Server port="8005" shutdown="SHUTDOWN" debug="0">
<!-- Uncomment these entries to enable JMX MBeans support -->
<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"
debug="0"/>
<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"
debug="0"/>
<!-- Global JNDI resources -->
<GlobalNamingResources>
<!-- Test entry for demonstration purposes -->
<Environment name="simpleValue" type="java.lang.Integer" value="30"/>
<!-- Editable user database that can also be used by
UserDatabaseRealm to authenticate users -->
<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved">
</Resource>
<ResourceParams name="UserDatabase">
<parameter>
<name>factory</name>
<value>org.apache.catalina.users.MemoryUserDatabaseFactory</value>
</parameter>
<parameter>
<name>pathname</name>
<value>conf/tomcat-users.xml</value>
</parameter>
</ResourceParams>
</GlobalNamingResources>
<!-- A "Service" is a collection of one or more "Connectors" that share
a single "Container" (and therefore the web applications visible
within that Container). Normally, that Container is an "Engine",
but this is not required.
Note: A "Service" is not itself a "Container", so you may not
define subcomponents such as "Valves" or "Loggers" at this level.
-->
<!-- Define the Tomcat Stand-Alone Service -->
<Service name="Tomcat-Standalone">
<!-- A "Connector" represents an endpoint by which requests are received
and responses are returned. Each Connector passes requests on to the
associated "Container" (normally an Engine) for processing.
By default, a non-SSL HTTP/1.1 Connector is established on port 8080.
You can also enable an SSL HTTP/1.1 Connector on port 8443 by
following the instructions below and uncommenting the second Connector
entry. SSL support requires the following steps (see the SSL Config
HOWTO in the Tomcat 4.0 documentation bundle for more detailed
instructions):
* Download and install JSSE 1.0.2 or later, and put the JAR files
into "$JAVA_HOME/jre/lib/ext".
* Execute:
%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
$JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix)
with a password value of "changeit" for both the certificate and
the keystore itself.
By default, DNS lookups are enabled when a web application calls
request.getRemoteHost(). This can have an adverse impact on
performance, so you can disable it by setting the
"enableLookups" attribute to "false". When DNS lookups are disabled,
request.getRemoteHost() will return the String version of the
IP address of the remote client.
-->
<!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -->
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8080" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" connectionTimeout="20000"
useURIValidationHack="false" />
<!-- Note : To disable connection timeouts, set connectionTimeout value
to -1 -->
<!-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -->
<!--
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8443" minProcessors="5" maxProcessors="75"
enableLookups="true"
acceptCount="10" debug="0" scheme="https" secure="true"
useURIValidationHack="false">
<Factory className="org.apache.coyote.tomcat4.CoyoteServerSocketFactory"
clientAuth="false" protocol="TLS" />
</Connector>
-->
<!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8009" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" connectionTimeout="20000"
useURIValidationHack="false"
protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>
<!-- Define an AJP 1.3 Connector on port 8009 -->
<!--
<Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
port="8009" minProcessors="5" maxProcessors="75"
acceptCount="10" debug="0"/>
-->
<!-- Define a Proxied HTTP/1.1 Connector on port 8082 -->
<!-- See proxy documentation for more information about using this. -->
<!--
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8082" minProcessors="5" maxProcessors="75"
enableLookups="true"
acceptCount="10" debug="0" connectionTimeout="20000"
proxyPort="80" useURIValidationHack="false" />
-->
<!-- Define a non-SSL legacy HTTP/1.1 Test Connector on port 8083 -->
<!--
<Connector className="org.apache.catalina.connector.http.HttpConnector"
port="8083" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" />
-->
<!-- Define a non-SSL HTTP/1.0 Test Connector on port 8084 -->
<!--
<Connector className="org.apache.catalina.connector.http10.HttpConnector"
port="8084" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" />
-->
<!-- An Engine represents the entry point (within Catalina) that processes
every request. The Engine implementation for Tomcat stand alone
analyzes the HTTP headers included with the request, and passes them
on to the appropriate Host (virtual host). -->
<!-- Define the top level container in our container hierarchy -->
<Engine name="Standalone" defaultHost="localhost" debug="0">
<!-- The request dumper valve dumps useful debugging information about
the request headers and cookies that were received, and the response
headers and cookies that were sent, for all requests received by
this instance of Tomcat. If you care only about requests to a
particular virtual host, or a particular application, nest this
element inside the corresponding <Host> or <Context> entry instead.
For a similar mechanism that is portable to all Servlet 2.3
containers, check out the "RequestDumperFilter" Filter in the
example application (the source for this filter may be found in
"$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").
Request dumping is disabled by default. Uncomment the following
element to enable it. -->
<!--
<Valve className="org.apache.catalina.valves.RequestDumperValve"/>
-->
<!-- Global logger unless overridden at lower levels -->
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="catalina_log." suffix=".txt"
timestamp="true"/>
<!-- Because this Realm is here, an instance will be shared globally -->
<!-- This Realm uses the UserDatabase configured in the global JNDI
resources under the key "UserDatabase". Any edits
that are performed against this UserDatabase are immediately
available for use by the Realm. -->
<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
debug="0" resourceName="UserDatabase"/>
<!-- Comment out the old realm but leave here for now in case we
need to go back quickly -->
<!--
<Realm className="org.apache.catalina.realm.MemoryRealm" />
-->
<!-- Replace the above Realm with one of the following to get a Realm
stored in a database and accessed via JDBC -->
<!--
<Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
driverName="org.gjt.mm.mysql.Driver"
connectionURL="jdbc:mysql://localhost/authority"
connectionName="test" connectionPassword="test"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />
-->
<!--
<Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
driverName="oracle.jdbc.driver.OracleDriver"
connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"
connectionName="scott" connectionPassword="tiger"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />
-->
<!--
<Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
driverName="sun.jdbc.odbc.JdbcOdbcDriver"
connectionURL="jdbc:odbc:CATALINA"
userTable="users" userNameCol="user_name" userCredCol="user_pass"
userRoleTable="user_roles" roleNameCol="role_name" />
-->
<!-- Define the default virtual host -->
<Host name="localhost" debug="0" appBase="webapps"
unpackWARs="true" autoDeploy="true">
<!-- Normally, users must authenticate themselves to each web app
individually. Uncomment the following entry if you would like
a user to be authenticated the first time they encounter a
resource protected by a security constraint, and then have that
user identity maintained across *all* web applications contained
in this virtual host. -->
<!--
<Valve className="org.apache.catalina.authenticator.SingleSignOn"
debug="0"/>
-->
<!-- Access log processes all requests for this virtual host. By
default, log files are created in the "logs" directory relative to
$CATALINA_HOME. If you wish, you can specify a different
directory with the "directory" attribute. Specify either a relative
(to $CATALINA_HOME) or absolute path to the desired directory.
-->
<!--
<Valve className="org.apache.catalina.valves.AccessLogValve"
directory="logs" prefix="localhost_access_log." suffix=".txt"
pattern="common" resolveHosts="false"/>
-->
<!-- Logger shared by all Contexts related to this virtual host. By
default (when using FileLogger), log files are created in the "logs"
directory relative to $CATALINA_HOME. If you wish, you can specify
a different directory with the "directory" attribute. Specify either a
relative (to $CATALINA_HOME) or absolute path to the desired
directory.-->
<Logger className="org.apache.catalina.logger.FileLogger"
directory="logs" prefix="localhost_log." suffix=".txt"
timestamp="true"/>
<!-- Define properties for each web application. This is only needed
if you want to set non-default properties, or have web application
document roots in places other than the virtual host's appBase
directory. -->
<!-- Tomcat Root Context -->
<!--
<Context path="" docBase="ROOT" debug="0"/>
-->
<Context
className="org.apache.catalina.core.StandardContext"
crossContext="false"
reloadable="true"
mapperClass="org.apache.catalina.core.StandardContextMapper"
useNaming="true"
debug="0"
swallowOutput="false"
privileged="false"
wrapperClass="org.apache.catalina.core.StandardWrapper"
docBase="/home/eduard/webapps"
cookies="true"
path="/mmbase"
cachingAllowed="true"
charsetMapperClass="org.apache.catalina.util.CharsetMapper"
>
<Logger
className="org.apache.catalina.logger.FileLogger"
debug="0"
verbosity="1"
prefix="mmbase_log."
directory="logs"
timestamp="true"
suffix=".txt"
/>
<!-- Define the resource for the jdbc connection of MMBase -->
<Resource name="jdbc/MMBase"
auth="Container"
type="javax.sql.DataSource"/>
<!-- MySQL resource -->
<!--
<ResourceParams name="jdbc/MMBase">
<parameter>
<name>factory</name>
<value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
</parameter>
<parameter>
<name>maxActive</name>
<value>100</value>
</parameter>
<parameter>
<name>maxIdle</name>
<value>30000</value>
</parameter>
<parameter>
<name>maxWait</name>
<value>100</value>
</parameter>
<parameter>
<name>username</name>
<value>mmbaseuser</value>
</parameter>
<parameter>
<name>password</name>
<value>secret</value>
</parameter>
<parameter>
<name>driverClassName</name>
<value>com.mysql.jdbc.Driver</value>
</parameter>
<parameter>
<name>url</name>
<value>jdbc:mysql://localhost:3306/mmbase</value>
</parameter>
</ResourceParams>
-->
<!-- PostgreSQL resource -->
<ResourceParams name="jdbc/MMBase">
<parameter>
<name>factory</name>
<value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
</parameter>
<parameter>
<name>driverClassName</name>
<value>org.postgresql.Driver</value>
</parameter>
<parameter>
<name>url</name>
<value>jdbc:postgresql://127.0.0.1:5432/mmbase</value>
</parameter>
<parameter>
<name>username</name>
<value>mmbaseuser</value>
</parameter>
<parameter>
<name>password</name>
<value>secret</value>
</parameter>
<parameter>
<name>maxActive</name>
<value>20</value>
</parameter>
<parameter>
<name>maxIdle</name>
<value>10</value>
</parameter>
<parameter>
<name>maxWait</name>
<value>-1</value>
</parameter>
</ResourceParams>
<!-- hsqldb resource -->
<!--
<ResourceParams name="jdbc/MMBase">
<parameter>
<name>validationQuery</name>
<value></value>
</parameter>
<parameter>
<name>maxWait</name>
<value>5000</value>
</parameter>
<parameter>
<name>maxActive</name>
<value>20</value>
</parameter>
<parameter>
<name>url</name>
<value>jdbc:hsqldb:../databases/mmbase</value>
</parameter>
<parameter>
<name>password</name>
<value></value>
</parameter>
<parameter>
<name>driverClassName</name>
<value>org.hsqldb.jdbcDriver</value>
</parameter>
<parameter>
<name>maxIdle</name>
<value>20</value>
</parameter>
<parameter>
<name>username</name>
<value>sa</value>
</parameter>
</ResourceParams>
-->
</Context>
<!-- Tomcat Examples Context -->
<Context path="/examples" docBase="examples" debug="0"
reloadable="true" crossContext="true">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="localhost_examples_log." suffix=".txt"
timestamp="true"/>
<Ejb name="ejb/EmplRecord" type="Entity"
home="com.wombat.empl.EmployeeRecordHome"
remote="com.wombat.empl.EmployeeRecord"/>
<!-- If you wanted the examples app to be able to edit the
user database, you would uncomment the following entry.
Of course, you would want to enable security on the
application as well, so this is not done by default!
The database object could be accessed like this:
Context initCtx = new InitialContext();
Context envCtx = (Context) initCtx.lookup("java:comp/env");
UserDatabase database =
(UserDatabase) envCtx.lookup("userDatabase");
-->
<!--
<ResourceLink name="userDatabase" global="UserDatabase"
type="org.apache.catalina.UserDatabase"/>
-->
<!-- PersistentManager: Uncomment the section below to test Persistent
Sessions.
saveOnRestart: If true, all active sessions will be saved
to the Store when Catalina is shutdown, regardless of
other settings. All Sessions found in the Store will be
loaded on startup. Sessions past their expiration are
ignored in both cases.
maxActiveSessions: If 0 or greater, having too many active
sessions will result in some being swapped out. minIdleSwap
limits this. -1 means unlimited sessions are allowed.
0 means sessions will almost always be swapped out after
use - this will be noticeably slow for your users.
minIdleSwap: Sessions must be idle for at least this long
(in seconds) before they will be swapped out due to
maxActiveSessions. This avoids thrashing when the site is
highly active. -1 or 0 means there is no minimum - sessions
can be swapped out at any time.
maxIdleSwap: Sessions will be swapped out if idle for this
long (in seconds). If minIdleSwap is higher, then it will
override this. This isn't exact: it is checked periodically.
-1 means sessions won't be swapped out for this reason,
although they may be swapped out for maxActiveSessions.
If set to >= 0, guarantees that all sessions found in the
Store will be loaded on startup.
maxIdleBackup: Sessions will be backed up (saved to the Store,
but left in active memory) if idle for this long (in seconds),
and all sessions found in the Store will be loaded on startup.
If set to -1 sessions will not be backed up, 0 means they
should be backed up shortly after being used.
To clear sessions from the Store, set maxActiveSessions, maxIdleSwap,
and minIdleBackup all to -1, saveOnRestart to false, then restart
Catalina.
-->
<!--
<Manager className="org.apache.catalina.session.PersistentManager"
debug="0"
saveOnRestart="true"
maxActiveSessions="-1"
minIdleSwap="-1"
maxIdleSwap="-1"
maxIdleBackup="-1">
<Store className="org.apache.catalina.session.FileStore"/>
</Manager>
-->
<Environment name="maxExemptions" type="java.lang.Integer"
value="15"/>
<Parameter name="context.param.name" value="context.param.value"
override="false"/>
<Resource name="jdbc/EmployeeAppDb" auth="SERVLET"
type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/EmployeeAppDb">
<parameter><name>username</name><value>sa</value></parameter>
<parameter><name>password</name><value></value></parameter>
<parameter><name>driverClassName</name>
<value>org.hsql.jdbcDriver</value></parameter>
<parameter><name>url</name>
<value>jdbc:HypersonicSQL:database</value></parameter>
</ResourceParams>
<Resource name="mail/Session" auth="Container"
type="javax.mail.Session"/>
<ResourceParams name="mail/Session">
<parameter>
<name>mail.smtp.host</name>
<value>localhost</value>
</parameter>
</ResourceParams>
<ResourceLink name="linkToGlobalResource"
global="simpleValue"
type="java.lang.Integer"/>
</Context>
</Host>
</Engine>
</Service>
<!-- The MOD_WEBAPP connector is used to connect Apache 1.3 with Tomcat 4.0
as its servlet container. Please read the README.txt file coming with
the WebApp Module distribution on how to build it.
(Or check out the "jakarta-tomcat-connectors/webapp" CVS repository)
To configure the Apache side, you must ensure that you have the
"ServerName" and "Port" directives defined in "httpd.conf". Then,
lines like these to the bottom of your "httpd.conf" file:
LoadModule webapp_module libexec/mod_webapp.so
WebAppConnection warpConnection warp localhost:8008
WebAppDeploy examples warpConnection /examples/
The next time you restart Apache (after restarting Tomcat, if needed)
the connection will be established, and all applications you make
visible via "WebAppDeploy" directives can be accessed through Apache.
-->
<!-- Define an Apache-Connector Service -->
<!--
<Service name="Tomcat-Apache">
<Connector className="org.apache.catalina.connector.warp.WarpConnector"
port="8008" minProcessors="5" maxProcessors="75"
enableLookups="true" appBase="webapps"
acceptCount="10" debug="0"/>
<Engine className="org.apache.catalina.connector.warp.WarpEngine"
name="Apache" debug="0">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="apache_log." suffix=".txt"
timestamp="true"/>
<Realm className="org.apache.catalina.realm.MemoryRealm" />
</Engine>
</Service>
-->
</Server>
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd";>
<web-app>
<servlet>
<servlet-name>version</servlet-name>
<description>To get the version of MMBase</description>
<servlet-class>org.mmbase.servlet.MMBaseServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet>
<servlet-name>images</servlet-name>
<description>To extract images from MMBase</description>
<servlet-class>org.mmbase.servlet.ImageServlet</servlet-class>
<init-param>
<!-- Expire time of original images. Cached images never expire. -->
<param-name>expire</param-name>
<!-- 10 minutes (default is one hour)-->
<param-value>600</param-value>
</init-param>
<load-on-startup>2</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>version</servlet-name>
<url-pattern>/version</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>images</servlet-name>
<url-pattern>/img.db</url-pattern>
</servlet-mapping>
<welcome-file-list>
<welcome-file>index.jsp</welcome-file>
<welcome-file>default.jsp</welcome-file>
<welcome-file>index.html</welcome-file>
</welcome-file-list>
<taglib>
<taglib-uri>http://www.mmbase.org/mmbase-taglib-1.0</taglib-uri>
<taglib-location>/WEB-INF/mmbase-taglib.tld</taglib-location>
</taglib>
<resource-ref>
<description>
MMBase Database
</description>
<res-ref-name>jdbc/MMBase</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</web-app>
