PQ46483: XMLCONFIG CHANGING LTPA TIMEOUT VALUES ON EXPORT


APAR

APAR status
Closed as program error.

Error description
The following is what I observed:
1. I set the token expiration to "45". The GUI indicates this is
   measured in minutes. 45 minutes is equal to 2700 seconds.
2. Upon the export, it changed the value to 2700000. It appears
   to have converted the 45 minutes to seconds and multiplied it
   by 1000.
3. I then imported the xml file.
4. I then did another Full XMLConfig export and the value was
   set to 162000000000. It had multiplied the previous value
   (2700000) times
   60 and then by 1000.
The following is what I observed:1. I set the token expiration to "45". The GUI indicates this ismeasured in minutes. 45 minutes is equal to 2700 seconds.2. Upon the export, it changed the value to 2700000. It appearsto have converted the 45 minutes to seconds and multiplied itby 1000.3. I then imported the xml file.4. I then did another Full XMLConfig export and the value wasset to 162000000000. It had multiplied the previous value(2700000) times60 and then by 1000.
Local fix
UPON A FULL XMLCONFIG EXPORT, XMLCONFIG CHANGES THE VALUE OF
THE LTPA TOKEN EXPIRATION BY MULTIPLYING THE ORIGINAL VALUE BY
60000.  THIS HAPPENS ON EACH EXPORT.  WHEN IMPORTING THE FILE,
XMLCONFIG DOES NOT CHANGE THIS NUMBER.
Problem summary
The following is what I observed:
1. I set the token expiration to "45". The GUI indicates this is
   measured in minutes. 45 minutes is equal to 2700 seconds.
2. Upon the export, it changed the value to 2700000. It appears
   to have converted the 45 minutes to seconds and multiplied it
   by 1000.
3. I then imported the xml file.
4. I then did another Full XMLConfig export and the value was
   set to 162000000000. It had multiplied the previous value
   (2700000) times
   60 and then by 1000.
LOCAL FIX:The following is what I observed:1. I set the token expiration to "45". The GUI indicates this ismeasured in minutes. 45 minutes is equal to 2700 seconds.2. Upon the export, it changed the value to 2700000. It appearsto have converted the 45 minutes to seconds and multiplied itby 1000.3. I then imported the xml file.4. I then did another Full XMLConfig export and the value wasset to 162000000000. It had multiplied the previous value(2700000) times60 and then by 1000.
UPON A FULL XMLCONFIG EXPORT, XMLCONFIG CHANGES THE VALUE OF THE LTPA TOKEN EXPIRATION BY MULTIPLYING THE ORIGINAL VALUE BY 60000. THIS HAPPENS ON EACH EXPORT. WHEN IMPORTING THE FILE, XMLCONFIG DOES NOT CHANGE THIS NUMBER.
LOCAL FIX:UPON A FULL XMLCONFIG EXPORT, XMLCONFIG CHANGES THE VALUE OFTHE LTPA TOKEN EXPIRATION BY MULTIPLYING THE ORIGINAL VALUE BY60000. THIS HAPPENS ON EACH EXPORT. WHEN IMPORTING THE FILE,XMLCONFIG DOES NOT CHANGE THIS NUMBER.
Problem conclusion
XMLConfig code fixed to solve this issue.
Temporary fix
Comments
APAR information
APAR numberPQ46483
Reported component nameWAS ADVANCED AI
Reported component ID5648C8400
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2001-02-28
Closed date2001-03-19
Last modified date2001-03-19

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:


Modules/Macros
XMLCFG
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information
Fixed component nameWAS ADVANCED AI
Fixed component ID5648C8400

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ46483
IBM Group: Software Group
Modified date: 2001-03-19