[JBoss JIRA] (TEIID-4817) Infinispan DSL Resource Adapter: can't query after JDG restart
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4817?page=com.atlassian.jira.plugin... ]
Van Halbert updated TEIID-4817:
-------------------------------
Fix Version/s: 8.12.10.6_3
> Infinispan DSL Resource Adapter: can't query after JDG restart
> --------------------------------------------------------------
>
> Key: TEIID-4817
> URL: https://issues.jboss.org/browse/TEIID-4817
> Project: Teiid
> Issue Type: Bug
> Components: JDG Connector
> Affects Versions: 8.12.10.6_3
> Reporter: Jan Stastny
> Assignee: Van Halbert
> Priority: Blocker
> Fix For: 9.3, 8.12.10.6_3
>
>
> There is an issue with Infinispan DSL connector when accessing JDG after it has been restarted.
> When I have a vdb accessing JDG only as datasource and I do following:
> 1. Start JDV and JDG
> 2. Configure JDV to use JDG as datasource (no materialization needed)
> 3. Deploy a vdb accessing the JDG instance using a pojo.
> 4. Query the vdb with no issues.
> 5. Restart JDG (call reload using DMR/CLI)
> 6. Wait for JDG to come up.
> 7. Query the vdb again
> Then in step 7 I get:
> {code:plain|title="WARN in server log"}
> 12:32:32,749 WARN [org.infinispan.client.hotrod.impl.protocol.Codec21] (Worker1_QueryProcessorQueue5) ISPN004005: Error received from the server: java.lang.IllegalStateException: Unknown entity name org.jboss.qe.jdg.remote.protobuf.SmallA
> {code}
> {code:plain|title="full stacktrace"}
> 12:32:32,749 WARN [org.infinispan.client.hotrod.impl.protocol.Codec21] (Worker1_QueryProcessorQueue5) ISPN004005: Error received from the server: java.lang.IllegalStateException: Unknown entity name org.jboss.qe.jdg.remote.protobuf.SmallA
> 12:32:32,753 WARN [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue5) Connector worker process failed for atomic-request=jUZx1bBd0k4L.0.3.1: org.teiid.translator.TranslatorException: java.lang.IllegalStateException: Unknown entity name org.jboss.qe.jdg.remote.protobuf.SmallA
> at org.teiid.translator.object.ObjectExecution.execute(ObjectExecution.java:275) [translator-object-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:363) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_121]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_121]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_121]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_121]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1]
> at com.sun.proxy.$Proxy89.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_121]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:280) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_121]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_121]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_121]
> Caused by: org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for message id[9] returned server error (status=0x85): java.lang.IllegalStateException: Unknown entity name org.jboss.qe.jdg.remote.protobuf.SmallA
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:343)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:133)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:119)
> at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:56)
> at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:62)
> at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:28)
> at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:56)
> at org.infinispan.client.hotrod.impl.query.RemoteQuery.executeQuery(RemoteQuery.java:61)
> at org.infinispan.client.hotrod.impl.query.RemoteQuery.list(RemoteQuery.java:51)
> at org.teiid.resource.adapter.infinispan.dsl.DSLSearch.performSearch(DSLSearch.java:196)
> at org.teiid.resource.adapter.infinispan.dsl.DSLSearch.performSearch(DSLSearch.java:149)
> at org.teiid.translator.object.ObjectExecution.execute(ObjectExecution.java:261) [translator-object-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1]
> ... 18 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-4817) Infinispan DSL Resource Adapter: can't query after JDG restart
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4817?page=com.atlassian.jira.plugin... ]
Van Halbert updated TEIID-4817:
-------------------------------
Fix Version/s: 9.3
> Infinispan DSL Resource Adapter: can't query after JDG restart
> --------------------------------------------------------------
>
> Key: TEIID-4817
> URL: https://issues.jboss.org/browse/TEIID-4817
> Project: Teiid
> Issue Type: Bug
> Components: JDG Connector
> Affects Versions: 8.12.10.6_3
> Reporter: Jan Stastny
> Assignee: Van Halbert
> Priority: Blocker
> Fix For: 9.3, 8.12.10.6_3
>
>
> There is an issue with Infinispan DSL connector when accessing JDG after it has been restarted.
> When I have a vdb accessing JDG only as datasource and I do following:
> 1. Start JDV and JDG
> 2. Configure JDV to use JDG as datasource (no materialization needed)
> 3. Deploy a vdb accessing the JDG instance using a pojo.
> 4. Query the vdb with no issues.
> 5. Restart JDG (call reload using DMR/CLI)
> 6. Wait for JDG to come up.
> 7. Query the vdb again
> Then in step 7 I get:
> {code:plain|title="WARN in server log"}
> 12:32:32,749 WARN [org.infinispan.client.hotrod.impl.protocol.Codec21] (Worker1_QueryProcessorQueue5) ISPN004005: Error received from the server: java.lang.IllegalStateException: Unknown entity name org.jboss.qe.jdg.remote.protobuf.SmallA
> {code}
> {code:plain|title="full stacktrace"}
> 12:32:32,749 WARN [org.infinispan.client.hotrod.impl.protocol.Codec21] (Worker1_QueryProcessorQueue5) ISPN004005: Error received from the server: java.lang.IllegalStateException: Unknown entity name org.jboss.qe.jdg.remote.protobuf.SmallA
> 12:32:32,753 WARN [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue5) Connector worker process failed for atomic-request=jUZx1bBd0k4L.0.3.1: org.teiid.translator.TranslatorException: java.lang.IllegalStateException: Unknown entity name org.jboss.qe.jdg.remote.protobuf.SmallA
> at org.teiid.translator.object.ObjectExecution.execute(ObjectExecution.java:275) [translator-object-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:363) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_121]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_121]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_121]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_121]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1]
> at com.sun.proxy.$Proxy89.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_121]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:280) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_121]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_121]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_121]
> Caused by: org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for message id[9] returned server error (status=0x85): java.lang.IllegalStateException: Unknown entity name org.jboss.qe.jdg.remote.protobuf.SmallA
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:343)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:133)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:119)
> at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:56)
> at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:62)
> at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:28)
> at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:56)
> at org.infinispan.client.hotrod.impl.query.RemoteQuery.executeQuery(RemoteQuery.java:61)
> at org.infinispan.client.hotrod.impl.query.RemoteQuery.list(RemoteQuery.java:51)
> at org.teiid.resource.adapter.infinispan.dsl.DSLSearch.performSearch(DSLSearch.java:196)
> at org.teiid.resource.adapter.infinispan.dsl.DSLSearch.performSearch(DSLSearch.java:149)
> at org.teiid.translator.object.ObjectExecution.execute(ObjectExecution.java:261) [translator-object-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1]
> ... 18 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-4819) Tree page modifications removing the previous page, don't remove immediately
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-4819:
-------------------------------------
Summary: Tree page modifications removing the previous page, don't remove immediately
Key: TEIID-4819
URL: https://issues.jboss.org/browse/TEIID-4819
Project: Teiid
Issue Type: Bug
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Critical
Fix For: 9.3, 9.1.5, 9.2.2
TEIID-3119 introduced logic to reuse the existing cacheentry, but the removal of the old entry was based upon the wrong remove method - just a remove from cache and not memory. That would delay the cleanup of the memory reference until eviction or when the buffer/tree is removed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-4661) Subsequent queries hang after materialized view TTL expires.
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4661?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-4661:
------------------------------------
Is that correct, you tested off the 8.12.x branch, instead of the patch?
> Subsequent queries hang after materialized view TTL expires.
> ------------------------------------------------------------
>
> Key: TEIID-4661
> URL: https://issues.jboss.org/browse/TEIID-4661
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12.x
> Reporter: Colin Mondesir
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 9.0.6, 9.1.2, 9.2, 8.12.10.6_3
>
>
> With a VDB using lazy-invalidate in a clustered configuration initially the materialized view is cached correctly but when the TTL expires (10 minutes) and the query is run again the state of the view changes to LOADING and never reverts to "LOADED", so the next query hangs.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (TEIID-4661) Subsequent queries hang after materialized view TTL expires.
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-4661?page=com.atlassian.jira.plugin... ]
Jan Stastny reopened TEIID-4661:
--------------------------------
The fix in 8.12.x branch doesn't seem to fix the issue.
I use two servers in standalone-ha mode.
When I followed the steps in unit test in the commit, I still observe, that the state is still LOADING.
The one difference compared to the unit test is, that I do the test more times. 5 times instead of 2 which are in the unit test. Sometimes the issue happens on second check, sometimes on third.
{code:java|title="test method in a nutshell"}
private void loadAndWaitTtlExpires(Connection con, int times) throws SQLException, InterruptedException {
Statement st = con.createStatement();
for (int i = 1; i <= times; i++) {
st.execute("SELECT * FROM View.Data");
assertLoadStateOfMatView(con, "Data",
"Loadstate is not changed to loaded, after matview loading no. " + i + ".");
Thread.sleep(2000); // expire ttl
}
}
private void assertLoadStateOfMatView(Connection con, String matview, String message) throws SQLException {
Statement st = con.createStatement();
ResultSet rs2 = st.executeQuery("select * from matviews where name = 'Data'");
Assert.assertTrue(rs2.next());
Assert.assertEquals(rs2.getString("loadstate"), "LOADED", message);
}
{code}
My cache configuration is on both machines following:
{code:xml|title="standalone-ha.xml snippet"}
<cache-container name="teiid-cache" default-cache="resultset">
<transport/>
<local-cache name="resultset" batching="true">
<locking isolation="READ_COMMITTED"/>
<transaction mode="NON_XA"/>
<eviction strategy="LIRS" max-entries="1024"/>
<expiration lifespan="7200000"/>
</local-cache>
<local-cache name="preparedplan" batching="true">
<locking isolation="READ_COMMITTED"/>
<eviction strategy="LIRS" max-entries="512"/>
<expiration lifespan="28800"/>
</local-cache>
<replicated-cache name="resultset-repl" mode="SYNC" batching="true">
<locking isolation="READ_COMMITTED"/>
<transaction mode="NON_XA"/>
<eviction strategy="LIRS" max-entries="1024"/>
<expiration lifespan="7200000"/>
</replicated-cache>
</cache-container>
{code}
> Subsequent queries hang after materialized view TTL expires.
> ------------------------------------------------------------
>
> Key: TEIID-4661
> URL: https://issues.jboss.org/browse/TEIID-4661
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12.x
> Reporter: Colin Mondesir
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 9.0.6, 9.1.2, 9.2, 8.12.10.6_3
>
>
> With a VDB using lazy-invalidate in a clustered configuration initially the materialized view is cached correctly but when the TTL expires (10 minutes) and the query is run again the state of the view changes to LOADING and never reverts to "LOADED", so the next query hangs.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years