WSO2アイデンティティサーバー：開いているファイルが多すぎます

Question

私はキーマネージャとしての私のインストールwso2isに問題をしました：私はWSO2 ESB too many open filesListeningIOReactor encountered a checked exception : Too many open filesException thrown when try to add documents to the lucene index continuously inside the for loopが、上の手順に従ってきた

dic 18 21:15:30 autenticacion.dominio.info wso2server.sh[825]: [2017-12-18 21:15:30,855] ERROR {org.apache.tomcat.util.net.NioEndpoint$Acceptor} - Socket accept failed 
dic 18 21:15:30 autenticacion.dominio.info wso2server.sh[825]: java.io.IOException: Too many open files 
dic 18 21:15:30 autenticacion.dominio.info wso2server.sh[825]: at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method) 
dic 18 21:15:30 autenticacion.dominio.info wso2server.sh[825]: at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:422) 
dic 18 21:15:30 autenticacion.dominio.info wso2server.sh[825]: at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:250) 
dic 18 21:15:30 autenticacion.dominio.info wso2server.sh[825]: at org.apache.tomcat.util.net.NioEndpoint$Acceptor.run(NioEndpoint.java:825) 
dic 18 21:15:30 autenticacion.dominio.info wso2server.sh[825]: at java.lang.Thread.run(Thread.java:748) 

エラーは続く。

私の現在の/etc/security/limits.confをコマンドulimitを使用して

# /etc/security/limits.conf 
# 
#This file sets the resource limits for the users logged in via PAM. 
#It does not affect resource limits of the system services. 
# 
#Also note that configuration files in /etc/security/limits.d directory, 
#which are read in alphabetical order, override the settings in this 
#file in case the domain is the same or more specific. 
#That means for example that setting a limit for wildcard domain here 
#can be overriden with a wildcard setting in a config file in the 
#subdirectory, but a user specific setting here can be overriden only 
#with a user specific setting in the subdirectory. 
# 
#Each line describes a limit for a user in the form: 
# 
#<domain>  <type> <item> <value> 
# 
#Where: 
#<domain> can be: 
#  - a user name 
#  - a group name, with @group syntax 
#  - the wildcard *, for default entry 
#  - the wildcard %, can be also used with %group syntax, 
#     for maxlogin limit 
# 
#<type> can have the two values: 
#  - "soft" for enforcing the soft limits 
#  - "hard" for enforcing hard limits 
# 
#<item> can be one of the following: 
#  - core - limits the core file size (KB) 
#  - data - max data size (KB) 
#  - fsize - maximum filesize (KB) 
#  - memlock - max locked-in-memory address space (KB) 
#  - nofile - max number of open file descriptors 
#  - rss - max resident set size (KB) 
#  - stack - max stack size (KB) 
#  - cpu - max CPU time (MIN) 
#  - nproc - max number of processes 
#  - as - address space limit (KB) 
#  - maxlogins - max number of logins for this user 
#  - maxsyslogins - max number of logins on the system 
#  - priority - the priority to run user process with 
#  - locks - max number of file locks the user can hold 
#  - sigpending - max number of pending signals 
#  - msgqueue - max memory used by POSIX message queues (bytes) 
#  - nice - max nice priority allowed to raise to values: [-20, 19] 
#  - rtprio - max realtime priority 
# 
#<domain>  <type> <item>   <value> 
# 

#*    soft core   0 
#*    hard rss    10000 
#@student  hard nproc   20 
#@faculty  soft nproc   20 
#@faculty  hard nproc   50 
#ftp    hard nproc   0 
#@student  -  maxlogins  4 

# End of file 

* soft nofile 4096 
* hard nofile 65535 

* soft nproc 20000 
* hard nproc 20000 

：WSO2のユーザーにコマンドのulimitを使用して

[root@autenticacion ~]# ulimit -a 
core file size   (blocks, -c) 0 
data seg size   (kbytes, -d) unlimited 
scheduling priority    (-e) 0 
file size    (blocks, -f) unlimited 
pending signals     (-i) 7283 
max locked memory  (kbytes, -l) 64 
max memory size   (kbytes, -m) unlimited 
open files      (-n) 4096 
pipe size   (512 bytes, -p) 8 
POSIX message queues  (bytes, -q) 819200 
real-time priority    (-r) 0 
stack size    (kbytes, -s) 8192 
cpu time    (seconds, -t) unlimited 
max user processes    (-u) 20000 
virtual memory   (kbytes, -v) unlimited 
file locks      (-x) unlimited 

を：

[root@autenticacion ~]# su wso2 
bash-4.2$ ulimit -a 
core file size   (blocks, -c) 0 
data seg size   (kbytes, -d) unlimited 
scheduling priority    (-e) 0 
file size    (blocks, -f) unlimited 
pending signals     (-i) 7283 
max locked memory  (kbytes, -l) 64 
max memory size   (kbytes, -m) unlimited 
open files      (-n) 4096 
pipe size   (512 bytes, -p) 8 
POSIX message queues  (bytes, -q) 819200 
real-time priority    (-r) 0 
stack size    (kbytes, -s) 8192 
cpu time    (seconds, -t) unlimited 
max user processes    (-u) 4096 
virtual memory   (kbytes, -v) unlimited 
file locks      (-x) unlimited 

おかげ

Answer 1

私の場合、私はgiですログ内のヴィングのようないくつかのエラー：始まりとWSO2が提供するサービスのご滞在がうまく機能しているので

ERROR {org.wso2.carbon.metrics.jdbc.reporter.JDBCReporter} - Error when reporting gauges 
org.h2.jdbc.JdbcSQLException: IO Exception: "JAVA.net.UnknownHostException: static-ip-1312323.cable.net.co: statict-ip 
at org.h2.message.DbException.getJdbcSQLException 
... 32 more 
Caused by: java.net.UnknownHostException: static-ip-1312323.cable.net.co: static-ip-1312323.cable.net.co:Name or service not know 
at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method) 

このエラーは気付か渡します。

私は/ etc/hostnameのIPをinternet ipからローカルのip（またはhostname）に変更しました。

例： autentication.organization.com（インターネットIP）（イントラネットIP）をautentication.intranetする

この変更は、サーバー構成の許容可能であり、これはリミットブレイクをrecurrentsためのソリューションを提供します。どうやら、このエラーは、ファイルを開くためのアキュミュライゼーションを引き起こし、決してこの接続を閉じることはありません。