Bug 1315279 - Server fails to shutdown if vdb with REST service generation is deployed
Summary: Server fails to shutdown if vdb with REST service generation is deployed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Teiid
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: ER1
: 6.3.0
Assignee: Van Halbert
QA Contact: Filip Elias
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-07 12:00 UTC by Filip Elias
Modified: 2016-08-24 11:44 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
DV 6.3 ER1
Last Closed: 2016-08-24 11:44:18 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
VDB (848 bytes, text/plain)
2016-03-07 12:00 UTC, Filip Elias 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIID-4024 0 Major Resolved Server fails to shutdown if vdb with REST service generation is deployed 2016-11-21 10:02:32 UTC

Description Filip Elias 2016-03-07 12:00:12 UTC 
Created attachment 1133716 [details]
VDB

DV sometimes won't stop if vdb with REST service generation is deployed.

Steps to reproduces:
1. Create a clean copy of DV 6.3 ER1
2. Deploy nosource-vdb.xml (in the attachment) using CLI: deploy /pathtovdb/nosource-vdb.xml
3. Shutdown the server using CLI: shutdown

Server log is in the associated jira.

When the server is killed and started again, it will stop correctly.

The issue is random. Server fails to stop in 50% of cases.
Comment 1 Alex Szczuczko 2016-03-07 12:06:24 UTC 
I was thinking this might be caused by a race condition involving a non-daemon thread, which I guess must be introduced in the scenario you identify. Just a guess. Maybe jconsole or a debugger could be used to check.
Comment 2 JBoss JIRA Server 2016-03-09 15:46:47 UTC 
Steven Hawkins <shawkins> updated the status of jira TEIID-4024 to Resolved
Comment 3 Van Halbert 2016-03-09 15:51:04 UTC 
This is included in ER1.2 build.
Note You need to log in before you can comment on or make changes to this bug.