Announcement Announcement Module
Collapse
No announcement yet.
Multiple webapp instances crash OAS 9.0.4 Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Multiple webapp instances crash OAS 9.0.4

    Hi all,

    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.
    • the database connection string in spring-servlet.xml
    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 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

    Spyros

  • #2
    Must we provide spring related jars to OAS globally? We prefer to have each war self contained...
    Self contained WARs whould be OK.

    Comment


    • #3
      Acegi encache configuration causing OutOfMemory exception??

      The logs seem to reveal some relation with ehcache configuration... After deploying the n' th application I get n entries in the log with the same line:

      2005-10-12 10:05:19,655 WARN [net.sf.ehcache.config.Configurator] - <No configuration found. Configuring ehcache from ehcache-failsafe.xml found in the classpath: classloader:/ehcache-failsafe.xml> (this repeat n times...)

      At the seventh instance I get the following:

      05/10/12 10:05:38 Uncaught exception RMICallHandler java.lang.OutOfMemoryError - null

      I use the cache configuration identical to the one in the contacts sample application for all instances:

      <bean id="cacheManager" class="org.springframework.cache.ehcache.EhCacheMa nagerFactoryBean"/>

      <bean id="userCacheBackend" class="org.springframework.cache.ehcache.EhCacheFa ctoryBean">
      <property name="cacheManager">
      <ref local="cacheManager"/>
      </property>
      <property name="cacheName">
      <value>userCache</value>
      </property>
      </bean>

      <bean id="userCache" class="net.sf.acegisecurity.providers.dao.cache.Eh CacheBasedUserCache">
      <property name="cache"><ref local="userCacheBackend"/></property>
      </bean>

      Please share any thoughts on this one

      Comment

      Working...
      X