Use of symbolic links leads to large disk usage in JBoss EAP

Solution Verified - Updated -

Issue

  • The server configuration directories ($JBOSS_HOME/server/$PROFILE) are linked via symbolic links (symlinks) to another file system. That is, $PROFILE is a symlink.
  • An application ear is deployed directly to the $JBOSS_HOME/server/$PROFILE/deploy directory without using symbolic links.
  • When a new web browser session is started for the application, the $JBOSS_HOME/server/$PROFILE/tmp/vfs-nested.tmp folder doubles in size causing the file system to fill up very quickly when there are many concurrent user sessions.
  • When we remove the symbolic links, everything works as expected and the $JBOSS_HOME/server/$PROFILE/tmp/vfs-nested.tmp folder does not double in size when a new session is created.
  • Having problems with the ./tmp path, the subpath vfs-nested.tmp is consuming lots of space. The only fix we're aplying is restart the jboss.
  • Vfs-nested.tmp is growing without limits.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 5.x.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content