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.