PM88520: DEPLOYMENT FAILS WHEN APPLICATION UPGRADED BY THE APPLICATION SERVER

Fixes are available

APAR status

Closed as program error.

Error description

Environment:

WebSphere Application Server V8.5 on Linux

Problem Description:

WebSphere Application Server is upgrading the Java EE version
of the application. This causes the deployment of the
application to fail when it is deployed from a deployment
manager to a node running a version of WebSphere Application
Server that implements a lower Java EE level.

Local fix

```
Local Fix:

None
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0 who are upgrading to V8.0 or    *
*                  V8.5 and who also have applications         *
*                  containing EJBs that have no interface.     *
****************************************************************
* PROBLEM DESCRIPTION: The installation fails when installing  *
*                      an application from a WebSphere         *
*                      Application Server V8.0 or V8.5         *
*                      deployment manager to a node running    *
*                      WebSphere Application Server V7.0.      *
****************************************************************
* RECOMMENDATION:  If you encounter this problem, first        *
*                  examine the bean to see if it truly has no  *
*                  interface.  If it has no interface, you     *
*                  should consider whether the bean can be     *
*                  removed from the application, as it may     *
*                  not have any value.                         *
****************************************************************
The installation fails because the application is upgraded
from Java EE 5.0 to Java EE 6.0 during installation.  The
upgrade occurs when no interface is found on an EJB 3.0 bean.
The code interprets this as an EJB 3.1 "No-interface view",
and it upgrades the EJB version and the application version
accordingly.  Once the application is upgraded, it is no
longer deployable to a node running WebSphere Application
Server V7.0.

Problem conclusion

This apar allows the usage of a custom property,
"org.eclipse.jst.j2ee.commonarchivecore.ignore.no.interface.view
=true".  Setting the property to true will prevent the
application from being upgraded when it contains a bean with
no interface.  The default value is false.

An option at the application level is also provided.
Adding the following to the application META-INF/MANIFEST.MF
file will also prevent the application upgrade:

Ignore-No-Interface-View: true


The fix for this APAR is currently targeted for inclusion in
fix packs 8.0.0.8 and 8.5.5.1.  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
PM88520
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-05-06
Closed date
2013-06-19
Last modified date
2013-07-18

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

R800 PSY
UP
R850 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":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
12 January 2022

Tips

PM88520: DEPLOYMENT FAILS WHEN APPLICATION UPGRADED BY THE APPLICATION SERVER

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

R850 PSY

Document Information

Share your feedback

Need support?