JDK-6547113 : ulimit issue with 5.0 U7 on Solaris 10
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.nio
  • Affected Version: 5.0u7
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris_10
  • CPU: sparc
  • Submitted: 2007-04-17
  • Updated: 2010-04-02
  • Resolved: 2007-05-22
Related Reports
Duplicate :  
JDK-6322825 - (se) Selector fails with invalid argument on Solaris 10
Description
Customer says they use a startup script to start a java process. Normally, this process handles HTTP requests. The script and the java process run fine on servers running Solaris 9 OS. They are currently using JDK 1.5.0_07.

They notice a problem when they moved to Solaris 10. After running the startup script, the server no longer handles HTTP requests.

They found 2 workarounds:

1. Replace "ulimit -n 8192" with "ulimit -Sn 8192" in the startup script, the java process will again accept HTTP requests.

2. Replace JDK 1.5.0_07 with JDK 1.5.0_11, the java process will again accept HTTP requests.

They asked if this is a bug.
Comments
EVALUATION After discussions with the customer, this bug is a duplicate of bug 6322825. This bug can be closed.
21-05-2007
EVALUATION There is insufficient information in this bug report. The bug report needs a detailed description of the problem (does the server hang, crash, ...). Can the fatal error log or thread dump be attached to the bug report? One possible bug to examine is 6322825 which was an issue in the /dev/poll Selector implementation that arises on Solaris 10 when the hard limit (default is 64k on Solaris 10) is changed in /etc/system to a limit less than 8193. The issue was resolved in jdk6 and 5.0u8.
18-04-2007
WORK AROUND 1. Replace "ulimit -n 8192" with "ulimit -Sn 8192" in the startup script. 2. Replace JDK 1.5.0_07 with JDK 1.5.0_11.
17-04-2007