PM04278: WHEN 64 BITS IS USED, THE PREVIOUSLY FOUND MACHINE TYPE INFORMATION IS CACHED LOCALLY.

Fixes are available

APAR status

Closed as program error.

Error description

The root cause of the problem is that when 64 bits is used, the

previously found machine type information is cached locally.
For
example, after this message in a 64 bits machine,

NTRegistryImp 3   Native line 251: CreateNTInfo Local system :
XYZ

the subsequent attempt to get the domain name from the domain
controller
will try to get the server name from the cached info that was
created
for the local registry.  This will fail since the domain
controller was
not contacted for the server name when that info was created.

Local fix

Workaround:

Add the following custom property and set the value to the word
domain
com.ibm.websphere.registry.UseRegistry

for more details about setting the custom property, please see,

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?
topic=/c
om.ibm.websphere.nd.multiplatform.doc/info/ae/ae/csec_localos.ht
ml

This workaround will force the initialization of the domain user
registry only. The information will then be retrieved from the
domain
controller

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application Server
****************************************************************
* PROBLEM DESCRIPTION: WebSphere Application Server for        *
*                      Windows (R) 64 bit Operating System     *
*                      configured with LocalOS user registry   *
*                      fails to obtain the domain name from    *
*                      the domain controller.                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
WebSphere Application Server on a Windows (R) 64 bit machine
with LocalOS user registry cannot obtain the domain name from
the domain controller. The local machine domain name is used
instead.  The user fails to login.  This causes the
deployment manager or server process to fail startup since the
server subject cannot be created

The security code is caching machine information the
first time it contacts the local machine user registry when
the architecture is 64 bit. When the code attempts to find the
domain name from the controller, it finds the locally cached
machine information and it tries to find the domain name from
it, but it cannot find it.

Problem conclusion

The security code was modified to correctly find the domain
name from the domain controller when executing on a 64 bit
architecture.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.33 and 7.0.0.13.  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
PM04278
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-12-31
Closed date
2010-06-03
Last modified date
2010-09-23

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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R61H PSY
UP
R61W PSY
UP
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":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021

Tips

PM04278: WHEN 64 BITS IS USED, THE PREVIOUSLY FOUND MACHINE TYPE INFORMATION IS CACHED LOCALLY.

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

R61H PSY

R61W PSY

R700 PSY

Document Information

Share your feedback

Need support?