we need to provide the same application to 5 different set of users, where each user group will connect to its own database schema. Since we could not find a way to redirect users to the correct instance after logging in (acegi - dao authentication provider) we create 5 identical wars with sole differences
- the web app.Root property in web.xml for log4j.
We use acegi for authentication - authorization and the jdbc support classes for db access. All spring etc. classes are copied to each war in the "lib" directory. Log4j output is enabled for the console only.
- the database connection string in spring-servlet.xml
The problem is that when deploying on OAS 9.0.4 on the client side the server crashes during deploying the third or fourth instance... The warnings we get for each war are related to the log4j and encache (which is used only by acegi):
05/10/07 12:22:24 log4j:WARN File option not set for appender [logfile].
05/10/07 12:22:24 log4j:WARN Are you using FileAppender instead of ConsoleAppender?
2005-10-07 12:22:26,311 WARN
05/10/07 12:22:26 log4j:ERROR No output stream or file set for the appender named [logfile].
2005-10-07 12:22:28,061 WARN
2005-10-07 12:22:28,238 WARN [net.sf.ehcache.config.Configurator] - <No configuration found. Configuring ehcache from ehcache-failsafe.xml
found in the classpath: classloader:/ehcache-failsafe.xml>
Should we provide ehcache with configuration information? Is this the problem?
Must we provide spring related jars to OAS globally? We prefer to have each war self contained...
Or am I missing something else here?
Thanks in advance