PQ65772: USING IIOP TUNNELING, SECOND CALL WILL CAUSE A HANG.

 Fixes are available

4.0.6: WebSphere Application Server Version 4.0 Fix Pack 6
PQ65772, 4.0.2,4.0.3: Application Server hang with IIOP Tunneling Servlet



APAR status
Closed as program error.

Error description
Customer found that when trying to use IIOP Tunneling servlet,
if the EJB on the other end was hung, the second call would
cause a hang in the app server.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users of    *
*                 IIOPTunneling feature.                       *
****************************************************************
* PROBLEM DESCRIPTION: User is unable to start a second        *
*                      session of IIOPTunnelServlet and its    *
*                      associated EJB until the first          *
*                      session is completed.                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
IIOPTunnelServlet is a special servlet developed by IBM
WebSphere Java ORB team to allow HTTP client (ie, java client
or HTTP browser) embedding with RMI-IIOP to communication with
WAS server.
1) After user invokes the client, an HTTP request will be
routed toward the IIOPTunnelServlet.
2) IIOPTunnelServlet first intercepts the HTTP request from
client, and then decodes and removes the RMI-IIOP out
of the HTTP request.
3) It then creates and establishs an endpoint between itself
and its back-end EJB, and caches the endpoint as well.
4) At this moment, IIOPTunnelServlet switches to use RMI-IIOP
instead of HTTP for communication to the EJB for service.
When EJB's result is returned, IIOPTunnelServlet encodes and
seals RMI-IIOP message within HTTP response and then
dispatchs this HTTP response back to the client. The protocol
being used between IIOPTunnelServlet and EJB is RMI-IIOP.
The protocol being used in between of client (ie, java client
or browser) and IIOPTunnelServlet is HTTP.

Since the endpoint is cached in step 3, IIOPTunnelServlet
doesn't always create a new endpoint for each single HTTP
request. When a current session is in the middle of the process,
IIOPTunnelServlet's endpoint is being used.  Therefore, the
user is unable to start a second session of
IIOPTunnelServlet and its EJB until completion of the current
session due to the endpoint is being used at that moment.
Problem conclusion
To resolve this problem, a new server side ORB property is
being introduced to allow the servlet to be multi-threaded:
com.ibm.ws.orb.services.redirector.UseMultipleSockets
Temporary fix Comments
APAR information
APAR number PQ65772
Reported component name WEBSPHERE AE SO
Reported component ID 5630A2202
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-08-30
Closed date 2002-12-10
Last modified date 2002-12-10

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
ORB          

SRLS

Fix information
Fixed component name WEBSPHERE AE SO
Fixed component ID 5630A2202

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ65772
IBM Group: Software Group
Modified date: Dec 10, 2002