commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raintung Li (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DAEMON-270) JSVC process capability issue
Date Thu, 06 Dec 2012 06:03:02 GMT
Raintung Li created DAEMON-270:
----------------------------------

             Summary: JSVC process capability issue
                 Key: DAEMON-270
                 URL: https://issues.apache.org/jira/browse/DAEMON-270
             Project: Commons Daemon
          Issue Type: Bug
          Components: Jsvc
    Affects Versions: 1.0.11
         Environment: Linux centos 6.3, jdk1.7, tomcat 
            Reporter: Raintung Li


For jsvc, start fork process to start JVM, then downgrade the process capability to 0.
Is it really requirement? or any concern? 
For my test env, it happen can't start more threads in the java.
After the check, it is limited by "ulimit -u" max process for user. It is very interesting
things, actually it doesn't control threads by this attribute in the normal process.
Downgrade the process capability cause this issue. Max threads number should be control by
env memory, kernel max threads parameter, stack size.

For my suggestion, we can remove downgrade the process capability, only inherit the parent's
process capability and add some "read/netbind/setuid.." extra privilege if don't have.

  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message