cocoon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sylv...@apache.org
Subject cvs commit: xml-cocoon2/xdocs faq.xml
Date Thu, 19 Jul 2001 09:46:33 GMT
sylvain     01/07/19 02:46:33

  Modified:    xdocs    Tag: cocoon_20_branch faq.xml
  Log:
  Added FAQs for SQL samples
  
  Revision  Changes    Path
  No                   revision
  
  
  No                   revision
  
  
  1.1.1.1.2.6 +41 -0     xml-cocoon2/xdocs/faq.xml
  
  Index: faq.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/xdocs/faq.xml,v
  retrieving revision 1.1.1.1.2.5
  retrieving revision 1.1.1.1.2.6
  diff -u -r1.1.1.1.2.5 -r1.1.1.1.2.6
  --- faq.xml	2001/07/18 14:23:22	1.1.1.1.2.5
  +++ faq.xml	2001/07/19 09:46:33	1.1.1.1.2.6
  @@ -284,4 +284,45 @@
        contributing it back to the group?</p>
    </answer>
   </faq>
  +<faq>
  + <question>
  +   The sql samples don't run.
  + </question>
  + <answer>
  +   <p>
  +     The sql samples are working when deploing the war file using the build system:
  +       <code>
  +./build.sh \
  +   -Dinclude.webapp.libs=yes \
  +   -Dinstall.war=path/to/tomcat/webapps install
  +       </code>
  +     This command will take care of the path inside the configuration file to the database
resources.
  +   </p>
  + </answer>
  +</faq>
  +<faq>
  + <question>
  +   I've been able to run the database samples, but they don't run anymore.
  + </question>
  + <answer>
  +   <p>
  +    This happens when the servlet engine has been stopped abruptly (e.g. with ctrl-C).
  +   </p>
  +   <p>
  +    Hsqldb - the database used by C2 samples - is a single-process engine that
  +    locks the database by setting the "modified" entry in
  +    "WEB-INF/db/cocoondb.properties" to the value "yes" while some JDBC
  +    connections exist. 
  +   </p>
  +   <p>
  +    With connection pooling, there's always some connections opened, and they're
  +    not closed properly when you stop abruptly the servlet engine, so the database
  +    stays in locked state and connections are refused at the next server startup.
  +   </p>
  +   <p>
  +    To unlock the database, change manually "modified" to "no" in the "cocoondb.properties"
  +    before restarting the server.
  +   </p>
  + </answer>
  +</faq>
   </faqs>
  
  
  

----------------------------------------------------------------------
In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          cocoon-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-cvs-help@xml.apache.org


Mime
View raw message