PI11856: DEPLOYMENT OF BATCH APPLICATION FROM RAD DOESN'T CAUSE TARGET SERVER TO BE ESTABLISHED AS GRID ENDPOINT.

Fixes are available

APAR status

Closed as program error.

Error description

Deployment of batch application from Rational Application
Developer doesn't cause target server to be established as a
"grid endpoint"  (capable of having jobs dispatched from the job
 scheduler).

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of WebSphere Extended Deployment      *
*                  Compute Grid 8.0 and the batch function     *
*                  of WebSphere Application Server 8.5,        *
*                  especially those using the Rational         *
*                  Application Developer batch tooling.        *
****************************************************************
* PROBLEM DESCRIPTION: Jobs submitted to job scheduler         *
*                      are not dispatched to the endpoint      *
*                      server, though it's active with the     *
*                      application started.                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The batch function in WebSphere Compute Grid 8.0 and WebSphere
Application Server 8.5 uses a hook into application install to
automatically configure an application server as a "grid
endpoint".  This configuration of a server as a "grid
endpoint" allows the batch "job scheduler" function to
dispatch jobs submitted to the scheduler to execute on the
"endpoint" server.
A bug existed in this application install routine such that,
when an application was deployed to a server using the
Rational Application Developer (RAD) batch function, the
server was not correctly configured as a "grid endpoint".
The symptom would be that the job, once submitted to the job
scheduler, would fail to be dispatched.
In the scheduler-side job log, the following message would
appear:
CWLRS6016I: Job cannot be dispatched at this moment. Make
sure the endpoint is active and the job application is started
and the HTTP ports are active. Job is waiting for an active
endpoint.
One more symptom to observe would be in the Administrative
Console.  Under the section:
System Administration->Job scheduler -> WebSphere grid
endpoints
the server in question would not be listed, (since it had
never been configured as a "grid endpoint".
Finally, the problem could occur outside of a RAD scenario, if
a batch application were deployed using certain values
including '*' (acting as a wild card) along with the
-MapModulesToServers option.

Problem conclusion

The application install routine was fixed to correctly detect
the batch application and configure the endpoint as a "grid
endpoint".

APAR PI11856 is currently targeted for inclusion in Service
Level (Fix Pack) 8.0.0.4 of WebSphere Compute Grid 8.0 and
8.5.5.2 of WebSphere Application Server.

Please refer to the Recommended Updates page for delivery
information:
http://www.ibm.com/support/docview.wss?uid=swg27022998 or
http://www.ibm.com/support/docview.wss?uid=swg27036319

Temporary fix

An interim fix is available upon request.

Comments

APAR Information

APAR number
PI11856
Reported component name
WXD COMPUTE GRI
Reported component ID
5725C9301
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-02-17
Closed date
2014-04-08
Last modified date
2014-05-21

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
WXD COMPUTE GRI
Fixed component ID
5725C9301

Applicable component levels

R800 PSY
UP

[{"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SSFVRM","label":"WebSphere Extended Deployment Compute Grid"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0"}]

Document Information

Modified date:
28 April 2022

Tips

PI11856: DEPLOYMENT OF BATCH APPLICATION FROM RAD DOESN'T CAUSE TARGET SERVER TO BE ESTABLISHED AS GRID ENDPOINT.

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

R800 PSY

Document Information

Share your feedback

Need support?