Use of log:tail in a remote Fuse console might cause memory problems in some circumstances

Solution Verified - Updated -

Issue

It has been reported that, in a particular set of circumstances, the use of the log:tail command in the Fuse 6.0 console could lead to excessive memory usage and eventually an outage. The problem is not readily reproducible, so the exact cause is unclear. However, it is likely that an administrator was running log:tail over a remote SSH session to Fuse, and the SSH client had a disorderly shut-down or an interruption of network connectivity. Tests have shown that, in these circumstances, a thread can continue to execute in the Fuse container, and log lines continue to be buffered by operations in that thread. Although the amount of memory used for this activity does seem to be bounded, it is possible that in some set-ups, given enough time, the extra memory load could be troublesome.

In Fuse 6.1 a disorderly shut-down of an SSH client does not cause a thread to remain running, so it is likely that the problem will not affect versions later than 6.0.

Environment

JBoss Fuse 6.0.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.