PQ91774: SYNC COMMAND ISSUED VIA THE NODESYNC MBEAN DOES NOT FORCE A SYNCHRONIZATION

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
The customer is using the Java WSAdmin API to deploy ear files.
After the deployment completes, they issue a 'sync' command via
the NodeSync MBean to force a full synchronization.  The sync
returns 'true', but full synchronization does not take place.
The only way the customer was able to get the sync to take place
was by adding logic to his Java deployment application to issue
a 'refreshRepositoryEpoch' on the ConfigRepository MBean prior
to issuing the 'sync' on the NodeSync MBean.  The customer is
able to verify that full synchronization is not taking place
becaue the binaries are not copied.  This customer is running
WebSphere Application Server on the z/OS platform.
Local fix
To circumvent this problem the customer was able to disable the
Status Cache by setting the following JVM option in the
Controller and Servant regions:
    com.ibm.websphere.management.status.disable = true
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: After making a change to the            *
*                      configuration, Node Synchronization     *
*                      does not appear to have worked.         *
*                      No messages are seen as to its          *
*                      success or failure.                     *
*                      The configuration changes are           *
*                      not reflected on the AppServer          *
*                      nodes.                                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Configuration changes made using the administrative console or
wsadmin are not reflected in the AppServer's xml files even
after saving with Node Synchronization.
Problem conclusion
StatusCache code was holding the document checkin thread, while
the sync thread continued.  As a result Node Synchronization did
not detect any changed files.  The StatusCache code was modified
such that it will not cause the file checkin thread to wait,
allowing the files to be checked in and Node Synchronization
will detect the changes.

APAR PQ91774 is associated with SERVICE LEVEL W502016 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ91774
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-07-21
Closed date 2004-10-07
Last modified date 2004-11-01

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ93769    UP04/10/15 P F410

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PQ91774.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ91774
IBM Group: Software Group
Modified date: Nov 1, 2004