[JBoss JIRA] (TEIID-3710) Model defined without source information causes NoSuchElementException and further IllegalStateException in teiid-async-threads
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3710?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-3710:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1265089
Bugzilla Update: Perform
> Model defined without source information causes NoSuchElementException and further IllegalStateException in teiid-async-threads
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIID-3710
> URL: https://issues.jboss.org/browse/TEIID-3710
> Project: Teiid
> Issue Type: Bug
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
>
> If a dynamic VDB is deployed with error (non-virtual model defined with no source information) then Teiid shows TEIID40093 (this is correct) and further error:
> - if the VDB is new, then "JBAS014612: Operation \("deploy"\) failed" is thrown - this seems to be correct as there is no stacktrace in the log and error description is logical \[1\]
> - if the VDB is redeployed, then NoSuchElementException is thrown with message "No child 'name' exists" \[2\]. Teiid seems to try to replace deployment, which has been previously removed.
> If the error is corrected (model type set to VIRTUAL), VDB is deployed successfully and its state is set to ACTIVE but post-metadata-load action throws IllegalStateException (_getBuffermanager_ method) \[3\]. It does not affect any other VDB, but seems to affect every further redeploying of the affected VDB.
> \[1\]
> {code:text}
> 07:18:12,883 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "oo3-vdb.xml" (runtime-name: "oo3-vdb.xml")
> 07:18:12,894 DEBUG [org.teiid.RUNTIME] (MSC service thread 1-1) VDB oo3-vdb.xml has been parsed.
> 07:18:12,901 ERROR [stderr] (MSC service thread 1-2) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> 07:18:12,902 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.teiid.vdb.odata3.1: org.jboss.msc.service.StartException in service jboss.teiid.vdb.odata3.1: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata3.1
> at org.teiid.jboss.VDBService.start(VDBService.java:185)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_40]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_40]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_40]
> Caused by: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata3.1
> at org.teiid.runtime.AbstractVDBDeployer.assignMetadataRepositories(AbstractVDBDeployer.java:88)
> at org.teiid.jboss.VDBService.start(VDBService.java:181)
> ... 5 more
> 07:18:12,906 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014612: Operation ("deploy") failed - address: ([("deployment" => "oo3-vdb.xml")]) - failure description: {"JBAS014671: Failed services" => {"jboss.teiid.vdb.odata3.1" => "org.jboss.msc.service.StartException in service jboss.teiid.vdb.odata3.1: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata3.1
> Caused by: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata3.1"}}
> 07:18:12,908 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015870: Deploy of deployment "oo3-vdb.xml" was rolled back with the following failure message:
> {"JBAS014671: Failed services" => {"jboss.teiid.vdb.odata3.1" => "org.jboss.msc.service.StartException in service jboss.teiid.vdb.odata3.1: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata3.1
> Caused by: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata3.1"}}
> 07:18:12,930 TRACE [org.teiid.RUNTIME] (MSC service thread 1-1) VDB odata3 metadata removed
> 07:18:12,937 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment oo3-vdb.xml (runtime-name: oo3-vdb.xml) in 27ms
> 07:18:12,938 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.teiid.vdb.odata3.1
> {code}
> \[2\]
> {code:text}
> 07:13:17,144 INFO [org.teiid.RUNTIME] (MSC service thread 1-4) TEIID50026 VDB "odata.1[Source{}]" undeployed.
> 07:13:17,145 TRACE [org.teiid.RUNTIME] (MSC service thread 1-3) VDB odata metadata removed
> 07:13:17,148 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment oo-vdb.xml (runtime-name: oo-vdb.xml) in 7ms
> 07:13:17,149 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "oo-vdb.xml" (runtime-name: "oo-vdb.xml")
> 07:13:17,168 DEBUG [org.teiid.RUNTIME] (MSC service thread 1-4) VDB oo-vdb.xml has been parsed.
> 07:13:17,187 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.teiid.vdb.odata.1: org.jboss.msc.service.StartException in service jboss.teiid.vdb.odata.1: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata.1
> at org.teiid.jboss.VDBService.start(VDBService.java:185)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
> 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: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata.1
> at org.teiid.runtime.AbstractVDBDeployer.assignMetadataRepositories(AbstractVDBDeployer.java:88)
> at org.teiid.jboss.VDBService.start(VDBService.java:181)
> ... 5 more
> 07:13:17,192 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014612: Operation ("full-replace-deployment") failed - address: ([]) - failure description: {"JBAS014671: Failed services" => {"jboss.teiid.vdb.odata.1" => "org.jboss.msc.service.StartException in service jboss.teiid.vdb.odata.1: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata.1
> Caused by: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata.1"}}
> 07:13:17,201 TRACE [org.teiid.RUNTIME] (MSC service thread 1-7) VDB odata metadata removed
> 07:13:17,204 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment oo-vdb.xml (runtime-name: oo-vdb.xml) in 10ms
> 07:13:17,205 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014781: Step handler org.jboss.as.server.deployment.DeploymentHandlerUtil$4@64ced7d6 for operation {"operation" => "full-replace-deployment","address" => [],"name" => "oo-vdb.xml","content" => [{"path" => "deployments/oo-vdb.xml","relative-to" => "jboss.server.base.dir","archive" => true}],"persistent" => false,"enabled" => true} at address [] failed handling operation rollback -- java.util.NoSuchElementException: No child 'name' exists: java.util.NoSuchElementException: No child 'name' exists
> at org.jboss.dmr.ModelValue.requireChild(ModelValue.java:369) [jboss-dmr-1.2.2.Final-redhat-1.jar:1.2.2.Final-redhat-1]
> at org.jboss.dmr.ObjectModelValue.requireChild(ObjectModelValue.java:299) [jboss-dmr-1.2.2.Final-redhat-1.jar:1.2.2.Final-redhat-1]
> at org.jboss.dmr.ModelNode.require(ModelNode.java:870) [jboss-dmr-1.2.2.Final-redhat-1.jar:1.2.2.Final-redhat-1]
> at org.jboss.as.server.deployment.DeploymentHandlerUtil$4$1.handleResult(DeploymentHandlerUtil.java:283) [jboss-as-server-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
> at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1151) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
> at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1108) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
> at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1083) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
> at org.jboss.as.controller.AbstractOperationContext$Step.access$300(AbstractOperationContext.java:1028) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
> at org.jboss.as.controller.AbstractOperationContext.finishStep(AbstractOperationContext.java:822) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:778) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:537) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:338) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:314) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1144) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:331) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:201) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
> at org.jboss.as.controller.ModelControllerImpl$3$1$1.run(ModelControllerImpl.java:652) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
> at org.jboss.as.controller.ModelControllerImpl$3$1$1.run(ModelControllerImpl.java:646) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_71]
> at org.jboss.as.controller.ModelControllerImpl$3$1.run(ModelControllerImpl.java:646) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_71]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_71]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) [rt.jar:1.7.0_71]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) [rt.jar:1.7.0_71]
> 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]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.2.Final-redhat-1.jar:2.1.2.Final-redhat-1]
> 07:13:17,209 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.teiid.vdb.odata.1
> {code}
> \[3\]
> {code:text}
> 07:19:05,346 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "oo3-vdb.xml" (runtime-name: "oo3-vdb.xml")
> 07:19:05,356 DEBUG [org.teiid.RUNTIME] (MSC service thread 1-6) VDB oo3-vdb.xml has been parsed.
> 07:19:05,361 ERROR [stderr] (MSC service thread 1-7) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> 07:19:05,362 INFO [org.teiid.RUNTIME] (MSC service thread 1-7) TEIID50029 VDB odata3.1 model "Source" metadata is currently being loaded. Start Time: 22.9.2015 7:19
> 07:19:05,363 TRACE [org.teiid.RUNTIME] (MSC service thread 1-7) Model Source in VDB odata3 was being loaded from its repository
> 07:19:05,363 INFO [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50030 VDB odata3.1 model "Source" metadata loaded. End Time: 22.9.2015 7:19
> 07:19:05,365 TRACE [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 3) Resolving command SELECT 'b'
> 07:19:05,366 INFO [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID40003 VDB odata3.1 is set to ACTIVE
> 07:19:05,369 ERROR [stderr] (teiid-async-threads - 3) Exception in thread "teiid-async-threads - 3" java.lang.IllegalStateException
> 07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
> 07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at org.teiid.jboss.VDBService.getBuffermanager(VDBService.java:502)
> 07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at org.teiid.jboss.VDBService.access$200(VDBService.java:85)
> 07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at org.teiid.jboss.VDBService$1.finishedDeployment(VDBService.java:156)
> 07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at org.teiid.deployers.VDBRepository.notifyFinished(VDBRepository.java:352)
> 07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at org.teiid.deployers.VDBRepository.finishDeployment(VDBRepository.java:308)
> 07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at org.teiid.runtime.AbstractVDBDeployer.metadataLoaded(AbstractVDBDeployer.java:202)
> 07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at org.teiid.jboss.VDBService.access$1100(VDBService.java:85)
> 07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at org.teiid.jboss.VDBService$6.run(VDBService.java:411)
> 07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at org.teiid.jboss.VDBService$7.run(VDBService.java:442)
> 07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at java.lang.Thread.run(Thread.java:745)
> 07:19:05,371 ERROR [stderr] (teiid-async-threads - 3) at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> 07:19:05,407 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015859: Deployed "oo3-vdb.xml" (runtime-name : "oo3-vdb.xml")
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (TEIID-3710) Model defined without source information causes NoSuchElementException and further IllegalStateException in teiid-async-threads
by Juraj Duráni (JIRA)
Juraj Duráni created TEIID-3710:
-----------------------------------
Summary: Model defined without source information causes NoSuchElementException and further IllegalStateException in teiid-async-threads
Key: TEIID-3710
URL: https://issues.jboss.org/browse/TEIID-3710
Project: Teiid
Issue Type: Bug
Reporter: Juraj Duráni
Assignee: Steven Hawkins
If a dynamic VDB is deployed with error (non-virtual model defined with no source information) then Teiid shows TEIID40093 (this is correct) and further error:
- if the VDB is new, then "JBAS014612: Operation \("deploy"\) failed" is thrown - this seems to be correct as there is no stacktrace in the log and error description is logical \[1\]
- if the VDB is redeployed, then NoSuchElementException is thrown with message "No child 'name' exists" \[2\]. Teiid seems to try to replace deployment, which has been previously removed.
If the error is corrected (model type set to VIRTUAL), VDB is deployed successfully and its state is set to ACTIVE but post-metadata-load action throws IllegalStateException (_getBuffermanager_ method) \[3\]. It does not affect any other VDB, but seems to affect every further redeploying of the affected VDB.
\[1\]
{code:text}
07:18:12,883 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "oo3-vdb.xml" (runtime-name: "oo3-vdb.xml")
07:18:12,894 DEBUG [org.teiid.RUNTIME] (MSC service thread 1-1) VDB oo3-vdb.xml has been parsed.
07:18:12,901 ERROR [stderr] (MSC service thread 1-2) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
07:18:12,902 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.teiid.vdb.odata3.1: org.jboss.msc.service.StartException in service jboss.teiid.vdb.odata3.1: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata3.1
at org.teiid.jboss.VDBService.start(VDBService.java:185)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_40]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_40]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_40]
Caused by: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata3.1
at org.teiid.runtime.AbstractVDBDeployer.assignMetadataRepositories(AbstractVDBDeployer.java:88)
at org.teiid.jboss.VDBService.start(VDBService.java:181)
... 5 more
07:18:12,906 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014612: Operation ("deploy") failed - address: ([("deployment" => "oo3-vdb.xml")]) - failure description: {"JBAS014671: Failed services" => {"jboss.teiid.vdb.odata3.1" => "org.jboss.msc.service.StartException in service jboss.teiid.vdb.odata3.1: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata3.1
Caused by: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata3.1"}}
07:18:12,908 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015870: Deploy of deployment "oo3-vdb.xml" was rolled back with the following failure message:
{"JBAS014671: Failed services" => {"jboss.teiid.vdb.odata3.1" => "org.jboss.msc.service.StartException in service jboss.teiid.vdb.odata3.1: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata3.1
Caused by: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata3.1"}}
07:18:12,930 TRACE [org.teiid.RUNTIME] (MSC service thread 1-1) VDB odata3 metadata removed
07:18:12,937 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment oo3-vdb.xml (runtime-name: oo3-vdb.xml) in 27ms
07:18:12,938 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.teiid.vdb.odata3.1
{code}
\[2\]
{code:text}
07:13:17,144 INFO [org.teiid.RUNTIME] (MSC service thread 1-4) TEIID50026 VDB "odata.1[Source{}]" undeployed.
07:13:17,145 TRACE [org.teiid.RUNTIME] (MSC service thread 1-3) VDB odata metadata removed
07:13:17,148 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment oo-vdb.xml (runtime-name: oo-vdb.xml) in 7ms
07:13:17,149 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "oo-vdb.xml" (runtime-name: "oo-vdb.xml")
07:13:17,168 DEBUG [org.teiid.RUNTIME] (MSC service thread 1-4) VDB oo-vdb.xml has been parsed.
07:13:17,187 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.teiid.vdb.odata.1: org.jboss.msc.service.StartException in service jboss.teiid.vdb.odata.1: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata.1
at org.teiid.jboss.VDBService.start(VDBService.java:185)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
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: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata.1
at org.teiid.runtime.AbstractVDBDeployer.assignMetadataRepositories(AbstractVDBDeployer.java:88)
at org.teiid.jboss.VDBService.start(VDBService.java:181)
... 5 more
07:13:17,192 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014612: Operation ("full-replace-deployment") failed - address: ([]) - failure description: {"JBAS014671: Failed services" => {"jboss.teiid.vdb.odata.1" => "org.jboss.msc.service.StartException in service jboss.teiid.vdb.odata.1: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata.1
Caused by: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata.1"}}
07:13:17,201 TRACE [org.teiid.RUNTIME] (MSC service thread 1-7) VDB odata metadata removed
07:13:17,204 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment oo-vdb.xml (runtime-name: oo-vdb.xml) in 10ms
07:13:17,205 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014781: Step handler org.jboss.as.server.deployment.DeploymentHandlerUtil$4@64ced7d6 for operation {"operation" => "full-replace-deployment","address" => [],"name" => "oo-vdb.xml","content" => [{"path" => "deployments/oo-vdb.xml","relative-to" => "jboss.server.base.dir","archive" => true}],"persistent" => false,"enabled" => true} at address [] failed handling operation rollback -- java.util.NoSuchElementException: No child 'name' exists: java.util.NoSuchElementException: No child 'name' exists
at org.jboss.dmr.ModelValue.requireChild(ModelValue.java:369) [jboss-dmr-1.2.2.Final-redhat-1.jar:1.2.2.Final-redhat-1]
at org.jboss.dmr.ObjectModelValue.requireChild(ObjectModelValue.java:299) [jboss-dmr-1.2.2.Final-redhat-1.jar:1.2.2.Final-redhat-1]
at org.jboss.dmr.ModelNode.require(ModelNode.java:870) [jboss-dmr-1.2.2.Final-redhat-1.jar:1.2.2.Final-redhat-1]
at org.jboss.as.server.deployment.DeploymentHandlerUtil$4$1.handleResult(DeploymentHandlerUtil.java:283) [jboss-as-server-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1151) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1108) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1083) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
at org.jboss.as.controller.AbstractOperationContext$Step.access$300(AbstractOperationContext.java:1028) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
at org.jboss.as.controller.AbstractOperationContext.finishStep(AbstractOperationContext.java:822) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:778) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:537) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:338) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:314) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1144) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:331) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:201) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
at org.jboss.as.controller.ModelControllerImpl$3$1$1.run(ModelControllerImpl.java:652) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
at org.jboss.as.controller.ModelControllerImpl$3$1$1.run(ModelControllerImpl.java:646) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_71]
at org.jboss.as.controller.ModelControllerImpl$3$1.run(ModelControllerImpl.java:646) [jboss-as-controller-7.5.3.Final-redhat-2.jar:7.5.3.Final-redhat-2]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_71]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_71]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) [rt.jar:1.7.0_71]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) [rt.jar:1.7.0_71]
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]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.2.Final-redhat-1.jar:2.1.2.Final-redhat-1]
07:13:17,209 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.teiid.vdb.odata.1
{code}
\[3\]
{code:text}
07:19:05,346 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "oo3-vdb.xml" (runtime-name: "oo3-vdb.xml")
07:19:05,356 DEBUG [org.teiid.RUNTIME] (MSC service thread 1-6) VDB oo3-vdb.xml has been parsed.
07:19:05,361 ERROR [stderr] (MSC service thread 1-7) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
07:19:05,362 INFO [org.teiid.RUNTIME] (MSC service thread 1-7) TEIID50029 VDB odata3.1 model "Source" metadata is currently being loaded. Start Time: 22.9.2015 7:19
07:19:05,363 TRACE [org.teiid.RUNTIME] (MSC service thread 1-7) Model Source in VDB odata3 was being loaded from its repository
07:19:05,363 INFO [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50030 VDB odata3.1 model "Source" metadata loaded. End Time: 22.9.2015 7:19
07:19:05,365 TRACE [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 3) Resolving command SELECT 'b'
07:19:05,366 INFO [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID40003 VDB odata3.1 is set to ACTIVE
07:19:05,369 ERROR [stderr] (teiid-async-threads - 3) Exception in thread "teiid-async-threads - 3" java.lang.IllegalStateException
07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at org.teiid.jboss.VDBService.getBuffermanager(VDBService.java:502)
07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at org.teiid.jboss.VDBService.access$200(VDBService.java:85)
07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at org.teiid.jboss.VDBService$1.finishedDeployment(VDBService.java:156)
07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at org.teiid.deployers.VDBRepository.notifyFinished(VDBRepository.java:352)
07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at org.teiid.deployers.VDBRepository.finishDeployment(VDBRepository.java:308)
07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at org.teiid.runtime.AbstractVDBDeployer.metadataLoaded(AbstractVDBDeployer.java:202)
07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at org.teiid.jboss.VDBService.access$1100(VDBService.java:85)
07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at org.teiid.jboss.VDBService$6.run(VDBService.java:411)
07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at org.teiid.jboss.VDBService$7.run(VDBService.java:442)
07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
07:19:05,370 ERROR [stderr] (teiid-async-threads - 3) at java.lang.Thread.run(Thread.java:745)
07:19:05,371 ERROR [stderr] (teiid-async-threads - 3) at org.jboss.threads.JBossThread.run(JBossThread.java:122)
07:19:05,407 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015859: Deployed "oo3-vdb.xml" (runtime-name : "oo3-vdb.xml")
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (TEIID-3707) Wrong Data returned when a procedure is executed in the SELECT clause
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-3707?page=com.atlassian.jira.plugin... ]
Kylin Soong edited comment on TEIID-3707 at 9/22/15 1:13 AM:
-------------------------------------------------------------
I have met a build error that new added
{code}
public void testSubqueryCache() throws Exception {
{code}
cause gc thread consume high cpu, seems create a lot of threads, some time will failed test.
was (Author: kylin):
I have met a build error that new added
{code}
public void testSubqueryCache() throws Exception {
{code}
cause cause gc thread consume high cpu, seems create a lot of threads, some time will failed test.
> Wrong Data returned when a procedure is executed in the SELECT clause
> ---------------------------------------------------------------------
>
> Key: TEIID-3707
> URL: https://issues.jboss.org/browse/TEIID-3707
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.6
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 8.12, 8.11.5
>
> Attachments: sample_coords.sql, wrong_data.jpg
>
>
> I've found the following problem when executing a stored procedure in the SELECT clause. It calculates wrong data in a seemingly random fashion.
> This is a stored procedure which was created to determine whether a given coordinate lies within a specific rectangle. If this procedure is tested in a simple manner (SELECT .. FROM (EXEC ..)) the results are correctly retuned (0 = outside the rectangle and 1 otherwise).
> {code:sql}
> CREATE virtual procedure point_inside_store (
> pos_x float
> ,pos_y float
> ) RETURNS (
> "insideFence" integer
> ) AS
> BEGIN
> DECLARE integer insideFence = 0 ;
> DECLARE float lowerLimit = 0.0 ;
> DECLARE float upperLimit = 17.0 ;
> DECLARE float leftLimit = 0.0 ;
> DECLARE float rightLimit = 53.0 ;
> IF (
> pos_x >= leftLimit
> AND pos_x <= rightLimit
> AND pos_y >= lowerLimit
> AND pos_y <= upperLimit
> )
> BEGIN
> insideFence = 1 ;
> END
> SELECT
> insideFence ;
> END
> {code}
> If now the same procedure is included in a SELECT clause of a query:
> {code:sql}
> SELECT
> "citmp.KoordX"
> ,"citmp.KoordY"
> ,(
> SELECT
> "store.insideFence"
> FROM
> (
> EXEC procs.point_inside_store (
> CAST (
> "citmp.KoordX" AS float
> )
> ,CAST (
> "citmp.KoordY" AS float
> )
> )
> ) as "store"
> ) as "insideStore"
> ,(
> SELECT
> "firstsection.insideFence"
> FROM
> (
> EXEC procs.point_inside_store (
> CAST (
> "citmp.KoordX" AS float
> )
> ,CAST (
> "citmp.KoordY" AS float
> )
> )
> ) as "firstsection"
> ) as "insideFirstsection"
> FROM
> "test.sample_coords" as "citmp"
> ORDER BY
> insideStore ASC
> ,insideFirstsection DESC;;
> {code}
> it calculates different results. The same coordinates that yielded 0 before now yield 1.
> !wrong_data.jpg|thumbnail!
> Note that the main query has 2 columns executing the exact same procedure but there are result sets, that have different values in the last two columns. This should not be possible.
> In attachment you will find sample_coords table with a sample of coordinates.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (TEIID-3707) Wrong Data returned when a procedure is executed in the SELECT clause
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-3707?page=com.atlassian.jira.plugin... ]
Kylin Soong commented on TEIID-3707:
------------------------------------
I have met a build error that new added
{code}
public void testSubqueryCache() throws Exception {
{code}
cause cause gc thread consume high cpu, seems create a lot of threads, some time will failed test.
> Wrong Data returned when a procedure is executed in the SELECT clause
> ---------------------------------------------------------------------
>
> Key: TEIID-3707
> URL: https://issues.jboss.org/browse/TEIID-3707
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.6
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 8.12, 8.11.5
>
> Attachments: sample_coords.sql, wrong_data.jpg
>
>
> I've found the following problem when executing a stored procedure in the SELECT clause. It calculates wrong data in a seemingly random fashion.
> This is a stored procedure which was created to determine whether a given coordinate lies within a specific rectangle. If this procedure is tested in a simple manner (SELECT .. FROM (EXEC ..)) the results are correctly retuned (0 = outside the rectangle and 1 otherwise).
> {code:sql}
> CREATE virtual procedure point_inside_store (
> pos_x float
> ,pos_y float
> ) RETURNS (
> "insideFence" integer
> ) AS
> BEGIN
> DECLARE integer insideFence = 0 ;
> DECLARE float lowerLimit = 0.0 ;
> DECLARE float upperLimit = 17.0 ;
> DECLARE float leftLimit = 0.0 ;
> DECLARE float rightLimit = 53.0 ;
> IF (
> pos_x >= leftLimit
> AND pos_x <= rightLimit
> AND pos_y >= lowerLimit
> AND pos_y <= upperLimit
> )
> BEGIN
> insideFence = 1 ;
> END
> SELECT
> insideFence ;
> END
> {code}
> If now the same procedure is included in a SELECT clause of a query:
> {code:sql}
> SELECT
> "citmp.KoordX"
> ,"citmp.KoordY"
> ,(
> SELECT
> "store.insideFence"
> FROM
> (
> EXEC procs.point_inside_store (
> CAST (
> "citmp.KoordX" AS float
> )
> ,CAST (
> "citmp.KoordY" AS float
> )
> )
> ) as "store"
> ) as "insideStore"
> ,(
> SELECT
> "firstsection.insideFence"
> FROM
> (
> EXEC procs.point_inside_store (
> CAST (
> "citmp.KoordX" AS float
> )
> ,CAST (
> "citmp.KoordY" AS float
> )
> )
> ) as "firstsection"
> ) as "insideFirstsection"
> FROM
> "test.sample_coords" as "citmp"
> ORDER BY
> insideStore ASC
> ,insideFirstsection DESC;;
> {code}
> it calculates different results. The same coordinates that yielded 0 before now yield 1.
> !wrong_data.jpg|thumbnail!
> Note that the main query has 2 columns executing the exact same procedure but there are result sets, that have different values in the last two columns. This should not be possible.
> In attachment you will find sample_coords table with a sample of coordinates.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (TEIID-3708) Undeployable dynamic VDB at start-up time removes all previously deployed artifacts
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3708?page=com.atlassian.jira.plugin... ]
Steven Hawkins edited comment on TEIID-3708 at 9/21/15 3:29 PM:
----------------------------------------------------------------
Unless there are any objections, I'll move this to an EAP issue. If there is a service start exception in the file system boot time scan, an UndeployScanRunnable task is run that will cause not only the failed deployment to be undeployed, but all other deployments from the scan to be undeployed. This may be a timing issue as with debugging delaying the action of the UndeployScanRunnable seems to produce the correct behavior as there scans triggered.
was (Author: shawkins):
Unless there are any objections, I'll move this to an EAP issue. If there is a service start exception in the file system boot time scan, an UndeployScanRunnable task is fun that will cause not only the failed deployment, but all other deployments from the scan to fail. This may be a timing issue as with debugging delaying the action of the UndeployScanRunnable seems to produce the correct behavior as there scans triggered.
> Undeployable dynamic VDB at start-up time removes all previously deployed artifacts
> -----------------------------------------------------------------------------------
>
> Key: TEIID-3708
> URL: https://issues.jboss.org/browse/TEIID-3708
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1.6_2
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
>
> If standalone/deployments directory contains undeployable dynamic VDB at start-up (reload) time all deployments previously deployed via mangement CLI are undeployed.
> Log:
> {code:text}
> 13:42:48,993 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015899: JBoss Red Hat JBoss Data Virtualization 6.2.0 (AS 7.5.3.Final-redhat-2) starting
> ...
> ...
> ...
> 13:42:53,258 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("deploy") failed - address: ([("deployment" => "oo-vdb.xml")]) - failure description: {"JBAS014671: Failed services" => {"jboss.teiid.vdb.odata.1" => "org.jboss.msc.service.StartException in service jboss.teiid.vdb.odata.1: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata.1
> Caused by: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata.1"}}
> 13:42:53,300 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015859: Deployed "QT_MySql55_Push.vdb" (runtime-name : "QT_MySql55_Push.vdb")
> 13:42:53,301 INFO [org.jboss.as.server] (ServerService Thread Pool -- 30) JBAS015859: Deployed "oo-vdb.xml" (runtime-name : "oo-vdb.xml")
> 13:42:53,302 INFO [org.jboss.as.server] (ServerService Thread Pool -- 52) JBAS015859: Deployed "modeshape-cmis.war" (runtime-name : "modeshape-cmis.war")
> 13:42:53,302 INFO [org.jboss.as.server] (ServerService Thread Pool -- 30) JBAS015859: Deployed "integration-platform-console.war" (runtime-name : "integration-platform-console.war")
> 13:42:53,302 INFO [org.jboss.as.server] (ServerService Thread Pool -- 52) JBAS015859: Deployed "modeshape-webdav.war" (runtime-name : "modeshape-webdav.war")
> 13:42:53,302 INFO [org.jboss.as.server] (ServerService Thread Pool -- 52) JBAS015859: Deployed "modeshape-rest.war" (runtime-name : "modeshape-rest.war")
> 13:42:53,303 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.teiid.vdb.odata.1: org.jboss.msc.service.StartException in service jboss.teiid.vdb.odata.1: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata.1
> 13:42:53,330 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
> 13:42:53,330 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
> 13:42:53,331 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss Red Hat JBoss Data Virtualization 6.2.0 (AS 7.5.3.Final-redhat-2) started (with errors) in 4336ms - Started 619 of 664 services (1 services failed or missing dependencies, 100 services are lazy, passive or on-demand)
> 13:42:53,529 INFO [org.jboss.web] (ServerService Thread Pool -- 26) JBAS018224: Unregister web context: /modeshape-rest
> 13:42:53,538 INFO [org.jboss.web] (ServerService Thread Pool -- 19) JBAS018224: Unregister web context: /modeshape-webdav
> 13:42:53,540 INFO [org.jboss.web] (ServerService Thread Pool -- 18) JBAS018224: Unregister web context: /modeshape-cmis
> 13:42:53,544 INFO [org.teiid.RUNTIME] (MSC service thread 1-4) TEIID50026 VDB "QT_MySql55_Push.1[Source{Source=Source, mysql5, MySQL55_PushDS}, XQTRecursiveSchema{}, BQT2{}, SP{SP=SP, mysql5, MySQL55_PushDS}, VirtProcs{}, XQTSchema{}, XQTRecursiveDoc{}, XQT{}, BQT1{}, VQT{}, XQTNestedDoc{}, XQTDoc{}]" undeployed.
> 13:42:53,569 INFO [javax.enterprise.resource.webservices.jaxws.servlet.http] (ServerService Thread Pool -- 18) WSSERVLET15: JAX-WS servlet destroyed
> 13:42:53,572 INFO [javax.enterprise.resource.webservices.jaxws.server.http] (ServerService Thread Pool -- 18) WSSERVLET13: JAX-WS context listener destroyed
> 13:42:53,578 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment modeshape-rest.war (runtime-name: modeshape-rest.war) in 50ms
> 13:42:53,580 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment oo-vdb.xml (runtime-name: oo-vdb.xml) in 43ms
> 13:42:53,582 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment modeshape-webdav.war (runtime-name: modeshape-webdav.war) in 45ms
> 13:42:53,583 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment QT_MySql55_Push.vdb (runtime-name: QT_MySql55_Push.vdb) in 46ms
> 13:42:53,607 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment modeshape-cmis.war (runtime-name: modeshape-cmis.war) in 70ms
> 13:42:53,647 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "oo-vdb.xml" (runtime-name: "oo-vdb.xml")
> 13:42:53,648 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) JBAS014901: Content removed from location /home/jdurani/redhat/data-virtualization/dv_6.2.0/untouched_tmp3/standalone/data/content/45/9c1839c446e700d7f0b713f5f949b068fbeb24/content
> 13:42:53,648 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "QT_MySql55_Push.vdb" (runtime-name: "QT_MySql55_Push.vdb")
> 13:42:53,649 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) JBAS014901: Content removed from location /home/jdurani/redhat/data-virtualization/dv_6.2.0/untouched_tmp3/standalone/data/content/a3/b37a584c66a65d33bf194ffa9fc0e93c83b9ca/content
> 13:42:53,649 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "modeshape-webdav.war" (runtime-name: "modeshape-webdav.war")
> 13:42:53,651 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) JBAS014901: Content removed from location /home/jdurani/redhat/data-virtualization/dv_6.2.0/untouched_tmp3/standalone/data/content/f2/00c83231bcb7a63276d49ac9e01bcbbde30424/content
> 13:42:53,651 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "modeshape-cmis.war" (runtime-name: "modeshape-cmis.war")
> 13:42:53,652 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) JBAS014901: Content removed from location /home/jdurani/redhat/data-virtualization/dv_6.2.0/untouched_tmp3/standalone/data/content/2b/4d8dbcf74227d075e54215d1f330da494a4b22/content
> 13:42:53,657 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "modeshape-rest.war" (runtime-name: "modeshape-rest.war")
> 13:42:53,658 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.teiid.vdb.odata.1
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (TEIID-3708) Undeployable dynamic VDB at start-up time removes all previously deployed artifacts
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3708?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3708:
---------------------------------------
Unless there are any objections, I'll move this to an EAP issue. If there is a service start exception in the file system boot time scan, an UndeployScanRunnable task is fun that will cause not only the failed deployment, but all other deployments from the scan to fail. This may be a timing issue as with debugging delaying the action of the UndeployScanRunnable seems to produce the correct behavior as there scans triggered.
> Undeployable dynamic VDB at start-up time removes all previously deployed artifacts
> -----------------------------------------------------------------------------------
>
> Key: TEIID-3708
> URL: https://issues.jboss.org/browse/TEIID-3708
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1.6_2
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
>
> If standalone/deployments directory contains undeployable dynamic VDB at start-up (reload) time all deployments previously deployed via mangement CLI are undeployed.
> Log:
> {code:text}
> 13:42:48,993 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015899: JBoss Red Hat JBoss Data Virtualization 6.2.0 (AS 7.5.3.Final-redhat-2) starting
> ...
> ...
> ...
> 13:42:53,258 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("deploy") failed - address: ([("deployment" => "oo-vdb.xml")]) - failure description: {"JBAS014671: Failed services" => {"jboss.teiid.vdb.odata.1" => "org.jboss.msc.service.StartException in service jboss.teiid.vdb.odata.1: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata.1
> Caused by: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata.1"}}
> 13:42:53,300 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015859: Deployed "QT_MySql55_Push.vdb" (runtime-name : "QT_MySql55_Push.vdb")
> 13:42:53,301 INFO [org.jboss.as.server] (ServerService Thread Pool -- 30) JBAS015859: Deployed "oo-vdb.xml" (runtime-name : "oo-vdb.xml")
> 13:42:53,302 INFO [org.jboss.as.server] (ServerService Thread Pool -- 52) JBAS015859: Deployed "modeshape-cmis.war" (runtime-name : "modeshape-cmis.war")
> 13:42:53,302 INFO [org.jboss.as.server] (ServerService Thread Pool -- 30) JBAS015859: Deployed "integration-platform-console.war" (runtime-name : "integration-platform-console.war")
> 13:42:53,302 INFO [org.jboss.as.server] (ServerService Thread Pool -- 52) JBAS015859: Deployed "modeshape-webdav.war" (runtime-name : "modeshape-webdav.war")
> 13:42:53,302 INFO [org.jboss.as.server] (ServerService Thread Pool -- 52) JBAS015859: Deployed "modeshape-rest.war" (runtime-name : "modeshape-rest.war")
> 13:42:53,303 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.teiid.vdb.odata.1: org.jboss.msc.service.StartException in service jboss.teiid.vdb.odata.1: org.teiid.deployers.VirtualDatabaseException: TEIID40093 Model Source specified with no source information in VDB odata.1
> 13:42:53,330 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
> 13:42:53,330 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
> 13:42:53,331 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss Red Hat JBoss Data Virtualization 6.2.0 (AS 7.5.3.Final-redhat-2) started (with errors) in 4336ms - Started 619 of 664 services (1 services failed or missing dependencies, 100 services are lazy, passive or on-demand)
> 13:42:53,529 INFO [org.jboss.web] (ServerService Thread Pool -- 26) JBAS018224: Unregister web context: /modeshape-rest
> 13:42:53,538 INFO [org.jboss.web] (ServerService Thread Pool -- 19) JBAS018224: Unregister web context: /modeshape-webdav
> 13:42:53,540 INFO [org.jboss.web] (ServerService Thread Pool -- 18) JBAS018224: Unregister web context: /modeshape-cmis
> 13:42:53,544 INFO [org.teiid.RUNTIME] (MSC service thread 1-4) TEIID50026 VDB "QT_MySql55_Push.1[Source{Source=Source, mysql5, MySQL55_PushDS}, XQTRecursiveSchema{}, BQT2{}, SP{SP=SP, mysql5, MySQL55_PushDS}, VirtProcs{}, XQTSchema{}, XQTRecursiveDoc{}, XQT{}, BQT1{}, VQT{}, XQTNestedDoc{}, XQTDoc{}]" undeployed.
> 13:42:53,569 INFO [javax.enterprise.resource.webservices.jaxws.servlet.http] (ServerService Thread Pool -- 18) WSSERVLET15: JAX-WS servlet destroyed
> 13:42:53,572 INFO [javax.enterprise.resource.webservices.jaxws.server.http] (ServerService Thread Pool -- 18) WSSERVLET13: JAX-WS context listener destroyed
> 13:42:53,578 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment modeshape-rest.war (runtime-name: modeshape-rest.war) in 50ms
> 13:42:53,580 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment oo-vdb.xml (runtime-name: oo-vdb.xml) in 43ms
> 13:42:53,582 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment modeshape-webdav.war (runtime-name: modeshape-webdav.war) in 45ms
> 13:42:53,583 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment QT_MySql55_Push.vdb (runtime-name: QT_MySql55_Push.vdb) in 46ms
> 13:42:53,607 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment modeshape-cmis.war (runtime-name: modeshape-cmis.war) in 70ms
> 13:42:53,647 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "oo-vdb.xml" (runtime-name: "oo-vdb.xml")
> 13:42:53,648 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) JBAS014901: Content removed from location /home/jdurani/redhat/data-virtualization/dv_6.2.0/untouched_tmp3/standalone/data/content/45/9c1839c446e700d7f0b713f5f949b068fbeb24/content
> 13:42:53,648 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "QT_MySql55_Push.vdb" (runtime-name: "QT_MySql55_Push.vdb")
> 13:42:53,649 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) JBAS014901: Content removed from location /home/jdurani/redhat/data-virtualization/dv_6.2.0/untouched_tmp3/standalone/data/content/a3/b37a584c66a65d33bf194ffa9fc0e93c83b9ca/content
> 13:42:53,649 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "modeshape-webdav.war" (runtime-name: "modeshape-webdav.war")
> 13:42:53,651 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) JBAS014901: Content removed from location /home/jdurani/redhat/data-virtualization/dv_6.2.0/untouched_tmp3/standalone/data/content/f2/00c83231bcb7a63276d49ac9e01bcbbde30424/content
> 13:42:53,651 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "modeshape-cmis.war" (runtime-name: "modeshape-cmis.war")
> 13:42:53,652 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) JBAS014901: Content removed from location /home/jdurani/redhat/data-virtualization/dv_6.2.0/untouched_tmp3/standalone/data/content/2b/4d8dbcf74227d075e54215d1f330da494a4b22/content
> 13:42:53,657 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "modeshape-rest.war" (runtime-name: "modeshape-rest.war")
> 13:42:53,658 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.teiid.vdb.odata.1
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (TEIID-3694) Netezza translator - add additional support for other regexp functions
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3694?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3694.
-----------------------------------
Fix Version/s: 8.12
(was: 8.9)
Resolution: Done
Added the pushdown function method declarations into the translator.
> Netezza translator - add additional support for other regexp functions
> ----------------------------------------------------------------------
>
> Key: TEIID-3694
> URL: https://issues.jboss.org/browse/TEIID-3694
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Fix For: 8.12
>
>
> Support for LIKE_REGEX predicate was added, now would like to add support for the following:
> Netezza doesn't support regular expression by default, but with the installation of SQL Extensions toolkit this functionality is added. After installation Netezza provide the regular expression functions:
> regexp_extract()
> regexp_extract_all()
> regexp_extract_all_sp()
> regexp_extract_sp()
> regexp_instr()
> regexp_like()
> regexp_match_count()
> regexp_replace()
> regexp_replace_sp()
> IBM Netezza SQL Extensions toolkit is an optional package for IBM Netezza data warehouse appliances.
> After installing this toolkit on Netezza and requires that regular expression in JBoss DV syntax are pushed down (delegated) to Netezza to prevent that filtering in the Jboss DV server most be done.
> So please provide a configurable option in the Netezza translator of Jboss DV by which we can enable the LIKE_REGEX predicate for Netezza. This option when enabled will assume that the Netezza SQL extension toolkit is installed and the function regexp_like() is available.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months
[JBoss JIRA] (TEIID-3520) Extend the Swagger support in the WS Translator
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3520?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3520:
-------------------------------------
No, to new translator/connector Swagger. Not needed. The intention behind this enhancement is ability to read swagger based metadata about REST based services and define the metadata model in Teiid automatically to integrate into, not that we need to use some Swagger swag.
Look at WSDLMetadatProcessor and WSWSDLProcedureExecution classes that are defined for WSDL based executions. We need something exactly same as that, SwaggerMetadataProcessor and SwaggerProcedureExecution that knows how to parse and interpret the Swagger metadata and able to handle the executions using BinaryWSprocedureExecution class.
To "WSConnection" class add "getSwaggerURL()" method. Add necessary properties in "connector-ws", but do not add any dependencies about Swagger in "connector-ws" module, and wire up in the translator.
> Extend the Swagger support in the WS Translator
> -----------------------------------------------
>
> Key: TEIID-3520
> URL: https://issues.jboss.org/browse/TEIID-3520
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Ramesh Reddy
> Assignee: Kylin Soong
> Fix For: 8.12
>
>
> http://swagger.io is popular REST service description framework, it defines a specification http://swagger.io/specification/ for REST service definition.
> Teiid WS translator should add the ability to read this file (like WSDL) and provide the REST methods as endpoints that can be consumed from Teiid.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 3 months