A follow-up for the archives -- after sitting idle for 18 hours,
magnolia is still working with the mysql backend. ?autoReconnect=true
tacked on to the end of the connection url definitely fixed the problem
of db connections going stale.
I've also written a wiki page taylored to getting 2.1.5 working with
mysql if anyone would like to refine it a bit.
http://www.magnolia.info/wiki/Wiki.jsp?page=UsingMysqlWithMagnolia2.1.5
--David
Richard Zeng wrote:
Hi David,
It just works perfect! Thank you very much for your help. I don't need
to worry about the memory used by Magnolia any more.
Cheers,
Richard
([EMAIL PROTECTED])
On 8/30/06, David Smith <[email protected]> wrote:
Hi.
I did restart tomcat after the initial bootstrap and all came back
normally.
Let me clarify the last part a little. I duplicated
jackrabbit-mysql-[no]search.xml for each repository for a total of eight
files to the effect of jackrabbit-mysql-website-search.xml,
jackrabbit-mysql-website-nosearch.xml,
jackrabbit-mysql-config-search.xml, etc., ...
In each, I changed the schemaObjectPrefix attribute of the
PersistenceManager element to prevent table collisions between
repositories. In the case of website, it became "web_${wsp.name}_" for
the workspace persistence manager and "web_version_" for the versioning
persistence manager.
The end result is there approximately 32 tables in the database -- 8 for
each repository (website, config, users, userroles).
I suppose if you left the derby database for versioning, there would be
only 16 tables in the database.
--David
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
