manager/deploy DELETED my web app

http://127.0.0.1:8080/manager/reload?path=/cp returned: FAIL - Encountered exception java.lang.IllegalStateException: Container StandardContext[/cp] has not been started So, I tried: http://127.0.0.1:8080/manager/deploy?path=/cp and it replied: Jun 1, 2004 5:48:36 PM

Re: Programmatic Authentication?

Yes, just write your own extension of org.apache.catalina.Realm (or extend o.a.c.realm.RealmBase)and read: http://jakarta.apache.org/tomcat/tomcat-5.0-doc/realm-howto.html then follow the instruction on how to install your own valve (search the list :-) ) -- Jeanfrancois Carl Howells wrote:

Re: Programmatic Authentication?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Carl Howells wrote: | Is it possible to set the Principal and Roles for a session in a manner | which will satisfy a role-name security constraint programmatically? | At all? I don't mind ignoring the servlet spec and doing something |

context paths, tomcat, apache, ensim 3.7

Okay I followed the below instructions, and added the bits to each file. I have therefore set up my configuration as follows : File /etc/httpd/siteXXX/tomcat4-aliases : IfModule mod_jk.c JkMount /manager ajp13 JkMount /manager/* ajp13 /IfModule File

Re: context paths, tomcat, apache, ensim 3.7

just so everyone knows this a 404 error problem with the manager application under a virtual host. Please help, been working on this for two weeks now.girlfriend and dog mad! On Jun 1, 2004, at 9:52 PM, stella luna wrote: Okay I followed the below instructions, and added the bits to

Re: context paths, tomcat, apache, ensim 3.7 ( with sever.xml) included

I figure it has to be something with my server.xml filecan someone take a look at it and see if something pops out? Thanks so much, TDG server_vwh.xml Description: application/xml On Jun 1, 2004, at 9:52 PM, stella luna wrote: Okay I followed the below instructions, and added the bits to

Re: context paths, tomcat, apache, ensim 3.7 ( with sever.xml) included

I am getting this error when i try to connect to localhost/managers/ Tue Jun 01 12:19:12 2004] [jk_connect.c (177)]: jk_open_socket, connect() failed errno = 111 [Tue Jun 01 12:19:12 2004] [jk_ajp_common.c (626)]: In jk_endpoint_t::ajp_connect_to_endpoint, failed errno = 111 [Tue Jun 01

Re: Tomcat starts poorly on Windows XP

Thanks for the suggestion; I hadn't thought of it. I doubt that my problem is caused by spaces in a directory path. It occurs even when I extract Tomcat to D:\tomcat. At 09:14 AM 6/1/2004, Jacob Kjome wrote: I suggest extracting Tomcat to a directory path with no spaces. Tomcat *should* work

Re: SSL Client Authorization

Sander, If what you want is to have the client present a certificate for validation, then in your connector have something like clientAuth=true See http://jakarta.apache.org/tomcat/tomcat-5.0-doc/ssl-howto.html If you are looking for something different let us know. Doug

Re: Jk2 compiling problem sorted ..Do you know.. How?

Filip Hanik - Dev wrote: Any clues on sorting this problem alternately? don't start apache until tomcat is up and running Which is an event not trivial to catch. I know of hacks, like tailing catalina.out log and seeing when the last of the Mohicans has loaded, but, again, it is not trivial to

Re: JSVC problems with Tomcat 5.0.19 Linux

[EMAIL PROTECTED] wrote: Hi Yoav Shapira, Look into a simple unix administration book - for granting rights for ports(binding) to non-root user and u might save some time (may be money too) for this tool. How does one go about it? I've never seen anything like that on our Digital UNIX or Tru64

character encoding of jsp output in Tomcat 5.24 JRE 1.4.2_04 jvm.dll

Hi, Does anyone have any hints as to why Tomcat would replace some characters with a question mark when being run inside the JVM dll on Windows, yet display the same characters correctly when run with java.exe ? - To

Re: character encoding of jsp output in Tomcat 5.24 JRE 1.4.2_04 jvm.dll

After comparing the system properties output by a dump from a JSP page (source below), I noticed a difference between the file.encoding properties. Using the service configuration tool I was able to add the following to the JVM's configuration options: file.encoding=ISO-8859-1 Eureka!

<    1   2