IBM Support

PK69577: METADATALOADER READS INCORRECT SERVER.XML. RESULTS IN ERROR: LOADWEBCONTAINERPORTS COULD NOT FIND ANY HTTP OR HTTPS PORTS.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When starting a web services application, the engine might
    report this error to the JVM log:
    
    DualMetaDataLoade E loadWebContainerPorts could not find any
    http or https ports
    

Local fix

  • na
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Developers and administrators of WebSphere  *
    *                  Application Server V6 web services that     *
    *                  are installed on web servers.               *
    ****************************************************************
    * PROBLEM DESCRIPTION: The message "MetaDataLoade E            *
    *                      loadWebContainerPorts could not find    *
    *                      any http or https ports" might appear   *
    *                      in SystemOut.log.                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a web services application is started, the message
    "MetaDataLoade E loadWebContainerPorts could not find any http
    or https ports" might appear in the SystemOut.log file.
    However, when the web service is invoked, no problems are
    observed and it works as expected.
    
    The web services runtime might issue the false error message
    if the application is installed on both a web server and an
    application server. This configuration is valid.
    
    Note that the message could indicate a real problem if the
    application server where the web service is installed is
    somehow misconfigured.
    

Problem conclusion

  • Assuming that the web service's server configuration is valid,
    the message can be prevented from appearing in SystemOut.log by
    setting the com.ibm.ws.webservices.searchForAppServer
    property to true. For more details on how to perform
    this task, refer to the article "Java virtual machine
    custom properties" in the Information Center for your WebSphere
    Application Server version and operating system.
    
    The fix for this APAR is currently targeted for inclusion in
    fixpack 6.0.2.33 and 6.1.0.23.  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

    PK69577

  • Reported component name

    WEBSPH APP SERV

  • Reported component ID

    5724J0800

  • Reported release

    60I

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-07-25

  • Closed date

    2008-10-24

  • Last modified date

    2009-02-03

  • 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

    WEBSPH APP SERV

  • Fixed component ID

    5724J0800

Applicable component levels

  • R60A PSY

       UP

  • R60H PSY

       UP

  • R60I PSY

       UP

  • R60P PSY

       UP

  • R60S PSY

       UP

  • R60W PSY

       UP

  • R60Z PSY

       UP

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 October 2021