Tomcat4 : specific settings for Context
Hello list, I would like to setup some specific settings per Tomcat Context. Debian flavour for Tomcat automatically detects all apps deployed in CATALINA_HOME/webapps and sets up all needed settings : there is no Context entry in server.xml for the different applications. Now I woul like to setup the reloadable attribute for a specific application in Tomcat : how should I do, since I can not find anything related to my application Context in Tomcat config files... I hope this was clear enough :-) Regards, -- Dominique Deleris http://potatoworld.tuxfamily.org -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Tomcat4 and encodeURL
Hi ! I'm new to J2EE, and therefore I am trying each and every example of the programming book I've bought. Now I am learning session handling w/ the servlet API, and would like to use the URL-encoding style for keeping sessions, when the browser's configuration does not allow to use cookies. My (simple) example servlet is using the following instruction: String lifeCycleURL = response.encodeURL(/jtests/servlet/lifeCycle); out.println(A href=\ + lifeCycleURL + ?action=newSession\); This should modify my URL, adding ;jsessionid=xxx where xxx is the session ID. I can not get this to work, Tomcat will only handle sessions using cookies... Maybe I'm missing something? I use : Tomcat 4.0.4 Apache 1.3.26 mod-jk Debian Woody (3.0) -- Dominique Deleris http://potatoworld.tuxfamily.org -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Tomcat4 on Debian Woody : /etc/init.d/tomcat4 stop won't unload apps properly
Hello, I use tomcat + apache on a debian box (woody): apache 1.3.26 j2sdk1.31.3.1 tomcat4 4.0.4 I have noticed the following problem in /etc/init.d/tomcat4: when called with the stop argument, it will kill the JVM before the shutdown of tomcat is correctly ended. This means that tomcat applications will not be ended correctly: for instance servlets destroy() methods are not called. stop) echo -n Stopping $DESC: if start-stop-daemon --test --start --pidfile $PIDFILE \ --user $TOMCAT4_USER --startas $JAVA_HOME/bin/java \ /dev/null; then echo (not running). else su -p $TOMCAT4_USER -c \$DAEMON\ stop \ /dev/null 21 || true # Fallback to kill the JVM process in case stopping didn't work sleep 2 HERE # DOD 31.07.2002 : JVM must not be killed before the tomcat apps are unloaded properly HERE #start-stop-daemon --stop --oknodo --quiet \ HERE # --pidfile $PIDFILE --user $TOMCAT4_USER rm -f $PIDFILE echo $NAME. fi ;; Is there a way to keep the fallback to kill JVM in case of problem, but allowing tomcat to stop correctly. I also could modify the sleep instruction to wait 30s, but... Should I report a bug to the package maintainer? Thanks for any help. Cheers, -- Dominique Deleris http://potatoworld.tuxfamily.org -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
