[JBoss JIRA] (TEIID-5151) cli scripts should set logging pattren
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-5151:
-------------------------------------
Summary: cli scripts should set logging pattren
Key: TEIID-5151
URL: https://issues.jboss.org/browse/TEIID-5151
Project: Teiid
Issue Type: Quality Risk
Components: Build/Kits
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Minor
Fix For: 10.1
Logging format patterns are only set in the auditcommand-logging.cli scripts, but should be in the base scripts to match the default standalone-teiid configuration.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5138) JGroups Channel creation in domain mode is invalid
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5138?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5138:
---------------------------------------
Doing:
./standalone.sh -c standalone-ha.xml
and applying
./jboss-cli.sh --file=scripts/teiid-standalone-ha-mode-install.cli
The script will error out on teiid:add with the same port error that went with this issue.
However adding a fork channel for both the caches and the stack to be used by the replicator just result in a different error. It would appear that the fork is not needed for the replicated cache, but even removing that results in yet another error.
> JGroups Channel creation in domain mode is invalid
> --------------------------------------------------
>
> Key: TEIID-5138
> URL: https://issues.jboss.org/browse/TEIID-5138
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 10.0
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Priority: Critical
> Fix For: 10.1, 10.0.1
>
>
> In domain mode configuration where the JGroups channel is configured, it is configured to be used as a separate channel where it would require separate protocol stack, which is also discouraged form. The suggested configuration is to create a forked channel as
> {code}
> <channel name="ee" stack="udp" cluster="ejb">
> <fork name="teiid-cluster"/>
> </channel>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5138) JGroups Channel creation in domain mode is invalid
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5138?page=com.atlassian.jira.plugin... ]
Steven Hawkins reopened TEIID-5138:
-----------------------------------
This needs to be applied to the ha script as well.
> JGroups Channel creation in domain mode is invalid
> --------------------------------------------------
>
> Key: TEIID-5138
> URL: https://issues.jboss.org/browse/TEIID-5138
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 10.0
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Priority: Critical
> Fix For: 10.1, 10.0.1
>
>
> In domain mode configuration where the JGroups channel is configured, it is configured to be used as a separate channel where it would require separate protocol stack, which is also discouraged form. The suggested configuration is to create a forked channel as
> {code}
> <channel name="ee" stack="udp" cluster="ejb">
> <fork name="teiid-cluster"/>
> </channel>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5150) JDG source model with 'v' letter at beginning of a name doesn't work.
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIID-5150?page=com.atlassian.jira.plugin... ]
Matej Kralik updated TEIID-5150:
--------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1514019
> JDG source model with 'v' letter at beginning of a name doesn't work.
> ---------------------------------------------------------------------
>
> Key: TEIID-5150
> URL: https://issues.jboss.org/browse/TEIID-5150
> Project: Teiid
> Issue Type: Bug
> Components: JDG Connector
> Affects Versions: 8.12.x-6.4
> Environment: Fedora 26
> Mac OS 10.12
> Reporter: Matej Kralik
> Assignee: Steven Hawkins
> Priority: Critical
> Attachments: BookMat-vdb.xml
>
>
> When the name of a JDG source model starts with 'v' letter, after run query at the materialized table (BooksMatView.viewBooks in attached VDB), the server shows exception:
> {code:java}
> 14:29:19,383 WARN [org.infinispan.client.hotrod.impl.protocol.Codec21] (Worker3_QueryProcessorQueue176) ISPN004005: Error received from the server: java.lang.IllegalArgumentException: Message descriptor not found : endorBookJDGSource.viewBooks
> 14:29:19,384 ERROR [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue176) Connector worker process failed for atomic-request=X6jNnAMTIgyp.0.6.248: org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=551 returned server error (status=0x85): java.lang.IllegalArgumentException: Message descriptor not found : endorBookJDGSource.viewBooks
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:363) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:152) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:138) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:60) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:68) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:30) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:57) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.query.RemoteQuery.executeQuery(RemoteQuery.java:68) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.infinispan.client.hotrod.impl.query.RemoteQuery.list(RemoteQuery.java:53) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
> at org.teiid.translator.infinispan.hotrod.InfinispanResponse.fetchNextBatch(InfinispanResponse.java:76) [translator-infinispan-hotrod-8.12.11.6_4-redhat-7.jar:8.12.11.6_4-redhat-7]
> at org.teiid.translator.infinispan.hotrod.InfinispanResponse.getNextRow(InfinispanResponse.java:92) [translator-infinispan-hotrod-8.12.11.6_4-redhat-7.jar:8.12.11.6_4-redhat-7]
> at org.teiid.translator.infinispan.hotrod.InfinispanQueryExecution.next(InfinispanQueryExecution.java:142) [translator-infinispan-hotrod-8.12.11.6_4-redhat-7.jar:8.12.11.6_4-redhat-7]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:433) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:236) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at sun.reflect.GeneratedMethodAccessor167.invoke(Unknown Source) [:1.8.0_65]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_65]
> at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_65]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at com.sun.proxy.$Proxy42.more(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:309) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_65]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_65]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_65]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_65]
> 14:29:19,389 WARN [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue177) TEIID30020 Processing exception for request X6jNnAMTIgyp.0 'TEIID30504 vendorBookJDGSource: java.lang.IllegalArgumentException: Message descriptor not found : endorBookJDGSource.viewBooks'. Originally TeiidProcessingException Codec20.java:363. Enable more detailed logging to see the entire stacktrace.
> {code}
> JDG source model has name *vendorBookJDGSource*.
> However, the name of JDG source model in the exception doesn't contain first 'v' letter ( Message descriptor not found : *endorBookJDGSource*.viewBooks ).
> Jdg server doesn't show any exception. I use DV 6.4.0 ER3, JDG 7.1 server and JDG 7.1.1 CR2 EAP module.
> In the attachments, I upload my VDB. Remove 'v' letter fix the issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5150) JDG source model with 'v' letter at beginning of a name doesn't work.
by Matej Kralik (JIRA)
Matej Kralik created TEIID-5150:
-----------------------------------
Summary: JDG source model with 'v' letter at beginning of a name doesn't work.
Key: TEIID-5150
URL: https://issues.jboss.org/browse/TEIID-5150
Project: Teiid
Issue Type: Bug
Components: JDG Connector
Affects Versions: 8.12.x-6.4
Environment: Fedora 26
Mac OS 10.12
Reporter: Matej Kralik
Assignee: Steven Hawkins
Priority: Critical
Attachments: BookMat-vdb.xml
When the name of a JDG source model starts with 'v' letter, after run query at the materialized table (BooksMatView.viewBooks in attached VDB), the server shows exception:
{code:java}
14:29:19,383 WARN [org.infinispan.client.hotrod.impl.protocol.Codec21] (Worker3_QueryProcessorQueue176) ISPN004005: Error received from the server: java.lang.IllegalArgumentException: Message descriptor not found : endorBookJDGSource.viewBooks
14:29:19,384 ERROR [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue176) Connector worker process failed for atomic-request=X6jNnAMTIgyp.0.6.248: org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=551 returned server error (status=0x85): java.lang.IllegalArgumentException: Message descriptor not found : endorBookJDGSource.viewBooks
at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:363) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:152) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:138) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:60) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:68) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:30) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:57) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
at org.infinispan.client.hotrod.impl.query.RemoteQuery.executeQuery(RemoteQuery.java:68) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
at org.infinispan.client.hotrod.impl.query.RemoteQuery.list(RemoteQuery.java:53) [infinispan-client-hotrod.jar:8.4.1.Final-redhat-2]
at org.teiid.translator.infinispan.hotrod.InfinispanResponse.fetchNextBatch(InfinispanResponse.java:76) [translator-infinispan-hotrod-8.12.11.6_4-redhat-7.jar:8.12.11.6_4-redhat-7]
at org.teiid.translator.infinispan.hotrod.InfinispanResponse.getNextRow(InfinispanResponse.java:92) [translator-infinispan-hotrod-8.12.11.6_4-redhat-7.jar:8.12.11.6_4-redhat-7]
at org.teiid.translator.infinispan.hotrod.InfinispanQueryExecution.next(InfinispanQueryExecution.java:142) [translator-infinispan-hotrod-8.12.11.6_4-redhat-7.jar:8.12.11.6_4-redhat-7]
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:433) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:236) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
at sun.reflect.GeneratedMethodAccessor167.invoke(Unknown Source) [:1.8.0_65]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_65]
at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_65]
at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
at com.sun.proxy.$Proxy42.more(Unknown Source)
at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:309) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_65]
at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_65]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_65]
14:29:19,389 WARN [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue177) TEIID30020 Processing exception for request X6jNnAMTIgyp.0 'TEIID30504 vendorBookJDGSource: java.lang.IllegalArgumentException: Message descriptor not found : endorBookJDGSource.viewBooks'. Originally TeiidProcessingException Codec20.java:363. Enable more detailed logging to see the entire stacktrace.
{code}
JDG source model has name *vendorBookJDGSource*.
However, the name of JDG source model in the exception doesn't contain first 'v' letter ( Message descriptor not found : *endorBookJDGSource*.viewBooks ).
Jdg server doesn't show any exception. I use DV 6.4.0 ER3, JDG 7.1 server and JDG 7.1.1 CR2 EAP module.
In the attachments, I upload my VDB. Remove 'v' letter fix the issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5149) Infinispan-hotrod translator used cache name 'default' as a default value, when it may not be configured
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-5149?page=com.atlassian.jira.plugin... ]
Van Halbert reassigned TEIID-5149:
----------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
> Infinispan-hotrod translator used cache name 'default' as a default value, when it may not be configured
> --------------------------------------------------------------------------------------------------------
>
> Key: TEIID-5149
> URL: https://issues.jboss.org/browse/TEIID-5149
> Project: Teiid
> Issue Type: Bug
> Components: JDG Connector
> Affects Versions: 8.12.x-6.4
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
>
> A JDG server was configured so that only the needed caches be configured, which included removing the 'default' cache. It was then determined that there was an issue with Teiid integrating with a JDG, because the default cache is referenced and causes a failure.
> Did notice in the ProtobufMetadataProcessor that the default value for "cacheName" is 'default'. So this maybe where the possible problem is.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5149) Infinispan-hotrod translator used cache name 'default' as a default value, when it may not be configured
by Van Halbert (JIRA)
Van Halbert created TEIID-5149:
----------------------------------
Summary: Infinispan-hotrod translator used cache name 'default' as a default value, when it may not be configured
Key: TEIID-5149
URL: https://issues.jboss.org/browse/TEIID-5149
Project: Teiid
Issue Type: Bug
Components: JDG Connector
Affects Versions: 8.12.x-6.4
Reporter: Van Halbert
Assignee: Steven Hawkins
A JDG server was configured so that only the needed caches be configured, which included removing the 'default' cache. It was then determined that there was an issue with Teiid integrating with a JDG, because the default cache is referenced and causes a failure.
Did notice in the ProtobufMetadataProcessor that the default value for "cacheName" is 'default'. So this maybe where the possible problem is.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5148) Native: Executing procedures without return values yields an error
by Fábio Franco (JIRA)
[ https://issues.jboss.org/browse/TEIID-5148?page=com.atlassian.jira.plugin... ]
Fábio Franco edited comment on TEIID-5148 at 11/15/17 2:58 PM:
---------------------------------------------------------------
Thank you for replying. A fix in my perspective would be, as you said, a general handling of the PGObject which would mean calling the native function and not having an exception thrown since there were no errors, just a void function. I agree when you say most functions will be non void and the workaround is easy... nevertheless it would be interesting to have this case covered as well. I mean, if possible, of course. Thanks in advance.
was (Author: mrfabiofranco):
Thank you for replying. A fix in my perspective would be, as you said, a general handling of the PGObject which would mean calling the native function and not having an exception thrown since there were no errors, just a void function. I agree when you say most functions will be non void and the workaround is easy... nevertheless it would be interesting to have this case covered as well, if possible, of course. Thanks in advance.
> Native: Executing procedures without return values yields an error
> ------------------------------------------------------------------
>
> Key: TEIID-5148
> URL: https://issues.jboss.org/browse/TEIID-5148
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 9.3.3
> Environment: * teiid 9.3.3
> * jdbc driver: postgresql-9.4.1212.jre7.jar
> * PostgreSQL 9.6.2 on x86_64-pc-linux-gnu, compiled by gcc (Debian 4.9.2-10) 4.9.2, 64-bit
> * java 1.8.0_141-b15
> Reporter: Fábio Franco
> Assignee: Steven Hawkins
>
> Executing procedures without return values yields an error when executed via native function from within teiid. The stacktrace is as follows:
> {code}
> [2017-11-14 11:25:48] [38000] org.postgresql.util.PGobject
> [2017-11-14 11:25:48] java.lang.ClassNotFoundException: org.postgresql.util.PGobject
> [2017-11-14 11:25:48] at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> [2017-11-14 11:25:48] at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> [2017-11-14 11:25:48] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> [2017-11-14 11:25:48] at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> [2017-11-14 11:25:48] at java.lang.Class.forName0(Native Method)
> [2017-11-14 11:25:48] at java.lang.Class.forName(Class.java:348)
> [2017-11-14 11:25:48] at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:677)
> [2017-11-14 11:25:48] at org.teiid.netty.handler.codec.serialization.CompactObjectInputStream.resolveClass(CompactObjectInputStream.java:112)
> [2017-11-14 11:25:48] at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1819)
> [2017-11-14 11:25:48] at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1713)
> [2017-11-14 11:25:48] at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1986)
> [2017-11-14 11:25:48] at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1535)
> [2017-11-14 11:25:48] at java.io.ObjectInputStream.readObject(ObjectInputStream.java:422)
> [2017-11-14 11:25:48] at org.teiid.client.BatchSerializer$ColumnSerializer.readObject(BatchSerializer.java:552)
> [2017-11-14 11:25:48] at org.teiid.client.BatchSerializer$ObjectColumnSerializer.readObject(BatchSerializer.java:283)
> [2017-11-14 11:25:48] at org.teiid.client.BatchSerializer$ObjectColumnSerializer.access$2400(BatchSerializer.java:228)
> [2017-11-14 11:25:48] at org.teiid.client.BatchSerializer$ArrayColumnSerializer2.readObject(BatchSerializer.java:177)
> [2017-11-14 11:25:48] at org.teiid.client.BatchSerializer$ColumnSerializer.readColumn(BatchSerializer.java:543)
> [2017-11-14 11:25:48] at org.teiid.client.BatchSerializer.readBatch(BatchSerializer.java:924)
> [2017-11-14 11:25:48] at org.teiid.client.ResultsMessage.processResults(ResultsMessage.java:120)
> [2017-11-14 11:25:48] at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:755)
> [2017-11-14 11:25:48] at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:65)
> [2017-11-14 11:25:48] at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:561)
> [2017-11-14 11:25:48] at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:135)
> [2017-11-14 11:25:48] at org.teiid.client.util.ResultsFuture.access$200(ResultsFuture.java:40)
> [2017-11-14 11:25:48] at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:79)
> [2017-11-14 11:25:48] at org.teiid.net.socket.SocketServerInstanceImpl.receivedMessage(SocketServerInstanceImpl.java:285)
> [2017-11-14 11:25:48] at org.teiid.net.socket.SocketServerInstanceImpl.read(SocketServerInstanceImpl.java:337)
> [2017-11-14 11:25:48] at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
> [2017-11-14 11:25:48] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [2017-11-14 11:25:48] at java.lang.reflect.Method.invoke(Method.java:498)
> [2017-11-14 11:25:48] at org.teiid.net.socket.SocketServerConnectionFactory$ShutdownHandler.invoke(SocketServerConnectionFactory.java:98)
> [2017-11-14 11:25:48] at com.sun.proxy.$Proxy3.read(Unknown Source)
> [2017-11-14 11:25:48] at org.teiid.net.socket.SocketServerInstanceImpl$RemoteInvocationHandler$1.get(SocketServerInstanceImpl.java:427)
> [2017-11-14 11:25:48] at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:570)
> [2017-11-14 11:25:48] at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:423)
> [2017-11-14 11:25:48] at org.teiid.jdbc.StatementImpl.executeQuery(StatementImpl.java:354)
> [2017-11-14 11:25:48] at com.intellij.database.remote.jdbc.impl.RemoteStatementImpl.executeQuery(RemoteStatementImpl.java:161)
> [2017-11-14 11:25:48] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [2017-11-14 11:25:48] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [2017-11-14 11:25:48] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [2017-11-14 11:25:48] at java.lang.reflect.Method.invoke(Method.java:498)
> [2017-11-14 11:25:48] at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:346)
> [2017-11-14 11:25:48] at sun.rmi.transport.Transport$1.run(Transport.java:200)
> [2017-11-14 11:25:48] at sun.rmi.transport.Transport$1.run(Transport.java:197)
> [2017-11-14 11:25:48] at java.security.AccessController.doPrivileged(Native Method)
> [2017-11-14 11:25:48] at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> [2017-11-14 11:25:48] at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
> [2017-11-14 11:25:48] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
> [2017-11-14 11:25:48] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
> [2017-11-14 11:25:48] at java.security.AccessController.doPrivileged(Native Method)
> [2017-11-14 11:25:48] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
> [2017-11-14 11:25:48] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [2017-11-14 11:25:48] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [2017-11-14 11:25:48] at java.lang.Thread.run(Thread.java:745) (no stack trace)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5139) Reached maximum thread count "10" for worker pool "async-teiid-threads"
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5139?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5139.
-----------------------------------
Fix Version/s: 10.1
10.0.1
Resolution: Done
Addressed by removing the logic around treating the element as an attribute. Also updated the docs with more on the async pool.
> Reached maximum thread count "10" for worker pool "async-teiid-threads"
> -----------------------------------------------------------------------
>
> Key: TEIID-5139
> URL: https://issues.jboss.org/browse/TEIID-5139
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 10.0
> Environment: Teiid 10.0.0
> Wildfly 11
> RHEL 7.2
> Reporter: Pedro Inácio
> Assignee: Steven Hawkins
> Fix For: 10.1, 10.0.1
>
> Attachments: teiid.7z
>
>
> Cannot configure system to remove the following warning:
> *TEIID30009 Reached maximum thread count "10" for worker pool "async-teiid-threads" with a queue size high of "44". Queued work waited 500 ms prior to executing. To avoid queuing of work you may consider increasing "max-threads" or decreasing the "max-active-plans" in the "standalone-teiid.xml" file.*
> Already tried what is explained [here|https://developer.jboss.org/thread/275761] but applied for the standalone mode without any success.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month