I have been struggling with the Too Many Open Files issue running Artemis as a service within a service (if that is not confusing enough). My /etc/security/limits.conf files contains:
----- . . . # End of file * soft nofile 81920 * hard nofile 81920 ----- Originally it was set to 8192 and I was able to start the service from the command line: /opt/artemis/bin/artemis-service start When I did so and ran: lsof -p <artemis pid> | wc -l it reported some 5K files open by the process, hence the reason it wouldn't run with the default limit of 1024. I then tried to start the SystemD service: sudo systemctl start artemis using this in /etc/systemd/system/artemis.service: ----- [Unit] Description=ActiveMQ Artemis Service After=network.target [Service] ExecStart=/opt/artemis/bin/artemis-service start ExecStop=/opt/artemis/bin/artemis-service stop Type=forking User=<my id> Group=<my group> [Install] WantedBy=multi-user.target ----- and it failed with the Too Many Open Files error. So I increased it to the 81920 shown above, rebooted, and I STILL get the Too Many Open Files error. Is there something special about the way services are started such that it doesn't use /etc/security/limits.conf to determine the number of open files allowed for a process? Regards, Rich Bergmann ________________________________ The information contained in this e-mail and any attachments from COLSA Corporation may contain company sensitive and/or proprietary information, and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by return e-mail and permanently delete the e-mail and any attachments. COLSA Proprietary
