Did you clean out the repositories folder in each magnolia webapp before
the next attempt? There's some stuff in there when an attempt is made
that needs to be cleaned out if the attempt fails.
--David
Thomas Duffey wrote:
>
>
> On Aug 20, 2009, at 7:41 AM, Grégory Joseph wrote:
>
>> So you configure a DS for each webapp (assuming using the same name,
>> for practical reasons, so you have identical webapps), correct ?
>> Now, it looks like both DS are connecting to the same database; that
>> just can't work.
>> Is that the case ?
>
> Tried a few different setups, including one with a DS for each webapp,
> named differently (jdbc/magnolia-public and jdbc/magnolia-author)
> connecting to different databases.
>
> Tom
>
>> On Aug 20, 2009, at 5:04 AM, Thomas Duffey wrote:
>>
>>>
>>> Hi All,
>>>
>>> This could probably go to several different lists but I'll start
>>> here...
>>>
>>> I am trying to run Magnolia 4.1 w/Tomcat 6 and a PostgreSQL database
>>> using Jackrabbit's PostgreSQL bundle DB persistence manager. Both
>>> the author and public instances of Magnolia are running inside the
>>> same instance of Tomcat. If I configure both author and public to
>>> use the JNDI data source and fire up Magnolia all the tables get
>>> created but the startup process hangs here:
>>>
>>> 2009-08-19 20:33:54,758 INFO
>>> info.magnolia.jackrabbit.ProviderImpl : Custom node
>>> types registered using /mgnl-nodetypes/magnolia-forum-nodetypes.xml
>>> 2009-08-19 20:33:54,771 INFO
>>> info.magnolia.jackrabbit.ProviderImpl : Registering
>>> nodetype {http://www.magnolia.info/jcr/mgnl}messageProperties
>>> 2009-08-19 20:33:54,790 INFO
>>> info.magnolia.jackrabbit.ProviderImpl : Registering
>>> nodetype {http://www.magnolia.info/jcr/mgnl}message
>>> 2009-08-19 20:33:54,875 INFO
>>> info.magnolia.jackrabbit.ProviderImpl : Registering
>>> nodetype {http://www.magnolia.info/jcr/mgnl}thread
>>> 2009-08-19 20:33:54,926 INFO
>>> info.magnolia.jackrabbit.ProviderImpl : Registering
>>> nodetype {http://www.magnolia.info/jcr/mgnl}forum
>>> 2009-08-19 20:33:54,959 INFO
>>> info.magnolia.cms.beans.config.ContentRepository : Loading
>>> workspace forum
>>> 2009-08-19 20:33:55,337 INFO
>>> info.magnolia.jackrabbit.ProviderImpl : Custom node
>>> types registered using
>>> /mgnl-nodetypes/magnolia-module-data-nodetypes.xml
>>> 2009-08-19 20:33:55,340 INFO
>>> info.magnolia.jackrabbit.ProviderImpl : Registering
>>> nodetype {}dataBase2009-08-19 20:33:55,359 INFO
>>> info.magnolia.jackrabbit.ProviderImpl : Registering
>>> nodetype {}dataItemBase2009-08-19 20:33:55,370 INFO
>>> info.magnolia.jackrabbit.ProviderImpl : Registering
>>> nodetype {}dataFolder
>>> 2009-08-19 20:33:55,385 INFO
>>> info.magnolia.jackrabbit.ProviderImpl : Registering
>>> nodetype {}dataItem
>>> 2009-08-19 20:33:55,401 INFO
>>> info.magnolia.jackrabbit.ProviderImpl : Registering
>>> nodetype {}dataItemNode
>>> 2009-08-19 20:33:55,412 INFO
>>> info.magnolia.cms.beans.config.ContentRepository : Loading
>>> workspace data
>>>
>>> Eventually I get an error about the pool timing out trying to get an
>>> idle connection. Funny, because if I look at the PostgreSQL server
>>> there are a bunch of active connections, all idle. Tried various
>>> settings on the JNDI data source but nothing made any difference.
>>>
>>> The weird thing is that if I only setup one instance of Magnolia to
>>> use the JNDI data source (The public side, for example) then
>>> everything works fine. This is what I'm doing now -- public is
>>> using the JNDI pooled connection and author is using a non-pooled,
>>> non-JNDI connection. Works fine but I'd really like to figure out
>>> what is going on here and also have both the author and public side
>>> use the pool. Has anyone seen this or know what is going on?
>>>
>>> Tom
>>>
>>>
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
