|
Home > Archive > BizTalk Server General > November 2005 > Service window & daylight saving
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Service window & daylight saving
|
|
| eXavier 2005-11-03, 5:55 pm |
| Hello,
we have set up service window on receive ports: 01:00 - 22:45. After
daylight saving switch we noticed that it was shifted to 02:00 - 23:45.
I didnt see anything about it in documentation. Could someone give full
explanation how the daylight saving shift is handled in BizTalk (2004). Or if
I missed something could you send a link to this topic? (I would like to know
if the time is changed also for something else, like tracking etc.)
The shift of the service windows caused us problems as we have scheduled
support tasks in maintenance window, when we do not expect any external
messages comming into the system.
Now we rescheduled service windows but I expect another shift on next
dayligth saving.
Thanks,
eXavier
| |
| Jon Flanders 2005-11-03, 5:55 pm |
| Funny - I am seeing the same behavior with Delay shapes on Beta 1 of BizTalk
2006.
Jon Flanders [MVP]
http://www.masteringbiztalk.com
> Hello,
> we have set up service window on receive ports: 01:00 - 22:45. After
> daylight saving switch we noticed that it was shifted to 02:00 -
> 23:45.
> I didnt see anything about it in documentation. Could someone give
> full explanation how the daylight saving shift is handled in BizTalk
> (2004). Or if I missed something could you send a link to this topic?
> (I would like to know if the time is changed also for something else,
> like tracking etc.)
>
> The shift of the service windows caused us problems as we have
> scheduled
> support tasks in maintenance window, when we do not expect any
> external
> messages comming into the system.
> Now we rescheduled service windows but I expect another shift on next
> dayligth saving.
> Thanks,
> eXavier
| |
| Matthew Berkland 2005-11-03, 5:55 pm |
| Interesting, so am I. Did you find a resolution for it? All my delay shapes
are taking an extra hour now....
Matt
"Jon Flanders" <jon.flanders@gmail.com> wrote in message
news:28a4873811e338c7ae777e7e6d00@news.microsoft.com...
> Funny - I am seeing the same behavior with Delay shapes on Beta 1 of
BizTalk
> 2006.
>
> Jon Flanders [MVP]
> http://www.masteringbiztalk.com
>
>
>
| |
| Jon Flanders 2005-11-03, 5:55 pm |
| Hello Matthew,
Yep - i changed my delay shape to take a negative one (-1) for the hour in
creatign the timespan. LOL - quite the hack.
Seems to me this is a bigger bug than I first thought. Anyone from MS listening
today?
Jon Flanders [MVP]
http://www.masteringbiztalk.com
[vbcol=seagreen]
> Interesting, so am I. Did you find a resolution for it? All my delay
> shapes are taking an extra hour now....
>
> Matt
>
> "Jon Flanders" <jon.flanders@gmail.com> wrote in message
> news:28a4873811e338c7ae777e7e6d00@news.microsoft.com...
>
> BizTalk
>
| |
| WenJun Zhang[msft] 2005-11-04, 7:48 am |
| Hi all,
It seems I haven't been able to reproduce the problem. What is the time
zone you are using?
I set Service Window on a receive location, change system to use Pacific
time and select 'Automatically adjust clock for daylight saving changes'.
Then I set date time to 1:59:55 AM, Oct 30 . After few secs, the clock is
adjusted to 1:0:0 AM. However the time span in Service Window hasn't been
changed at all.
Our BizTalk SDE has ever confirmed they performed many tests on daylight
saving. The time saved in database is in local time, which shouldn't be
affected.
So could you please provide me with detailed info to reproduce the symptom
you met? Thanks.
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no rights.
| |
| Matthew Berkland 2005-11-04, 5:56 pm |
| I am in central time zone. While I am not having issues with the service
window, I am having issues with my delay/wait shapes in orchestrations.
Their time span value is being used from a businessobject that is returned
from calling a ruleset. I tried changing the rule that creates the delay by
using a -1 in the hours argument (this is really just a timespan object
right?) and then the orchestrations would complete very quickly, before they
should have. So I then undeployed that policy and put the old one in place
and everything worked like I expected it would.... until this morning. Now
it is back to having longer delays then the wait shape should have. This
seems like a bug of some sort, but I have no idea where to start working on
it.
Any help would be greatly appreciated.
Matt
""WenJun Zhang[msft]"" <wjzhang@online.microsoft.com> wrote in message
news:hTqzDHU4FHA.1144@TK2MSFTNGXA01.phx.gbl...
> Hi all,
>
> It seems I haven't been able to reproduce the problem. What is the time
> zone you are using?
>
> I set Service Window on a receive location, change system to use Pacific
> time and select 'Automatically adjust clock for daylight saving changes'.
> Then I set date time to 1:59:55 AM, Oct 30 . After few secs, the clock is
> adjusted to 1:0:0 AM. However the time span in Service Window hasn't been
> changed at all.
>
> Our BizTalk SDE has ever confirmed they performed many tests on daylight
> saving. The time saved in database is in local time, which shouldn't be
> affected.
>
> So could you please provide me with detailed info to reproduce the symptom
> you met? Thanks.
>
> Best regards,
>
> WenJun Zhang
> Microsoft Online Partner Support
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
| |
| Jon Flanders 2005-11-04, 5:56 pm |
| Hi WenJun - I was able to reproduct it with a simple project.
Here is the string that I sent in - <string>foo</string>
Here is the string I got out -
<?xml version="1.0" encoding="utf-8"?>
<string>11/2/2005 9:08:13 PM start:11/2/2005 10:08:45 PM end:</string>
If you notice - the delay was set to 30 seconds in the Orch - but came out to an hour and 30 seconds.
This is BizTalk 2006 beta 1 and SQL 2000
Jon Flanders [MVP]
http://www.masteringbiztalk.com
> Hi all,
>
> It seems I haven't been able to reproduce the problem. What is the
> time zone you are using?
>
> I set Service Window on a receive location, change system to use
> Pacific time and select 'Automatically adjust clock for daylight
> saving changes'. Then I set date time to 1:59:55 AM, Oct 30 . After
> few secs, the clock is adjusted to 1:0:0 AM. However the time span in
> Service Window hasn't been changed at all.
>
> Our BizTalk SDE has ever confirmed they performed many tests on
> daylight saving. The time saved in database is in local time, which
> shouldn't be affected.
>
> So could you please provide me with detailed info to reproduce the
> symptom you met? Thanks.
>
> Best regards,
>
> WenJun Zhang
> Microsoft Online Partner Support
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
| |
| Jon Flanders 2005-11-04, 5:56 pm |
| Just to add a little more information - if you look at the BTXTimer message
for the delay (or at least when I did) - it had the correct Timestamp (in
UTC) for the delay.
My computer (from DateTime.UtcNow) reported the correct UTC time.
SQL Server also reported the correct UTC time.
The only thing I can assume is that the code that kicks the BTXTimer back
off to the Orchestration has started doing its date time comparison wrong
after switching back to standard time.
Jon Flanders [MVP]
http://www.masteringbiztalk.com
[vbcol=seagreen]
> Hi WenJun - I was able to reproduct it with a simple project.
>
> Here is the string that I sent in - <string>foo</string>
>
> Here is the string I got out -
> <?xml version="1.0" encoding="utf-8"?>
> <string>11/2/2005 9:08:13 PM start:11/2/2005 10:08:45 PM end:</string>
> If you notice - the delay was set to 30 seconds in the Orch - but came
> out to an hour and 30 seconds.
>
> This is BizTalk 2006 beta 1 and SQL 2000
>
> Jon Flanders [MVP]
> http://www.masteringbiztalk.com
| |
| WenJun Zhang[msft] 2005-11-08, 6:20 pm |
| Hi Jon,
I've seen the problem, but the result is different than yours. (Maybe the
difference is on time zone. I use Oct 30, 1:59:55 AM Pacific Time to do the
test.)
The behavior I saw is the output file thrown out immediately without 30
secs delay when the timespan is cross the daylight saving. Maybe there is
problem on the timespan calculation.
I'll report this issue to our internal to be discussed. Please wait for my
update.
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no rights.
| |
| WenJun Zhang[msft] 2005-11-08, 6:20 pm |
| Hi Jon,
I just got update from our SDE. The issue is fixed in the next Beta 2 build.
Thanks very much for reporting this!
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no rights.
| |
| eXavier 2005-11-08, 6:20 pm |
| Hello,
I didn't get notification on changes in this thread although I still can see
'Notify me of replies' in the Web based news reader on Managed Newsgroups. So
sorry for delayed reply.
We have Biztalk 2004 Enterprise with SP1 on Windows Server 2003 Standard. If
I understand well your statement, it will be fixed only in Biztalk 2006? Is
it possible to make hotfix or service pack also for BT 2004? (I'm not sure if
the fix is same for delay shapes but we would need it for service window.)
Our Time zone is GMT+1.
Thanks
eXavier
""WenJun Zhang[msft]"" wrote:
> Hi Jon,
>
> I just got update from our SDE. The issue is fixed in the next Beta 2 build.
>
> Thanks very much for reporting this!
>
> Best regards,
>
> WenJun Zhang
> Microsoft Online Partner Support
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
| |
| WenJun Zhang[msft] 2005-11-09, 7:48 am |
| Hi eXavier,
The problem applies to delay shape of BizTalk 2006 Beta 1. It shouldn't
been the one you met.
As I previous posted, I tried to reproduce the service windows issue you
met but it didn't occur. Could you please provide me with some detailed
steps to repro it?
Also please let me know the daylight saving time that you met the issue.
Thanks.
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no rights.
| |
| Tomas Novotny 2005-11-09, 5:51 pm |
| Hello,
I have found the same problem on our production server as eXavier.
Even we have BizTalk 2004, SP1, Windows Server 2003 Standard Edition
installed.
We have set up Start Time of the service window on send port at 13:00. But
after daylight saving switch it was shifted to 14:00. (Our Time zone is
GMT+1).
Can you provide some more investigation regarding to this issue?
Thank you,
Tomas Novotny
""WenJun Zhang[msft]"" wrote:
> Hi eXavier,
>
> The problem applies to delay shape of BizTalk 2006 Beta 1. It shouldn't
> been the one you met.
>
> As I previous posted, I tried to reproduce the service windows issue you
> met but it didn't occur. Could you please provide me with some detailed
> steps to repro it?
>
> Also please let me know the daylight saving time that you met the issue.
>
> Thanks.
>
> Best regards,
>
> WenJun Zhang
> Microsoft Online Partner Support
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
| |
| eXavier 2005-11-10, 2:47 am |
| Hello WenJun,
currently I cannot try to reproduce it as I don't have a testing environment.
I will describe you our settings. I think the most important are settings of
Date and Time properties but if it wouldn't help, here is all our environment
setup:
All servers run Windows 2003 Server Standard, updated with Windows Update.
We have 2 machines (lets call them A and B) in cluster making it single
virtual machine (C). On C runs SQL Server 2000 SP3 and ESSO. Further, servers
D and E have BizTalk 2004 Enterprise SP1 installed and runs in BizTalk Server
Group. D and E have identical installation. We separated receive adapters,
send adapters and orchestration to individual Biztalk Hosts, so there are 3
instances of biztalk service on each server (D,E). All servers have same
configuration:
Regional Settings
Standards and formats: German(Switzerland)
Location: Switzerland
Date and Time Properties
TimeZone: (GMT+01:00) Amsterdam, Berlin, Bern,...
Automatically adjust clock for daylight saving changes: checked
We noticed the shift of service window after last daylight savings which was
on October 30th at 3am. (at 3am the time was moved back to 2am)
Our service window 01:00-22:45 was then shifted to 02:00-23:45.
Hope this helps.
eXavier
""WenJun Zhang[msft]"" wrote:
> Hi eXavier,
>
> The problem applies to delay shape of BizTalk 2006 Beta 1. It shouldn't
> been the one you met.
>
> As I previous posted, I tried to reproduce the service windows issue you
> met but it didn't occur. Could you please provide me with some detailed
> steps to repro it?
>
> Also please let me know the daylight saving time that you met the issue.
>
> Thanks.
>
> Best regards,
>
> WenJun Zhang
> Microsoft Online Partner Support
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
| |
| eXavier 2005-11-10, 7:50 am |
| Maybe I should add that we noticed of the service window shift after few
days, not the same day when the automatical clock adjustment occured (could
it be modified when service is started again?) We didn't check that as we did
not expect anything like this.
And next one thing - if I try to replicate it locally (on Win2K) then I am
not able to change data in SSO due to current time is older then last written
into SSO. If Bts would try to change the time in config it would fail. So
probably it would be better to test it on the next daylight saving (set local
time to the future).
eXavier
"eXavier" wrote:
[vbcol=seagreen]
> Hello WenJun,
> currently I cannot try to reproduce it as I don't have a testing environment.
>
> I will describe you our settings. I think the most important are settings of
> Date and Time properties but if it wouldn't help, here is all our environment
> setup:
>
> All servers run Windows 2003 Server Standard, updated with Windows Update.
> We have 2 machines (lets call them A and B) in cluster making it single
> virtual machine (C). On C runs SQL Server 2000 SP3 and ESSO. Further, servers
> D and E have BizTalk 2004 Enterprise SP1 installed and runs in BizTalk Server
> Group. D and E have identical installation. We separated receive adapters,
> send adapters and orchestration to individual Biztalk Hosts, so there are 3
> instances of biztalk service on each server (D,E). All servers have same
> configuration:
> Regional Settings
> Standards and formats: German(Switzerland)
> Location: Switzerland
> Date and Time Properties
> TimeZone: (GMT+01:00) Amsterdam, Berlin, Bern,...
> Automatically adjust clock for daylight saving changes: checked
>
> We noticed the shift of service window after last daylight savings which was
> on October 30th at 3am. (at 3am the time was moved back to 2am)
> Our service window 01:00-22:45 was then shifted to 02:00-23:45.
>
> Hope this helps.
> eXavier
>
> ""WenJun Zhang[msft]"" wrote:
>
| |
| WenJun Zhang[msft] 2005-11-10, 6:00 pm |
| Hi eXavier,
I think I've repro the issue:
1) Set time zone to use GMT+01(Madrid, Paris). Enable ¡®Automaticallt
adjust clock for daylight saving changes¡¯.
2) In Regional Options, set Time display format to French(France).
3) Set system date to a day before Oct 30 (summer time).
4) On a receive location, enable Service Window and set the Start Time
and Stop Time.
5) Set system date time to OCT 30 02:59:59.
6) After it runs into winter time, refresh and check the time setting
in Service Window again, there should be 1 extra hour added.
I've contacted our BizTalk group about this problem. Not sure if this is a
known issue. Please wait for my reply. Thanks.
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no rights.
| |
| eXavier 2005-11-10, 6:00 pm |
| Hi WenJun,
I am interested in results from your communication with BizTalk Group.
Thanks for solving it.
Best regards
eXavier
""WenJun Zhang[msft]"" wrote:
> Hi eXavier,
>
> I think I've repro the issue:
>
> 1) Set time zone to use GMT+01(Madrid, Paris). Enable ¡®Automaticallt
> adjust clock for daylight saving changes¡¯.
>
> 2) In Regional Options, set Time display format to French(France).
>
> 3) Set system date to a day before Oct 30 (summer time).
>
> 4) On a receive location, enable Service Window and set the Start Time
> and Stop Time.
>
> 5) Set system date time to OCT 30 02:59:59.
>
> 6) After it runs into winter time, refresh and check the time setting
> in Service Window again, there should be 1 extra hour added.
>
> I've contacted our BizTalk group about this problem. Not sure if this is a
> known issue. Please wait for my reply. Thanks.
>
> Best regards,
>
> WenJun Zhang
> Microsoft Online Partner Support
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
| |
| WenJun Zhang[msft] 2005-11-14, 2:48 am |
| Hi eXavier,
We've RFC this issue and currently working on it. There may be several days
before our developer team can give the conclusion. Please keep monitoring
this issue and waiting for my update. Thanks.
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no rights.
| |
| WenJun Zhang[msft] 2005-11-16, 7:52 am |
| Hi eXavier,
We are checking the code currently. I'll keep you updated. Thanks.
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no rights.
| |
| David Bailie 2005-11-17, 6:10 pm |
| Hi there, we are running BTS 2004 on Server 2003 and have service windows set
up to begin processing at 12:00 midnight. Ever since the time change though,
the service window is trying to process earlier than 12:00. My processes are
failing because the messages they're receiving are dated (for example) 16/11
and it's trying to process them at 11:45PM on 15/11, although the service
window is set to 12:00.
The time on the server is set to PST and the time is correct.
Is there another time setting within BizTalk that we're not aware of?
Thanks,
David Bailie.
""WenJun Zhang[msft]"" wrote:
> Hi eXavier,
>
> We are checking the code currently. I'll keep you updated. Thanks.
>
> Best regards,
>
> WenJun Zhang
> Microsoft Online Partner Support
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
| |
| WenJun Zhang[msft] 2005-11-18, 7:48 am |
| Hi eXavier,
We've got the conclusion. The behavior of biztalk is expected.
If you check the code and all the related settings stored in the below
three fields in the table ¡°adm_receivelocation¡±in¡°biztalkmgmtdb
¡±, the
columns controlling service window are:
operatingwindowenabled
srvwinstartdt
srvwinstopdt
In summer time:
I set the start time and stop time to 2:00 and 3:00 in service
window(operating window). The data of srvwinstartdt and srvwinstopdt in
adm_receivelocation table are:
01/01/2000 03:00:00
01/01/2000 04:00:59
After went into winter time:
The displayed time in service window becomes: 3:00 and 4:00, but the data
in SQL table hasn¡¯t been changed. Still:
01/01/2000 03:00:00
01/01/2000 04:00:59
Also if you use SQL profile to trace the process of setting/loading the
start time and stop time, you should see 2 user defined functions are
called to save the setting in local time:
adm_fnConvertUTCToLocalDate - setting
adm_fnConvertLocalToUTCDate - loading
The data will not be modified by biztalk itself at all. So the time will be
displayed with 1 hour difference between summer and winter time. This isn't
a bug because it's absolutely correct on coding logic. However if this does
hit problem on business logic, we should manually adjust the time for day
light saving, just as what we always do in the real world.
Please let me know if you have any further concern. Thanks.
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no rights.
| |
|
| I've noticed this behavior, but haven't experienced any adverse effects
because of it. All the times of my service window enabled receive locations
are now showing times that are 1 hour later than they were prior to daylight
savings time, but hte time they are actually executing is still correct.
i.e. A receive location originally set to run from 1 a.m. to 2 a.m. is still
running at that time, even though the receive location properties lists the
window as 2 a.m. to 3 a.m.
|
|
|
|
|