[
https://jira.jboss.org/jira/browse/JBAS-7628?page=com.atlassian.jira.plug...
]
Dietmar Scheidl commented on JBAS-7628:
---------------------------------------
In our development environment we are using cargo to deploy the artifact to the server
within the maven build.
I know that its possible to use the conf/bootstrap/profile.xml and conf/bootstrap/vfs.xml
to specify additional folders for deployment. If you miss the vfs.xml file and onyl
specify the additional deployment directory in profile.xml the same happens.
There are two points on that:
1. lack of documentation
2. why does the cache spam the tmp/vfs-nested.tmp folder (i/o load also reduces the
performance of the server)
CombinedVFSCache fills tmp/vfs-nested.tmp for deployments not listed
in permanentRoots
--------------------------------------------------------------------------------------
Key: JBAS-7628
URL:
https://jira.jboss.org/jira/browse/JBAS-7628
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: VFS
Affects Versions: JBossAS-5.1.0.GA
Reporter: Dietmar Scheidl
Assignee: Ales Justin
Priority: Critical
CombinedVFSCache starts to fill the harddisk with copies of nested libraries from
ear-deployment.
This happens only if the location of the deployment is not listed in permanentRoots.
We encounter this behavior by using the jmx-console to deploy the ear-file.
Space is stable for about 30mins. After that any request to the web application
(JSF/Richfaces/Seam/EJB3/...) leads to a new copy of all nested libraries into the
vfs-nested.tmp folder.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira