Bug 1094279 - [QE] (6.2.3) Appclient hangs after application is stopped
Summary: [QE] (6.2.3) Appclient hangs after application is stopped
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Application Client
Version: 6.2.3
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: CR3
: EAP 6.2.3
Assignee: Stuart Douglas
QA Contact: Petr Kremensky
Russell Dickenson
URL:
Whiteboard:
Depends On: 1082461
Blocks: eap62-cp03-blockers
TreeView+ depends on / blocked
 
Reported: 2014-05-05 12:05 UTC by Petr Kremensky
Modified: 2014-06-09 12:48 UTC (History)
6 users (show)

Fixed In Version:
Clone Of: 1082461
Environment:
Last Closed: 2014-06-09 12:48:01 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
calc.ear (11.43 KB, application/zip)
2014-05-05 12:05 UTC, Petr Kremensky 		no flags Details
View All

Description Petr Kremensky 2014-05-05 12:05:02 UTC 
Created attachment 892508 [details]
calc.ear

+++ This bug was initially created as a clone of Bug #1082461 +++

Description of problem:
Appclient hangs after server stop

Version-Release number of selected component (if applicable):
EAP 6.2.3.CP.CR2

How reproducible:
Always

Steps to Reproduce:
1. start standalone server 
2. deploy calc.ear (see attachment)
3. run following command: 
./appclient.sh /home/pkremens/devel/eap-tests-scripts/scripts-testing/target/test-classes/appclient/calc.ear#jboss-as-ejb-remote-client-7.1.1.CR1.jar
4. run the command again
./appclient.sh /home/pkremens/devel/eap-tests-scripts/scripts-testing/target/test-classes/appclient/calc.ear#jboss-as-ejb-remote-client-7.1.1.CR1.jar

Actual results:
program hangs with last line stating JBoss EAP stopped

Expected results:
program terminates and returns to command line

Additional info:
See BZ1012968
Comment 2 Vladimir Dosoudil 2014-05-06 10:47:11 UTC 
Backported BZ#1082461.
PR: https://github.com/jbossas/jboss-eap/pull/1301
Comment 3 Petr Kremensky 2014-05-19 06:13:42 UTC 
Verified on EAP 6.2.3.CR3.
Note You need to log in before you can comment on or make changes to this bug.