[
https://issues.jboss.org/browse/AS7-6031?page=com.atlassian.jira.plugin.s...
]
Bartosz Baranowski commented on AS7-6031:
-----------------------------------------
'W' - with hack
'W/O' - no hack to cleanup tmp
No deployment with shutdown hook
{noformat}
W W/O
1. 3064ms 2858ms
2. 3028ms 2790ms
3. 2960ms 2831ms
4. 3061ms 2917ms
5. 2977ms 2828ms
6. 2958ms 2843ms
7. 2909ms 2872ms
8. 2898ms 2856ms
9. 2945ms 2915ms
10. 2937ms 2969ms
{noformat}
No deployment without shutdown hook '-Xrs'
{noformat}
1. 2903ms 2796ms
2. 2854ms 2943ms
3. 2941ms 2808ms
4. 2937ms 2935ms
5. 3234ms 2964ms
6. 2922ms 2862ms
7. 2829ms 2841ms
8. 2854ms 2885ms
9. 2931ms 2874ms
10. 2975ms 2922ms
{noformat}
ls -laR ( part of it, after W/O runs
{noformat}
ls -laR standalone/tmp/
total 20
drwxrwxr-x 5 baranowb baranowb 4096 2013-01-10 11:20 .
drwxrwxr-x 8 baranowb baranowb 4096 2013-01-10 11:20 ..
drwx------ 2 baranowb baranowb 4096 2013-01-10 11:18 auth
drwxrwxr-x 15 baranowb baranowb 4096 2013-01-10 11:28 vfs
drwxrwxr-x 3 baranowb baranowb 4096 2013-01-10 11:20 work
standalone/tmp/auth:
total 8
drwx------ 2 baranowb baranowb 4096 2013-01-10 11:18 .
drwxrwxr-x 5 baranowb baranowb 4096 2013-01-10 11:20 ..
standalone/tmp/vfs:
total 60
drwxrwxr-x 15 baranowb baranowb 4096 2013-01-10 11:28 .
drwxrwxr-x 5 baranowb baranowb 4096 2013-01-10 11:20 ..
drwxrwxr-x 2 baranowb baranowb 4096 2013-01-10 11:20 temp22b2c3b8d74354
drwxrwxr-x 2 baranowb baranowb 4096 2013-01-10 11:20 temp269ff1e8171ea873
drwxrwxr-x 2 baranowb baranowb 4096 2013-01-10 11:23 temp35501bb7f0ce71e9
drwxrwxr-x 2 baranowb baranowb 4096 2013-01-10 11:23 temp3aade92f81fedb68
drwxrwxr-x 2 baranowb baranowb 4096 2013-01-10 11:26 temp47abae8a39472109
drwxrwxr-x 2 baranowb baranowb 4096 2013-01-10 11:26 temp4d48ba76bb40266d
drwxrwxr-x 2 baranowb baranowb 4096 2013-01-10 11:25 temp637e885234a2a17f
drwxrwxr-x 2 baranowb baranowb 4096 2013-01-10 11:23 temp7072ea6391eafbf3
drwxrwxr-x 2 baranowb baranowb 4096 2013-01-10 11:28 tempa64d5ddb1e490c42
drwxrwxr-x 2 baranowb baranowb 4096 2013-01-10 11:26 tempac343cb5209d61b9
drwxrwxr-x 2 baranowb baranowb 4096 2013-01-10 11:24 tempc7627e794eb55c6b
drwxrwxr-x 2 baranowb baranowb 4096 2013-01-10 11:26 tempcf0338e402de1067
drwxrwxr-x 2 baranowb baranowb 4096 2013-01-10 11:20 tempd1beed9b1b302b7c
{noformat}
Deployment, with shutdown hook
{noformat}
W W/O
1. 7684ms/285ms 7996ms/236ms
2. 7959ms/256ms 7795ms/234ms
3. 7772ms/279ms 7633ms/248ms
4. 7445ms/244ms 7950ms/218ms
5. 8033ms/264ms 7822ms/230ms
6. 7888ms/310ms 7673ms/223ms
7. 7642ms/221ms 7739ms/302ms
8. 7890ms/264ms 7920ms/1952ms (wow)
9. 7367ms/208ms 7242ms/301ms
10. 7548ms/243ms 7528ms/195ms
{noformat}
Deployment, with out shutdown hook '-Xrs'
{noformat}
W W/O
1. 7864ms 7783ms
2. 7653ms 7406ms
3. 7505ms 7926ms
4. 7685ms 7759ms
5. 7808ms 7730ms
6. 7796ms 7336ms
7. 7822ms 7223ms
8. 7589ms 7758ms
9. 7589ms 7952ms
10. 7818ms 7366ms
{noformat}
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: 7.2.0.Alpha1, 7.1.4.Final (EAP)
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