The error messages you highlighted are actually from Tomcat ... the clue from Magnolia is probably the last message above that - startup of the fliter chain. Can you temporarily remove magnoliaAuthor from the webapps and try to start out with just public instance? Most of the time I've seen something like that on the default bundle was when people started it up without proper memory and other settings (always use bin/magnolia_control.sh(bat) to start the instance) or when there were not enough file handles configured on the system to satisfy derby needs.
HTH, Jan On May 11, 2011, at 7:49 PM, Vinny wrote: > > Hello All, > I was trying out the latest community edition of Magnolia bundled with Tomcat. > As I was working through the templating tutorial something must have > happened to my > magnoliaPublic context. I started getting a 500 errors when I tried to > activate my changes to the public context: > > Caused by: info.magnolia.cms.exchange.ExchangeException: 1 error detected: > Not able to send the activation request > [http://localhost:8080/magnoliaPublic/.magnolia/activation]: Server > returned HTTP response code: 500 for URL: > http://localhost:8080/magnoliaPublic/.magnolia/activation on > magnoliaPublic8080 > at > info.magnolia.module.exchangesimple.SimpleSyndicator.activate(SimpleSyndicator.java:107) > at > info.magnolia.module.exchangesimple.BaseSyndicatorImpl.activate(BaseSyndicatorImpl.java:305) > > > looking a little deeper into the tomcat logs I noticed that this has > been happening: > > 2011-05-11 11:09:29,160 INFO > info.magnolia.cms.beans.config.ConfigLoader : Configuration > loaded (took 3 seconds) > 2011-05-11 11:09:29,171 WARN info.magnolia.cms.filters.MgnlMainFilter > : No filters configured at /server/filters > 2011-05-11 11:09:29,172 INFO info.magnolia.cms.filters.MgnlMainFilter > : Initializing filters > May 11, 2011 11:09:29 AM org.apache.catalina.core.StandardContext start > > SEVERE: Error filterStart <------------ My troubles begin > > May 11, 2011 11:09:29 AM org.apache.catalina.core.StandardContext start > > SEVERE: Context [/magnoliaPublic] startup failed due to previous > errors <------------- startup fails > > > 2011-05-11 11:09:29,174 INFO info.magnolia.module.ModuleManagerImpl > : Stopping module samples > 2011-05-11 11:09:29,174 INFO > info.magnolia.module.samples.SamplesModule : Samples module is > stopping > 2011-05-11 11:09:29,174 INFO info.magnolia.module.ModuleManagerImpl > : Stopping module mail > 2011-05-11 11:09:29,174 INFO info.magnolia.module.ModuleManagerImpl > : Stopping module cache > 2011-05-11 11:09:29,180 INFO info.magnolia.module.ModuleManagerImpl > : Stopping module adminInterface > 2011-05-11 11:09:29,180 INFO info.magnolia.module.ModuleManagerImpl > : Stopping module templating > 2011-05-11 11:09:29,180 INFO info.magnolia.module.ModuleManagerImpl > : Stopping module core > 2011-05-11 11:09:29,181 INFO > info.magnolia.cms.beans.config.ContentRepository : Shutting down JCR > 2011-05-11 11:09:29,181 INFO info.magnolia.jackrabbit.ProviderImpl > : Shutting down repository bound to 'magnoliaPublic' > 2011-05-11 11:09:29,440 WARN > info.magnolia.context.AbstractRepositoryStrategy : session has been > already closed config > Shutting down Log4J > > > Is there anyway to find out more about the filter error that is > causing magnoliaPublic not too start ? > Has anyone seen this error before? > > Thanks! > > > > -- > biz: http://www.linkedin.com/in/vincentstoessel/ > personal: http://xaymaca.tumblr.com/ > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
