Try to start eXist during application startup by declaring the
DatabaseAdminServlet in web.xml and starting in before Cocoon servlet, e.g.:
<servlet>
<servlet-name>DatabaseAdminServlet</servlet-name>
<servlet-class>org.exist.http.servlets.DatabaseAdminServlet</servlet-cla
ss>
<init-param>
<param-name>configuration</param-name>
<param-value>conf.xml</param-value>
</init-param>
<init-param>
<param-name>basedir</param-name>
<param-value>WEB-INF/</param-value>
</init-param>
<init-param>
<param-name>start</param-name>
<param-value>true</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet>
<servlet-name>Cocoon</servlet-name>
<display-name>Cocoon</display-name>
<description>Cocoon</description>
<servlet-class>org.apache.cocoon.servlet.CocoonServlet</servlet-class>
.....
<load-on-startup>2</load-on-startup>
</servlet>
HTH, Kai
[EMAIL PROTECTED] <> wrote:
> Hi all,
>
> My application uses cocoon 2.2 and an embedded eXist
> database. The eXist part runs well on my developpement
> environement (XP, jetty) but I run into problems
> deploying it on my production server (Linux, tomcat
> 5.5.9).
> After (re)starting the webapp, I connect to my base
> URL and get the "Local Database Server is not running"
> message. At that point, eXists seem to have started
> correctly (exist.log) and no error besides the
> "Database not running" can be found in cocoon.log or
> tomcat log.
>
> I manage to start it eventually doing the following:
> - delete the lock file dbx_dir.lck on the database
> - delete the lock file WEB-INF/data/journal.lck
> - access directly the exist servlet in the URL:
> http://domain.com/mywebapp/servlet/db/../resource.xml
>
> After doing that, I can access my cocoon URL with no
> problem. But this is off course not a viable solution
> for a production environement.
>
> My prod environement is running on a shared Linux
> account so I do not have control over the tomcat part.
>
> Any idea where this problem could come from ?
> One big difference between dev and prod is of course
> Linux permissions. I installed my app using my user
> account but the web server is running as
> tomcat:nobody. So I guess tomcat:nobody needs
> permissions to some directories. I for now (to get
> started until I find a better solution) gave full
> permission (777) to the database and logs directories.
>
> Any help appreciated.
> Jerome
>
>
>
>
> Jerome Benezech
> [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
