Dear Magnolians
Please excuse my ignorance, but I just now discovered something odd in the logs when starting up a Tomcat with an author and a public Magnolia instance which have different JAAS config files. The public instance starts up first (everything o.k.) followed by the author instance. And here is where things get interesting:
2012-02-03 12:45:15,471 INFO fo.magnolia.cms.beans.config.PropertiesInitializer: Loading configuration at /path/to/tomcat/webapps/magnoliaAuthor/WEB-INF/config/default/magnolia.properties
Initializing Log4J
Initializing Log4J from [WEB-INF/config/default/log4j.xml]
2012-02-03 12:45:15,506 INFO info.magnolia.cms.beans.config.ConfigLoader : JAAS config file set by parent container or some other application
2012-02-03 12:45:15,513 INFO info.magnolia.cms.beans.config.ConfigLoader : Config in use /path/to/tomcat/webapps/magnoliaPublic/WEB-INF/config/jaas.config
2012-02-03 12:45:15,514 INFO info.magnolia.cms.beans.config.ConfigLoader : Please make sure JAAS config has all necessary modules (refer config/jaas.config) configured
So am I doing something wrong or does the first webapp with a JAAS configuration set the config for all following webapps (which would suck big time)?
Thanks for shedding some light on this!
-will
----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <user-list-unsubscribe <at> magnolia-cms.com>
----------------------------------------------------------------