RE: Dreaded: Sitemap handler's sitemap is not available
Hi Ted., 1. By restart, I mean, tomcat. Since cocoon is webapp which lives inside a servlet engine, there is no restart for cocoon by itself.. 2. The sitemap is recompiled at the startup automatically unless you use something like pre-compile stuff(forget it for now).. 3. Earlier, you or someone mentioned about FAQ..but again IMHO, the sitemap could have compile problems 'coz of zillion thingies...so there is no one particular stuff to blame... 4. You may have posted the log before..sorry if i missed it...if ur problem persists, please send ME zip log and i shall have look at it.. Cheers --- Ted Mead [EMAIL PROTECTED] wrote: Srini, Thanks for your thoughts. May I ask some clarifying questions? Regarding Sitemap... is there instructions on how to compile Sitemap on C2 startup? I am not sure I know what do do here? This could be the watershed event. When you say restart the server... I assume you mean Tomcat or Cocoon? If you mean Cocoon, how do you do that? Incidently, I sent log excerpts doing exactly what you said. Did they not have useful information? Thanks! Ted -Original Message- From: java guru [mailto:[EMAIL PROTECTED]] Sent: Sunday, August 19, 2001 5:20 PM To: [EMAIL PROTECTED] Subject: Re: Dreaded: Sitemap handler's sitemap is not available Hi., I hate to say search the mail archive but here is simple explanation... 1. Sitemap is one BIG java program to be compiled on c2 startup... 2. Any problem resulting from sitemap compilation could result in sitemap being NOT compiled and hence component for hint: sitemap not found.. 3. Now the reasons could range to anything and everything.. 4. Please note that JDBC problem reported is little mis-leading as this does NOT pose any threat to sitemap compilation and hence can be ignored for now.. 5. Please delete the c2 log, restart the server, try to access the main page ONLY once...stop the server...read the log from BOTTOM UP... 6. 95% of the time, you get the clue..but if still same..then zip the log and post it here... 7. As i hate to suggest, but you may want to search mailing list archive.. good luck = Thanks and have great day srini Do You Yahoo!? For regular News updates go to http://in.news.yahoo.com - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] = Thanks and have great day srini Do You Yahoo!? Send a newsletter, share photos files, conduct polls, organize chat events. Visit http://in/ groups.yahoo.com - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dreaded: Sitemap handler's sitemap is not available
Hi., I hate to say search the mail archive but here is simple explanation... 1. Sitemap is one BIG java program to be compiled on c2 startup... 2. Any problem resulting from sitemap compilation could result in sitemap being NOT compiled and hence component for hint: sitemap not found.. 3. Now the reasons could range to anything and everything.. 4. Please note that JDBC problem reported is little mis-leading as this does NOT pose any threat to sitemap compilation and hence can be ignored for now.. 5. Please delete the c2 log, restart the server, try to access the main page ONLY once...stop the server...read the log from BOTTOM UP... 6. 95% of the time, you get the clue..but if still same..then zip the log and post it here... 7. As i hate to suggest, but you may want to search mailing list archive.. good luck = Thanks and have great day srini Do You Yahoo!? For regular News updates go to http://in.news.yahoo.com - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dreaded: Sitemap handler's sitemap is not available
Dear Ted and all the rest,
This is exactly what happened to me when I tried to install Cocoon2 b2.
In my case, I have already installed Cocoon2 b1 without a problem, and it
happened when I tried to move to beta 2 maintaining exactly the same
configuration (Windows2K, Tomcat 3.2.3, Sun JDK 1.3.1).
This problem is appearing cyclically in this list. Some esoteric answers has
been given, but no a scientific and definitively one (even if it were the fruit
of our ignorance). In that case, that precious answer should be entered into the
Install and the FAQ's documentation.
Thank you very much in advance to those of you able to shed some light to this
recurrent question.
Pedro Pastor.
Ted Mead wrote:
Folks,
I am running the following:
RedHat 7.0
Tomcat 3.2.3
Cocoon 2b1
JDK 1.3
I have installed, reinstall, read
http://xml.apache.org/cocoon2/install.html, read the README, INSTALL, FAQ,
searched the mailing list archives until I could not find any further
reference and still get the following error when going to:
http://localhost:8080/cocoon:
type internal-server-error
message The sitemap handler's sitemap is not available. Please check
/home/tomcat/webapps/cocoon/WEB-INF/logs/cocoon.log for the exact error.
description org.apache.cocoon.ProcessingException: The sitemap handler's
sitemap is not available. Please check
/home/tomcat/webapps/cocoon/WEB-INF/logs/cocoon.log for the exact error.
sender org.apache.cocoon.servlet.CocoonServlet
source Cocoon servlet
request-uri
/cocoon/
exception
org.apache.cocoon.ProcessingException: The sitemap handler's sitemap is not
available. Please check /home/tomcat/webapps/cocoon/WEB-INF/logs/cocoon.log
for the exact error.
$TOMCAT_HOME/lib
I have also done the following to my $TOMCAT_HOME/lib directory:
deleted jaxp.jar
renamed parser.jar to zparser.jar
copied /home/cocoon/xerces_1_4_1.jar to $TOMCAT_HOME/lib
in this directory, I now have:
ant.jar, jasper.jar, servlet.jar, webserver.jar, xerces_1_4_1.jar,
zparser.jar
COCOON LOG FILE
===
I read some things about adding a classpath-attribute to the web.xml file in
/home/tomcat/webapps/cocoon/WEB-INF for Tomcat. I tried this and to no
avail. I now have it restored to the original. Here are some excerpts from
my cocoon.log file. I basically summarized what I thought was important.
First I stopped Tomcat and cleared the log. I then started Tomcat and made
some notes. Then I accessed /cocoon and recorded the observations.
STOPPED and STARTED TOMCAT
MESSAGES RIGHT AFTER STARTING TOMCAT
CLASSPATH:
java.class.path=:/home/storesense/system/java
/StoreSenseO.jar:/home/storesense/system/java/StoreSenseExt.jar:/home/stores
ense
/system/java/support/xml.jar:/home/storesense/system/java/support/mysql.jar:
/hom
e/storesense/system/java/support/activation.jar:/home/storesense/system/java
/sup
port/mail.jar:/home/storesense/system/java/support/pop3.jar:/home/storesense
/sys
tem/java/support/cdkjava3210.jar:/home/storesense/system/java/support/jnet.j
ar:/
home/storesense/system/java/support/jcert.jar:/home/storesense/system/java/s
uppo
rt/jsse.jar:/home/storesense/system/java/support/oroinc.jar:/home/storesense
/sys
tem/java/support/Signio.jar:/home/storesense/system/java/support/jce1_2_1.ja
r:/h
ome/storesense/system/java/support/sunjce_provider.jar:/home/storesense/syst
em/j
ava/support/local_policy.jar:/home/storesense/system/java/support/US_export_
poli
cy.jar:/home/storesense/system/java/support/sax2.jar:/home/tomcat/lib/ant.ja
r:/h
ome/tomcat/lib/backups:/home/tomcat/lib/jasper.jar:/home/tomcat/lib/servlet.
jar:
/home/tomcat/lib/test:/home/tomcat/lib/webserver.jar:/home/tomcat/lib/xerces
_1_4
_1.jar:/home/tomcat/lib/zparser.jar:/home/jdk/lib/tools.jar
DATABASE ISSUES:
DEBUG 2247[cocoon ] (Thread-6):
org.apache.avalon.excalibur.datasource.Jd
bcConnection: could not be instantiated.
java.sql.SQLException: File input/output error:
${install.war}/cocoon/WEB-INF/db
/cocoondb.properties
at java.lang.Throwable.init(Throwable.java:96)
at java.lang.Exception.init(Exception.java:44)
at java.sql.SQLException.init(SQLException.java:66)
at org.hsqldb.Trace.getError(Trace.java:180)
at org.hsqldb.Trace.getError(Trace.java:144)
at org.hsqldb.Trace.error(Trace.java:205)
at org.hsqldb.Log.saveProperties(Log.java:621)
at org.hsqldb.Log.create(Log.java:512)
at org.hsqldb.Log.open(Log.java:159)
at org.hsqldb.Database.init(Database.java:96)
at org.hsqldb.jdbcConnection.openStandalone(jdbcConnection.java:926)
at org.hsqldb.jdbcConnection.init(jdbcConnection.java:682)
at org.hsqldb.jdbcDriver.connect(jdbcDriver.java:116)
at java.sql.DriverManager.getConnection(DriverManager.java:523)
at
Re: Dreaded: Sitemap handler's sitemap is not available
I found it necessary to include more jar files. Specifically, ALL the jar files :o) For example, I'm pretty sure the avalon jars get used, so that might be part of it. Also I think that when I built there was a difference in the files size between the cocoon.jar that came with installation and the cocoon.jar that was generated when building (not sure why). Try putting the generated cocoon.jar in your tomcat/lib directory instead of the original. For me, there was also a classpath problem to beging with. Do you have your classpath set up outside of Cocoon? Originally, I had a %CLASSPATH% variable in my autoexec.bat (this was on a win98 machine) that was throwing everything off. Best of luck... --- Liam Morley light the deep, and bring silence to the world. light the world, and bring depth to the silence. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Dreaded: Sitemap handler's sitemap is not available
Hi Liam, I tried copying all the files from /home/cocoon/lib to the /home/tomcat/lib directory with no success. I had actually tried this before I sent the email and the log files ended up looking the same as it did without copying the jar files. I uninstalled everything and then reinstalled per the INSTALL and noticed that it actually created a lib file within /home/tomcat/webapps/cocoon/WEB-INF/ that contained all of the jar files. I will try the suggestion with cocoon.jar. Also, I don't believe I have the classpath set outside of Cocoon. I had tried to add something to the web.xml file, but I was unsure what to put there. Can you offer an additional suggestion? Thanks for your time! Ted -Original Message- From: Liam Morley [mailto:[EMAIL PROTECTED]] Sent: Sunday, August 19, 2001 6:03 PM To: [EMAIL PROTECTED] Subject: Re: Dreaded: Sitemap handler's sitemap is not available I found it necessary to include more jar files. Specifically, ALL the jar files :o) For example, I'm pretty sure the avalon jars get used, so that might be part of it. Also I think that when I built there was a difference in the files size between the cocoon.jar that came with installation and the cocoon.jar that was generated when building (not sure why). Try putting the generated cocoon.jar in your tomcat/lib directory instead of the original. For me, there was also a classpath problem to beging with. Do you have your classpath set up outside of Cocoon? Originally, I had a %CLASSPATH% variable in my autoexec.bat (this was on a win98 machine) that was throwing everything off. Best of luck... --- Liam Morley light the deep, and bring silence to the world. light the world, and bring depth to the silence. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Dreaded: Sitemap handler's sitemap is not available
Srini, Thanks for your thoughts. May I ask some clarifying questions? Regarding Sitemap... is there instructions on how to compile Sitemap on C2 startup? I am not sure I know what do do here? This could be the watershed event. When you say restart the server... I assume you mean Tomcat or Cocoon? If you mean Cocoon, how do you do that? Incidently, I sent log excerpts doing exactly what you said. Did they not have useful information? Thanks! Ted -Original Message- From: java guru [mailto:[EMAIL PROTECTED]] Sent: Sunday, August 19, 2001 5:20 PM To: [EMAIL PROTECTED] Subject: Re: Dreaded: Sitemap handler's sitemap is not available Hi., I hate to say search the mail archive but here is simple explanation... 1. Sitemap is one BIG java program to be compiled on c2 startup... 2. Any problem resulting from sitemap compilation could result in sitemap being NOT compiled and hence component for hint: sitemap not found.. 3. Now the reasons could range to anything and everything.. 4. Please note that JDBC problem reported is little mis-leading as this does NOT pose any threat to sitemap compilation and hence can be ignored for now.. 5. Please delete the c2 log, restart the server, try to access the main page ONLY once...stop the server...read the log from BOTTOM UP... 6. 95% of the time, you get the clue..but if still same..then zip the log and post it here... 7. As i hate to suggest, but you may want to search mailing list archive.. good luck = Thanks and have great day srini Do You Yahoo!? For regular News updates go to http://in.news.yahoo.com - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
