IBM Support

PK49029: IN WSAS RUNTIME SERVER FAILS TO START AFTER ASSOCIATING SHARED LIBRARY WITH AN ENTERPRISE APPLICATION.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In IBMᄅ Rationalᄅ Application Developer (RAD), when you are
    associating a shared library with an enterprise application
    module through the Administrative Console interface of the
    WebSphereᄅ Application Server (WAS) Test Environment version
    6.1, you receive the following error message:
    
    com.ibm.websphere.management.exception.AdminException: ADMA017EE
    
    Cause
    This message indicates that the Admin Console failed to find
    necessary metadata for the EAR and therefore could not complete
    the operation.
    
    This most likely occurs when an EAR is published to the
    WebSphere Test Environment 6.1 using RAD when the server is set
    to "Run server with resources in the workspace" as well as
    "Minimize application files copied to the server".
    

Local fix

  • Workaround:
    -----------
    Alter the server settings to ensure that the necessary metadata
    is copied to the server so that the Admin Console can operate
    properly:
    
       1. In the Servers view, double-click the server on which the
          application is being published
       2. The Server Overview editor comes up. In the Publishing
          section, uncheck the option, "Minimize application files
          copied to the server"
       3. Save the changes (Ctrl+S)
       4. Remove your project from the server.
       5. Add your project to the server for the new changes to take
          effect.
    
    
    After performing these steps you should be able to associate a
    shared library with your enterprise application using the
    WebSphere Admin Console.
    
    Microsoftᄅ Windows users might find that after associating a
    shared library with your application with the Admin Console a
    server restarting can throw the following error:
    
          WSVR0501E: Error creating component
    com.ibm.ws.runtime.component.ApplicationMgrImpl@5d125d12
          com.ibm.ws.exception.RuntimeWarning:
    com.ibm.ws.exception.ConfigurationWarning: Multiple
    ConfigurationWarning exceptions encountered
          at
    com.ibm.ws.runtime.component.ApplicationMgrImpl.start(Applicatio
    nMgrImpl.java:550)
          at
    com.ibm.ws.runtime.component.ContainerImpl.startComponents(Conta
    inerImpl.java:977)
          at
    com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.j
    ava:673)
          ...
    
    
    Subsequent attempts to manually start the application through
    the Admin Console will also fail.
    
    This is because when the Admin Console saves the shared lib
    association, it also rewrites some configuration data in an
    incorrect format which causes the application to fail to start.
    The only solution at the time of writing is to manually edit the
    deployment.xml file in the server's configuration directory to
    use the correct format which will allow the application to start
    successfully:
    
       1. Using Windows Explorer (or your preferred file manager)
          navigate to the WebSphere Test Environment directory.
          Assuming a default installation:
    
          C:\Program
    Files\IBM\SDP70\runtimes\base_v61\profiles\AppSrv01\config\cells
    \<cellName>\applications\<AppName>.ear\deployments\<AppName>
    
       2. Open up deployment.xml in a text editor. Locate the XML
          attribute, binariesURL on the <deployedObject> element,
          for examle:
    
          <deployedObject binariesURL="C:/MyWorkspace/MyEAR" ...
    
    Notice the path is specified with forward slashes instead
    of the Windows standard backward slashes as directory
    delimiters.
    
       3. Change the forward slashes to backward slashes as in the
          following:
    
          <deployedObject binariesURL="C:\MyWorkspace\MyEAR" ...
       4. Save the file.
       5. From the Admin Console you can now start your application.
          Assuming you make no further changes to the application's
          metadata through the Admin Console, the next time you
          restart the test environment the application should start
          correctly.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IBM WebSphere Application Server    *
    *                 version 6.1 who may be deploying             *
    *                 applications through Rational Application    *
    *                 Developer 7.0 and needing to configure       *
    *                 shared libraries.                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: Deploying applications with Rational    *
    *                      Application Developer 7.0 may fail      *
    *                      upon server restart when                *
    *                      user-specified libraries can not be     *
    *                      found.                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    You may develop and deploy an application in Rational
    Application Developer 7.0. You may also use the
    administrative functions of WebSphere Application Server to
    define shared libraries. When both of these scenarios are
    employed, you may not be able to restart the server
    because of the following error:
    
       WSVR0501E: Error creating component
    com.ibm.ws.runtime.component.ApplicationMgrImpl
    

Problem conclusion

  • WebSphere Application Server is not handling the folder
    separator character correctly for when these scenarios are
    used. Code has been changed to handle this correctly.
    
    The fix for this APAR is currently targeted for inclusion
    in fix pack 6.1.0.13.
    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

    PK49029

  • Reported component name

    WEBSPH APP SERV

  • Reported component ID

    5724J0800

  • Reported release

    61W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-07-16

  • Closed date

    2007-10-31

  • Last modified date

    2007-10-31

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • WCCM
    

Fix information

  • Fixed component name

    WEBSPH APP SERV

  • Fixed component ID

    5724J0800

Applicable component levels

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z 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