I'm not sure from the logs you provided. Looks like you may have had an
out of memory exception during the bootstrap process that rendered the
magnoliaAuthor instance unuseable. If that's the case, it will show in
the magnolia-debug.log from your first startup. Delete the repositories
directory in your magnoliaAuthor instance and restart tomcat to see if
it starts working correctly.
The bootstrap process is very resource intensive and requires a lot more
memory than the normal runtime magnolia does.
--David
Skip Strickland wrote:
This is real frustrating! The instructions below causes all kinds of errors. To clear
it up, I deleted the project, rebooted my workstation, then reinstalled from the
downloaded zip file "magnolia-3.0.2-bundle.zip".
Without making any changes at all:
I then ran a simple test...execute "C:\magnolia-3.0.2\tomcat\bin\startup.bat"
and accessed magnoliaPublic and magnoliaAuthor..Works fine.
I then ran "C:\magnolia-3.0.2\tomcat\bin\shutdown.bat"
I then ran again...execute "C:\magnolia-3.0.2\tomcat\bin\startup.bat"
and accessed magnoliaPublic (works fine) and magnoliaAuthor (doesn't work at all).
So...I deleted, rebooted, reloaded, reran, shutdown, and found the following in
the logs:
C:\magnolia-3.0.2\tomcat\webapps\magnoliaPublic\logs
INFO info.magnolia.cms.cache.BaseCacheManager 26.04.2007
14:51:25 -- CacheManager is now stopped.
INFO info.magnolia.cms.beans.config.ModuleLoader 26.04.2007
14:51:25 -- Shutting down module: adminInterface
INFO info.magnolia.jackrabbit.ProviderImpl 26.04.2007
14:51:25 -- Shutting down repository bound to 'magnoliaPublic'
WARN info.magnolia.jackrabbit.ProviderImpl 26.04.2007
14:51:26 -- Failed to shutdown repository magnoliaPublic:
java.lang.NullPointerException null
java.lang.NullPointerException
at
org.apache.lucene.store.FSDirectory.create(FSDirectory.java:149)
at
org.apache.lucene.store.FSDirectory.<init>(FSDirectory.java:128)
<more>
C:\magnolia-3.0.2\tomcat\webapps\magnoliaAuthor\logs
INFO info.magnolia.cms.beans.config.ModuleLoader 26.04.2007
14:51:21 -- Shutting down module: adminInterface
INFO info.magnolia.jackrabbit.ProviderImpl 26.04.2007
14:51:21 -- Shutting down repository bound to 'magnoliaAuthor'
WARN info.magnolia.jackrabbit.ProviderImpl 26.04.2007
14:51:22 -- Failed to shutdown repository magnoliaAuthor:
java.lang.NullPointerException null
java.lang.NullPointerException
at
org.apache.lucene.store.FSDirectory.create(FSDirectory.java:149)
at
org.apache.lucene.store.FSDirectory.<init>(FSDirectory.java:128)
<more>
I then re-ran the startup.bat...magnoliaPublic executes fine...magnoliaAuthor
still doesn't. Here are both logs after startup:
C:\magnolia-3.0.2\tomcat\webapps\magnoliaPublic\logs
INFO info.magnolia.cms.beans.config.ContentRepository
26.04.2007 15:14:15 -- System : loading JCR magnolia
INFO info.magnolia.jackrabbit.ProviderImpl 26.04.2007
15:14:15 -- Loading repository at
C:\magnolia-3.0.2\tomcat\webapps\magnoliaPublic\repositories\magnolia (config
file:
C:\magnolia-3.0.2\tomcat\webapps\magnoliaPublic\WEB-INF\config\repo-conf\jackrabbit-derby-search.xml)
ERROR org.apache.jackrabbit.core.RepositoryImpl 26.04.2007
15:14:20 -- Unable to initialize workspace 'Expressions'
javax.jcr.RepositoryException
at
org.apache.jackrabbit.core.SearchManager.initializeQueryHandler(SearchManager.java:531)
at
org.apache.jackrabbit.core.SearchManager.<init>(SearchManager.java:273)
<more errors>
C:\magnolia-3.0.2\tomcat\webapps\magnoliaAuthor\logs
INFO info.magnolia.cms.beans.config.ContentRepository
26.04.2007 15:14:04 -- System : loading JCR magnolia
INFO info.magnolia.jackrabbit.ProviderImpl 26.04.2007
15:14:04 -- Loading repository at
C:\magnolia-3.0.2\tomcat\webapps\magnoliaAuthor\repositories\magnolia (config
file:
C:\magnolia-3.0.2\tomcat\webapps\magnoliaAuthor\WEB-INF\config\repo-conf\jackrabbit-derby-search.xml)
ERROR org.apache.jackrabbit.core.RepositoryImpl 26.04.2007
15:14:08 -- Unable to initialize workspace 'users'
javax.jcr.RepositoryException
at
org.apache.jackrabbit.core.SearchManager.initializeQueryHandler(SearchManager.java:531)
at
org.apache.jackrabbit.core.SearchManager.<init>(SearchManager.java:273)
<more errors>
I still haven't attempted again to access DB2. Anyone know what's up? Using
Windows XP.
Skip
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 11:24 AM
To: [email protected]
Subject: Re: [magnolia-user] Magnolia DB2 Setup
3.0.2. Ok..
Setup should be relatively easy.
1. Find the version of repository config file in
WEB-INF/config/repo-config that best matches the db2 config and make a
copy named 'jackrabbit-db2-search.xml'. Modify as needed to match your
db2 setup.
2. modify WEB-INF/config/default/mangolia.properties updating the
property 'magnolia.repositories.jackrabbit.config' to point to your new
jackrabbit-db2-search.xml' file.
3. Clear out the repositories directory. The pre-bootstrapped
repository will get in the way and case all sorts of problems.
4. Make sure the db2 driver jar is in the WEB-INF/lib directory.
4. Start tomcat and watch the logs.
--David
Skip Strickland wrote:
Just downloaded this week: magnolia-3.0.2
I have it running as is on Windows XP, using the included server Tomcat 5.0,
and the built in database. I need it to run against DB2 like Jackrabbit does.
Any ideas?
Skip
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 10:53 AM
To: [email protected]
Subject: Re: [magnolia-user] Magnolia DB2 Setup
You've got the right forum. More info would help a lot -- like what
version of magnolia are you working with?
--David
Skip Strickland wrote:
Did I send this to the wrong forum?
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 25, 2007 2:54 PM
To: [email protected]
Subject: [magnolia-user] Magnolia DB2 Setup
I am attempting to configure Magnolia to use DB2 for data. In Jackrabbit, I modified the repository.xml file with my jdbc settings specifying db2.ddl, then deleted the localhost folders containing the repository indexes.
Does anyone know where I make the jdbc modification, and if other requirements
are needed to get magnolia to recognize the new configuration?
An example would also be greatly appreciated!
Thank you,
Skip Strickland, Analyst
Information Access Group
Costco WHOLESALE
(425) 313-2521
[EMAIL PROTECTED]
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
