IBM Support

PI65924: PIPE "|" SYMBOL CANNOT BE USED FOR EXTERNAL PROVIDER URL WHEN CONFIGURING A 3RD PARTY JMS PROVIDER.

Fixes are available

9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
9.0.5.6: WebSphere Application Server traditional Version 9.0.5 Fix Pack 6

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When configuring a new 3rd party JMS Provider, such as Tibco,
    one of the required configuration parameters is "External
    provider URL".
    
    If a value is entered which contains a "|" (pipe) symbol, the
    administrative console will throw an error message when trying
    to save the value:
    "The field, External provider URL, does not contain a valid
    value."
    
    For example, the following External provider URL value would
    fail validation:
    
    ssl://my.jms.host.com:1234|ssl://my.jms.host2.com:5678
    
    Tibco requires the use of the "|" symbol as a delimiter in
    order to achieve load balancing.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere Application Server users of       *
    *                  third party JMS providers that require the  *
    *                  pipe symbol in the external provider URL    *
    *                  value.                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: A "|" character could not be            *
    *                      specified in the "External provider     *
    *                      URL" for a JMS Provider in the          *
    *                      administration console.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The administration console policed the value for the external
    provider URL ensuring it conformed to the specification of a
    valid URL.  Since the "|" character is not an allowed
    character of a URL it rejected the value.  However, some third
    party JMS provider client software allows non-valid URL
    characters as a means of configuring extended function.
    

Problem conclusion

  • The administration console was modified to allow a standard
    string value to be specified for the external provider URL.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.13, 8.5.5.11 and 9.0.0.2.  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

    PI65924

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-07-14

  • Closed date

    2016-11-15

  • Last modified date

    2016-11-15

  • 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

  • R800 PSY

       UP

  • R850 PSY

       UP

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
14 October 2021