PQ73674: WEBSPHERE AAT390 CAUSES EAR FILE TO GROW EXPONENTIALLY WITH EACHDEPLOYMENT

APAR status
Closed as fixed if next.

Error description
When the customer imports, deploys and exports a particular ear
file via the AAT, it grows exponentially in size with every
deployment.  For example, the size of the ibm-ejb-jar-ext.xmi
member in the ear was initially 47,397.  After the first import,
deployment and export of the ear, it's size increased to 93,315.
After importing, deploying and exporting this resultant ear,
it's size increased from 93,315 to 139,233.  This growth appears
to be occuring in the </runAsSettings> tag.  After each
deployment, the xmi contains many more methodElements.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 version 4.0.1 for z/OS and OS/390            *
****************************************************************
* PROBLEM DESCRIPTION: WebSphere for zOS AAT 32 causes EAR     *
*                      file to grow with each deployment.      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When the customer imports, deploys and exports a particular ear
file via the AAT, it grows in size with every deployment.
For example, the size of the ibm-ejb-jar-ext.xmi member in the
ear was initially 47,397 bytes. After the first import,
deployment and export of the ear, it's size increased to 93,315
bytes. After importing, deploying and exporting this resultant
ear, it's size increased from 93,315 to 139,233.

WebSphere for zOS AAT 32 introduced a bi-directional conversion
error which always regenerated the same metadata every time the
EAR file was deployed and left the older metadata in as well.
Although this does not cause any runtime problems since
duplicate metadata entry is ignored during retrieval processing,
it caused an EAR file with method level metadata attribute to
increase in size each time it is deployed.
Problem conclusion Temporary fix Comments
This APAR is being closed FIN with concurrence from the
submitting customer. A solution to this problem will be
delivered in a WebSphere Application Server for z/OS
and OS/390 release within the next 18 months.
APAR information
APAR number PQ73674
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED FIN
PE NoPE
HIPER NoHIPER
Submitted date 2003-04-29
Closed date 2003-10-30
Last modified date 2003-10-30

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Fix information

Applicable component levels
R401 PSN    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ73674
IBM Group: Software Group
Modified date: Oct 30, 2003