Fixes are available
APAR status
Closed as program error.
Error description
When the clipping portlet is used, the socket is left in the state of CLOSE_WAIT. In situations where the portal server is under heavy use, this can cause a large number of sockets to be left in CLOSE_WAIT state and using up available file descriptors. As a result, the crash of the portal system might be caused. For this case, the following errors are written in SystemOut.log: ProxiedURLCon E com.ibm.wps.pe.pc.legacy.service.proxysupport.ProxiedURLConnecti on prepareIndexedFields IOException while getting header. Saving IOException to throw later. java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java(Compiled Code)) at java.io.BufferedInputStream.fill(BufferedInputStream.java(Compil ed Code)) at java.io.BufferedInputStream.read(BufferedInputStream.java(Compil ed Code)) at com.ibm.wps.pe.pc.legacy.service.proxysupport.ContentAccess.read ResponseHeader(ContentAccess.java(Compiled Code)) at com.ibm.wps.pe.pc.legacy.service.proxysupport.ContentAccess.getI nputStream0(ContentAccess.java(Compiled Code)) at com.ibm.wps.pe.pc.legacy.service.proxysupport.DirectContentAcces s.getInputStream(DirectContentAccess.java(Compiled Code)) at com.ibm.wps.pe.pc.legacy.service.proxysupport.ContentAccess.getI nputStream(ContentAccess.java(Inlined Compiled Code)) at com.ibm.wps.pe.pc.legacy.service.proxysupport.ProxiedURLConnecti on.executeFetchIfNecessary(ProxiedURLConnection.java(Compiled Code)) ProxiedURLCon E com.ibm.wps.pe.pc.legacy.service.proxysupport.ProxiedURLConnecti on prepareIndexedFields IOException while getting header. Saving IOException to throw later. java.net.SocketException: Resource temporarily unavailable at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java(Compiled Code)) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java(C ompiled Code)) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java(Compiled Code)) at java.net.Socket.connect(Socket.java(Compiled Code)) at java.net.Socket.connect(Socket.java(Compiled Code)) at java.net.Socket.<init>(Socket.java(Compiled Code)) at java.net.Socket.<init>(Socket.java(Inlined Compiled Code)) at com.ibm.wps.pe.pc.legacy.service.proxysupport.DirectContentAcces s.getSocket(DirectContentAccess.java(Compiled Code))
Local fix
Problem summary
A code fix is required to correct the condition.
Problem conclusion
A fix is available from Fix Central: http://www.ibm.com/eserver/support/fixes/fixcentral/swg/quickord er?apar=PK64750&productid=WebSphere%20Portal&brandid=5 You may need to type or paste the complete address into your Web browser.
Temporary fix
Comments
APAR Information
APAR number
PK64750
Reported component name
WEBSPHERE PORTA
Reported component ID
5724E7600
Reported release
601
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-04-22
Closed date
2008-05-20
Last modified date
2008-06-13
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 PORTA
Fixed component ID
5724E7600
Applicable component levels
R600 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHRKX","label":"WebSphere Portal"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
13 June 2008