PK71806: WsEjbDeploy Ant task may fail to compile the generated code WHEN RUN ON A WEBSPHERE APPLICATION SERVER RUNNING ON UNIX

Fixes are available

APAR status

Closed as program error.

Error description

The WebSphere Application Server Ant tasks parse the
setupCmdLine.sh file in order to determine the values of the
various WebSphere Application Server environment variables.
One of the variables, WAS_EXT_DIRS, does not get processed
properly and as a result the classpath for the Java compiler
that EJBDeploy uses is not setup correctly and results in the
generated deployment code to fail compilation.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of the WebSphere Application      *
*                  Server V6.1 and V7.0 Ant tasks on a UNIX    *
*                  platform.                                   *
****************************************************************
* PROBLEM DESCRIPTION: The Ant task launcher fails to          *
*                      resolve some WebSphere Application      *
*                      Server environment variables defined    *
*                      in the setupCmdLine script.             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The WebSphere Application Server Ant task launcher (ws_ant)
processes the setupCmdLine script before invoking any of the
available Ant tasks.  This is needed to ensure that all
variables defined in this script are also available to the Ant
task framework.  The logic for this parsing was designed to
stop parsing whenever the word 'case' was found as there was
never a reason (in past releases) to parse the file after this
word was found.  However, in WebSphere Application Server v6.1
and beyond there are additional varilables defined after the
first instance of the word 'case' and therefore are never
available to the Ant task framework.  This can cause problems
with launching certain Ant tasks, such as the WsEjbDeploy task,
because some variables are not available to the Ant task
framework and therefore are passed as null values to the
corresponding task being invoked.

Problem conclusion

The Ant task launcher will no longer stop parsing the
setupCmdLine script file when it reads a line that starts with
the word 'case'.

The fix for this APAR is currently targeted for inclusion in
fixpacks 6.1.0.23 and 7.0.0.3.  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
PK71806
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61S
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-09-10
Closed date
2008-11-21
Last modified date
2009-03-12

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

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S 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

PK71806: WsEjbDeploy Ant task may fail to compile the generated code WHEN RUN ON A WEBSPHERE APPLICATION SERVER RUNNING ON UNIX

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?