Hi Marc,
I've run into similar symptoms with eXist and Cocoon 2.1, usually when upgrading the eXist version (no logs or messages - just db not running). One time for me it was a jar compatibility problem where rolling back log4j-1.2.15.jar to log4j-1.2.14.jar in the eXist build fixed it. I think eXist also needs the correct serializer/xerces so Cocoon may need to be rebuilt with that. Other times I have not been able to figure it out. I wish I knew more about jar compatibility because it's tedious trial and error. When you find your solution please post. Thanks, gary _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Marc Salvetti Sent: Friday, March 14, 2008 8:02 AM To: [EMAIL PROTECTED] Subject: [Exist-open] Startup problem with cocoon 2.2 and embedded Exist1.1.1 Hello, I have a strange problem on a test server that was running fine for about 2 weeks with a cocoon 2.2 and exist 1.1.1 With no apparent change in the config, the db server suddenly stopped working. I guess the problem must have happened after a restart of tomcat but I have no way to be sure about this. I have no apparent error in either the tomcat, cocoon or exist logs, I can see the line of exist initialization in catalina.out, I can see from the logs that it is finding the conf.xml and the log config file with no apparent problem. The only way to see there is a problem is to try to access the database, which result in the error org.xmldb.api.base.XMLDBException: Local database server is not running I tried to read the data files from my local cocoon / exist installation and it's initializing fine, so the data is not corrupted. I'm really running out of ideas here, so I would really appreciate and hint on how to find the source of the problem. Marc
