PK35705: SERVER STARTUP HANGS WITH JAVA.IO.IOEXCEPTION: INVALID ARGUMENT

Fixes are available

APAR status

Closed as change to accomodate OEM Vendor's code.

Error description

When using WebSphere Application Server Version 6.1 on Solaris
x64 (also known as x86-64) or SPARC 64-bit, startup of an
application server or the deployment manager might hang and
eventually time out.  The following exception is seen in FFDC.

Exception = java.io.IOException
Source = com.ibm.ws.tcp.channel.impl.ChannelSelector
probeid = 288
Stack Dump = java.io.IOException: Invalid argument
    at sun.nio.ch.DevPollArrayWrapper.poll0(Native Method)

Local fix

A workaround is to set the hard limit for maximum number of file
descriptors to 8193 or greater.  Open a command prompt and issue
the following command as root.

ulimit -n -H

If the value displayed is less than 8193, edit /etc/system and
add the following line or modify it if it already exists.

set rlim_fd_max=8193

Then reboot the system.

Problem summary

****************************************************************
* USERS AFFECTED: Users of WebSphere Application Server and    *
*                 WebSphere Application Server Network         *
*                 Deployment, Version 6.1, on Solaris x64      *
*                 (also known as x86-64) or SPARC 64-bit       *
****************************************************************
* PROBLEM DESCRIPTION: The application server or the           *
*                      deployment manager fails to start.      *
*                      It appears to hang and eventually       *
*                      times out.                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The application server or the deployment manager fails to
start. It appears to hang and eventually times out. The
exception
"java.io.IOException: Invalid argument at
sun.nio.ch.DevPollArrayWrapper.poll0"
is seen in FFDC.

The failure occurs on systems where the hard limit for maximum
number of file descriptors is 8192 or less.  It is caused by
Sun bug #6322825.  This fix executes one of the workarounds
for this problem as documented by Sun, which is to use the
poll based SelectorProvider.

Problem conclusion

The fix for this APAR is currently targeted for inclusion in
fixpack 6.1.0.7.  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
PK35705
Reported component name
WEBSPH APP SERV
Reported component ID
5724J0800
Reported release
61S
Status
CLOSED OEM
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2006-12-05
Closed date
2006-12-11
Last modified date
2006-12-11

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Modules/Macros

```
ADMIN
```

Fix information

Applicable component levels

R61S 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

Tips

PK35705: SERVER STARTUP HANGS WITH JAVA.IO.IOEXCEPTION: INVALID ARGUMENT

Fixes are available

Subscribe

APAR status

Closed as change to accomodate OEM Vendor's code.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Fix information

Applicable component levels

R61S PSY

Document Information

Share your feedback

Need support?