IBM Support

PI32791: WORKLIGHT CONSOLE DOESN'T WITH LIBERTY IF THE 'WASJMSSERVER-1.0'FEATURE IS ENABLED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The Worklight console fails to display the runtimes when the
    'wasJmsServer-1.0'  feature is enabled in the Liberty server.xml
    file.
    The endpoint detection of the management service takes the JMS
    port number instead of the http or https port number.
    In the Liberty messages.log files,  messages show the the ping
    service fails due to the use of the wrong port number. For
    example :
    
    Accessing the ping service
    http://localhost:7276/worklightadmin/ping
    I/O exception (org.apache.http.NoHttpResponseException) caught
    when processing request to {}->http://localhost:7276: The target
    server failed to respond
    

Local fix

  • Workaround is to add the following JNDI properties in the
    Liberty server.xml file : ibm.worklight.admin.proxy.protocol,
    ibm.worklight.admin.proxy.host,
    ibm.worklight.admin.proxy.protocol.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Worklight console users                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * WORKLIGHT CONSOLE FAILS IN LIBERTY IF THE 'WASJMSSERVER-1.0  *
    * 'FEATURE IS ENABLED                                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * -                                                            *
    ****************************************************************
    

Problem conclusion

  • The Worklight console fails to display the runtimes when the
    'wasJmsServer-1.0'  feature is enabled in the Liberty server.xml
    file.
    The endpoint detection of the management service takes the JMS
    port number instead of the http or https port number.
    In the Liberty messages.log filesmessages show that the ping
    service fails due to the use of the wrong port number. For
    example :
    
    Accessing the ping service
    http://localhost:7276/worklightadmin/ping
    I/O exception (org.apache.http.NoHttpResponseException) caught
    when processing request to {}->http://localhost:7276: The target
    server failed to respond.
    
    The fix detects the use of the 'wasJmsServer-1.0'  feature and
    takes the http or https endpoint when pinging the management
    service.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI32791

  • Reported component name

    WL/MFPF CONSUME

  • Reported component ID

    5725I4301

  • Reported release

    620

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-01-15

  • Closed date

    2015-01-26

  • Last modified date

    2015-01-26

  • 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

    WL/MFPF CONSUME

  • Fixed component ID

    5725I4301

Applicable component levels

  • R620 PSY

       UP

  • R630 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSZH4A","label":"IBM Worklight"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"620","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 October 2021