IBM Support

PK56560: JAVA.NET.MALFORMEDURLEXCEPTION: UNKNOWN PROTOCOL: GENERATED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Same problem as RAD APAR PK56008 which states:
    Project fails when deployed from RAD v7 to WAS v6.1 using Debug
    mode, but works when it is using Normal mode.
    The DTD files containing ?!DOCTYPE? lines cannot be properly pro
    cessed.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: IBM Websphere Application Server version 6.1 *
    *                 users whose application performs XSLT        *
    *                 transformations using                        *
    *                 javax.xml.transformer.sax.SAXSource          *
    *                 during startup.                              *
    *                 Websphere Application Server users whose     *
    *                 application performs XSLT transformations    *
    *                 using custom entity resolver during          *
    *                 startup.                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Websphere Application Server fails to   *
    *                      start user applications properly if     *
    *                      the server is started in debug mode.    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    You will receive an error with the following error message
    during application startup:  java.net.MalformedURLException:
    unknown protocol: generated
    

Problem conclusion

  • A temporary file is generated to display the input SAXSource
    content during a debug session.  The filename used for this
    temporary file no longer starts with "generated:", which
    caused the XSLT transformation to fail at startup. Also, if
    the application has specified a custom entity resolver for the
    SAXSource, that resolver is now used rather than ignored.
    
    The fix for this APAR is currently targeted for inclusion
    in fix pack 6.1.0.15.
    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

    PK56560

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    61W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-11-14

  • Closed date

    2008-01-21

  • Last modified date

    2008-01-21

  • 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

  • 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