qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-8152) [Broker-J][BDB] Virtual host start-up fails with IOException: User limit of inotify instances reached or too many open files
Date Tue, 03 Apr 2018 16:16:00 GMT

     [ https://issues.apache.org/jira/browse/QPID-8152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Keith Wall updated QPID-8152:
-----------------------------
    Description: 
Newer versions of BDB JE register {{java.nio.file.WatchService}} to detect unexpected deletion
of the data files owned by JE.  BDB registers a Watcher per Environment.  In Broker-J terms
this amounts to one watcher per BDB backed virtualhost or virtualhost node.

Watchers consume operating system resources.  If the resources are exceeded, Broker-J will
fail with an exception like this:

{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}



  was:
Newer versions of BDB JE register {{java.nio.file.WatchService}} to detect unexpected deletion
of the data files owned by JE.

In some poorly 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}

Though the root of the problem is a poorly configured environment, it would be safer to disable
file deletion detection watcher by default.


> [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.0, qpid-java-broker-7.0.3
>            Reporter: Alex Rudyy
>            Priority: Minor
>
> Newer versions of BDB JE register {{java.nio.file.WatchService}} to detect unexpected
deletion of the data files owned by JE.  BDB registers a Watcher per Environment.  In Broker-J
terms this amounts to one watcher per BDB backed virtualhost or virtualhost node.
> Watchers consume operating system resources.  If the resources are exceeded, Broker-J
will fail with an exception like this:
> {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}



--
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


Mime
View raw message