Hello,
anyone knows how to switch off session persistence across all
applications deployed on a toncat server? I know how to do it for a
single app, by declaring explicitly a PersitentManager () within the in server.xml. However,
each time I deploy a new app I need to edit the server.xml fil
ok, found it! Small correction though. Each app has its own
SESSIONS.ser file. Hence needs to be deleted for each app deployed. I
guess one could search all files and delete, but it is still not a clean
solution.
If no is defined, then the default used by Tomcat is the one
that persist
Hello Vincent,
fro problem 1:
you are using the correct procedure, but it looks like your server was
never started in the first place. The connection refused is due to the
fact that it tries to connect to a port (for shutdown procedure) which
is not open. Alternatively, tomcat can some time g
I agree, a few extra words go along way with these answers.
Persistence is a good thing (no pun intended ;) .
Vrata
Angus Mezick wrote:
Don't know, with the scattered nature of the FM, any one stating RTFM
probably should include which part (FP?) of which FM they want you to R.
Or at least giv
note you can also define the classpath to the catalina-ant.jar from the
taskdef itself:
this way you may wish to keep the path independant rather than copying
the jar to the ant home!
Steph Richardson wrote:
Juraj
Look for TOMCAT_HOME/server/lib/catalina-ant.jar and copy it to your ANT_HOME
Hi Yoav,
thanks for the pointer. I will look it up. Indeed now that you mention
the DefaultContext, that rings a bell. I will experiment with that.
Apologies for my RTFQ!
Vrata
--
V
. . . . . . . . .
tel:+34.918.131.331
--
thanks, I did already! But I don't think you understand my question!
I know you can reset the defaut, but that's only on a per context
basis. I want to reset the default for all contexts, ie if a new
context is deployed and not defined, then the default should
not persist! The manual doesn'
that worked thanks!
Shapira, Yoav wrote:
Howdy,
I see in the manual that it is possible to have customised loggers
(Logger tag within a Context). I managed to do a customised FileLogger
for my web app, but I couldn't override the default std output and std
error logger (cantalina.out). An
Hi,
I see in the manual that it is possible to have customised loggers
(Logger tag within a Context). I managed to do a customised FileLogger
for my web app, but I couldn't override the default std output and std
error logger (cantalina.out). Any ideas how to do that?
thanks
vrta
--
V
. .
delete all SESSIONS.ser under work before you start tomcat)
Aurele Venet wrote:
Hello,
I am having a strange effect with my tomcat server. My web app sends
a session cookie (JSESSIONID) to the browser for session tracking.
This keeps a boolean flag to say wether or not a user is logged in.
I find t
Hello,
I am having a strange effect with my tomcat server. My web app sends a
session cookie (JSESSIONID) to the browser for session tracking. This
keeps a boolean flag to say wether or not a user is logged in. I find
that when I stop and restart the server, the cookie is sent back from
the
used a we.xml example file that he picked in a
tutorial which has a lot of extra tag declarations.
Aurele Venet wrote:
Hola,
we've just upgrade our tomcat server from 4.0.3 to 4.1.24 and after a
few teething problems which I managed to fix, I am left with one app
that refused to start up.
, then you can even ftp it using ssh from the ant script without
requiring any password exchanges!
Michael Kessler wrote:
The Idea behind is to deploy a webapp automatically on severals servers
in the cluster, manual deploy is not the problem ;-)
On Wed, 2003-07-23 at 17:15, Aurele Venet wrote
sorry... I meant server.xml file!
Aurele Venet wrote:
then copy the war to your webapps dir first and make an install from
there! Make sure autodeploy war file is set in your servlet.xml file
so at restart it will get redeployed!
Michael Kessler wrote:
With the install task the webapp is
On Wed, 2003-07-23 at 16:55, Aurele Venet wrote:
I managed to deploy using ant with the following script:
http://localhost:8000/manager"; username="root"/>
http://localhost:8000/manager"; username="root"
war="file:/
Elisabeth,
not sure what you use for uploading mechanism (i use the o-reilly
classes - cos.jar) but just to say that we upload images to a dir on the
server which are then included in a dyanmic page which is served by a
jsp works fine! Not sure the content of your files, but if you
manage
I managed to deploy using ant with the following script:
http://localhost:8000/manager"; username="root"/>
http://localhost:8000/manager"; username="root"
war="file://${d_build}XAT.war"/>
note you need tomcat/4.1.24 + tomcatAntLib path variable pointing to
Hola,
we've just upgrade our tomcat server from 4.0.3 to 4.1.24 and after a
few teething problems which I managed to fix, I am left with one app
that refused to start up. This webapp worked fine in the previous
installation. Here is the log error message I get, can any one be so
kind as to s
18 matches
Mail list logo