[JBoss JIRA] (TEIID-3666) VDB can deploy before datasource is bound
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3666?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3666:
-------------------------------------
This looks like some timing/synchronization issue, looking at code could not figure out what could be the issue.
> VDB can deploy before datasource is bound
> -----------------------------------------
>
> Key: TEIID-3666
> URL: https://issues.jboss.org/browse/TEIID-3666
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.3
> Environment: JDBC driver for datasource is deployed in deployments/ directory of standalone instance
> Reporter: Marc Shirley
> Assignee: Steven Hawkins
>
> A VDB can be deployed before the datasources it depends on are fully deployed and bound, resulting in the VDB never being marked as ACTIVE. This appears to be exclusive to environments where the JDBC driver for the datasource is deployed through use of the standalone deployments/ directory. If the driver is deployed as a module, then the risk of the issue is lowered or eliminated.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (TEIID-3661) Spatial functions broken
by Tom Arnold (JIRA)
[ https://issues.jboss.org/browse/TEIID-3661?page=com.atlassian.jira.plugin... ]
Tom Arnold commented on TEIID-3661:
-----------------------------------
Thanks!
> Spatial functions broken
> ------------------------
>
> Key: TEIID-3661
> URL: https://issues.jboss.org/browse/TEIID-3661
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Affects Versions: 8.11, 8.12, 8.11.1, 8.11.2
> Reporter: Tom Arnold
> Assignee: Steven Hawkins
> Fix For: 8.12, 8.11.3
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Spatial functions (like {{ST_GeomFromText}}) are broken in the JBoss kit by the module refactor that happened around 8.11.0.Beta2.
> {code}
> select st_geomfromtext('POINT(0 0)');
> {code}
> {code}
> Caused by: java.lang.NoClassDefFoundError: org/xml/sax/helpers/DefaultHandler
> at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.7.0_79]
> at java.lang.ClassLoader.defineClass(ClassLoader.java:800) [rt.jar:1.7.0_79]
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:361) [jboss-modules.jar:1.3.6.Final-redhat-1]
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:482) [jboss-modules.jar:1.3.6.Final-redhat-1]
> ... 61 more
> Caused by: java.lang.ClassNotFoundException: org.xml.sax.helpers.DefaultHandler from [Module "com.vividsolutions:main" from local module loader @1de368ab (finder: local module finder @3cecc1e1 (roots: /home/tom/wkspace/teiid-8.12.0.Beta2-SNAPSHOT/modules,/home/tom/wkspace/teiid-8.12.0.Beta2-SNAPSHOT/modules/system/layers/dv,/home/tom/wkspace/teiid-8.12.0.Beta2-SNAPSHOT/modules/system/layers/base))]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.6.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.6.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.6.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.6.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.6.Final-redhat-1]
> ... 65 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (TEIID-3666) VDB can deploy before datasource is bound
by Marc Shirley (JIRA)
[ https://issues.jboss.org/browse/TEIID-3666?page=com.atlassian.jira.plugin... ]
Marc Shirley commented on TEIID-3666:
-------------------------------------
A sample log excerpt illustrating the issue is below. The metadata load is attempted but fails due to the datasource still being in the process of deployment. In this case, the datasource was fully deployed and bound 15 ms after the metadata load failed. The metadata load is never reattempted and the VDB is never marked active in this scenario.
13:28:40,202 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB DB2.1,608,121,347 model "TR" metadata failed to load. Reason:TEIID31097 Metadata load requires a connection factory: TEIID30481 Failed to find the Connection Factory with JNDI name TR. Please check the name or deploy the Connection Factory with specified name.
...
13:28:40,217 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:/TR]
> VDB can deploy before datasource is bound
> -----------------------------------------
>
> Key: TEIID-3666
> URL: https://issues.jboss.org/browse/TEIID-3666
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.3
> Environment: JDBC driver for datasource is deployed in deployments/ directory of standalone instance
> Reporter: Marc Shirley
> Assignee: Steven Hawkins
>
> A VDB can be deployed before the datasources it depends on are fully deployed and bound, resulting in the VDB never being marked as ACTIVE. This appears to be exclusive to environments where the JDBC driver for the datasource is deployed through use of the standalone deployments/ directory. If the driver is deployed as a module, then the risk of the issue is lowered or eliminated.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (TEIID-3666) VDB can deploy before datasource is bound
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3666?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3666:
---------------------------------------
> A VDB can be deployed before the datasources it depends on are fully deployed and bound
That is expected.
> resulting in the VDB never being marked as ACTIVE
That is not expected. The sequence of events shown in the ticket doesn't quite make sense either as there are vdb reloads, but I didn't see what is triggering that.
In any case this may be expected behavior:
If data sources do not initially exist, since the vdb has dependencies on those services it will wait to start until they are available.
If the data sources are available, but not usable due to stale connections, network problems, etc., then the vdb service will attempt the start and fail. It will retry only if the data source is removed and re-added or if an explicit Admin.markDataSourceAvailable call is made to notify us that the data source is back up. We do not perform any polling or retries.
> VDB can deploy before datasource is bound
> -----------------------------------------
>
> Key: TEIID-3666
> URL: https://issues.jboss.org/browse/TEIID-3666
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.3
> Environment: JDBC driver for datasource is deployed in deployments/ directory of standalone instance
> Reporter: Marc Shirley
> Assignee: Steven Hawkins
>
> A VDB can be deployed before the datasources it depends on are fully deployed and bound, resulting in the VDB never being marked as ACTIVE. This appears to be exclusive to environments where the JDBC driver for the datasource is deployed through use of the standalone deployments/ directory. If the driver is deployed as a module, then the risk of the issue is lowered or eliminated.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (TEIID-3663) ST_Transform only works in tests
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3663?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3663.
-----------------------------------
Fix Version/s: 8.12
8.11.3
Resolution: Done
There are two issues here. The first is the regression, which was corrected with a new method to get the subject name from a context. The next issue is that this was only working for local connections. On remote connections our check of the session could fail as it was against the local transport rather than the originating transport. The fix here was to instead use a closed flag on the session rather than checking with the session service.
We will likely want to consider moving back to a single session service in Teiid 9 as most of the constraints will be specified on a vdb basis and not on a transport basis.
> ST_Transform only works in tests
> --------------------------------
>
> Key: TEIID-3663
> URL: https://issues.jboss.org/browse/TEIID-3663
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12
> Reporter: Tom Arnold
> Assignee: Steven Hawkins
> Fix For: 8.12, 8.11.3
>
>
> From one of the tests; this fails against an actual server (JBoss kit).
> {code}
> select st_transform(st_geomfromtext('POINT(-118 34)',4326),3310);
> {code}
> {code}
> ERROR: TEIID30328 Unable to evaluate st_transform(?, 3310): TEIID30384 Error while evaluating function st_transform
> DETAIL: org.teiid.jdbc.TeiidSQLException: TEIID30328 Unable to evaluate st_transform(?, 3310): TEIID30384 Error while evaluating function st_transform
> {code}
> {code}
> 00:02:59,143 INFO [org.teiid.SECURITY] (Worker2_QueryProcessorQueue6) tF6aPUsmLmU/ TEIID40115 Local pass-through connection implicitly closing session tF6aPUsmLmU/ so that the connection can be used in a different security context.
> 00:02:59,144 WARN [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue6) tF6aPUsmLmU/ TEIID30020 Processing exception for request tF6aPUsmLmU/.4 'TEIID30328 Unable to evaluate st_transform(?, 3310): TEIID30384 Error while evaluating function st_transform'. Originally ExpressionEvaluationException 'Expected argument to be non-null but got null' ArgCheck.java:303.: org.teiid.api.exception.query.ExpressionEvaluationException: TEIID30328 Unable to evaluate st_transform(?, 3310): TEIID30384 Error while evaluating function st_transform
> at org.teiid.query.eval.Evaluator.evaluate(Evaluator.java:631) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.rewriter.QueryRewriter.evaluate(QueryRewriter.java:2122) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.rewriter.QueryRewriter.rewriteExpressionDirect(QueryRewriter.java:2112) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.rewriter.QueryRewriter.access$000(QueryRewriter.java:101) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.rewriter.QueryRewriter$3.replaceExpression(QueryRewriter.java:626) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.sql.visitor.ExpressionMappingVisitor.visit(ExpressionMappingVisitor.java:162) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.sql.symbol.ExpressionSymbol.acceptVisitor(ExpressionSymbol.java:63) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.sql.navigator.AbstractNavigator.visitVisitor(AbstractNavigator.java:54) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.postVisitVisitor(PreOrPostOrderNavigator.java:61) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:183) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.sql.symbol.ExpressionSymbol.acceptVisitor(ExpressionSymbol.java:63) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:63) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.sql.navigator.AbstractNavigator.visitNodes(AbstractNavigator.java:76) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:342) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.sql.lang.Select.acceptVisitor(Select.java:168) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.sql.navigator.PostOrderNavigator.doVisit(PostOrderNavigator.java:40) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.rewriter.QueryRewriter.rewriteExpressions(QueryRewriter.java:633) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.rewriter.QueryRewriter.rewriteQuery(QueryRewriter.java:471) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.rewriter.QueryRewriter.rewriteCommand(QueryRewriter.java:222) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.rewriter.QueryRewriter.rewrite(QueryRewriter.java:167) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.rewriter.QueryRewriter.rewrite(QueryRewriter.java:171) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:413) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.Request.processRequest(Request.java:461) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:632) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:333) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:271) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
> Caused by: org.teiid.api.exception.query.FunctionExecutionException: TEIID30384 Error while evaluating function st_transform
> at org.teiid.query.function.FunctionDescriptor.invokeFunction(FunctionDescriptor.java:295) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.eval.Evaluator.evaluate(Evaluator.java:1320) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.eval.Evaluator.internalEvaluate(Evaluator.java:659) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.eval.Evaluator.evaluate(Evaluator.java:629) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> ... 32 more
> Caused by: org.teiid.api.exception.query.FunctionExecutionException: 38000 TEIID31163 Failed to lookup proj4 text.
> at org.teiid.query.function.GeometryTransformUtils.lookupProj4Text(GeometryTransformUtils.java:109) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.function.GeometryTransformUtils.transform(GeometryTransformUtils.java:78) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.function.GeometryTransformUtils.transform(GeometryTransformUtils.java:64) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.function.GeometryFunctionMethods.transform(GeometryFunctionMethods.java:253) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_79]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_79]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_79]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_79]
> at org.teiid.query.function.FunctionDescriptor.invokeFunction(FunctionDescriptor.java:281) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> ... 35 more
> Caused by: org.teiid.jdbc.TeiidSQLException: Expected argument to be non-null but got null
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135) [teiid-client-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71) [teiid-client-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:671) [teiid-client-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:535) [teiid-client-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:261) [teiid-client-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:73) [teiid-client-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.query.function.GeometryTransformUtils.lookupProj4Text(GeometryTransformUtils.java:103) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> ... 43 more
> Caused by: org.teiid.core.TeiidComponentException: Expected argument to be non-null but got null
> at org.teiid.client.util.ExceptionUtil.convertException(ExceptionUtil.java:65) [teiid-client-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:186) [teiid-runtime-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at com.sun.proxy.$Proxy18.executeRequest(Unknown Source)
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:669) [teiid-client-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> ... 47 more
> Caused by: java.lang.IllegalArgumentException: Expected argument to be non-null but got null
> at org.teiid.core.util.ArgCheck.isNotNull(ArgCheck.java:303) [teiid-common-core-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.core.util.ArgCheck.isNotNull(ArgCheck.java:289) [teiid-common-core-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.services.SessionServiceImpl.createSession(SessionServiceImpl.java:150) [teiid-runtime-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.transport.LogonImpl.logon(LogonImpl.java:137) [teiid-runtime-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.transport.LogonImpl.logon(LogonImpl.java:121) [teiid-runtime-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_79]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_79]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_79]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_79]
> at org.teiid.transport.LocalServerConnection$1$1.call(LocalServerConnection.java:180) [teiid-runtime-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_79]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:260) [teiid-engine-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:178) [teiid-runtime-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at com.sun.proxy.$Proxy48.logon(Unknown Source)
> at org.teiid.transport.LocalServerConnection.authenticate(LocalServerConnection.java:142) [teiid-runtime-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:174) [teiid-runtime-8.12.0.Beta2-SNAPSHOT.jar:8.12.0.Beta2-SNAPSHOT]
> ... 49 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (TEIID-3661) Spatial functions broken
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3661?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3661.
-----------------------------------
Resolution: Done
Updated the module names and added missing dependencies.
> Spatial functions broken
> ------------------------
>
> Key: TEIID-3661
> URL: https://issues.jboss.org/browse/TEIID-3661
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Affects Versions: 8.11, 8.12, 8.11.1, 8.11.2
> Reporter: Tom Arnold
> Assignee: Steven Hawkins
> Fix For: 8.12, 8.11.3
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Spatial functions (like {{ST_GeomFromText}}) are broken in the JBoss kit by the module refactor that happened around 8.11.0.Beta2.
> {code}
> select st_geomfromtext('POINT(0 0)');
> {code}
> {code}
> Caused by: java.lang.NoClassDefFoundError: org/xml/sax/helpers/DefaultHandler
> at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.7.0_79]
> at java.lang.ClassLoader.defineClass(ClassLoader.java:800) [rt.jar:1.7.0_79]
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:361) [jboss-modules.jar:1.3.6.Final-redhat-1]
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:482) [jboss-modules.jar:1.3.6.Final-redhat-1]
> ... 61 more
> Caused by: java.lang.ClassNotFoundException: org.xml.sax.helpers.DefaultHandler from [Module "com.vividsolutions:main" from local module loader @1de368ab (finder: local module finder @3cecc1e1 (roots: /home/tom/wkspace/teiid-8.12.0.Beta2-SNAPSHOT/modules,/home/tom/wkspace/teiid-8.12.0.Beta2-SNAPSHOT/modules/system/layers/dv,/home/tom/wkspace/teiid-8.12.0.Beta2-SNAPSHOT/modules/system/layers/base))]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.6.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.6.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.6.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.6.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.6.Final-redhat-1]
> ... 65 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (TEIID-3666) VDB can deploy before datasource is bound
by Marc Shirley (JIRA)
Marc Shirley created TEIID-3666:
-----------------------------------
Summary: VDB can deploy before datasource is bound
Key: TEIID-3666
URL: https://issues.jboss.org/browse/TEIID-3666
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.7.3
Environment: JDBC driver for datasource is deployed in deployments/ directory of standalone instance
Reporter: Marc Shirley
Assignee: Steven Hawkins
A VDB can be deployed before the datasources it depends on are fully deployed and bound, resulting in the VDB never being marked as ACTIVE. This appears to be exclusive to environments where the JDBC driver for the datasource is deployed through use of the standalone deployments/ directory. If the driver is deployed as a module, then the risk of the issue is lowered or eliminated.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (TEIID-3658) VDBs may start before transport service
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3658?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3658:
-------------------------------------
- The system property is "org.teiid.addPGMetadata", which default to "true" and adds the Pg metadata unless set to false.
- If above property is set to false, and a specific VDB wants to override the system behavior, then can set "include-pg-metadata" VDB property to include the PG metadata.
In absence both properties, always pg metadata is loaded
> VDBs may start before transport service
> ---------------------------------------
>
> Key: TEIID-3658
> URL: https://issues.jboss.org/browse/TEIID-3658
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.0
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Priority: Critical
> Labels: Beta2
> Fix For: 8.12
>
>
> VDBs may start before transport services, which is an issue for ODBC access as the enabled flag on the vdbrepository is toggled in by the transport. Any vdbs loaded prior to that point will not be properly accessible.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months