PQ75913; 5.0.2: Performance Regression in
interruptible processes
Downloadable files
Abstract
Performance Regression in interruptible processes
Download Description
PQ75913 resolves the following problem:
USERS AFFECTED:
IBM® WebSphere® Application Server Enterprise Edition users of Process
Choreographer:
problems a & e
WebSphere Application Server users of WSIF(WebServices Invocation
Framework):
problems a, c & d
WebSphere Application Server Network Deployment users of WebServices
Gateway:
problems b & c
ERROR DESCRIPTION:
Regression in performance of interruptible processes. In the earlier
drivers, the performance of interruptible processes is 30% better than the
similar processes on Fix Pack 1. But on the latest drivers, this
performance improvement has been reduced to 16%. This accounts for a
regression of 14%.
PROBLEM DESCRIPTION:
a) Performance is not as good as expected when processing business
processes (both non-interruptible and interruptible processes) using
Process Choreographer. Although the performance of the Process
Choreographer process engine in 5.0.2 has improved significantly over
5.0.1, it might not be as good as expected in certain situations. There is
a significant process overhead due to the inefficient handling of messages
by Web Services Invocation Framework (WSIF) when they consist of parts
that are instances of primitive types, or their object equivalents i.e.
Integer Float String Double Short Long Boolean Byte.
b) Web Services clients using the Web Services Gateway fail with an
exception: unable to map type JROMValue. If a service is deployed to the
Web Services Gateway as using 'generic classes', the first invocation
through gateway using this service will cause subsequent services that use
'deployed classes' will fail with an exception a unable to map type
JROMValue.
c) WSIF invoked from a managed container throws an
UnsupportedOperationException. The SOAP engine does not allow complex
types to be registered against it if the application is running in a
managed container. This is for JSR109 compliance. If a service that uses
complex types is invoked using the WSIF SOAP provider from a managed
container the SOAP engine.
d) A NullPointerException occurs in WSIFOperation_JCA. A WSIF message can
be constructed with no parts in order to send a message with no body. If
this WSIFMessage is sent through the WSIF JCA provider a
NullPointerException can occur in WSIFOperation_JCA.
e) "WSWS3037E: Error: Serialization cannot occur for <classname>"
when using WebSphere Process Choreographer. Beans generated to represent
WSDL 'Elements' do not have serializers and deserializers registered for
them in the IBM.
PROBLEM CONCLUSION:
a) The performance overhead added by WSIF's handling of messages is more
significant in non-interruptible processes than in interruptible
processes.
b) Type mappings were not being supplied to the SOAP engine. This has been
rectified.
c) The serializers and deserializers for the complex type were not
registered against the IBM SOAP engine, this has been rectified.
d) Extra checks made for empty messages to prevent the exception.
e) WSIF now registers the correct serializer and deserializer for the
beans
Prerequisites
UpdateInstaller is REQUIRED for this interim fix
Note: The install tool, UpdateInstaller, is separate download from this
interim fix.
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > Web Services (for example: SOAP or UDDI or WSGW or WSIF)
Operating system(s): Windows
Software version: 5.0.2
Software edition: Reference #: 4004999
IBM Group: Software Group
Modified date: Aug 17, 2004
(C) Copyright IBM Corporation 2000, 2009. All Rights
Reserved.