?
To: Tomcat Users List users@tomcat.apache.org
Date: Tuesday, November 4, 2008, 6:45 PM
From: Fu-Tung Cheng [mailto:[EMAIL PROTECTED]
Subject: Does the Server element have a listen
address?
I have two ip addresses and I would like the server
element
with the shutdown port to listen on only
Hi,
I have two ip addresses and I would like the server element with the shutdown
port to listen on only one. Is that possible or will it just listen on all?
I did look at the docs:
http://tomcat.apache.org/tomcat-6.0-doc/config/server.html
but they don't mention a way to do that.
Thank
Hi,
I am trying to have my tomcat instance listen on a specific external ip address.
I do that with the Connector address=207.203.10.45
Now I also would like to have tomcat remain listening on 127.0.0.1.
Any idea how I get that to happen?
Thank you,
Fu-Tung
: Thursday, October 23, 2008, 6:52 PM
From: Fu-Tung Cheng [mailto:[EMAIL PROTECTED]
Subject: One instance listen on 127.0.0.1 and on
single external ip
I do that with the Connector
address=207.203.10.45
Now I also would like to have tomcat remain listening
on 127.0.0.1.
Just configure
Hi,
My application has an ajax layer which asynchronously polls my tomcat server.
When the session for the user is destroyed, the next request causes a forward
to the login jsp defined for the form realm.
On the login jsp I would like to output an error message like Your session has
been
Timeout and Realm Authentication and Posted Error Message
To: Tomcat Users List users@tomcat.apache.org
Date: Thursday, October 9, 2008, 9:29 PM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fu-Tung,
Fu-Tung Cheng wrote:
The way the realm typically works is that you request
a url say
Slackware Linux
Well, no way is a bit strong a statement. For
example Linux' netfilter
provides an owner match for locally generated packets. This
should be
usable to indeed create a per-user restriction of access to
the shutdown
port.
But since the OP didn't bother to tell us which OS
That might be the simpliest but using kill to stop tomcat can prevent services
from properly shutting down potentially causing data loss depending on your
application. In a development environment that is likely a good solution but
in a production environment I don't think that is a good idea.
Hi,
I have different instances of tomcat running on different ports of the same
machine. The processes are running as different users. In this case could a
user different than the one who launched the process connect to the tomcat
shutdown port and cause the other instance to shutdown?
It
List users@tomcat.apache.org
Date: Thursday, August 21, 2008, 6:58 PM
Fu-Tung Cheng wrote:
Hi,
I have different instances of tomcat running on
different ports of the same machine. The processes are
running as different users. In this case could a user
different than the one who
I suggest you start with a working example and modify it once you have it
working.
You might also provide the following information if you expect help. In
general though I think you should have a read of the following:
http://www.catb.org/~esr/faqs/smart-questions.html
What realm do you
Hi,
I was wondering what solutions people are using to monitor their tomcat
processes.
I've been having a look at the following:
http://code.google.com/p/tomcat-monitor/wiki/TomcatMonitor
Are there better scripts or alternatives for handling restarting the vm in the
case of out of memory
Hi,
I am using tc 6.0.16 with jdk 1.6.0.
I get the following error on startup:
java.lang.IllegalAccessException:
Class org.apache.catalina.core.StandardContext
can not access a member of class
com.mycom.Myclass
with modifiers private
web.xml:
listener
I found the issue. Listeners must implement a public zero argument
constructor.
Fu-Tung
--- On Tue, 7/22/08, Deepak Mishra [EMAIL PROTECTED] wrote:
From: Deepak Mishra [EMAIL PROTECTED]
Subject: Re: IllegalAccessException for listener
To: Tomcat Users List users@tomcat.apache.org
Date:
Hi,
When a user logs into the system he is given a session. If that same user logs
into the system he is given another session - if the browser is different such
that there is no cookie collision.
In this case I'd like to invalidate the original session on login.
How can I accomplish this?
Might have to do with this:
Any declared listener will be reported as declared twice due to this bug
http://www.mail-archive.com/[EMAIL PROTECTED]/msg23408.html
Fu-Tung
--- On Tue, 7/22/08, Caldarale, Charles R [EMAIL PROTECTED] wrote:
From: Caldarale, Charles R [EMAIL
Hi,
I have two war files. One is an authentication war and the other is setup to
use the authentication war via the servlet context.xml mechanism.
On windows my issues appears to be that the context.xml from the auth.war is
being cached inside tc/conf/Catalina/localhost/... and that on the
17 matches
Mail list logo
