Process Mapping Logo

Process Mapping - Forums

Sharing 19 years of knowledge and experience

 
Metastorm BPM forums
Sign up Latest Topics
 
 
 


Reply
  Author   Comment  
BMellert

Guru
Registered:
Posts: 688
Reply with quote  #1 
The MBPM documentation -- buried in a small byline in the administration document, not included at all in the installation documentation -- which states (9.3.2 documentation):
Quote:
Note:  All servers (Database, MBPM Process Engine, and Web servers) should be in the same Time Zone.  You should turn off DST on the servers.  When changing the time zone on a client machine, you must reboot on the client machine for the Time Zone adjustment to work correctly.

We never did this in V7 nor V9, and I got caught by this since I missed my code change to block it this past weekend.

Just curious, how are other installations set for DST and server clocks?
0
Jas

Senior Veteran
Registered:
Posts: 429
Reply with quote  #2 
Not sure if it helps but this is an excerpt from the v9.0 manual -

The way the Metastorm Process Engine handles Time Zone adjustments has changed from version 7.x. In
version 9.0 Time Zone adjustments is done by the Engine and is calculated as the difference between the
browser client and the Database management System (DBMS) server time.
This means that if the browser machine is in a timezone +2 hours ahead of the DBMS machine and is also
10 minutes fast then, then the extra 10 minutes will also be reflected in the time displayed to the client.
For this reason we recommend the time of a service is not changed while users are offline. Although not
essential, we also recommend that all Engine servers in a service are time-synchronized with the database
server in case user-defined server side scripts make use of .NET date/time or calendar types.

It is essential that Daylight Saving Time is disabled for the DBMS server. However if a service needs to support only users in a single time zone, or many time zones for which Daylight Saving Time is always applied on the same date (such as in the European Union), Daylight Saving Time can still be applied on the Engines in that service.
0
Nils

Member
Registered:
Posts: 23
Reply with quote  #3 
You might also be interested in the following bug:

If you have a timed loopback action on a stage that is timed to the future and is triggered before a daylight saving event, this action will be called continuously for an hour or so. 
This is especially annoying, if you send emails in this action (happened to us - 95k mails!!!). 

Be aware of this error, it is extremely annoying.


0
BMellert

Guru
Registered:
Posts: 688
Reply with quote  #4 
Yea, we got caught by that once on an action I forgot to put a "blocker" in.  (It also happens of the DB and engine server clocks get slightly out of sync if not accounted for.)

In my case I built a "blocker" action which checks to see if the current timed action had run within the past 10 minutes, and if so don't execute the action again.  Wouldn't necessarily take care of the 1 hour difference, but at least if something happened again the user may get 6 messages verses hundreds.
0
JoeOmerta

Veteran
Registered:
Posts: 210
Reply with quote  #5 
I coded all my email alerts to send only once per action to prevent things like that.  After the head of HR and CFO receive over 15k emails you come up with a fix pretty quick :)
0
BMellert

Guru
Registered:
Posts: 688
Reply with quote  #6 
I hear ya Joe.  I did something similar a while ago, but alas I missed one timed email reminder (in November's time change).
Needless to say, its something I recheck on every timed email ... speaking of which, I just added one I have to add the block condition to....
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:


Create your own forum with Website Toolbox!