Fixes are available
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
The IIOP Tunneling suddenly stops working. It seems that the in coming HTTP tunneling requests aer forwarded to a websphere inte rnal director component (com.ibm.CORBA.services.redirector.Redir ector) which opens an IIOP socket connection and forwards the re quest via IIOP transport to the local port 9100. After some tim e, on of the request just times out. The is configured by setti ng the following custom property in the WebSphere ORB: com.ibm.w s.orb.services.redirector.RequestTimout = 60. Settings were trie d up to 1200 seconds but the redirector never gets a response back from the ORB/EJB container. . The communication between the J2EE application client and the se rver-side EAF(EJBs) is running fine when the iiop tunneling is s witched off. If the iiop tunneling is turned on in a case such as having a firewall, several client-server interactions are pro cessed successfully but then suddenly the client-server communic ation stops as the redirector component is waiting for some inpu t which never comes and the redirector times out. After the red irector times out, the application continues to work. Here is the exception that is shown after the timeout: . 8/14/07 16:25:21:218 CEST] 0000003d WebApp A SRVE0180I: [ePBN#webApp/IIOPTunnelServlet.war] [/iiop-via-http] [Servlet.LOG]: IIOPTunnelServlet: service(): About to call redirector.handle() method [8/14/07 16:25:31:859 CEST] 0000003a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened incident stream file X:\prg\WebSphere61\AppServer\profiles\pbn-profile\logs\ffdc\ser ver1_7844 7844_07.08.14_16.25.31_0.txt [8/14/07 16:25:31:906 CEST] 0000003a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file X:\prg\WebSphere61\AppServer\profiles\pbn-profile\logs\ffdc\ser ver1_7844 7844_07.08.14_16.25.31_0.txt [8/14/07 16:25:31:906 CEST] 0000003a ORBRas E com.ibm.CORBA.services.redirector.Redirector handleReply WebContainer : 2 ORBX0360E: handleReply(): IOException occurred while redirecting the server reply packet back to the client. Exception=java.net.SocketTimeoutException: Read timed out. java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:155) at com.ibm.CORBA.services.redirector.Redirector.readFully(Redirect or.java:4 87) at com.ibm.CORBA.services.redirector.Redirector.handleReply(Redire ctor.java :338) at com.ibm.CORBA.services.redirector.Redirector.handle(Redirector. java:221) at com.ibm.CORBA.services.IIOPTunnelServlet.service(IIOPTunnelServ let.java: 213) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletW rapper.ja va:989) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(Se rvletWrap per.java:501) at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(S ervletWr apper.java:464) at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleReque st(CacheS ervletWrapper.java:90) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer .java:744 ) at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContain er.java:1 433) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLi nk.java:1 11) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDisc riminatio n(HttpInboundLink.java:454) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewI nformatio n(HttpInboundLink.java:383) at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.comple te(HttpIC LReadCallback.java:102) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCom pleted(Ai oReadCompletionListener.java:165) at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsy ncFuture. java:217) at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(Async ChannelFu ture.java:161) com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136) at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195) at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHan dler.java :743) at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469) [8/14/07 16:25:31:937 CEST] 0000003a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl open FFDC0009I: FFDC opened incident stream file X:\prg\WebSphere61\AppServer\profiles\pbn-profile\logs\ffdc\ser ver1_7844 7844_07.08.14_16.25.31_1.txt [8/14/07 16:25:31:937 CEST] 0000003a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file X:\prg\WebSphere61\AppServer\profiles\pbn-profile\logs\ffdc\serv er1_7844 7844_07.08.14_16.25.31_1.txt [8/14/07 16:25:31:953 CEST] 0000003a WebApp A SRVE0180I: [ePBN#webApp/IIOPTunnelServlet.war] [/iiop-via-http] [Servlet.LOG]: IIOPTunnelServlet: ORBX0310E: service(): IOException occurred while setting up client/server sockets. Exception=java.net.SocketTimeoutException: Read timed out. [8/14/07 16:25:31:953 CEST] 0000003a WebApp A SRVE0180I: [ePBN#webApp/IIOPTunnelServlet.war] [/iiop-via-http] [Servlet.LOG]: IIOPTunnelServlet: service(): entered... [8/14/07 16:25:31:953 CEST] 0000003a WebApp A SRVE0180I: [ePBN#webApp/IIOPTunnelServlet.war] [/iiop-via-http] [Servlet.LOG]: IIOPTunnelServlet: service(): target host = katja.hfp.de target port = 9100 [8/14/07 16:25:31:953 CEST] 0000003a WebApp A SRVE0180I: [ePBN#webApp/IIOPTunnelServlet.war] [/iiop-via-http] [Servlet.LOG]: IIOPTunnelServlet: service(): About to call redirector.handle() method [8/14/07 16:25:37:312 CEST] 0000003a WebApp A SRVE0180I: [ePBN#webApp/IIOPTunnelServlet.war] [/iiop-via-http] [Servlet.LOG]: IIOPTunnelServlet: end of service method [8/14/07 16:25:37:359 CEST] 0000003d WebApp A SRVE0180I: [ePBN#webApp/IIOPTunnelServlet.war] [/iiop-via-http] [Servlet.LOG]: IIOPTunnelServlet: end of service method [8/14/07 16 [8/14/07 16:26:10:015 CEST] 0000002d ORBRas E com.ibm.CORBA.services.redirector.Redirector handleReply WebContainer : 1 ORBX0360E: handleReply(): IOException occurred while redirecting the server reply packet back to the client. Exception=java.net.SocketTimeoutException: Read timed out. java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:155) at com.ibm.CORBA.services.redirector.Redirector.readFully(Redirect or.java:4 87) at com.ibm.CORBA.services.redirector.Redirector.handleReply(Redire ctor.java :338) at com.ibm.CORBA.services.redirector.Redirector.handle(Redirector. java:221) at com.ibm.CORBA.services.IIOPTunnelServlet.service(IIOPTunnelServ let.java: 213) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletW rapper.ja va:989) at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleReque st(CacheS ervletWrapper.java:90) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer .java:744 ) at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContain er.java:1 433) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLin k.java:1 11) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDisc riminatio n(HttpInboundLink.java:454) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewI nformatio n(HttpInboundLink.java:383) at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.comple te(HttpIC LReadCallback.java:102) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCom pleted(Ai P oReadCompletionListener.java:165) at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsy ncFuture. java:217) at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(Async ChannelFu ture.java:161) at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136) at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195) at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHan dler.java :743) at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469) .
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of IIOP tunneling in IBM WebSphere * * Application Server V6.0.2 and V6.1 when * * the client request is bigger than 1kb * **************************************************************** * PROBLEM DESCRIPTION: With IIOP tunneling on, a client * * request bigger than 1kb is not * * completely sent to the server. * **************************************************************** * RECOMMENDATION: * **************************************************************** Base ORB in java breaks client requests bigger than 1kb into chunks of data and sends them to the Application Server orb extension, which flushes only the 1st chunk to the server.
Problem conclusion
A fix has been put in the ORB extension in Application Server to always accumulate chunks of data sent from the base ORB until a complete client request is received, then flush the complete request to the server. The fix for this APAR is currently targeted for inclusion in fix packs 6.0.2.29 and v6.1.0.17. 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
PK59761
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-01-22
Closed date
2008-04-04
Last modified date
2008-04-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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
29 December 2021