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 2nd
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:
com.mycom.Myclass
where Myclass is located
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"
> Date: Tuesday, July
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 PRO
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 er
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 hav
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 se
sers
> can anyone shutdown?
> To: "Tomcat Users List"
> 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 di
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
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.
11 matches
Mail list logo