[
https://issues.apache.org/jira/browse/QPID-8152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16424205#comment-16424205
]
Keith Wall commented on QPID-8152:
----------------------------------
Qpid Broker-J v7.0.0 and higher shipped Berkeley DB JE 7.4.5. This JE release
has a safety feature that monitors the data directory owned by BDB checking for
external modification. If external modification is detected, JE now fails
early. To perform this check JE uses a {{WatchService}} - which imposes
demands on the Operating System. The user of Broker-J needs to be aware of
this new environmental demand and ensure that the environment gives sufficient
resources.
I am not sure that turning off this useful feature is the right thing to do.
Surely better to document? If the user wants to turn off the feature then
this is possible via Broker-J by setting {{je.log.detectFileDelete}} to false.
> [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-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
