PK98999; 7.0.0.5: replacing a module using fine grained application update fails

Download Description

PK98999 resolves the following problem:

ERROR DESCRIPTION:
Fine grained application update fails with the following error.

[9/29/09 3:17:00:859 CST] 0000001a AddBinaryTask 1 fineGrainUpdate
FFDC:
sourceId=com.ibm.ws.management.application.sync.AddBinaryTask.fineGrainU pdate, probeId=183

java.io.FileNotFoundException:

C:\IBM\WebSphere\AppServer\profiles\demo\installedApps\WC_demo_cell\WC_d emo.ear\LOBTools.war (Access is denied.)

at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
...
[9/29/09 3:17:00:937 CST] 0000001a AppBinaryProc E
Exception from run:
com.ibm.websphere.management.exception.AdminException:
AddBinaryTask failed on fineGrainUpdate.
...

This error occurs even if auto-start is turned off for applications.

LOCAL FIX:
N/A

PROBLEM SUMMARY

USERS AFFECTED:
All users of IBM WebSphere Application Server V6.1.0, V6.1.0 Feature Pack for Enterprise JavaBeans 3.0, and V7.0.0.

PROBLEM DESCRIPTION:
The Application Profile service is not closing EAR file resources.

RECOMMENDATION:
None

At WebSphere Application Server start-up, the Application Profile service opens all EAR files which are installed on the server. The Application Profile service leaves these EAR files open even though the service will not make use of them after server start-up, as such, they should be closed.

PROBLEM CONCLUSION:
With this fix, the Application Profile service will ensure that it closes an EAR file after it is done using the EAR file.

The fix for this APAR is currently targeted for inclusion in Service Levels (Fix Packs) 6.1.0.37, Enterprise JavaBeans 3.0 Feature Pack Fix Pack 37 (6.1.0.37), and 7.0.0.9 of WebSphere Application Server versions 6.1.0, and 7.0.0.

Please refer to the recommended updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980