Start Date issue in Timer Process for every application on one particular domain which has to do with region/locale of the machine.

Start Date issue in Timer Process for every application on one particular domain which has to do with region/locale of the machine.

book

Article ID: KB0093032

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix BusinessWorks -
Not Applicable -

Description

Description:
The same timer process could work on one machine but fails on another, reporting that the "start time" GV value given is not in the right format.

Symptoms:
The same timer process works on one machine but fails on another, reporting that the "start time" GV value given is not in the right format. The GV has a value resembling the following:  "2004 Apr 28 20:35:11 EST".  If changing the region -> format (drop down list) to "English (United States)" on the Windows machine where the timer process failed, it now works.

Cause:
JVM would use the machine locale when it starts up if no property is specified. Then the JVM would not be affected if the machine locale changed after the JVM is started. On the failed Windows machine, the "region -> format(drop down list)" is using "Chinease(RPC)". Changing to "English (United States)" and restart Designer to make it work.

Resolution

Set the following property in the .tra files to resolve this issue.


java.property.user.language=en

Or: 


java.extended.properties=-Duser.language=en


The other property is "java.property.user.region=US" or "-Duser.region=US", but these could be ignored since thwy may help other timer issues.

Issue/Introduction

Start Date issue in Timer Process for every application on one particular domain which has to do with region/locale of the machine.