[
https://issues.jboss.org/browse/AS7-6031?page=com.atlassian.jira.plugin.s...
]
Brad Maxwell commented on AS7-6031:
-----------------------------------
Hello, was this actually resolved? It looks like it was committed and then reverted:
commit 9be6eef40b9e7f4a3a8cbcd70934f989f3aec23b
Author: Thomas Diesler <thomas.diesler(a)jboss.com>
Date: Mon Jan 21 19:43:32 2013 +0100
[AS7-6371] Revert "Move clear tmp dir hack to bootstrap impl"
commit ad3e878098129cb2ac925a50abe809aced6b070b
Author: baranowb <baranowb(a)gmail.com>
Date: Fri Jan 11 08:40:43 2013 +0100
Move clear tmp dir hack to bootstrap impl
Thanks,
Brad
deploy directories not cleaned up
---------------------------------
Key: AS7-6031
URL:
https://issues.jboss.org/browse/AS7-6031
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.3.Final (EAP)
Reporter: Shaun Appleton
Assignee: Bartosz Baranowski
Fix For: EAP 6.1.0.Alpha (7.2.0.Final)
Attachments: deployment_with_hack_no_hook.txt
JBoss EAP 6.0.0 (and 6.0.1.ER3) doesn't clean up it's tmp/vfs directories.
The following reproduces this -
i) ensure run.conf has the -Xrs set
ii) ensure deployments has a deployable .ear in it
iii) ./run standalone.sh and allow the deployments to deploy
iv) stop the EAP process ie kill <process_id>
v) observe content tmp/vfs
(The -Xrs parameter is used to "-Xrs" to prevent possible interference when JVM
is running as a service and receives CTRL_LOGOFF_EVENT or SIGHUP)
This will eventually cause problems with lack of disk space.
Note if the -Xrs parameter content is removed but the tmp/vfs dirs stills exist. This
could potentially cause inode problems.
It would be better if there were any additional code so the temp dirs are cleaned up on
start up. That would resolve both the -Xrs problem and the excessive dir creation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira