Re: tomcat cache wierd behaviour

2008-04-09 Thread loredana loredana
I still can't understand how winscp has any part in this. I don't copy 
anything, I only use it to view the files. Tomcat automatically creates the 
.java and .class files. I could use putty or some other tool and the result 
would be the same. But it's even wierder. Now I see even the catalina.out file 
(which is updated very often) has the timestamp +1 hour. Like that wouldn't be 
enough, the servers are in Italy, where the time is now 9:05 (so the server 
time is 9:05), i'm in Romania where the time is 10:05, and catalina out was 
last modified(aparently) at 11:05.  too wierd

- Original Message 
From: David Smith [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
Sent: Tuesday, April 8, 2008 10:49:35 PM
Subject: Re: tomcat cache wierd behaviour

Winscp isn't a command line tool -- it's one of those GUI enabled 
transfer tools with the split panels.  Think of something more along the 
lines of Explorer or Norton Commander -- the two interfaces styles 
available from winscp out of the box.  By default it set's the date/time 
of the recently sent file to the client's date/time so it can implement 
a synchronize feature.  I changed the settings in mine to prevent this 
because my server time would float a little between ntp updates.  Tomcat 
wouldn't see the updates until a couple of minutes after I uploaded them. 

Issues of times on the remote system being off by an hour are discussed 
on the winscp website (as the OP described in his example in the 
original post):
http://winscp.net/eng/docs/timestamp

The setting to preserve timestamps on uploads can be changed:
http://winscp.net/eng/docs/ui_copy -- here you can see the checkbox 
labeled Preserve timestamp in the screenshot, far right side under 
'Attributes'.


--David

Christopher Schultz wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 David,

 David Smith wrote:
 | I've seen some transfer clients (like winscp) default to setting the
 | date/time on the remote copy the same as the local.

 If 'winscp' acts anything like UNIX scp, then the default mode is to set
 the modification time on the destination to the destination's current
 date (basically, 'touch' the file upon creation). The -p switch allows
 you to preserve the existing modification time of the source file, so
 that the destination matches the source after the copy. It's unclear how
 different time zones are handled.

 I would check to see what 'winscp' does by default. You probably want
 any files you copy to your server to be date-stamped with the current
 date on the server, rather than preserving the source file's
 modification time.

 The OP never mentioned what the timezone was on the source machine, only
 the destination (CEST, UTC +2).

 - -chris

 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.8 (MingW32)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

 iEYEARECAAYFAkf7xUUACgkQ9CaO5/Lv0PCT8gCggO1z8trzf40N1YNbgAgy0cUP
 SjkAoJqJiFYvg56JthbKEkFihH3LARPq
 =LrfO
 -END PGP SIGNATURE-

 -
 To start a new topic, e-mail: users@tomcat.apache.org
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  

You rock. That's why Blockbuster's offering you one month of Blockbuster Total 
Access, No Cost.  
http://tc.deals.yahoo.com/tc/blockbuster/text5.com


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: tomcat cache wierd behaviour

2008-04-09 Thread loredana loredana
Solved

well, i guess you guys were right. problem was winscp which had an option 
preserve timestamp in the preferences panel. Disabled it and now it seems to 
show all times corectly.

10x a lot for everybody's help! really thanks!

- Original Message 
From: loredana loredana [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
Sent: Wednesday, April 9, 2008 10:06:10 AM
Subject: Re: tomcat cache wierd behaviour

I still can't understand how winscp has any part in this. I don't copy 
anything, I only use it to view the files. Tomcat automatically creates the 
.java and .class files. I could use putty or some other tool and the result 
would be the same. But it's even wierder. Now I see even the catalina.out file 
(which is updated very often) has the timestamp +1 hour. Like that wouldn't be 
enough, the servers are in Italy, where the time is now 9:05 (so the server 
time is 9:05), i'm in Romania where the time is 10:05, and catalina out was 
last modified(aparently) at 11:05.  too wierd

- Original Message 
From: David Smith [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
Sent: Tuesday, April 8, 2008 10:49:35 PM
Subject: Re: tomcat cache wierd behaviour

Winscp isn't a command line tool -- it's one of those GUI enabled 
transfer tools with the split panels.  Think of something more along the 
lines of Explorer or Norton Commander -- the two interfaces styles 
available from winscp out of the box.  By default it set's the date/time 
of the recently sent file to the client's date/time so it can implement 
a synchronize feature.  I changed the settings in mine to prevent this 
because my server time would float a little between ntp updates.  Tomcat 
wouldn't see the updates until a couple of minutes after I uploaded them. 

Issues of times on the remote system being off by an hour are discussed 
on the winscp website (as the OP described in his example in the 
original post):
http://winscp.net/eng/docs/timestamp

The setting to preserve timestamps on uploads can be changed:
http://winscp.net/eng/docs/ui_copy -- here you can see the checkbox 
labeled Preserve timestamp in the screenshot, far right side under 
'Attributes'.


--David

Christopher Schultz wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 David,

 David Smith wrote:
 | I've seen some transfer clients (like winscp) default to setting the
 | date/time on the remote copy the same as the local.

 If 'winscp' acts anything like UNIX scp, then the default mode is to set
 the modification time on the destination to the destination's current
 date (basically, 'touch' the file upon creation). The -p switch allows
 you to preserve the existing modification time of the source file, so
 that the destination matches the source after the copy. It's unclear how
 different time zones are handled.

 I would check to see what 'winscp' does by default. You probably want
 any files you copy to your server to be date-stamped with the current
 date on the server, rather than preserving the source file's
 modification time.

 The OP never mentioned what the timezone was on the source machine, only
 the destination (CEST, UTC +2).

 - -chris

 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.8 (MingW32)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

 iEYEARECAAYFAkf7xUUACgkQ9CaO5/Lv0PCT8gCggO1z8trzf40N1YNbgAgy0cUP
 SjkAoJqJiFYvg56JthbKEkFihH3LARPq
 =LrfO
 -END PGP SIGNATURE-

 -
 To start a new topic, e-mail: users@tomcat.apache.org
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  

You rock. That's why Blockbuster's offering you one month of Blockbuster Total 
Access, No Cost.  
http://tc.deals.yahoo.com/tc/blockbuster/text5.com


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: tomcat cache wierd behaviour

2008-04-08 Thread William Bonnet

Hi

 Hi, I have a wierd problem with tomcat cache. Let's say now time its
15:00.
 i create a test.jsp in the application folder. Using winscp, I see the
tab
 Changed(last modified) 15:00. I access the jsp in the browser. In the
 work folder now will appear 2 new files: test.java and test.class
files.
 The wierd thing is these files have the tab changed 16:00. how is that
 possible? This is the reason why my jsp files are not updated. But I
can't
 understand why those 2 files show 16:00 at last changed when the time
is
 15:00did anyone ever had similar problem?

It seems you have a problem with your date  time settings on your
machines. Are you sure your timezone is well configured ? any problem with
summer time or daylight saving time ? 

Regards

-- 
William  http://www.wbonnet.net

http://www.sunwizard.net Le site français des amateurs de stations Unix
http://www.blastwave.org An OpenSolaris Community Site
http://www.guses.org French speaking Solaris User Group


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: tomcat cache wierd behaviour

2008-04-08 Thread loredana loredana
I don't think so. 
I run a date command on the server (which is ubuntu) and got Tue Apr  8 
15:50:01 CEST 2008
Is there any configurations I have to do in tomcat? set TZ variables or 
anything?



- Original Message 
From: William Bonnet [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
Sent: Tuesday, April 8, 2008 3:43:12 PM
Subject: Re: tomcat cache wierd behaviour


Hi

 Hi, I have a wierd problem with tomcat cache. Let's say now time its
15:00.
 i create a test.jsp in the application folder. Using winscp, I see the
tab
 Changed(last modified) 15:00. I access the jsp in the browser. In the
 work folder now will appear 2 new files: test.java and test.class
files.
 The wierd thing is these files have the tab changed 16:00. how is that
 possible? This is the reason why my jsp files are not updated. But I
can't
 understand why those 2 files show 16:00 at last changed when the time
is
 15:00did anyone ever had similar problem?

It seems you have a problem with your date  time settings on your
machines.. Are you sure your timezone is well configured ? any problem with
summer time or daylight saving time ? 

Regards

-- 
William  http://www.wbonnet.net

http://www.sunwizard.net Le site français des amateurs de stations Unix
http://www.blastwave.org An OpenSolaris Community Site
http://www.guses.orgFrench speaking Solaris User Group


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  

You rock.. That's why Blockbuster's offering you one month of Blockbuster Total 
Access, No Cost.  
http://tc.deals.yahoo.com/tc/blockbuster/text5.com


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: tomcat cache wierd behaviour

2008-04-08 Thread Hassan Schroeder
On Tue, Apr 8, 2008 at 7:12 AM, loredana loredana
[EMAIL PROTECTED] wrote:

  I run a date command on the server (which is ubuntu) and got Tue Apr  8 
 15:50:01 CEST 2008

 Using winscp, I see ...

So it sounds like your problem is with winscp, whatever that is, not
Tomcat :-)Maybe this is a question for the winscp user list?

-- 
Hassan Schroeder  [EMAIL PROTECTED]

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: tomcat cache wierd behaviour

2008-04-08 Thread loredana loredana
winscp is a tool...like windows commander or total commander, . is just to view 
the files in an organized matter. :) i'm sure the problem is not winscp :)

- Original Message 
From: Hassan Schroeder [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
Sent: Tuesday, April 8, 2008 5:33:44 PM
Subject: Re: tomcat cache wierd behaviour

On Tue, Apr 8, 2008 at 7:12 AM, loredana loredana
[EMAIL PROTECTED] wrote:

  I run a date command on the server (which is ubuntu) and got Tue Apr  8 
 15:50:01 CEST 2008

 Using winscp, I see ...

So it sounds like your problem is with winscp, whatever that is, not
Tomcat :-)Maybe this is a question for the winscp user list?

-- 
Hassan Schroeder  [EMAIL PROTECTED]

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  

You rock. That's why Blockbuster's offering you one month of Blockbuster Total 
Access, No Cost.  
http://tc.deals.yahoo.com/tc/blockbuster/text5.com


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: tomcat cache wierd behaviour

2008-04-08 Thread David Smith
I've seen some transfer clients (like winscp) default to setting the 
date/time on the remote copy the same as the local.  If the local system 
time isn't in sync with the server, it could cause issues like this.  
When the jsp is compiled, tomcat uses the server's date, time and time 
zone.  In your specific case, it may be either your local system or the 
server doesn't have the right time zone or maybe hasn't handled the 
daylight savings time transition correctly.


--David

loredana loredana wrote:

winscp is a tool...like windows commander or total commander, . is just to view 
the files in an organized matter. :) i'm sure the problem is not winscp :)

- Original Message 
From: Hassan Schroeder [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
Sent: Tuesday, April 8, 2008 5:33:44 PM
Subject: Re: tomcat cache wierd behaviour

On Tue, Apr 8, 2008 at 7:12 AM, loredana loredana
[EMAIL PROTECTED] wrote:

  

 I run a date command on the server (which is ubuntu) and got Tue Apr  8 
15:50:01 CEST 2008



  

Using winscp, I see ...



So it sounds like your problem is with winscp, whatever that is, not
Tomcat :-)Maybe this is a question for the winscp user list?

  



-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: tomcat cache wierd behaviour

2008-04-08 Thread Hassan Schroeder
On Tue, Apr 8, 2008 at 7:37 AM, loredana loredana
[EMAIL PROTECTED] wrote:
 winscp is a tool...like windows commander or total commander, . is just to 
 view the files in an organized matter. :) i'm sure the problem is not winscp 
 :)

Your original description of a problem refers only to what you see
in 'winscp' -- what exactly is the problem you're trying to diagnose?

-- 
Hassan Schroeder  [EMAIL PROTECTED]

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: tomcat cache wierd behaviour

2008-04-08 Thread Greg Vilardi
You probably need to update your JVM. There is a bug in the internal 
time handling of the new DST rules here in the USA (at least). THe 
latest Java 5 and Java 6 JVM from Sun have fixed this. I know that the 
issue exists in the build 1.6.0-b105 Sun JVM, and I think that 1.5.0_14-
b103 also exhibits the issue, but I can't down our main development 
server right now to confirm that.

We are not experiencing the symptoms that you are describing, but we 
are seeiong that all of our logging is off by an hour as a result. It's 
certainly worth checking in any case.

Regards,
-Greg


On 8 Apr 2008 at 7:37, loredana loredana wrote:

 winscp is a tool...like windows commander or total commander, . is just
 to view the files in an organized matter. :) i'm sure the problem is not
 winscp :)
 
 - Original Message 
 From: Hassan Schroeder [EMAIL PROTECTED]
 To: Tomcat Users List users@tomcat.apache.org
 Sent: Tuesday, April 8, 2008 5:33:44 PM
 Subject: Re: tomcat cache wierd behaviour
 
 On Tue, Apr 8, 2008 at 7:12 AM, loredana loredana
 [EMAIL PROTECTED] wrote:
 
   I run a date command on the server (which is ubuntu) and got Tue
   Apr  8 15:50:01 CEST 2008
 
  Using winscp, I see ...
 
 So it sounds like your problem is with winscp, whatever that is, not
 Tomcat :-)Maybe this is a question for the winscp user list?
 
 -- 
 Hassan Schroeder  [EMAIL PROTECTED]
 
 - To
 start a new topic, e-mail: users@tomcat.apache.org To unsubscribe,
 e-mail: [EMAIL PROTECTED] For additional commands,
 e-mail: [EMAIL PROTECTED]
 
 
   __
   __
 You rock. That's why Blockbuster's offering you one month of Blockbuster
 Total Access, No Cost. 
 http://tc.deals.yahoo.com/tc/blockbuster/text5.com
 
 
 - To
 start a new topic, e-mail: users@tomcat.apache.org To unsubscribe,
 e-mail: [EMAIL PROTECTED] For additional commands,
 e-mail: [EMAIL PROTECTED]
 


