[JBoss JIRA] (TEIID-2537) NPE Executing Against REST Web Service Source
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2537?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2537:
----------------------------------
Issue Type: Bug (was: Enhancement)
This doesn't seem possible as there are checks for the number of arguments and arguments and their values cannot be null.
Can you reproduce this in 8.4? What is the actual procedure invocation and procedure metadata that you are calling? Did the metadta come from the designer or from a dynamic scenario?
> NPE Executing Against REST Web Service Source
> ---------------------------------------------
>
> Key: TEIID-2537
> URL: https://issues.jboss.org/browse/TEIID-2537
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.3
> Reporter: Ted Jones
> Assignee: Steven Hawkins
>
> Using Designer 8.1/Teiid 8.3 and executing against the following:
> http://gw.esworkplace.sap.com/sap/opu/sdata/iwcnt/contact/ContactCollecti...
>
> gives me the following NPE:
> 13:00:28,345 ERROR [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue25) YH9sbL1HZbxJ TEIID30019 Unexpected exception for request YH9sbL1HZbxJ.6: java.lang.NullPointerException
> at org.teiid.translator.ws.BinaryWSProcedureExecution.getOutputParameterValues(BinaryWSProcedureExecution.java:178)
> at org.teiid.dqp.internal.datamgr.ProcedureBatchHandler.getParameterRow(ProcedureBatchHandler.java:86) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:356) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:141) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:467) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:178) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:175) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [classes.jar:1.6.0_45]
> at java.util.concurrent.FutureTask.run(FutureTask.java:138) [classes.jar:1.6.0_45]
> at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:120) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:264) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:123) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:298) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_45]
> at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_45]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (TEIID-2537) NPE Executing Against REST Web Service Source
by Ted Jones (JIRA)
Ted Jones created TEIID-2537:
--------------------------------
Summary: NPE Executing Against REST Web Service Source
Key: TEIID-2537
URL: https://issues.jboss.org/browse/TEIID-2537
Project: Teiid
Issue Type: Enhancement
Components: Misc. Connectors
Affects Versions: 8.3
Reporter: Ted Jones
Assignee: Steven Hawkins
Using Designer 8.1/Teiid 8.3 and executing against the following:
http://gw.esworkplace.sap.com/sap/opu/sdata/iwcnt/contact/ContactCollecti...
gives me the following NPE:
13:00:28,345 ERROR [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue25) YH9sbL1HZbxJ TEIID30019 Unexpected exception for request YH9sbL1HZbxJ.6: java.lang.NullPointerException
at org.teiid.translator.ws.BinaryWSProcedureExecution.getOutputParameterValues(BinaryWSProcedureExecution.java:178)
at org.teiid.dqp.internal.datamgr.ProcedureBatchHandler.getParameterRow(ProcedureBatchHandler.java:86) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:356) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:141) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:467) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:178) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:175) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [classes.jar:1.6.0_45]
at java.util.concurrent.FutureTask.run(FutureTask.java:138) [classes.jar:1.6.0_45]
at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:120) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:264) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:123) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:298) [teiid-engine-8.3.0.Final.jar:8.3.0.Final]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_45]
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_45]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (TEIID-2536) MetadataFactory datatype issue on boot up
by Van Halbert (JIRA)
Van Halbert created TEIID-2536:
----------------------------------
Summary: MetadataFactory datatype issue on boot up
Key: TEIID-2536
URL: https://issues.jboss.org/browse/TEIID-2536
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.4
Reporter: Van Halbert
Assignee: Steven Hawkins
Occurs on server startup. Deployed a vdb and was able to connect, etc. Bounced the server and now get a bunch of these errors:
21:03:39,432 ERROR [org.jboss.threads.executor] (teiid-async-threads -
1) Task execution failed for task org.teiid.jboss.VDBService$6@54241d18:
java.lang.NullPointerException
at
org.teiid.metadata.MetadataFactory.addDatatype(MetadataFactory.java:589)
[teiid-api-8.4.0.CR2-SNAPSHOT.jar:8.4.0.CR2-SNAPSHOT]
at
org.teiid.metadata.MetadataFactory.correctDataTypes(MetadataFactory.java:583)
[teiid-api-8.4.0.CR2-SNAPSHOT.jar:8.4.0.CR2-SNAPSHOT]
at
org.teiid.metadata.MetadataFactory.correctDatatypes(MetadataFactory.java:559)
[teiid-api-8.4.0.CR2-SNAPSHOT.jar:8.4.0.CR2-SNAPSHOT]
at org.teiid.jboss.VDBService$6.run(VDBService.java:367)
[teiid-jboss-integration-8.4.0.CR2-SNAPSHOT.jar:8.4.0.CR2-SNAPSHOT]
at
org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33)
at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:806)
at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45)
at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:847)
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
------------
Looking at MetadataFactory I noticed the following:
Datatype dt = this.builtinDataTypes.get(c.getDatatype().getName());
if (dt != null) {
c.setDatatype(dt);
} else {
//must be an enterprise type
//if it's used in a single schema, we're ok, but when used in multiple there's an issue
--> addDatatype(dt);
}
}
---------
that addDatatype(dt) was passing dt when null, and therefore, in addDatatype, the NPE was caused when datatype.getName() is called. But I think what was intended was to pass in c.getDatatype() when it wasn't found in the builtinDataTypes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (TEIID-2534) Object protocol errors provide no client information
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2534?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2534.
-----------------------------------
Labels: 8.4.Final (was: )
Resolution: Done
Modified the objectencoder to throw a meaningful exception when an encoding error occurs and modified the client/server to use a special message to indicate that there was a problem. This allows the connection to remain open and the client to see the exception.
This will only work with 8.4 Final (or later) clients and servers.
> Object protocol errors provide no client information
> ----------------------------------------------------
>
> Key: TEIID-2534
> URL: https://issues.jboss.org/browse/TEIID-2534
> Project: Teiid
> Issue Type: Quality Risk
> Components: JDBC Driver, Server
> Affects Versions: 6.0.0
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Critical
> Labels: 8.4.Final
> Fix For: 8.4
>
>
> Issues when writing an object value to output result in a terminated connection and no meaningful client exception. It would be better to have a meaningful exception and to not terminate the connection - as it actually hasn't been corrupted.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (TEIID-2534) Object protocol errors provide no client information
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2534:
-------------------------------------
Summary: Object protocol errors provide no client information
Key: TEIID-2534
URL: https://issues.jboss.org/browse/TEIID-2534
Project: Teiid
Issue Type: Quality Risk
Components: JDBC Driver, Server
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Critical
Fix For: 8.4
Issues when writing an object value to output result in a terminated connection and no meaningful client exception. It would be better to have a meaningful exception and to not terminate the connection - as it actually hasn't been corrupted.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (TEIID-2533) ConcurrentModificationException when list-sessions operation is issued
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2533?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-2533:
--------------------------------
Affects Version/s: 8.0
(was: 8.4)
> ConcurrentModificationException when list-sessions operation is issued
> ----------------------------------------------------------------------
>
> Key: TEIID-2533
> URL: https://issues.jboss.org/browse/TEIID-2533
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.0
> Environment: Teiid 8.4.CR2 and EAP 6.1 Alpha
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Labels: Final
> Fix For: 8.4
>
>
> Saw the following exception in the server log, but not sure what I did to trigger it (unable to reproduce):
> 07:31:32,834 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("list-sessions") failed - address: ([("subsystem" => "teiid")]): java.util.ConcurrentModificationException
> at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:819) [rt.jar:1.7.0_13]
> at java.util.ArrayList$Itr.next(ArrayList.java:791) [rt.jar:1.7.0_13]
> at org.teiid.jboss.ListSessions.executeOperation(TeiidOperationHandler.java:245)
> at org.teiid.jboss.ListSessions.executeOperation(TeiidOperationHandler.java:225)
> at org.teiid.jboss.BaseOperationHandler$1.execute(BaseOperationHandler.java:72)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:142) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:112) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) [jboss-as-protocol-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) [jboss-as-protocol-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months