You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (JIRA)" <ji...@apache.org> on 2018/04/03 15:55:00 UTC
[jira] [Resolved] (QPID-8152) [Broker-J][BDB] Virtual host start-up
fails with IOException: User limit of inotify instances reached or too many
open files
[ https://issues.apache.org/jira/browse/QPID-8152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy resolved QPID-8152.
------------------------------
Resolution: Won't Fix
> [Broker-J][BDB] Virtual host start-up fails with IOException: User limit of inotify instances reached or too many open files
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-8152
> URL: https://issues.apache.org/jira/browse/QPID-8152
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
> Affects Versions: qpid-java-broker-7.0.3
> Reporter: Alex Rudyy
> Priority: Major
>
> BDB JE use registers watcher service to detect unexpected deletion of the file.
> In some purely configured environments the user inotify limit can be breached on virtual host/virtual host node start-up. This situation ends-up in exception like the one below:
> {noformat}
> Caused by: java.io.IOException: User limit of inotify instances reached or too many open files
> at sun.nio.fs.LinuxWatchService.<init>(LinuxWatchService.java:64)
> at sun.nio.fs.LinuxFileSystem.newWatchService(LinuxFileSystem.java:47)
> at com.sleepycat.je.log.FileDeletionDetector.<init>(FileDeletionDetector.java:85)
> ... 29 common frames omitted
> {noformat}
> Thought the root of the problem is a poorly configured environment, it would be safer to disable file deletion detection watcher by default.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org