Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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 but adding that config made no difference.

Edit: Starting up with -Djboss.vfs.forceCopy=false does not create such directory at all. But does that affect clustered setup somehow?

share|improve this question
up vote 0 down vote accepted

Some discussion:

Deployment using MainDeployer seems to be the cause as this problem did not happen when deploying exploded ear manually in to the server/all/deploy.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.