, and not
due to using 7.0.10.
JMuse
-Original Message-
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
Sent: Wednesday, June 12, 2013 3:18 PM
To: Tomcat Users List
Subject: RE: Class cast exception when starting tomcat 7.0.1
From: Jane Muse [mailto:jm
is:
-Original Message-
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
Sent: Thursday, June 13, 2013 8:52 AM
To: Tomcat Users List
Subject: RE: Class cast exception when starting tomcat 7.0.1
From: Jane Muse [mailto:jm...@rocketsoftware.com]
Subject: RE: Class cast exception when
: Class cast exception when starting tomcat 7.0.1
From: Jane Muse [mailto:jm...@rocketsoftware.com]
Subject: RE: Class cast exception when starting tomcat 7.0.1
Just saying, I wasn't using a 3 year unreleased version. Maybe a 3
year version, yes. Here's my original email:
I'm getting a class
, 2013 11:09 AM
To: Tomcat Users List
Subject: Re: Class cast exception when starting tomcat 7.0.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jane,
On 6/13/13 12:38 PM, Jane Muse wrote:
In the archives I thought the only unreleased versions would be
specified beta. Please let me know
[javac] 2 errors
[javac] 1 warning
-Original Message-
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
Sent: Thursday, June 13, 2013 1:41 PM
To: Tomcat Users List
Subject: RE: Class cast exception when starting tomcat 7.0.1
From: Jane Muse [mailto:jm
7.0.1
From: Jane Muse [mailto:jm...@rocketsoftware.com]
Subject: Class cast exception when starting tomcat 7.0.1
I'm getting a class cast exception when starting up tomcat 7.0.1
You can't be serious. That version was never released, and would be almost
three years old if it had been. Use
I'm getting a class cast exception when starting up tomcat 7.0.1. I've migrated
from 6.0.18 to 7.0.1. I got the same error when migrating directly to 7.0.4.
The error is:
SEVERE: Begin event threw exception
Throwable occurred: java.lang.ClassCastException:
,
On 10/13/2010 5:41 PM, Jane Muse wrote:
We have a directory called COMPANY_NAME/tomcat that is CATALINA_BASE.
I sent the contents of CATALINA_BASE/conf/context.xml in the email
below.
Great. It's probably not necessary to comment-out the WatchedResource
as the context should not be reloadable
Thanks for the java program Chris, I ran it on the version of the O/S where we
get the problem and got results that show a last modified date that differs by
one hour when the time changes due to DST.
Current GMT time (no DST): 2010-10-12 22:53:27 GMT
Current local time (with DST):
List
Subject: Re: Disable class monitoring for reloading container classes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jane,
On 10/9/2010 11:09 AM, Jane Muse wrote:
My understanding from the docs is that reloading=false means you
can't drop in a war file while tomcat is running and expect
, 2010 11:26 AM
To: Tomcat Users List
Subject: Re: Disable class monitoring for reloading container classes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jane,
On 10/13/2010 1:51 PM, Jane Muse wrote:
I found that reloadable=false does not suppress tomcat from watching
if files change in WEB-INF
From: Jane Muse [mailto:jm...@aldon.com]
Subject: RE: Disable class monitoring for reloading container classes
Here's my context.xml:
!-- WatchedResourceWEB-INF/web.xml/WatchedResource --
That may not be illegal syntax for XML, but it certainly is confusing.
Better to do
for reloading container classes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jane,
On 10/13/2010 1:40 PM, Jane Muse wrote:
Thanks for the java program Chris, I ran it on the version of the
O/S where we get the problem and got results that show a last
modified date that differs
to IBM's O/S,
or Oracle's JVM 8-)
Thanks.
Jane
-Original Message-
From: Jane Muse [mailto:jm...@aldon.com]
Sent: Friday, October 08, 2010 9:03 PM
To: Tomcat Users List
Subject: RE: Disable class monitoring for reloading container classes
Chris wrote:
It's too bad the
log doesn't show
Message-
From: André Warnier [mailto:a...@ice-sa.com]
Sent: Saturday, October 09, 2010 7:19 AM
To: Tomcat Users List; Jane Muse
Subject: Re: Disable class monitoring for reloading container classes
Caldarale, Charles R wrote:
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Subject
Chris wrote:
Jane, if you increase your logging level to DEBUG, you should be able
to see the modified() method being called, and it should tell you what
resource is triggering the reload in the webapp's log file.
I set the system date to: 11/07/10 at 1:53:00 and started tomcat. At
2:00 the
-
Hash: SHA1
Jane,
On 10/8/2010 7:40 PM, Jane Muse wrote:
Chris wrote:
Jane, if you increase your logging level to DEBUG, you should be able
to see the modified() method being called, and it should tell you what
resource is triggering the reload in the webapp's log file.
I set
: André Warnier [mailto:a...@ice-sa.com]
Sent: Thursday, October 07, 2010 3:26 AM
To: Tomcat Users List
Subject: Re: Disable class monitoring for reloading container classes
Jane Muse wrote:
André - you are correct. We actually modified autoDeploy attribute
on the Host element to false
.
Thanks much,
Jane
-Original Message-
From: Pid [mailto:p...@pidster.com]
Sent: Thursday, October 07, 2010 2:52 PM
To: Tomcat Users List
Subject: Re: Disable class monitoring for reloading container classes
On 07/10/2010 22:30, Christopher Schultz wrote:
Jane,
On 10/6/2010 3:39 PM, Jane
07, 2010 8:23 AM
To: Tomcat Users List
Subject: Re: Disable class monitoring for reloading container classes
On 06/10/2010 20:39, Jane Muse wrote:
There's a backgroundProcessor method in tomcat that checks whether
container classes need to be reloaded, and checks for session
expirations
There's a backgroundProcessor method in tomcat that checks whether
container classes need to be reloaded, and checks for session
expirations. Is it possible to disable this method, like you can disable
class reloading for the context with reloadable=false? I'm using
tomcat 6.0.18 on an IBM i
Subject: Re: Disable class monitoring for reloading container classes
Jane Muse wrote:
There's a backgroundProcessor method in tomcat that checks whether
container classes need to be reloaded, and checks for session
expirations. Is it possible to disable this method, like you can
disable class
22 matches
Mail list logo