[teiid-issues] [JBoss JIRA] (TEIID-2511) NullPointerException in JDBCExecutionFactory.getDatabaseCalendar()

Steven Hawkins (JIRA) jira-events at lists.jboss.org
Tue May 21 05:49:06 EDT 2013


     [ https://issues.jboss.org/browse/TEIID-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-2511.
-----------------------------------

    Resolution: Rejected


When you supply your own translator instances, you are expected to call .start() prior to registering them with the EmbeddedServer.
                
> NullPointerException in JDBCExecutionFactory.getDatabaseCalendar()
> ------------------------------------------------------------------
>
>                 Key: TEIID-2511
>                 URL: https://issues.jboss.org/browse/TEIID-2511
>             Project: Teiid
>          Issue Type: Bug
>          Components: Embedded
>    Affects Versions: 8.1
>            Reporter: RAKESH BALGURI
>            Assignee: Steven Hawkins
>         Attachments: TestNullPointerExceptionGetDatabaseCalendar.java
>
>
> We are getting NPE in JDBCExecutionFactory.getDatabaseCalendar() when running using the Embedded Teiid Connection.
> SEVERE: Connector worker process failed for atomic-request=mAIqLopt6urZ.0.0.0
> java.lang.NullPointerException
> 	at org.teiid.translator.jdbc.JDBCExecutionFactory.getDatabaseCalendar(JDBCExecutionFactory.java:468)
> 	at org.teiid.translator.jdbc.JDBCExecutionFactory.retrieveValue(JDBCExecutionFactory.java:903)
> 	at org.teiid.translator.jdbc.JDBCQueryExecution.next(JDBCQueryExecution.java:101)
> 	at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:316)
> 	at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:141)
> 	at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:428)
> 	at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:270)
> 	at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:279)
> 	at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:279)
> 	at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:148)
> 	at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:146)
> 	at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:112)
> 	at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:153)
> 	at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:382)
> 	at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:291)
> 	at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51)
> 	at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:219)
> 	at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:386)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:601)
> 	at org.teiid.transport.LocalServerConnection$1$1.call(LocalServerConnection.java:131)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> 	at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:249)
> 	at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:233)
> 	at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:129)
> 	at $Proxy12.executeRequest(Unknown Source)
> 	at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:631)
> 	at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:506)
> 	at org.teiid.jdbc.StatementImpl.executeQuery(StatementImpl.java:327)
> 	at testcase.TestNullPointerExceptionGetDatabaseCalendar.testNullPointer(TestNullPointerExceptionGetDatabaseCalendar.java:64)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:601)
> 	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> 	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> 	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> 	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
> 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> 	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> 	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> 	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> 	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> 	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> 	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> 	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
> 	at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> 	at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> 	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)

--
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


More information about the teiid-issues mailing list