Fixes are available
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
PK98081; 7.0.0.7: outofmemoryerror may occur during long runs of web service app
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
APAR status
Closed as program error.
Error description
When a JAX-WS developer uses a @WebServiceRef, the JAX-WS runtime constructs a service for a managed client: @WebServiceRef(name=?service/FredsBankService?) FredsBankService service; <-- managed service If the developer directly initializes the service, the service then becomes a service for an unmanaged client: @WebServiceRef(name=?service/FredsBankService?) FredsBankService service; service = new FredsBankService(); // becomes unmanaged. The "overriddenEndpointURI" is a managed property that is normally set with the Administrative Console. Only services for managed clients should use this managed property. The unmanaged client is incorrectly accessing this managed property and sending the request to the endpoint specified by "overriddenEndpointURI".
Local fix
If the user is willing to use unmanaged client, do not specify @WebServiceRef annotation.
Problem summary
**************************************************************** * USERS AFFECTED: Administrators of IBM WebSphere Application * * Server V7 JAX-WS clients. * **************************************************************** * PROBLEM DESCRIPTION: The "overriddenEndpointURI" * * property for unmanaged JAX-WS clients * * should be ignored. * **************************************************************** * RECOMMENDATION: Install a fixpack that includes this APAR. * **************************************************************** When a JAX-WS developer uses a @WebServiceRef, the JAX-WS runtime constructs a service for a managed client: @WebServiceRef(name=?service/FredsBankService?) FredsBankService service; <-- managed service If the developer directly initializes the service, the service then becomes a service for an unmanaged client. Here are two examples: @WebServiceRef(name=?service/FredsBankService?) FredsBankService service; // managed ... service = new FredsBankService(); // becomes unmanaged. Or: @WebServiceRef(name=?service/FredsBankService?) FredsBankService service; // managed ... FredBankService service2 = new FredsBankService(); // unmanaged Note that the prior code sequences are valid, but they are not best practices. Customers should not have a mixture of services that are managed and unmanaged in the same application. The JAX-WS runtime cannot detect this usage. "overriddenEndpointURI" is a managed property that is normally set with the Administrative Console. Only services for managed clients should use this managed property. Due to a flaw in the JAX-WS runtime, the service for the unmanaged client is accessing this managed property and sending the request to the endpoint specified by the "overriddenEndpointURI" property. There are some customers with production applications that are dependent on this incorrect behavior. For example, they may have services for unmanaged clients that will fail if the JAX-WS runtime enforces the rule that unmanaged clients don't use "overriddenEndpointURI". There are other customers who need to enforce the correct behavior. For example, the customer may be running final testing and wants to make sure that unmanaged clients are not accidentally being used.
Problem conclusion
A JVM property is introduced to allow customers to enforce the proper behavior. The new JVM property is "com.ibm.ws.websvcs.unmanaged.client. dontUseOverriddenEndpointUri". The valid settings for this property are "true" and "false". The default setting, "false", will allow the services for unmanaged clients to use the managed property "overriddenEndpointURI". If a customer sets the property to "true", the services for unmanaged clients will use the normal endpoint URI (which is usually defined in the WSDL file). For more details on how to set custom properties, refer to the article "Java? virtual machine custom properties" in the Information Center for your WebSphere Application Server version and operating system. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.9. 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
PK89340
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-19
Closed date
2009-10-04
Last modified date
2009-10-04
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
Document Information
Modified date:
24 October 2021