On 15.04.2010 14:57, Matteo Pelucco wrote:
On 15.04.2010 12:20, Jan Haderka wrote:
XJ040/40000 - is the derby "failed to start up" error.
... since I could not find the follow up code (reason why it failed) in
the stack trace I can only speculate:
- either derby is already started by some other process in the same
jvm/classloader hierarchy
Maybe. I'll check.
...
unrelated, but double check there are not multiple versions of derby jar
in your classpath anywhere.
It can be, I'll check.
I've found a derby.jar in GlassFish installation.
I think it is used by GlassFish admin panel to store datas and it is
present in a standard GF 3 Prelude bundle.
I've tried to delete (backup) the previous repository and start Magnolia
with a fresh new one (empty).
* Everything works fine *
Almost sure a wrong derby version was the cause..
- Magnolia: 10.3.1.4
- GlassFish: read from DBMS.properties >>
derby.product.external.version=10.2
In this case, it is possible to check if GlassFish will release a future
version with an updated Derby release or simply remove the derby.x.jar
from Magnolia WEB-INF/lib
Matteo
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