-- 
Gregory H. Vilardi631-752-2701x240 [EMAIL PROTECTED]
Project Manager / Lead Software Engineer   
Recurrent Software Solutions, a division of PES Payroll 
1 Huntington Quadrangle, Suite 1C02, Melville, NY 11747 
Fax: 631-752-3397 
http://www.recurrentsoft.com


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: tomcat cache wierd behaviour

2008-04-08 Thread Christopher Schultz

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

David,

David Smith wrote:
| I've seen some transfer clients (like winscp) default to setting the
| date/time on the remote copy the same as the local.

If 'winscp' acts anything like UNIX scp, then the default mode is to set
the modification time on the destination to the destination's current
date (basically, 'touch' the file upon creation). The -p switch allows
you to preserve the existing modification time of the source file, so
that the destination matches the source after the copy. It's unclear how
different time zones are handled.

I would check to see what 'winscp' does by default. You probably want
any files you copy to your server to be date-stamped with the current
date on the server, rather than preserving the source file's
modification time.

The OP never mentioned what the timezone was on the source machine, only
the destination (CEST, UTC +2).

- -chris

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkf7xUUACgkQ9CaO5/Lv0PCT8gCggO1z8trzf40N1YNbgAgy0cUP
SjkAoJqJiFYvg56JthbKEkFihH3LARPq
=LrfO
-END PGP SIGNATURE-

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: tomcat cache wierd behaviour

