Why do you use Derby? AFAIK Derby is not recommended to be used in a
productive environment. Furthermore there have existed some general
memory problems with Magnolia, which hopefully seems to be fixed with
the latest release 3.5.7.
Regards, Sebastian
Zdenko P. wrote:
Hi,
we migrated from BerkleyDB to Derby in last weeks. Since the migration
we have a serious memory problem. The server is frequently going
down.
With BDB we had never such problems. On this server are two
applications in addition to the magnolia author and public instance.
We migrated from Magnolia 3.0.5 (BDB) to 3.5 (Derby). Also we tried
Magnolia 3.0.5 with Derby. But the problems are the same.
So, we think it's a Derby Problem.
Have anybody same problems? Need Magnolia with Derby significantly
much more memory as BerkleyDB?
Or are you really using Magnolia public and author instance on one
server alone with no other applications?
Best regards,
Zdenko
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
