Prasad- If you can get Tomcat to resolve any of the hundreds of OS specific binary or construct (such as symlink).. you can always exit the VM to the OS thru Runtime.exec() ..but then again that would spawn a process
Anyone else? M- --------------------------------------------------------------------------- This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. --------------------------------------------------------------------------- Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire. ----- Original Message ----- From: "Aditya Prasad" <[EMAIL PROTECTED]> To: "Tomcat Users List" <users@tomcat.apache.org> Sent: Monday, March 12, 2007 8:15 PM Subject: Re: The requested resource (/) is not available. > Thanks for the suggestion. > > It turns out that the problem was that my web.xml was a symlink. I > had to figure this out through trial and error. Is there no better > way to debug this sort of thing? > > Cheers, > Aditya > > On 3/12/07, Rashmi Rubdi <[EMAIL PROTECTED]> wrote: >> I had a similar problem too, I did a few things that got it resolved. >> >> One thing I remember is, setting the directory listings to "true" in >> server.xml , at that time if there's no index page in the directory >> it listed the directory listings instead of giving a 404 error. >> >> Other possible causes: >> >> -Check for conflicting ports - see if another app is using the same port as >> Tomcat. On my machine Oracle 10g HTML interface was using port 8080, so I >> changed >> Tomcat port to 9090. >> >> -Check CATALINA_HOME path >> >> -Rashmi >> >> ----- Original Message ---- >> From: Aditya Prasad <[EMAIL PROTECTED]> >> To: users@tomcat.apache.org >> Sent: Monday, March 12, 2007 5:35:39 PM >> Subject: The requested resource (/) is not available. >> >> >> I've set my JULI logging to FINE to figure out why I always get "The >> requested resource (/) is not available." Unfortunately, the log >> seems to indicate that the ROOT context was started up all right: >> >> Mar 12, 2007 2:32:56 PM org.apache.catalina.startup.HostConfig >> deployDirectory >> FINE: Deploying web application directory ROOT >> ... >> Mar 12, 2007 2:32:56 PM org.apache.catalina.core.StandardContext start >> FINE: Starting ROOT >> >> And there are no errors in the log. Any suggestions on where to go to >> figure out why my webapp stopped working all of a sudden? I don't >> recall making any changes that should have broken it. >> >> Thanks! >> >> >> >> ____________________________________________________________________________________ >> Don't pick lemons. >> See all the new 2007 cars at Yahoo! Autos. >> http://autos.yahoo.com/new_cars.html >> >> --------------------------------------------------------------------- >> To start a new topic, e-mail: users@tomcat.apache.org >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
