Bug 1315378 - After terminating long running queries remains CPU load > 100% on JBoss java process [NEEDINFO]
Summary: After terminating long running queries remains CPU load > 100% on JBoss java ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Teiid
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
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 15:26 UTC by Colin Mondesir
Modified: 2016-08-24 11:47 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-24 11:47:10 UTC
Type: Bug
jdurani: needinfo? (vhalbert)


Attachments (Terms of Use)
reproducer (123.80 KB, application/zip)
2016-03-07 15:26 UTC, Colin Mondesir
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIID-3781 0 Major Closed Queries are not killed even if the client sends a cancel request 2018-05-18 06:28:42 UTC

Description Colin Mondesir 2016-03-07 15:26:37 UTC
Created attachment 1133821 [details]
reproducer

Once the request is submitted the CPU% load on the server remains > 100% despite cancelling the request and terminating the session. The only way I have found to bring the %CPU back to "normal" is to re-start the JDV instance.


1. Created two files file1.csv (1M rows) and file2.csv (1M rows)
2. Created two source and view models and VDB
SQL statement is a carthesion product
3. Deploy VDB
4. select * from combinedcsv from SQL scrapbook on cancelLongRunningQueries VDB
5. Goto admin console 
6. Go to the cancelLongRunningQueries VDB
7. Goto tab Requests and select Terminate
8. Goto tab Sessions and select Terminate JDBC session
9. CPU% load on JBoss java process remains > 100%

Comment 2 Juraj Duráni 2016-06-20 11:59:19 UTC
Is this issue fixed in 6.3.0? I can see that last commit in JIRA is "Revert".

Comment 3 Juraj Duráni 2016-06-28 10:26:32 UTC
Verified. Note, that there is another bug with synchronization - BZ1350333.

Setting this to VERIFIED.


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