Bug 1238263

Summary: [QA] (6.4.z) jboss-cli client prints "Accept certificate? [N]o, [T]emporarily, [P]ermenantly" indefinitely
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Filip Brychta <fbrychta>
Component: CLIAssignee: Chao Wang <chaowan>
Status: CLOSED CURRENTRELEASE QA Contact: Peter Mackay <pmackay>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4.1CC: bmaxwell, brian.stansberry, chaowan, istudens, pmackay, rnetuka
Target Milestone: CR1   
Target Release: EAP 6.4.15   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-19 08:05:25 UTC 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: 1419353    
Attachments:
Description Flags
standalone xml none

Description Filip Brychta 2015-07-01 13:38:46 UTC
Created attachment 1045057 [details]
standalone xml

Description of problem:
When running jboss-cli client against secured EAP and jboss-cli does not yet trust certs so you see following output:

./jboss-cli.sh --connect --controller=10.16.23.184:10099
Unable to connect due to unrecognised server certificate
Subject    - CN=client,OU=rhq,O=redhat
Issuer     - CN=client, OU=rhq, O=redhat
Valid From - Thu Mar 13 06:15:46 EDT 2014
Valid To   - Sun Mar 10 06:15:46 EDT 2024
SHA1 : 07:2e:d3:88:65:f4:66:a7:ed:83:af:1b:9b:6b:e9:8e:3d:11:ed:2b
MD5 : ed:ee:32:b1:de:88:49:5a:93:4e:76:2f:4b:0a:2a:48

Accept certificate? [N]o, [T]emporarily, [P]ermenantly : 

last msg "Accept certificate? [N]o, [T]emporarily, [P]ermenantly :" is printed many times when you kill the client without answering the question.

This issue was found during investigation of JON issue bz1226413 and is causing the OutOfMemoryError: Java heap space exception because the JON agent reads jboss-cli output which very very long.

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

How reproducible:
Always

Steps to Reproduce:
1. configure secured EAP (standalone.xml is attached)
2. run cli client (e.g. ./jboss-cli.sh --connect --controller=10.16.23.184:10099)
3. wait a few seconds
4. kill it (ctrl+c)

Actual results:
./jboss-cli.sh --connect --controller=10.16.23.184:10099
Unable to connect due to unrecognised server certificate
Subject    - CN=client,OU=rhq,O=redhat
Issuer     - CN=client, OU=rhq, O=redhat
Valid From - Thu Mar 13 06:15:46 EDT 2014
Valid To   - Sun Mar 10 06:15:46 EDT 2024
SHA1 : 07:2e:d3:88:65:f4:66:a7:ed:83:af:1b:9b:6b:e9:8e:3d:11:ed:2b
MD5 : ed:ee:32:b1:de:88:49:5a:93:4e:76:2f:4b:0a:2a:48

Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly : Accept certificate? [N]o, [T]emporarily, [P]ermenantly :
...
...
...
[hudson@eap62-sec bin]$ 


Expected results:
./jboss-cli.sh --connect --controller=10.16.23.184:10099^C
[hudson@fbr-eap62-sec bin]$ ./jboss-cli.sh --connect --controller=10.16.23.184:10099
Unable to connect due to unrecognised server certificate
Subject    - CN=client,OU=rhq,O=redhat
Issuer     - CN=client, OU=rhq, O=redhat
Valid From - Thu Mar 13 06:15:46 EDT 2014
Valid To   - Sun Mar 10 06:15:46 EDT 2024
SHA1 : 07:2e:d3:88:65:f4:66:a7:ed:83:af:1b:9b:6b:e9:8e:3d:11:ed:2b
MD5 : ed:ee:32:b1:de:88:49:5a:93:4e:76:2f:4b:0a:2a:48

Accept certificate? [N]o, [T]emporarily, [P]ermenantly :[hudson@eap62-sec bin]$ 

Additional info:
This is regression, the issue is not visible on EAP 6.2.4

Comment 6 Mike McCune 2016-03-28 22:24:40 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 7 Peter Mackay 2017-05-15 14:56:23 UTC
Verified with EAP 6.4.15.CP.CR3

Comment 8 Petr Penicka 2017-05-19 08:05:25 UTC
Released on May 18 as part of EAP 6.4.15.