Bug 1120243

Summary: Business-central deployed on EAP cannot be stopped.
Product: [Retired] JBoss BRMS Platform 6 Reporter: Radovan Synek <rsynek>
Component: Business CentralAssignee: manstis
Status: CLOSED EOL QA Contact: Radovan Synek <rsynek>
Severity: high Docs Contact:
Priority: high    
Version: 6.1.0CC: kverlaen, rrajasek, rzhang
Target Milestone: DR2Keywords: TestBlocker
Target Release: 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 20:02:11 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:
Attachments:
Description Flags
thread dump none

Description Radovan Synek 2014-07-16 14:07:46 UTC
Created attachment 918427 [details]
thread dump

Description of problem:
Having Business-central deployed on EAP 6.3.0 or EAP 6.1.1, after an attempt to stop the server via SIGINT (ctrl+c), it's still running. Attaching thread dump from the described situation, there are several threads waiting in org.uberfire.java.nio.fs.jgit.JGitFileSystem$4.take(JGitFileSystem.java:298).

In comparison with BRMS-6.0.2.GA, there are 2 additional threads waiting inside the method stated above:
"EJB default - 1" and "EJB default - 2"
java.lang.Thread.State: TIMED_WAITING (sleeping)
	at java.lang.Thread.sleep(Native Method)
	at org.uberfire.java.nio.fs.jgit.JGitFileSystem$4.take(JGitFileSystem.java:298)
	at org.uberfire.backend.server.AbstractWatchService$1.execute(AbstractWatchService.java:118)
	at org.uberfire.backend.server.ExecutorManager.execute(ExecutorManager.java:48)

Please see the attached thread dump for more details.

Version-Release number of selected component (if applicable):
6.1.0.DR1

How reproducible:
always

Steps to Reproduce:
1. deploy Business-central to EAP 6.3.0 (tried with EAP 6.3.0.Beta1)
2. stop the EAP by using ctrl+c => still running

alternatively, use EAP 6.1.1, the issue shows itself there as well.

Comment 4 Radovan Synek 2014-09-11 14:47:37 UTC
Verified with both BPMS and BRMS 6.1.0.DR2