PK78762: PREVENT REGISTRATION OF MANAGED NODE WITH JOBMANAGER IF THE CLOCK IS NOT SYNCHRONIZED WITHIN 5 MINUTES OF EACH OTHER.

Fixes are available

APAR status

Closed as program error.

Error description

Jobs submitted to a managed node which is more than 5 minutes
off of JobManager are never run because of token expiration.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of IBM WebSphere Application Server   *
*                  V7 who use the job manager.                 *
****************************************************************
* PROBLEM DESCRIPTION: Registration to a job manager           *
*                      succeeds when system clocks             *
*                      are not synchronized, which can lead    *
*                      to failures.                            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When enrolling a deployment manager or application server node
to a job manager, there is no check that the system clocks of
the two machines are synchronized. If a managed node is
allowed to register with a job manager even when the clocks
are not in sync, then the authentication mechanism between job
manager and the managed node can fail in future
communications, and jobs submitted to that node may not be
run.

Problem conclusion

Registration with job manager has been modified to fail if
clocks are not in sync.

The code was updated so that when the job manager receives a
registration request, it will compare the timestamp in the
request to its own clock. If they differ by more than five
minutes, the registration will not succeed and an error
message will be displayed saying that the clocks are not
synchronized.

Please note that this does NOT prevent a node in one time zone
from registering with a job manager in a different time zone.
The time comparison is done using coordinated universal time
(UTC); thus system clocks should be in sync even when the
machines are in different time zones.

If a node that does not have this fix applied attempts to
register with a job manager that does have the fix applied,
the job manager will see that no timestamp is provided in the
registration request; thus no clock sync check will be made and
registration will succeed, regardless of any difference in
clocks.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.5.  Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK78762
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-01-15
Closed date
2009-04-09
Last modified date
2009-04-09

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

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PK78762: PREVENT REGISTRATION OF MANAGED NODE WITH JOBMANAGER IF THE CLOCK IS NOT SYNCHRONIZED WITHIN 5 MINUTES OF EACH OTHER.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?