Use of symbolic links leads to large disk usage in JBoss EAP
Issue
- The server configuration directories (
$JBOSS_HOME/server/$PROFILE) are linked via symbolic links (symlinks) to another file system. That is,$PROFILEis a symlink. - An application ear is deployed directly to the
$JBOSS_HOME/server/$PROFILE/deploydirectory without using symbolic links. - When a new web browser session is started for the application, the
$JBOSS_HOME/server/$PROFILE/tmp/vfs-nested.tmpfolder 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.tmpfolder does not double in size when a new session is created. - Having problems with the
./tmppath, the subpathvfs-nested.tmpis consuming lots of space. The only fix we're aplying is restart the jboss. Vfs-nested.tmpis 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.