IBM Support

PI35285: WSWS7027E AND WSWS7054E ERRORS (WSDL FILE COULD NOT BE GENERATED) MAY OCCUR DURING WEB SERVICE DEPLOYMENT OR STARTUP

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Due to a change introduced by APAR PI05855, the following
    problem may occur after WebSphere Application Server is upgraded
    to V7.0.0.33, V8.0.0.9, V8.5.5.2, or later fix packs that do
    not include the fix for this APAR.
    
    Applications containing Web Services may fail during application
    deployment or may fail to start due to an error generating a
    WSDL file.  The following error may be seen in the
    SystemOut.log:
    
    WSWS7027E: JAX-WS Service Descriptions could not be correctly
    built because of the following error:
    javax.xml.ws.WebServiceException: WSWS7054E: The Web Services
    Description Language (WSDL) file could not be generated for the
    com.mycompany.mypackage.MyService Web service implementation
    class because of the following error: java.lang.Exception: A
    WSDL Definition could not be generated for the implementation
    class: com.mycompany.mypackage.MyService
        at
    com.ibm.ws.websvcs.wsdl.WASWSDLGenerator.generateWsdl(WASWSDLGen
    erator.java:245)
        at
    org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.
    generateWSDL(EndpointDescriptionImpl.java:1958)
        at
    org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.
    <init>(EndpointDescriptionImpl.java:422)
    ...
    Caused by: java.lang.Exception: A WSDL Definition could not be
    generated for the implementation class:
    com.mycompany.mypackage.MyService
        at
    com.ibm.ws.websvcs.wsdl.WASWSDLGenerator.generateWsdl(WASWSDLGen
    erator.java:225)
        ... 19 more
    

Local fix

  • The problem can be avoided by configuring all of the dependency
    JAR files of the ServiceImpl class on the classpath attribute of
    the MANIFEST.MF of the module (WAR or EJB JAR).
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server users of   *
    *                  JAX-WS web service applications             *
    ****************************************************************
    * PROBLEM DESCRIPTION: Applications containing JAX-WS Web      *
    *                      Services may fail during deployment     *
    *                      or startup due to an error generating   *
    *                      a WSDL file.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    For a performance improvement, APAR PI05855 changes the
    strategy of module extraction when generating a WSDL file.
    Only the JARs specified in the MANIFEST classpath of the WAR
    or EJB JAR module containing JAX-WS web services will be
    extracted during WSDL generation.
    

Problem conclusion

  • Add a JVM custom property
    "com.ibm.websphere.webservices.ExtractEntireModuleForWsgen" and
    set it to "true" to restore the old behavior before
    APAR PI05855. The default value of this property is false.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.39, 8.0.0.11 and 8.5.5.6.  Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • Configure all the dependency JARs of JAX-WS implementation
    class in the the MANIFEST classpath of the WAR or EJB JAR
    module containing JAX-WS web services.
    

Comments

APAR Information

  • APAR number

    PI35285

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-02-18

  • Closed date

    2015-03-17

  • Last modified date

    2015-03-17

  • 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

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PI35285

Modified date: 17 March 2015