IBM Support

PK87845: WEB SERVICES NOTIFICATION RETURNS INCORRECT SUB RESPONSE EPR IN CLUSTER

Fixes are available

7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for AIX
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for IBM i
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Windows
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for HP-UX
7.0.0.5: Java SDK 1.6 SR5 Cumulative Fix for WebSphere Application Server
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Solaris
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Linux
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for IBM i
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for AIX
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Windows
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for HP-UX
7.0.0.7: Java SDK 1.6 SR6 Cumulative Fix for WebSphere Application Server
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Solaris
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Linux
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for IBM i
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Windows
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for AIX
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for HP-UX
7.0.0.9: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Solaris
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Linux
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An extended test that used Web Sservices Notifcation ( WSN )
    /Web Services Reliable Messaging  ( WSRM )in a clustered
    environment with the WSN broker fronted by a WebSphere
    Application Server proxy running on port 80. with a a seperate
    single-server machine hosting the WSN consumerand publisher
    applications. When an attempt to unsubscribe my consumer
    application from the broker was tried the following FFDC on the
    
    consumer AppServer was observed:
    
    FFDC Exception:org.apache.axis2.AxisFault SourceId:com.ibm.ws.w
    ebsvcs.transport.http.SOAPOverHTTPSender.sendChunkedRequest Pro
    beId:552 Reporter:com.ibm.ws.websvcs.transport.http.SOAPOverHTT
    PSender@19791979
    org.apache.axis2.AxisFault: WSWS7095E: An incorrect -1 HTTP
    port value was specified within the URL http://p6tpm04e.hursley
    .ibm.com:-1/TestWSNServiceTestWSNServicePointSM/Service
    at com.ibm.ws.websvcs.transport.http.SOAPOverHTTPSender.prepare
    HttpRequestHeaders(SOAPOverHTTPSender.java:2228)
    ...
    more
    
    The consumer picked up the URI of the broker from the
    SubscriberResponse message (returned at the time the
    subscription was made, and then stored). In this case it
    appeared that the broker incorrectly returned "-1" for the port
    
    number of the broker, when is should in fact have returned "80".
    
    
    I have traced the client and both cluster members and noticed
    this error in the second cluster member trace which appears to
    show the error coming from the WSN broker code:
    
    00000033 WSNMarshaller 3   (com.ibm.ws.sib.wsn.webservices.util
    s.WSNMarshallerImpl) [:] Encoding endpoint reference Address[[h
    ttp://p6tpm04e.hursley.ibm.com:-1/TestWSNServiceTestWSNServiceP
    ointSM/Service]], ReferenceParams[<subscriptionId xmlns="http:/
    /www.ibm.com/websphere/wsn/reference">sub_d092bef11a37000c16912
    6e9_1215498fbb5_1</subscriptionId><wsaucf:RoutingInformation xm
    lns:wsaucf="http://ucf.wsaddressing.ws.ibm.com"><wsaucf:HAClust
    erId xmlns:wsaucf="http://ucf.wsaddressing.ws.ibm.com">00000000
    020004747970650010575341465f5349425f4d455f555549440004757569640
    01035323231433537344545304237453735</wsaucf:HAClusterId></wsauc
    f:RoutingInformation><wsaucf:IntermediaryPresent xmlns:wsaucf="
    http://ucf.wsaddressing.ws.ibm.com">1</wsaucf:IntermediaryPrese
    nt><messagingEngineUuid xmlns="http://www.ibm.com/websphere/wsn
    /reference">5221C574EE0B7E75</messagingEngineUuid><wsaucf:Virtu
    alHostName xmlns:wsaucf="http://ucf.wsaddressing.ws.ibm.com">de
    fault_host</wsaucf:VirtualHostName>],MetaData[ServiceName[[{htt
    p://www.ibm.com/websphere/wsn/subscription-manager}TestWSNServi
    ceTestWSNServicePointSM,SubscriptionManagerPort]]]
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All IBM WebSphere Application Server V7.0   *
    *                  users of Web Services Addressing.           *
    ****************************************************************
    * PROBLEM DESCRIPTION: Message WSWS7095E was produced after    *
    *                      entering a HTTP URL prefix with no      *
    *                      port number.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    After entering a HTTP URL prefix without a port in the
    ?Provide HTTP endpoint URL information? for the application
    the following fault and message was received:
    
    Org.apache.axis2.Axisfault: WSWS7095E: An incorrect -1 HTTP
    port value was specified within the URL <url>
    

Problem conclusion

  • The Web Services Addressing ( WS-Addressing ) service will be
    changed to prevent the AxisFault if the user enters a HTTP URL
    prefix without a port in the ?Provide endpoint URL
    information? for the application.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.5.  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

    PK87845

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-06-03

  • Closed date

    2009-06-17

  • Last modified date

    2009-06-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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R700 PSY

       UP

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

Document Information

Modified date:
25 October 2021