PK86340: THE ISAPPREADY COMMAND RETURNS FALSE, WHEN THE APPLICATION IS MAPPED TO WEBSERVER.

Fixes are available

APAR status

Closed as program error.

Error description

The wsadmin "isAppReady" command returns "false" when the
application is mapped to only a WebServer on a node in version
6.1.0.23. It fails when it's mapped only to the WebServer
server on a node. If it mapped to any other appServer on the
same node, it returns correct status.

Local fix

```
n/a
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server version 6.0.2, 6.1 and 7.0           *
****************************************************************
* PROBLEM DESCRIPTION: The isAppReady() command returns the    *
*                      wrong status for applications having    *
*                      a target node which contains only Web   *
*                      server targets.                         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Node synchroniziation behavior was previously changed to not
distribute application binaries to nodes which contained only
Web server targets for the application.  This change adversely
affected the isAppReady command, causing it to never return a
status of true if one of the application's target nodes
contained only Web server targets.

Problem conclusion

The default node synchronization behavior has been reverted
back to its original behavior.  However, users, through a
property setting, can now control whether or not application
binaries are distributed to target nodes in which the
application only targets Web servers.  If the property,
com.ibm.websphere.management.nodesync.skipWebServerTarget, is
set to a value of "true", application binaries will not be
distributed to target nodes which contain only Web server
targets.  A value of "false" causes the application binaries
to be distributed to those nodes, which again is the default
behavior.  In order to make isAppReady function correctly with
either application distribution choice, the command ignores
nodes containing only Web server targets if the property is
set to true.  System behavior is not affected, and never was
affected, by this change or the node synchronization change
leading to this change for target nodes which contain
application server targets, whether or not any Web server
targets are also included on that same node.

The sample output below illustrates isAppReady output
generated for Web-server-only target nodes when the above
property is set to true:

wsadmin>$AdminApp isAppReady SuperSnoop
ADMA5071I: Distribution status check started for application
SuperSnoop.
WebSphere:cell=BRODIECell10,node=BRODIENode30,distribution=true,
expansion=skipped
ADMA5011I: The cleanup of the temp directory for application
SuperSnoop is complete.
ADMA5072I: Distribution status check completed for application
SuperSnoop.
true

To change node synchronziation behavior from the adminatrative
console:

1)  Navigate to System administration -> Deployment manager
--> Java and Process Management --> Process Definition -->
Java Virtual Machine -> Custom Properties
2) Define a property setting as follows:
Name :
com.ibm.websphere.management.nodesync.skipWebServerTarget
Value : true/false
3) Restart the dmgr.

To change node synchronization behavior from wsadmin:
1) Start wsadmin.bat in the
<websphere_install>/profiles/<dmgr_profile>/bin directory
either in jython or jacl (the example is in jython).
2) Issue the following command (replace <dmgrNode> with the
name of the dmgr's node and the property value can be
true/false):
wsadmin>AdminTask.setJVMSystemProperties('[-serverName
dmgr -nodeName <dmgrNode> -propertyName
com.ibm.websphere.management.nodesync.skipWebServerTarget
-propertyValue true]')
3) Restart the dmgr.


The fix for this APAR is currently targeted for inclusion in
fix pack 6.0.2.39, 6.1.0.29 and 7.0.0.7. 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
PK86340
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61I
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-05-11
Closed date
2009-08-05
Last modified date
2009-10-05

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

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"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:
29 December 2021

Tips

PK86340: THE ISAPPREADY COMMAND RETURNS FALSE, WHEN THE APPLICATION IS MAPPED TO WEBSERVER.

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

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?