2008-04-08 Thread David Smith
Winscp isn't a command line tool -- it's one of those GUI enabled 
transfer tools with the split panels.  Think of something more along the 
lines of Explorer or Norton Commander -- the two interfaces styles 
available from winscp out of the box.  By default it set's the date/time 
of the recently sent file to the client's date/time so it can implement 
a synchronize feature.  I changed the settings in mine to prevent this 
because my server time would float a little between ntp updates.  Tomcat 
wouldn't see the updates until a couple of minutes after I uploaded them. 

Issues of times on the remote system being off by an hour are discussed 
on the winscp website (as the OP described in his example in the 
original post):

http://winscp.net/eng/docs/timestamp

The setting to preserve timestamps on uploads can be changed:
http://winscp.net/eng/docs/ui_copy -- here you can see the checkbox 
labeled Preserve timestamp in the screenshot, far right side under 
'Attributes'.



--David

Christopher Schultz wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

David,

David Smith wrote:
| I've seen some transfer clients (like winscp) default to setting the
| date/time on the remote copy the same as the local.

If 'winscp' acts anything like UNIX scp, then the default mode is to set
the modification time on the destination to the destination's current
date (basically, 'touch' the file upon creation). The -p switch allows
you to preserve the existing modification time of the source file, so
that the destination matches the source after the copy. It's unclear how
different time zones are handled.

I would check to see what 'winscp' does by default. You probably want
any files you copy to your server to be date-stamped with the current
date on the server, rather than preserving the source file's
modification time.

The OP never mentioned what the timezone was on the source machine, only
the destination (CEST, UTC +2).

- -chris

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkf7xUUACgkQ9CaO5/Lv0PCT8gCggO1z8trzf40N1YNbgAgy0cUP
SjkAoJqJiFYvg56JthbKEkFihH3LARPq
=LrfO
-END PGP SIGNATURE-

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]