APAR status
Closed as program error.
Error description
When using the com.ibm.CORBA.services.IIOPTunnelServlet, a small
amount of load is handled successfully. However, when
the load is increased, the requests just seem to hang and
do not return.
The problem occurs only when there are multiple requests which
arrive at the same time and each must be handled in sequence,
not in parallel.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Servers users of the *
* IIOP HTTP Tunnel (IIOPTunnelServlet) *
****************************************************************
* PROBLEM DESCRIPTION: Increased load to the IIOP HTTP Tunnel *
* servlet can cause client requests to *
* time out. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The WebSphere IIOP HTTP Tunnel servlet serializes all client
requests to the same target host/port through the same
TCP/IP socket. This causes a bottleneck that can cause
client requests through the tunnel to the same target
host/port to time out.
Problem conclusion
The IIOP HTTP Tunnel Servlet
(com.ibm.CORBA.services.IIOPTunnelServlet) was modified so
that it will maintain a cache of sockets for use to each target
host/port. The maximum number of sockets to maintain in the
cache for each target host/port is customizable with a new ORB
property:
com.ibm.ws.orb.services.redirector.MaxOpenSocketsPerEndpoint
MaxOpenSocketsPerEndpoint defaults to 3. If a new client
request is received for a target host/port that already has
the maximum number of sockets cached, a new socket will be
opened for this new request that will subsequently be closed
after the reply is sent back to the client.
A request timeout was also added to the IIOP HTTP Tunnel
servlet. The following ORB property was added:
com.ibm.ws.orb.services.redirector.RequestTimeout
This specifies the number of seconds the IIOPTunnelServlet
should wait before timing out when waiting on a reply from
the target server on behalf of the client. If not specified,
or specified improperly, this property will default to the
current setting for com.ibm.CORBA.RequestTimeout on the
Application Server on which the IIOPTunnelservlet is installed.
This preperty should be set to at least as high as the highest
client setting for com.ibm.CORBA.RequestTimeout, otherwise the
IIOPTunnelServlet could time out waiting on a reply before the
client ordinarily would. If this property is set to zero, the
IIOPTunnelServlet will not time out.
This is apar is targetted for inclusion in the following
releases:
5.0.2.16
5.1.1.10
6.0.2.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 |
PK17967 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2006-01-16 |
Closed date |
2006-03-09 |
Last modified date |
2006-03-09 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
|
Fix information |
Fixed component name |
WAS BASE 5.0 |
Fixed component ID |
5630A3600 |
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|