[
https://issues.jboss.org/browse/TEIID-3404?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-3404:
------------------------------------
This was driven by a customer. And H2 is NOT recommended for production, and is
configurable at installation time. Also, the teiid-dashboard has a new logging
workspace that is made available when the logging database used.
Teiid DatabaseAppender JPA perisist Command log consume high CPU
----------------------------------------------------------------
Key: TEIID-3404
URL:
https://issues.jboss.org/browse/TEIID-3404
Project: Teiid
Issue Type: Bug
Components: Tools
Affects Versions: 8.7.1
Environment: * DV 6.1
* dynamicvdb-datafederation quickstart
Reporter: Kylin Soong
Assignee: Kylin Soong
I have 4 - 5 concurrent client query to Portfolio VDB, this cause log DatabaseAppender
JPA perisist Command log thread consume high CPU. In my test, one log threads always
swallow high CPU, if the concurrent client query more than 10, it swallow 100% cpu.
[1] have detailed reproduce steps, including thread dumps.
[1]
https://github.com/kylinsoong/teiid-samples/tree/master/command-logging-h...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)