[JBoss JIRA] (TEIID-4029) After terminating long running queries remains CPU load > 100% on JBoss java process
by Colin Mondesir (JIRA)
Colin Mondesir created TEIID-4029:
-------------------------------------
Summary: After terminating long running queries remains CPU load > 100% on JBoss java process
Key: TEIID-4029
URL: https://issues.jboss.org/browse/TEIID-4029
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.7.4
Reporter: Colin Mondesir
Assignee: Steven Hawkins
Fix For: 8.12.x
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%
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (TEIID-4013) ODBC sessions never release
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4013?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4013:
---------------------------------------
We don't have enough here to determine if there is an issue. I can confirm with normal usage of JDBC/ODBC over our pg socket transport that connections are closed as expected. You should open a corresponding support issue so that you and support can work on reproduciblity and then we can follow up here if needed.
> ODBC sessions never release
> ---------------------------
>
> Key: TEIID-4013
> URL: https://issues.jboss.org/browse/TEIID-4013
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1.6_2
> Environment: Red Hat JBoss Data Virtualization 6.2.2 on EAP6.4.0 patched to version 6.4.5,
> JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157
> 64-bit Windows 7 environment
> Reporter: Steve Tran
> Assignee: Steven Hawkins
> Attachments: Capture.PNG, Capture2.PNG, Capture3.PNG
>
>
> I have 3 ODBC System DSNs on a Windows server. When I'm viewing the Deployed VDBs and looking at the Sessions tab, the ODBC connections never seem to time out or release. Not really sure if/when they should release, but they continue to multiply. See screenshots.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (TEIID-3782) OData V4: Support system options over the operation based collections
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3782?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3782:
-------------------------------------
The DataRequest was always around the EntityTypes, so isCountRequest became as sub-class of the DataRequest. Where as Function/Action are may or may not be based on EntityTypes so I did not design. It may be easier add corresponding code to Teiid for now.
> OData V4: Support system options over the operation based collections
> ---------------------------------------------------------------------
>
> Key: TEIID-3782
> URL: https://issues.jboss.org/browse/TEIID-3782
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.11
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Fix For: 8.12.x
>
>
> Currently the system options like $top, $skip, $filter are not supported on results returned from Functions/Actions. Per OData specification this should be supported.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (TEIID-4024) Server fails to shutdown if vdb with REST service generation is deployed
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4024?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4024:
---------------------------------------
I can see the hang in:
org.jboss.msc.service.StabilityMonitor.awaitStability(StabilityMonitor.java:347)
I haven't yet tracked down why it considers the state unstable. I'm also seeing bad behavior with the automatic war deployment in general - it seems inconsistent. On initial load it may not be generated, but generally is on :reload
> Server fails to shutdown if vdb with REST service generation is deployed
> ------------------------------------------------------------------------
>
> Key: TEIID-4024
> URL: https://issues.jboss.org/browse/TEIID-4024
> Project: Teiid
> Issue Type: Bug
> Components: VDB
> Affects Versions: 8.12.5
> Environment: DV 6.3 ER1
> Reporter: Filip Elias
> Assignee: Steven Hawkins
> Attachments: nosource-vdb.xml, server_trace.log
>
>
> DV sometimes won't stop if vdb with REST service generation is deployed.
> Server log is in the attachment.
> When the server is killed and started again, it will stop correctly.
> The issue is random. Server fails to stop in 50% of cases.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (TEIID-3782) OData V4: Support system options over the operation based collections
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3782?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3782:
---------------------------------------
> Should give you access to the system options, or I am mis-reading something
It seems inconsistent that DataRequest for example has isCountRequest, but OperationRequest (Action/Function) do not. If it's just expected that we revisit the url ourselves, then we can easily do that.
> OData V4: Support system options over the operation based collections
> ---------------------------------------------------------------------
>
> Key: TEIID-3782
> URL: https://issues.jboss.org/browse/TEIID-3782
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.11
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Fix For: 8.12.x
>
>
> Currently the system options like $top, $skip, $filter are not supported on results returned from Functions/Actions. Per OData specification this should be supported.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (TEIID-4025) Web admin console typo when setting time-slice-in-milliseconds attribute
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4025?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4025:
---------------------------------------
Was there a change made for this?
> Web admin console typo when setting time-slice-in-milliseconds attribute
> ------------------------------------------------------------------------
>
> Key: TEIID-4025
> URL: https://issues.jboss.org/browse/TEIID-4025
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Affects Versions: 8.12.5
> Reporter: Filip Elias
> Assignee: Van Halbert
> Fix For: 9.0, 8.12.x
>
>
> Admin console prints error when editing Threading attributes.
> Typo in attribute name: time-slice-in-millseconds
> {code}
> Unknown error
> Unexpected HTTP response: 500
> Request
> {
> "operation" => "composite",
> "address" => [],
> "steps" => [{
> "address" => [("subsystem" => "teiid")],
> "operation" => "write-attribute",
> "name" => "time-slice-in-millseconds",
> "value" => 10000
> }]
> }
> Response
> Internal Server Error
> {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "failure-description" => "JBAS014792: Unknown attribute time-slice-in-millseconds",
> "rolled-back" => true
> }},
> "failure-description" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014792: Unknown attribute time-slice-in-millseconds"}},
> "rolled-back" => true,
> "response-headers" => {"process-state" => "reload-required"}
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (TEIID-4026) Web Admin Console: Invalid attribute in SSL configuration
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4026?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4026.
-----------------------------------
Resolution: Duplicate Issue
Duplicate of TEIIDWEBCN-20
> Web Admin Console: Invalid attribute in SSL configuration
> ---------------------------------------------------------
>
> Key: TEIID-4026
> URL: https://issues.jboss.org/browse/TEIID-4026
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Affects Versions: 8.12.5
> Environment: ER1
> Reporter: Filip Elias
> Assignee: Steven Hawkins
>
> It seems ssl-enable is invalid attribute (ssl can be enabled through attribute 'mode'). I assume it can be removed from menu. Configuration fails when SSL Enabled is checked.
> Error:
> {code}
> Unknown error
> Unexpected HTTP response: 500
> Request
> {
> "operation" => "composite",
> "address" => [],
> "steps" => [{
> "address" => [
> ("subsystem" => "teiid"),
> ("transport" => "embedded")
> ],
> "operation" => "write-attribute",
> "name" => "ssl-enable",
> "value" => true
> }]
> }
> Response
> Internal Server Error
> {
> "outcome" => "failed",
> "result" => {"step-1" => {
> "outcome" => "failed",
> "failure-description" => "JBAS014792: Unknown attribute ssl-enable",
> "rolled-back" => true
> }},
> "failure-description" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014792: Unknown attribute ssl-enable"}},
> "rolled-back" => true,
> "response-headers" => {"process-state" => "reload-required"}
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (TEIID-4027) Cache Hit Ratio Cache Statistics always NaN and despite appearing under the VDB tab don't change per VDB
by Van Halbert (JIRA)
Van Halbert created TEIID-4027:
----------------------------------
Summary: Cache Hit Ratio Cache Statistics always NaN and despite appearing under the VDB tab don't change per VDB
Key: TEIID-4027
URL: https://issues.jboss.org/browse/TEIID-4027
Project: Teiid
Issue Type: Bug
Components: Tooling
Reporter: Van Halbert
Assignee: Barry LaFond
Cache Hit Ratio Cache Statistics always NaN and despite appearing under the VDB tab don't change per VDB
Steps to Reproduce:
- goto admin console of the running JDV environment http://host:9990/console
- select tab Runtime
- select menu option Virtual Database
- select VDB
- select Caching tab
Notice that Cache Hit Ratio is always NaN, furthermore note that the Total entries Request count are not changed per VDB
Additional info:
As these are Global metrics they should be moved to the Runtime
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month