8 Replies Latest reply on Apr 7, 2010 7:40 AM by jaikiran

JBoss 5.1.0.GA, load test and huge vfs-nested.tmp

pepez Apr 1, 2010 10:13 AM

I noticed this while running a performance test with JMeter. For first half an hour everything was fine and the /server/all/tmp directory size was around 36M.

Then suddenly the tmp directory grew up to 6.1G. The space was taken by jar files inside vfs-nested.tmp. If I let the server sit idle there is no such behaviour.

I found https://jira.jboss.org/jira/browse/JBAS-7126 but adding that config made no difference.

Any advices?

1. Re: JBoss 5.1.0.GA, load test and huge vfs-nested.tmp

jaikiran Apr 2, 2010 2:30 AM (in response to pepez)

Post the contents of your JBOSS_HOME/server/all/conf/bootstrap/vfs.xml and JBOSS_HOME/server/all/conf/bootstrap/profile.xml file.
Actions
2. Re: JBoss 5.1.0.GA, load test and huge vfs-nested.tmp

pepez Apr 2, 2010 4:23 AM (in response to jaikiran)
Here you are. I am running on Ubuntu 9.04.

profile.xml 11.0 KB

vfs.xml 1.6 KB
Actions
3. Re: JBoss 5.1.0.GA, load test and huge vfs-nested.tmp

jaikiran Apr 5, 2010 7:33 AM (in response to pepez)

Your config files look OK to me. Can you provide more details about what kind of load testing you are doing? And which files in the vfs-nested.tmp keep increasing? And how frequently do they keep adding to that folder?
Actions
4. Re: JBoss 5.1.0.GA, load test and huge vfs-nested.tmp

pepez Apr 6, 2010 11:21 AM (in response to jaikiran)
The directory is stable for first 30 minutes. I attached a list of contents right after deployment and after 30 minutes. The directory started grow after 30 minutes passed and it kept growing until I killed JBoss. During the next 15minutes the directory size became 7.2GB - same JARs all over again with different prefixes.

jars after 30min.txt.zip 8.4 KB

jars after deployment.txt.zip 1.2 KB
Actions
5. Re: JBoss 5.1.0.GA, load test and huge vfs-nested.tmp

pepez Apr 7, 2010 6:54 AM (in response to pepez)

Alright, this seems to happen only when I use maven deployment. If I deploy manually the exploded ear to the /server/all/deploy/ there is no such behavior.
Actions
6. Re: JBoss 5.1.0.GA, load test and huge vfs-nested.tmp

jaikiran Apr 7, 2010 7:06 AM (in response to pepez)

Petteri Hietavirta wrote:

Alright, this seems to happen only when I use maven deployment.
How does Maven (I guess, you mean some maven plugin) deploy the deployment and to which folder does it deploy?
Actions
7. Re: JBoss 5.1.0.GA, load test and huge vfs-nested.tmp

pepez Apr 7, 2010 7:31 AM (in response to jaikiran)

Oh yes, I was a bit sloppy in my previous post.

We use jboss-maven-plugin 1.3.1 (org.codehaus.mojo)

The deploy path is:
/jmx-console/HtmlAdaptor?action=invokeOpByName&name=jboss.system:service%3DMainDeployer&methodName=redeploy&argType=java.net.URL&arg0=
Actions
8. Re: JBoss 5.1.0.GA, load test and huge vfs-nested.tmp

jaikiran Apr 7, 2010 7:40 AM (in response to pepez)

Petteri Hietavirta wrote:

The deploy path is:
/jmx-console/HtmlAdaptor?action=invokeOpByName&name=jboss.system:service%3DMainDeployer&methodName=redeploy&argType=java.net.URL&arg0=
Okay, so it's a direct deployment through the MainDeployer. The MainDeployer deploys it directly to the tmp folders. It does not place the app in the deploy folder. The VFS cache fix, for that ever growing disk space usage issue, can only handle the deploy (and farm) folders.

Hmm, this one is interesting - If users use the MainDeployer to deploy their apps, then I guess they don't have a solution to prevent the disk space usage issue. Although I am not sure how many users use the MainDeployer to deploy the app (given that the app will not survive a server restart).
Actions

Go to original post