Bug 1237035

Summary: [GSS](6.4.z) aesh logs remain under tmp directory when run JBoss CLI
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Eiichi Nagai <enagai>
Component: CLIAssignee: Ryan Emerson <remerson>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Kremensky <pkremens>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4.1CC: bmaxwell, brian.stansberry, cdewolf, jboss-set, mkopecky, remerson
Target Milestone: CR1   
Target Release: EAP 6.4.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1235744, 1240537    

Description Eiichi Nagai 2015-06-30 09:01:28 UTC 
Description of problem:
JBoss CLI process creates aesh log files under the tmp directory when it runs. However, JBoss CLI's logging flag for the aesh log is false. It means that JBoss CLI does not output any log for these files and these files remain even if the JBoss CLI process shuts down.

Version-Release number of selected component (if applicable):
EAP 6.4.1

Steps to Reproduce:
1.Run JBoss CLI
2.Stop JBoss CLI
3.You can confirm aesh logs in the tmp directory like below.
~~~
/tmp $ls 
-rw-rw-r-- 1 xxxx xxxxx     0 Jun 30 16:55 aesh.log.1
-rw-rw-r-- 1 xxxx xxxxx     0 Jun 30 16:55 aesh.log.1.lck
-rw-rw-r-- 1 xxxx xxxxx     0 Jun 30 16:55 aesh.log
-rw-rw-r-- 1 xxxx xxxxx     0 Jun 30 16:55 aesh.log.lck
~~~

Additional info:
aesh log files increase with the number of running JBoss CLI process. If this logs are not necessary for JBoss CLI, the customer wants not to create it on JBoss CLI process.
Comment 1 Ryan Emerson 2015-07-06 08:23:22 UTC 
PR https://github.com/aeshell/aesh/pull/174
Comment 3 Ryan Emerson 2015-07-07 07:28:05 UTC 
Upstream PR: https://github.com/aeshell/aesh/pull/175
Comment 4 JBoss JIRA Server 2015-07-07 07:29:24 UTC 
Ryan Emerson <remerson> updated the status of jira AESH-323 to Resolved
Comment 6 Petr Kremensky 2015-09-24 12:12:08 UTC 
Verified on EAP 6.4.4.CP.CR3
Comment 7 Petr Penicka 2017-01-17 10:51:44 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.
Comment 8 Petr Penicka 2017-01-17 10:51:46 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.