Bug 1120243 - Business-central deployed on EAP cannot be stopped.
Summary: Business-central deployed on EAP cannot be stopped.
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: DR2
: 6.1.0
Assignee: Maciej Swiderski
QA Contact: Radovan Synek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-16 14:07 UTC by Radovan Synek
Modified: 2014-09-11 14:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)
thread dump (94.17 KB, text/plain)
2014-07-16 14:07 UTC, Radovan Synek
no flags Details

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


Note You need to log in before you can comment on or make changes to this bug.