[JBoss JIRA] (TEIID-5130) Document/refine behavior of treating result parameter as the first parameter
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-5130?page=com.atlassian.jira.plugin... ]
Jan Stastny commented on TEIID-5130:
------------------------------------
[~shawkins] Is the change limited only to ws translator? Anyway, I tried on 8.12.12.6_4 and 9.3.4 with both virtual and foreign procedure, but the property doesn't seem to work.
I can deploy following vdbs:
{code:xml}
<vdb name="teiid5130" version="1">
<model name="View">
<source connection-jndi-name="java:/rest-swagger" name="test" translator-name="ws" />
<metadata type="DDL">
<![CDATA[
CREATE FOREIGN PROCEDURE resultParameterOnPosition1(out param1 string result, out param2 string);
CREATE FOREIGN PROCEDURE resultParameterOnPosition2(out param1 string, out param2 string result);
]]>
</metadata>
</model>
</vdb>
{code}
or
{code:xml}
<vdb name="teiid5130" version="1">
<model name="View" type="VIRTUAL">
<metadata type="DDL">
<![CDATA[
CREATE VIRTUAL PROCEDURE resultParameterOnPosition1(out param1 string result, out param2 string) AS
BEGIN
param1='1';
param2='2';
END
CREATE VIRTUAL PROCEDURE resultParameterOnPosition2(out param1 string, out param2 string result) AS
BEGIN
param1='1';
param2='2';
END
]]>
</metadata>
</model>
</vdb>
{code}
when I have following system property on server:
{code:xml}
<system-properties>
<property name="org.teiid.resultAnyPosition" value="false"/>
</system-properties>
{code}
[~jolee]
What concerns me in the backport is, that class BinaryWSProcedureExecution.java is backported as a brand new class. I believe this is due to the different location of this class in upstream vs. 8.12.12.6_4.
> Document/refine behavior of treating result parameter as the first parameter
> ----------------------------------------------------------------------------
>
> Key: TEIID-5130
> URL: https://issues.jboss.org/browse/TEIID-5130
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.0, 9.3.5, 8.12.12.6_4
>
>
> DDL and metadata import make the assumption that the return parameter is the first in the underlying metadata (in part to ensure support of varargs), but we still allowed the result parameter to appear anywhere in the parameter list as to maintain backwards compatibility with legacy/Designer ddl. However in index metadata there is slightly different behavior in that the result parameter remains in it's original position.
> We need to clarify this behavior - more documentation, enforce/validate that the result parameter is first in ddl, or perform the same reordering for index metadata.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (TEIID-5130) Document/refine behavior of treating result parameter as the first parameter
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-5130?page=com.atlassian.jira.plugin... ]
Jan Stastny edited comment on TEIID-5130 at 2/27/18 3:52 AM:
-------------------------------------------------------------
[~shawkins] Is the change limited only to ws translator? Anyway, I tried on 8.12.12.6_4 with both virtual and foreign procedure, but the property doesn't seem to work.
I can deploy following vdbs:
{code:xml}
<vdb name="teiid5130" version="1">
<model name="View">
<source connection-jndi-name="java:/rest-swagger" name="test" translator-name="ws" />
<metadata type="DDL">
<![CDATA[
CREATE FOREIGN PROCEDURE resultParameterOnPosition1(out param1 string result, out param2 string);
CREATE FOREIGN PROCEDURE resultParameterOnPosition2(out param1 string, out param2 string result);
]]>
</metadata>
</model>
</vdb>
{code}
or
{code:xml}
<vdb name="teiid5130" version="1">
<model name="View" type="VIRTUAL">
<metadata type="DDL">
<![CDATA[
CREATE VIRTUAL PROCEDURE resultParameterOnPosition1(out param1 string result, out param2 string) AS
BEGIN
param1='1';
param2='2';
END
CREATE VIRTUAL PROCEDURE resultParameterOnPosition2(out param1 string, out param2 string result) AS
BEGIN
param1='1';
param2='2';
END
]]>
</metadata>
</model>
</vdb>
{code}
when I have following system property on server:
{code:xml}
<system-properties>
<property name="org.teiid.resultAnyPosition" value="false"/>
</system-properties>
{code}
[~jolee]
What concerns me in the backport is, that class BinaryWSProcedureExecution.java is backported as a brand new class. I believe this is due to the different location of this class in upstream vs. 8.12.12.6_4.
was (Author: jstastny):
[~shawkins] Is the change limited only to ws translator? Anyway, I tried on 8.12.12.6_4 and 9.3.4 with both virtual and foreign procedure, but the property doesn't seem to work.
I can deploy following vdbs:
{code:xml}
<vdb name="teiid5130" version="1">
<model name="View">
<source connection-jndi-name="java:/rest-swagger" name="test" translator-name="ws" />
<metadata type="DDL">
<![CDATA[
CREATE FOREIGN PROCEDURE resultParameterOnPosition1(out param1 string result, out param2 string);
CREATE FOREIGN PROCEDURE resultParameterOnPosition2(out param1 string, out param2 string result);
]]>
</metadata>
</model>
</vdb>
{code}
or
{code:xml}
<vdb name="teiid5130" version="1">
<model name="View" type="VIRTUAL">
<metadata type="DDL">
<![CDATA[
CREATE VIRTUAL PROCEDURE resultParameterOnPosition1(out param1 string result, out param2 string) AS
BEGIN
param1='1';
param2='2';
END
CREATE VIRTUAL PROCEDURE resultParameterOnPosition2(out param1 string, out param2 string result) AS
BEGIN
param1='1';
param2='2';
END
]]>
</metadata>
</model>
</vdb>
{code}
when I have following system property on server:
{code:xml}
<system-properties>
<property name="org.teiid.resultAnyPosition" value="false"/>
</system-properties>
{code}
[~jolee]
What concerns me in the backport is, that class BinaryWSProcedureExecution.java is backported as a brand new class. I believe this is due to the different location of this class in upstream vs. 8.12.12.6_4.
> Document/refine behavior of treating result parameter as the first parameter
> ----------------------------------------------------------------------------
>
> Key: TEIID-5130
> URL: https://issues.jboss.org/browse/TEIID-5130
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.0, 9.3.5, 8.12.12.6_4
>
>
> DDL and metadata import make the assumption that the return parameter is the first in the underlying metadata (in part to ensure support of varargs), but we still allowed the result parameter to appear anywhere in the parameter list as to maintain backwards compatibility with legacy/Designer ddl. However in index metadata there is slightly different behavior in that the result parameter remains in it's original position.
> We need to clarify this behavior - more documentation, enforce/validate that the result parameter is first in ddl, or perform the same reordering for index metadata.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (TEIID-4653) SybaseIQ translator: Input parameter not set in prepared statement in source command
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4653?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-4653:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1549212
Bugzilla Update: Perform
> SybaseIQ translator: Input parameter not set in prepared statement in source command
> ------------------------------------------------------------------------------------
>
> Key: TEIID-4653
> URL: https://issues.jboss.org/browse/TEIID-4653
> Project: Teiid
> Issue Type: Sub-task
> Components: JDBC Connector
> Affects Versions: 8.12.8.6_3
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 9.3, 9.2.1
>
>
> There seems to be problem with prepared statements which are being push to the datasource without binding parameters.
> The query engine fails with following error:
> {code}
> 13:08:00,044 WARN [org.teiid.CONNECTOR] (Worker18_QueryProcessorQueue72) Connector worker process failed for atomic-request=PYp5BTTPF3pK.25.0.16: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [{ts '2000-01-01 00:00:03.0'}] SQL: SELECT g_0."intkey", g_0."timestampvalue" FROM "bqt-server"."dvqe"."SmallA" AS g_0 WHERE g_0."timestampvalue" = ?]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:366)
> at sun.reflect.GeneratedMethodAccessor169.invoke(Unknown Source) [:1.7.0_71]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_71]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_71]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy80.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_71]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:280)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_71]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_71]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71]
> Caused by: java.sql.SQLException: JZ0SA: Prepared Statement: Input parameter not set, index: 0.
> at com.sybase.jdbc4.jdbc.ErrorMessage.raiseError(Unknown Source)
> at com.sybase.jdbc4.tds.TdsParam.prepareForSend(Unknown Source)
> at com.sybase.jdbc4.jdbc.ParamManager.checkParams(Unknown Source)
> at com.sybase.jdbc4.tds.TdsCursor.a(Unknown Source)
> at com.sybase.jdbc4.tds.TdsCursor.open(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybStatement.executeQuery(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybPreparedStatement.executeQuery(Unknown Source)
> at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:123) [translator-jdbc-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1]
> ... 17 more
> {code}
> The message indicates, that a prepared statement which is being pushed has not bound parameter values set.
> h2.First Example
> Example query:
> {code:sql}
> SELECT IntKey, timestampvalue FROM BQT1.SmallA WHERE timestampvalue = TIMESTAMPCREATE( {d'2000-01-01'}, {t'00:00:03'})
> {code}
> Resulting DATA SRC COMMAND:
> {code:sql}
> SELECT g_0.intkey, g_0.timestampvalue FROM BQT1.SmallA AS g_0 WHERE g_0.timestampvalue = {ts'2000-01-01 00:00:03.0'}
> {code}
> Resulting SOURCE SRC COMMAND:
> {code:sql}
> [SELECT g_0."intkey", g_0."timestampvalue" FROM "bqt-server"."dvqe"."SmallA" AS g_0 WHERE g_0."timestampvalue" = ?]
> {code}
> h2. Second example
> Query:
> {code:sql}
> SELECT bqt2.smalla.intkey, g2.intkey, bqt2.smalla.bytenum FROM bqt2.smalla LEFT JOIN LATERAL (SELECT intkey FROM bqt2.mediuma WHERE bqt2.smalla.bytenum = bqt2.mediuma.bytenum) AS g2 ON true ORDER BY bqt2.smalla.intkey, g2.intkey
> {code}
> DATA SRC COMMAND 1:
> {code:sql}
> SELECT g_0.bytenum, g_0.intkey FROM BQT2.SmallA AS g_0
> {code}
> SOURCE SRC COMMAND 1:
> {code:sql}
> [SELECT g_0."bytenum", g_0."intkey" FROM "bqt-server"."dvqe"."SmallA" AS g_0]
> {code}
> DATA SRC COMMAND 2:
> {code:sql}
> SELECT g_0.intkey FROM BQT2.MediumA AS g_0 WHERE g_0.bytenum = -128
> {code}
> SOURCE SRC COMMAND 2:
> {code:sql}
> [SELECT g_0."intkey" FROM "bqt-server"."dvqe"."MediumA" AS g_0 WHERE g_0."bytenum" = ?]
> {code}
> h4.Note:
> There should be more DATA SRC commands similar to DATA SRC COMMAND 2, as such query should be performed in a loop for every result from DATA SRC COMMAND 1. But due to error in DATA SRC COMMAND 2, the loop is ended.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (TEIID-4651) SybaseIQ translator: different order of arguments in LOCATE function
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4651?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-4651:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1549208
Bugzilla Update: Perform
> SybaseIQ translator: different order of arguments in LOCATE function
> --------------------------------------------------------------------
>
> Key: TEIID-4651
> URL: https://issues.jboss.org/browse/TEIID-4651
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12.8.6_3
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 9.1.2, 9.2, 8.12.11.6_4
>
>
> Teiid's and SAP IQ's LOCATE function differs in order of arguments. Translator is pushing the LOCATE function as is into the source, which results in undesirable results. This is critical issue, as the queries seemingly work, but are not producing correct results.
> See [SAP IQ LOCATE function docs|http://help.sap.com/saphelp_iq1611_iqrefbb/helpdata/en/a5/5fae8484f2...]
> Query:
> {code:sql}
> SELECT INTKEY, STRINGNUM, LOCATE(1,STRINGNUM) FROM BQT1.SmallA ORDER BY intkey
> {code}
> being pushed as:
> {code:sql}
> [SELECT g_0."intkey" AS c_0, g_0."stringnum" AS c_1, locate('1', g_0."stringnum") AS c_2 FROM "bqt-server"."dvqe"."SmallA" AS g_0 ORDER BY c_0]
> {code}
> Results in:
> || intkey || stringnum || expr3 ||
> |0 | -24 | 0|
> |1 | <null> | <null>|
> |2 | -22 | 0|
> |3 | -21 | 0|
> |4 | -20 | 0|
> |5 | -19 | 0|
> |6 | -18 | 0|
> |7 | -17 | 0|
> |8 | -16 | 0|
> |9 | -15 | 0|
> |10 | -14 | 0|
> |11 | -13 | 0|
> |12 | -12 | 0|
> |13 | -11 | 0|
> |14 | -10 | 0|
> |15 | -9 | 0|
> |16 | -8 | 0|
> |17 | <null> | <null>|
> |18 | -6 | 0|
> |19 | -5 | 0|
> |20 | -4 | 0|
> |21 | -3 | 0|
> |22 | -2 | 0|
> |23 | -1 | 0|
> |24 | 0 | 0|
> |25 | 1 | 1|
> |26 | 2 | 0|
> |27 | 3 | 0|
> |28 | 4 | 0|
> |29 | 5 | 0|
> |30 | 6 | 0|
> |31 | 7 | 0|
> |32 | 8 | 0|
> |33 | <null> | <null>|
> |34 | 10 | 0|
> |35 | 11 | 0|
> |36 | 12 | 0|
> |37 | 13 | 0|
> |38 | 14 | 0|
> |39 | 15 | 0|
> |40 | 16 | 0|
> |41 | 17 | 0|
> |42 | 18 | 0|
> |43 | 19 | 0|
> |44 | 20 | 0|
> |45 | 21 | 0|
> |46 | 22 | 0|
> |47 | 23 | 0|
> |48 | 24 | 0|
> |49 | <null> | <null> |
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (TEIID-5265) AssertionError: Batch not found in storage
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5265?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5265:
---------------------------------------
I can recreate something that looks like this by adding the cache entry, evicting the cache entry to disk, then re-adding the cache entry but with a larger size than before - which I believe can happen when we attempt to reuse the same page id in the tree logic. If this is the case, it should not be a hard error situation, but rather effectively remove the old entry and add the modified.
> AssertionError: Batch not found in storage
> ------------------------------------------
>
> Key: TEIID-5265
> URL: https://issues.jboss.org/browse/TEIID-5265
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 10.1
> Reporter: Bram Gadeyne
> Assignee: Steven Hawkins
>
> While executing the following query:
> {code:sql}
> insert into rep149_cci(PatientID,age,Orig,Upd,agepointsO,agepointsU,AMI,CHF,PVD,CVD,DEM,CPD,PUD,MLD,SLD,DNC,DWC,HEM,RED,MAL,MST,HIV)
> select cci.patientid as patientid,cci.age as age,cci.orig as orig,cci.upd as upd,cci.agepointso as agepointso,cci.agepointsu as agepointsu,
> cci.charlson_ami as ami,cci.charlson_chf as chf,cci.charlson_pvd as pvd,cci.charlson_cvd as cvd,cci.charlson_dem as dem,cci.charlson_cpd as cpd,cci.charlson_pud as pud,
> cci.charlson_mld as mld,cci.charlson_sld as sld,cci.charlson_dnc as dnc,cci.charlson_dwc as dwc,cci.charlson_hem as hem,cci.charlson_red as red,cci.charlson_mal as mal,
> cci.charlson_mst as mst,cci.charlson_hiv as hiv
> from rep149_cohort gd
> join izisviews.pr_calculate_cci cci on
> cci.patientid_in = gd.patientid;
> {code}
> rep149_cci is defined as
> {code:sql}
> create foreign temporary table rep149_cci(
> PatientID integer not null,
> age bigdecimal,
> Orig long,
> Upd long,
> agepointsO integer,
> agepointsU integer,
> AMI integer,
> CHF integer,
> PVD integer,
> CVD integer,
> DEM integer,
> CPD integer,
> PUD integer,
> MLD integer,
> SLD integer,
> DNC integer,
> DWC integer,
> HEM integer,
> RED integer,
> MAL integer,
> MST integer,
> HIV integer,
> primary key(patientid)
> )OPTIONS (UPDATABLE true) on tmptables;
> {code}
> pr_calculate_cci is a virtual procedure. (I can't however share this code for confidentiality reasons).
> {code:sql}
> CREATE VIRTUAL PROCEDURE pr_calculate_cci(patientid_in integer)
> RETURNS (
> PatientID integer,
> age bigdecimal,
> Orig long,
> Upd long,
> agepointsO integer,
> agepointsU integer,
> AMI integer,
> CHF integer,
> PherVascDis integer,
> CerebVascDis integer,
> Dement integer,
> ChrPulmDis integer,
> PeptUlcer integer,
> MildLivDis integer,
> SevLivDis integer,
> DiabetesNoCompl integer,
> DiabetesWithCompl integer,
> HemiPara integer,
> RenalDis integer,
> Malign integer,
> Metastase integer,
> HIV_AIDS integer
> )
> AS
> BEGIN
> ...
> END
> {code}
> There are a few error reports like this one:
> 2018-02-23 08:33:05,478 ERROR [org.teiid.BUFFER_MGR] (Worker291_QueryProcessorQueue571476) mh0bsTIbs7qY TEIID30001 Max block number exceeded by object 1,366,497 from group 5,068,016. It is a Batch of 1797 rows of [Ljava.lang.String;@10953478. The estimated size was 172,528, but the actual size was 14,410. Increase the maxStorageObjectSize to support larger storage objects. Alternatively you could make the processor batch size smaller.
> The final stack trace is:
> 2018-02-23 08:33:05,539 ERROR [org.teiid.PROCESSOR] (Worker291_QueryProcessorQueue571476) mh0bsTIbs7qY TEIID30019 Unexpected exception for request mh0bsTIbs7qY.90: java.lang.AssertionError: Batch not found in storage 5067771
> at org.teiid.common.buffer.impl.BufferManagerImpl$BatchManagerImpl.getBatch(BufferManagerImpl.java:382)
> at org.teiid.common.buffer.SPage.getValues(SPage.java:234)
> at org.teiid.common.buffer.SPage.search(SPage.java:135)
> at org.teiid.common.buffer.STree.find(STree.java:247)
> at org.teiid.common.buffer.STree.insert(STree.java:295)
> at org.teiid.query.processor.relational.WindowFunctionProjectNode.saveValues(WindowFunctionProjectNode.java:419)
> at org.teiid.query.processor.relational.WindowFunctionProjectNode.buildResults(WindowFunctionProjectNode.java:380)
> at org.teiid.query.processor.relational.WindowFunctionProjectNode.nextBatchDirect(WindowFunctionProjectNode.java:229)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277)
> at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277)
> at org.teiid.query.processor.relational.UnionAllNode.nextBatchDirectInternal(UnionAllNode.java:165)
> at org.teiid.query.processor.relational.UnionAllNode.nextBatchDirect(UnionAllNode.java:138)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277)
> at org.teiid.query.processor.relational.SelectNode.nextBatchDirect(SelectNode.java:100)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:160)
> at org.teiid.query.processor.relational.SourceState.prefetch(SourceState.java:207)
> at org.teiid.query.processor.relational.SourceState.rowCountLE(SourceState.java:154)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (TEIID-5265) AssertionError: Batch not found in storage
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5265?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5265:
---------------------------------------
Is that TEIID30001 the earliest such exception related to batch size/storage?
> AssertionError: Batch not found in storage
> ------------------------------------------
>
> Key: TEIID-5265
> URL: https://issues.jboss.org/browse/TEIID-5265
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 10.1
> Reporter: Bram Gadeyne
> Assignee: Steven Hawkins
>
> While executing the following query:
> {code:sql}
> insert into rep149_cci(PatientID,age,Orig,Upd,agepointsO,agepointsU,AMI,CHF,PVD,CVD,DEM,CPD,PUD,MLD,SLD,DNC,DWC,HEM,RED,MAL,MST,HIV)
> select cci.patientid as patientid,cci.age as age,cci.orig as orig,cci.upd as upd,cci.agepointso as agepointso,cci.agepointsu as agepointsu,
> cci.charlson_ami as ami,cci.charlson_chf as chf,cci.charlson_pvd as pvd,cci.charlson_cvd as cvd,cci.charlson_dem as dem,cci.charlson_cpd as cpd,cci.charlson_pud as pud,
> cci.charlson_mld as mld,cci.charlson_sld as sld,cci.charlson_dnc as dnc,cci.charlson_dwc as dwc,cci.charlson_hem as hem,cci.charlson_red as red,cci.charlson_mal as mal,
> cci.charlson_mst as mst,cci.charlson_hiv as hiv
> from rep149_cohort gd
> join izisviews.pr_calculate_cci cci on
> cci.patientid_in = gd.patientid;
> {code}
> rep149_cci is defined as
> {code:sql}
> create foreign temporary table rep149_cci(
> PatientID integer not null,
> age bigdecimal,
> Orig long,
> Upd long,
> agepointsO integer,
> agepointsU integer,
> AMI integer,
> CHF integer,
> PVD integer,
> CVD integer,
> DEM integer,
> CPD integer,
> PUD integer,
> MLD integer,
> SLD integer,
> DNC integer,
> DWC integer,
> HEM integer,
> RED integer,
> MAL integer,
> MST integer,
> HIV integer,
> primary key(patientid)
> )OPTIONS (UPDATABLE true) on tmptables;
> {code}
> pr_calculate_cci is a virtual procedure. (I can't however share this code for confidentiality reasons).
> {code:sql}
> CREATE VIRTUAL PROCEDURE pr_calculate_cci(patientid_in integer)
> RETURNS (
> PatientID integer,
> age bigdecimal,
> Orig long,
> Upd long,
> agepointsO integer,
> agepointsU integer,
> AMI integer,
> CHF integer,
> PherVascDis integer,
> CerebVascDis integer,
> Dement integer,
> ChrPulmDis integer,
> PeptUlcer integer,
> MildLivDis integer,
> SevLivDis integer,
> DiabetesNoCompl integer,
> DiabetesWithCompl integer,
> HemiPara integer,
> RenalDis integer,
> Malign integer,
> Metastase integer,
> HIV_AIDS integer
> )
> AS
> BEGIN
> ...
> END
> {code}
> There are a few error reports like this one:
> 2018-02-23 08:33:05,478 ERROR [org.teiid.BUFFER_MGR] (Worker291_QueryProcessorQueue571476) mh0bsTIbs7qY TEIID30001 Max block number exceeded by object 1,366,497 from group 5,068,016. It is a Batch of 1797 rows of [Ljava.lang.String;@10953478. The estimated size was 172,528, but the actual size was 14,410. Increase the maxStorageObjectSize to support larger storage objects. Alternatively you could make the processor batch size smaller.
> The final stack trace is:
> 2018-02-23 08:33:05,539 ERROR [org.teiid.PROCESSOR] (Worker291_QueryProcessorQueue571476) mh0bsTIbs7qY TEIID30019 Unexpected exception for request mh0bsTIbs7qY.90: java.lang.AssertionError: Batch not found in storage 5067771
> at org.teiid.common.buffer.impl.BufferManagerImpl$BatchManagerImpl.getBatch(BufferManagerImpl.java:382)
> at org.teiid.common.buffer.SPage.getValues(SPage.java:234)
> at org.teiid.common.buffer.SPage.search(SPage.java:135)
> at org.teiid.common.buffer.STree.find(STree.java:247)
> at org.teiid.common.buffer.STree.insert(STree.java:295)
> at org.teiid.query.processor.relational.WindowFunctionProjectNode.saveValues(WindowFunctionProjectNode.java:419)
> at org.teiid.query.processor.relational.WindowFunctionProjectNode.buildResults(WindowFunctionProjectNode.java:380)
> at org.teiid.query.processor.relational.WindowFunctionProjectNode.nextBatchDirect(WindowFunctionProjectNode.java:229)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277)
> at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277)
> at org.teiid.query.processor.relational.UnionAllNode.nextBatchDirectInternal(UnionAllNode.java:165)
> at org.teiid.query.processor.relational.UnionAllNode.nextBatchDirect(UnionAllNode.java:138)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277)
> at org.teiid.query.processor.relational.SelectNode.nextBatchDirect(SelectNode.java:100)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:160)
> at org.teiid.query.processor.relational.SourceState.prefetch(SourceState.java:207)
> at org.teiid.query.processor.relational.SourceState.rowCountLE(SourceState.java:154)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (TEIID-5252) Teiid Wildfly Swarm Odata
by Arvind Gopinath (JIRA)
[ https://issues.jboss.org/browse/TEIID-5252?page=com.atlassian.jira.plugin... ]
Arvind Gopinath closed TEIID-5252.
----------------------------------
All good. Thank you
> Teiid Wildfly Swarm Odata
> --------------------------
>
> Key: TEIID-5252
> URL: https://issues.jboss.org/browse/TEIID-5252
> Project: Teiid
> Issue Type: Feature Request
> Reporter: Arvind Gopinath
> Assignee: Ramesh Reddy
> Priority: Minor
>
> Through Teiid Wildfly SWARM (examples code), I could able to run connecting below VDB and through SQL client, I could able to access my tables as well.
> To expose the same through Odata, in my pom.xml, I added below dependency.
> <dependency>
> <groupId>org.wildfly.swarm</groupId>
> <artifactId>odata</artifactId>
> <version>2018.1.0</version>
> </dependency>
> When my jar starts, I saw odata.war deployed and even my VDB added and through Sql client I could able to connect.
> 2018-02-08 15:30:31,119 INFO [org.jboss.as.server] (main) WFLYSRV0010: Deployed "odata.war" (runtime-name : "odata.war")
> 2018-02-08 15:30:31,493 INFO [org.teiid.RUNTIME.VDBLifeCycleListener] (MSC service thread 1-2) TEIID40118 VDB sqlite.1 added to the repository
> 2018-02-08 15:30:31,497 INFO [org.teiid.RUNTIME] (MSC service thread 1-2) TEIID50029 VDB sqlite.1 model "client" metadata is currently being loaded. Start Time: 8/02/18 3:30 PM
> But when I hit the URL,
> http://localhost:8080/odata4/sqlite.1/client.client
> I am getting error message below - Is it something I am missing?
> { "error": { "code": "38000", "message": "38000 TEIID10036 org.teiid.core.TeiidException: TEIID10036 org.teiid.core.TeiidRuntimeException: TEIID40067 javax.naming.NameNotFoundException: teiid\/queryengine\/odata -- service jboss.naming.context.java.teiid.queryengine.odata" } }
> Teiid Designer - Generated simple VDB.xml
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <vdb name="sqlite" version="1">
> <description>SQLite VDB</description>
> <model name="client">
> <property name="importer.useFullSchemaName" value="false"/>
> <!-- https://access.redhat.com/documentation/en-us/red_hat_jboss_data_virtuali... -->
> <!-- <property name="importer.tableNamePattern" value="CLI%"/> -->
> <property name="importer.excludeTables" value="FIL.*|ORDER.*"/>
> <source name="sqlite-connector" translator-name="jdbc-simple" connection-jndi-name="java:jboss/datasources/demoDS"/>
> </model>
> </vdb>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (TEIID-5238) Issue in the example while running through Docker
by Arvind Gopinath (JIRA)
[ https://issues.jboss.org/browse/TEIID-5238?page=com.atlassian.jira.plugin... ]
Arvind Gopinath closed TEIID-5238.
----------------------------------
All good. Thank you
> Issue in the example while running through Docker
> --------------------------------------------------
>
> Key: TEIID-5238
> URL: https://issues.jboss.org/browse/TEIID-5238
> Project: Teiid
> Issue Type: Feature Request
> Components: WildFly Swarm
> Reporter: Arvind Gopinath
> Assignee: Steven Hawkins
> Labels: Swarm, Teiid, wildfy
>
> When I run the below example, without docker it works fine. But when I try the same through docker, i am getting below error message. Please advise and appreciate all the help.
> https://github.com/teiid/wildfly-swarm-teiid-examples/tree/master/vdb-dat...
> Error-
> C:\projects\teiid-examples>docker run -p 31000:31000 vdb-datafederation-swarm
> C:\projects\teiid-examples>docker run -p 31000:31000 vdb-datafederation-swarm
> 2018-01-30 23:39:47,310 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: Logging - STABLE org.wildfly.swarm:logging:2017.6.0
> 2018-01-30 23:39:47,319 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: JCA - STABLE org.wildfly.swarm:jca:2017.6.0
> 2018-01-30 23:39:47,320 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: Datasources - STABLE org.wildfly.swarm:datasources:2017.6.0
> 2018-01-30 23:39:47,321 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: JMX - STABLE org.wildfly.swarm:jmx:2017.6.0
> 2018-01-30 23:39:47,321 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: Resource Adapters - STABLE org.wildfly.swarm:resource-adapters:2017.6.0
> 2018-01-30 23:39:47,322 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: Infinispan - STABLE org.wildfly.swarm:infinispan:2017.6.0
> 2018-01-30 23:39:47,322 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: Remoting - STABLE org.wildfly.swarm:remoting:2017.6.0
> 2018-01-30 23:39:47,322 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: Teiid - STABLE org.wildfly.swarm:teiid:2017.6.0
> 2018-01-30 23:39:47,323 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: Transactions - STABLE org.wildfly.swarm:transactions:2017.6.0
> 2018-01-30 23:39:49,081 INFO [org.wildfly.swarm.jmx] (main) JMX not configured for remote access
> 2018-01-30 23:39:49,124 INFO [org.wildfly.swarm.datasources] (main) WFSWARM1003: Auto-detected JDBC driver for h2
> 2018-01-30 23:39:49,147 INFO [org.wildfly.swarm.datasources] (main) WFSWARM1003: Auto-detected JDBC driver for teiid
> 2018-01-30 23:39:49,482 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.Final
> 2018-01-30 23:39:49,538 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Swarm 2017.6.0 (WildFly Core 2.2.1.Final) starting
> 2018-01-30 23:39:49,573 INFO [org.wildfly.swarm] (MSC service thread 1-1) WFSWARM0019: Install MSC service for command line args: []
> 2018-01-30 23:39:51,225 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 18) WFLYNAM0001: Activating Naming Subsystem
> 2018-01-30 23:39:51,235 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 23) WFLYCLINF0001: Activating Infinispan subsystem.
> 2018-01-30 23:39:51,227 INFO [org.jboss.as.security] (ServerService Thread Pool -- 20) WFLYSEC0002: Activating Security Subsystem
> 2018-01-30 23:39:51,229 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 24) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
> 2018-01-30 23:39:51,266 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 22) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors
> 2018-01-30 23:39:51,293 INFO [org.xnio] (MSC service thread 1-3) XNIO version 3.4.3.Final
> 2018-01-30 23:39:51,302 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.6.Final
> 2018-01-30 23:39:51,356 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.4.3.Final
> 2018-01-30 23:39:51,365 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 21) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
> 2018-01-30 23:39:51,421 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 21) WFLYJCA0005: Deploying non-JDBC-compliant driver class org.teiid.jdbc.TeiidDriver (version 10.0)
> 2018-01-30 23:39:51,443 INFO [org.jboss.as.connector] (MSC service thread 1-4) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.4.Final)
> 2018-01-30 23:39:51,577 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2
> 2018-01-30 23:39:51,610 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = teiid
> 2018-01-30 23:39:51,609 INFO [org.jboss.as.naming] (MSC service thread 1-3) WFLYNAM0003: Starting Naming Service
> 2018-01-30 23:39:51,636 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.21.Final
> 2018-01-30 23:39:51,949 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/accounts-ds]
> 2018-01-30 23:39:53,772 INFO [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-1) IJ020001: Required license terms for file:/tmp/module-jar6903489841680264781.jar_d/modules/org/jboss/teiid/resource-adapter/file/main/
> 2018-01-30 23:39:53,838 INFO [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-1) IJ020001: Required license terms for file:/tmp/module-jar6903489841680264781.jar_d/modules/org/jboss/teiid/resource-adapter/file/main/
> 2018-01-30 23:39:53,856 INFO [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-1) IJ020018: Enabling <validate-on-match> for java:/marketdata-file
> 2018-01-30 23:39:53,870 INFO [org.teiid.RUNTIME] (ServerService Thread Pool -- 16) TEIID50006 Teiid translator "h2" added.
> 2018-01-30 23:39:53,871 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0007: Registered connection factory java:/marketdata-file
> 2018-01-30 23:39:53,885 INFO [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-1) IJ020002: Deployed: file:/tmp/module-jar6903489841680264781.jar_d/modules/org/jboss/teiid/resource-adapter/file/main/
> 2018-01-30 23:39:53,889 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/marketdata-file]
> 2018-01-30 23:39:53,904 INFO [org.teiid.RUNTIME] (ServerService Thread Pool -- 16) TEIID50006 Teiid translator "file" added.
> 2018-01-30 23:39:54,060 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.4.Final
> 2018-01-30 23:39:54,346 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 30) WFLYCLINF0002: Started resultset cache from teiid-cache container
> 2018-01-30 23:39:54,354 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 28) WFLYCLINF0002: Started preparedplan cache from teiid-cache container
> 2018-01-30 23:39:54,357 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 29) WFLYCLINF0002: Started resultset-repl cache from teiid-cache container
> 2018-01-30 23:39:54,393 INFO [org.teiid.RUNTIME] (MSC service thread 1-3) TEIID50001 Teiid Engine 9.2.0.Final Started = Tue Jan 30 23:39:54 UTC 2018
> 2018-01-at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1919) to start service jboss.teiid.transport.jdbc: org.jboss.msc.service.StartException in service jboss.teiid.
> transporat java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.lang.Thread.run(Thread.java:748)or$Worker.run(ThreadPoolExecutor.java:617)
> Caused bat sun.nio.ch.Net.bind0(Native Method)family unavailable
> at sun.nio.ch.Net.bind(Net.java:425)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)java:223)
> at io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:485)el.java:125)
> at io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:440)
> at io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:903)text.java:425)
> at io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:348)
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)ks(SingleThreadEventExecutor.java:358)
> ... 1 morey.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
> 2018-01-30 23:39:54,563 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "teiid"),
> ("transport" => "jdbc")
> ]) - failure description: {
> "WFLYCTL0080: Failed services" => {"jboss.teiid.transport.jdbc" => "org.jboss.msc.service.StartException in service jboss.teiid.transport.jdbc: Failed to start service
> Caused by: java.net.SocketException: Protocol family unavailable"},
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.teiid.transport.jdbc"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> }
> 2018-01-30 23:39:54,613 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0186: Services which failed to start: service jboss.teiid.transport.jdbc: org.jboss.msc.service.StartException in service jboss.teiid.transport.jdbc: Failed to start service
> 2018-01-30 23:39:54,684 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Swarm 2017.6.0 (WildFly Core 2.2.1.Final) started (with errors) in 5229ms - Started 212 of 317 services (1 services failed or missing dependencies, 170 services are lazy, passive or on-demand)
> 2018-01-30 23:39:54,703 ERROR [stderr] (main) java.lang.reflect.InvocationTargetException
> 2018-01-30 23:39:54,704 ERROR [stderr] (main) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2018-01-30 23:39:54,704 ERROR [stderr] (main) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 2018-01-30 23:39:54,704 ERROR [stderr] (main) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 2018-01-30 23:39:54,705 ERROR [stderr] (main) at java.lang.reflect.Method.invoke(Method.java:498)
> 2018-01-30 23:39:54,705 ERROR [stderr] (main) at org.wildfly.swarm.bootstrap.MainInvoker.invoke(MainInvoker.java:39)
> 2018-01-30 23:39:54,705 ERROR [stderr] (main) at org.wildfly.swarm.bootstrap.Main.run(Main.java:46)
> 2018-01-30 23:39:54,706 ERROR [stderr] (main) at org.wildfly.swarm.bootstrap.Main.main(Main.java:37)
> 2018-01-30 23:39:54,706 ERROR [stderr] (main) Caused by: java.lang.RuntimeException: org.jboss.msc.service.StartException in service jboss.teiid.transport.jdbc: Failed to start service
> 2018-01-30 23:39:54,707 ERROR [stderr] (main) at org.wildfly.swarm.spi.api.ClassLoading.withTCCL(ClassLoading.java:45)
> 2018-01-30 23:39:54,707 ERROR [stderr] (main) at org.wildfly.swarm.container.runtime.ServerBootstrapImpl.bootstrap(ServerBootstrapImpl.java:113)
> 2018-01-30 23:39:54,707 ERROR [stderr] (main) at org.wildfly.swarm.Swarm.start(Swarm.java:369)
> 2018-01-30 23:39:54,708 ERROR [stderr] (main) at com.scentre.teiid.examples.Main.main(Main.java:46)
> 2018-01-30 23:39:54,709 ERROR [stderr] (main) ... 7 more
> 2018-01-30 23:39:54,709 ERROR [stderr] (main) Caused by: org.jboss.msc.service.StartException in service jboss.teiid.transport.jdbc: Failed to start service
> 2018-01-30 23:39:54,709 ERROR [stderr] (main) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1919)
> 2018-01-30 23:39:54,709 ERROR [stderr] (main) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 2018-01-30 23:39:54,710 ERROR [stderr] (main) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 2018-01-30 23:39:54,710 ERROR [stderr] (main) at java.lang.Thread.run(Thread.java:748)
> 2018-01-30 23:39:54,710 ERROR [stderr] (main) Caused by: java.net.SocketException: Protocol family unavailable
> 2018-01-30 23:39:54,710 ERROR [stderr] (main) at sun.nio.ch.Net.bind0(Native Method)
> 2018-01-30 23:39:54,712 ERROR [stderr] (main) at sun.nio.ch.Net.bind(Net.java:433)
> 2018-01-30 23:39:54,713 ERROR [stderr] (main) at sun.nio.ch.Net.bind(Net.java:425)
> 2018-01-30 23:39:54,713 ERROR [stderr] (main) at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
> 2018-01-30 23:39:54,713 ERROR [stderr] (main) at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
> 2018-01-30 23:39:54,713 ERROR [stderr] (main) at io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:125)
> 2018-01-30 23:39:54,714 ERROR [stderr] (main) at io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:485)
> 2018-01-30 23:39:54,714 ERROR [stderr] (main) at io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1089)
> 2018-01-30 23:39:54,714 ERROR [stderr] (main) at io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:440)
> 2018-01-30 23:39:54,714 ERROR [stderr] (main) at io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:425)
> 2018-01-30 23:39:54,714 ERROR [stderr] (main) at io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:903)
> 2018-01-30 23:39:54,715 ERROR [stderr] (main) at io.netty.channel.AbstractChannel.bind(AbstractChannel.java:198)
> 2018-01-30 23:39:54,718 ERROR [stderr] (main) at io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:348)
> 2018-01-30 23:39:54,718 ERROR [stderr] (main) at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358)
> 2018-01-30 23:39:54,718 ERROR [stderr] (main) at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)
> 2018-01-30 23:39:54,718 ERROR [stderr] (main) at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
> 2018-01-30 23:39:54,719 ERROR [stderr] (main) ... 1 more
> 2018-01-30 23:39:54,719 ERROR [stderr] (main) Exception in thread "main" java.lang.reflect.InvocationTargetException
> 2018-01-30 23:39:54,719 ERROR [stderr] (main) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2018-01-30 23:39:54,719 ERROR [stderr] (main) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 2018-01-30 23:39:54,720 ERROR [stderr] (main) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 2018-01-30 23:39:54,720 ERROR [stderr] (main) at java.lang.reflect.Method.invoke(Method.java:498)
> 2018-01-30 23:39:54,720 ERROR [stderr] (main) at org.wildfly.swarm.bootstrap.MainInvoker.invoke(MainInvoker.java:39)
> 2018-01-30 23:39:54,720 ERROR [stderr] (main) at org.wildfly.swarm.bootstrap.Main.run(Main.java:46)
> 2018-01-30 23:39:54,720 ERROR [stderr] (main) at org.wildfly.swarm.bootstrap.Main.main(Main.java:37)
> 2018-01-30 23:39:54,721 ERROR [stderr] (main) Caused by: java.lang.RuntimeException: org.jboss.msc.service.StartException in service jboss.teiid.transport.jdbc: Failed to start service
> 2018-01-30 23:39:54,721 ERROR [stderr] (main) at org.wildfly.swarm.spi.api.ClassLoading.withTCCL(ClassLoading.java:45)
> 2018-01-30 23:39:54,721 ERROR [stderr] (main) at org.wildfly.swarm.container.runtime.ServerBootstrapImpl.bootstrap(ServerBootstrapImpl.java:113)
> 2018-01-30 23:39:54,726 ERROR [stderr] (main) at org.wildfly.swarm.Swarm.start(Swarm.java:369)
> 2018-01-30 23:39:54,726 ERROR [stderr] (main) at com.scentre.teiid.examples.Main.main(Main.java:46)
> 2018-01-30 23:39:54,726 ERROR [stderr] (main) ... 7 more
> 2018-01-30 23:39:54,726 ERROR [stderr] (main) Caused by: org.jboss.msc.service.StartException in service jboss.teiid.transport.jdbc: Failed to start service
> 2018-01-30 23:39:54,727 ERROR [stderr] (main) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1919)
> 2018-01-30 23:39:54,727 ERROR [stderr] (main) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 2018-01-30 23:39:54,727 ERROR [stderr] (main) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 2018-01-30 23:39:54,727 ERROR [stderr] (main) at java.lang.Thread.run(Thread.java:748)
> 2018-01-30 23:39:54,727 ERROR [stderr] (main) Caused by: java.net.SocketException: Protocol family unavailable
> 2018-01-30 23:39:54,728 ERROR [stderr] (main) at sun.nio.ch.Net.bind0(Native Method)
> 2018-01-30 23:39:54,728 ERROR [stderr] (main) at sun.nio.ch.Net.bind(Net.java:433)
> 2018-01-30 23:39:54,728 ERROR [stderr] (main) at sun.nio.ch.Net.bind(Net.java:425)
> 2018-01-30 23:39:54,728 ERROR [stderr] (main) at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
> 2018-01-30 23:39:54,728 ERROR [stderr] (main) at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
> 2018-01-30 23:39:54,728 ERROR [stderr] (main) at io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:125)
> 2018-01-30 23:39:54,729 ERROR [stderr] (main) at io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:485)
> 2018-01-30 23:39:54,729 ERROR [stderr] (main) at io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1089)
> 2018-01-30 23:39:54,729 ERROR [stderr] (main) at io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:440)
> 2018-01-30 23:39:54,729 ERROR [stderr] (main) at io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:425)
> 2018-01-30 23:39:54,729 ERROR [stderr] (main) at io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:903)
> 2018-01-30 23:39:54,730 ERROR [stderr] (main) at io.netty.channel.AbstractChannel.bind(AbstractChannel.java:198)
> 2018-01-30 23:39:54,730 ERROR [stderr] (main) at io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:348)
> 2018-01-30 23:39:54,730 ERROR [stderr] (main) at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358)
> 2018-01-30 23:39:54,730 ERROR [stderr] (main) at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)
> 2018-01-30 23:39:54,730 ERROR [stderr] (main) at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
> 2018-01-30 23:39:54,730 ERROR [stderr] (main) ... 1 more
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months