I changed the memory pool settings and tried to bootstrap Magnolia 2.1 again. This time, I changed the memory settings to "-Xms512m -Xmx764m".
JBoss went up without a hitch in 25 seconds, but the /magnoliaAuthor URI still gives the dreaded 403 error. Here are the relevent log messages from the JBoss log: ----- 2005-10-06 10:44:49,668 INFO [STDOUT] Initializing Log4J 2005-10-06 10:44:49,678 INFO [STDOUT] Setting the magnolia root system property: [magnolia.author.root] to [C:\Program Files\jboss-4.0.2\server\default\.\deploy\magnoliaAuthor.war\] 2005-10-06 10:44:49,678 INFO [STDOUT] Initializing Log4J from [WEB-INF/config/log4j.xml] 2005-10-06 10:44:49,758 INFO [STDOUT] INFO info.magnolia.cms.beans.config.ConfigLoader ConfigLoader.java(<init>:66) 06.10.2005 10:44:49 Assuming paths relative to C:\Program Files\jboss-4.0.2\server\default\.\deploy\magnoliaAuthor.war 2005-10-06 10:44:49,848 INFO [STDOUT] --------------------------------------------- 2005-10-06 10:44:49,848 INFO [STDOUT] MAGNOLIA LICENSE 2005-10-06 10:44:49,848 INFO [STDOUT] --------------------------------------------- 2005-10-06 10:44:49,858 INFO [STDOUT] Version number : 2.1 2005-10-06 10:44:49,858 INFO [STDOUT] Build : 1454 September 5. 2005 2005-10-06 10:44:49,858 INFO [STDOUT] Provider : obinary ltd ([EMAIL PROTECTED]) 2005-10-06 10:44:49,858 INFO [STDOUT] INFO info.magnolia.cms.beans.config.ConfigLoader ConfigLoader.java(load:102) 06.10.2005 10:44:49 Init content repositories 2005-10-06 10:44:49,868 INFO [STDOUT] INFO info.magnolia.cms.beans.config.ContentRepository ContentRepository.java(init:171) 06.10.2005 10:44:49 System : loading JCR 2005-10-06 10:44:49,878 INFO [STDOUT] ERROR info.magnolia.cms.beans.config.ContentRepository ContentRepository.java(init:179) 06.10.2005 10:44:49 C:\Program%20Files\jboss-4.0.2\server\default\.\deploy\magnoliaAuthor.war\WEB-INF\config\repositories.xml java.io.FileNotFoundException: C:\Program%20Files\jboss-4.0.2\server\default\.\deploy\magnoliaAuthor.war\WEB-INF\config\repositories.xml ------- I think this problem can be resolved in one of 2 ways: 1) JBoss needs config work to report the right root directory (without the /./) 2) Magnolia has to do a sanity check on the application root, then correct it. Well, that's the time I had today for this. Hope you can make something out of this! François-Léonard Gilbert ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
