IBM Support

PM56963: GETDEPLOYMENTDESCRIPTOR USES INCORRECT APPLICATION PATH

Fixes are available

8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Problem :
    getDeploymentDescriptor uses incorrect application path
    
    The path to the .ear that is used for this is pointing to the
    resources directory of the deployed application. That would be
    the WSAS_HOME/profiles/<appserver>/config/.../applications
    directory.
    This path only contains the metadata files for the application
    though. The class files are located in a separate path, under
    the WSAS_HOME/profiles/<appserver>/installedApps..  directory.
    During the open of the application, a list of files in the
    application is generated, and nested archives are identified
    and typed. During the process of typing the TestEJB.jar
    archive, since there is no deployment descriptor, the
    discrimination process examines the class files looking for
    annotations which would identify it as an EJB jar. Since there
    are no class files found, there is nothing to indicate that
    this is an EJB jar so it  is identified as a simple file. That
    ultimately leads to the reported error.
    
    Error :
    WARNING: ADMC0046W
    Dec 6, 2011 3:54:39 PM
    com.ibm.ws.management.connector.interop.JMXClassLoader
    WARNING: Could not find aaaaaaa.jar in
    null/etc/aaaaaaa.jar - Inte
    roperability to older versions of WebSphere is disabled
    Dec 6, 2011 3:54:39 PM com.ibm.ws.ssl.config.SSLConfigManager
    INFO: ssl.disable.url.hostname.verification.CWPKI0027I
    War: TestWeb.war @ Server: server1
    scanning the application...
    javax.management.MBeanException: RuntimeException thrown in
    RequiredModelMBean while trying to invoke operation
    getDeploymentDescriptor
    at
    com.ibm.ws.management.connector.soap.SOAPConnectorClient.handleA
    dminFault(SOAPConnectorClient.java:948)
    at
    com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeT
    emplateOnce(SOAPConnectorClient.java:916)
    at
    com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeT
    emplate(SOAPConnectorClient.java:682)
    at
    com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeT
    emplate(SOAPConnectorClient.java:672)
    at
    com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(
    SOAPConnectorClient.java:658)
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0 and V8.0                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: getDeploymentDescriptor uses the        *
    *                      incorrect location for application      *
    *                      binaries                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The Deployed Object MBean's getDeploymentDescriptor method was
    using data from the application's metadata resource location,
    rather than the binaries location.  This caused issues with
    applications that did not have XML deployment descriptors, as
    their binaries were not scanned.
    

Problem conclusion

  • The method was updated to utilize the binaries location
    instead of the metadata location.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.25 and 8.0.0.4.  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

    PM56963

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-01-30

  • Closed date

    2012-03-29

  • Last modified date

    2012-03-29

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R700 PSY

       UP

  • R800 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 8.0

Reference #: PM56963

Modified date: 29 March 2012