[JBoss JIRA] (TEIID-2508) Admin api getSchema fails for long schema
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2508?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-2508.
---------------------------------
Resolution: Rejected
mark, if you can recreate with new client as Steve mentions re-open.
> Admin api getSchema fails for long schema
> -----------------------------------------
>
> Key: TEIID-2508
> URL: https://issues.jboss.org/browse/TEIID-2508
> Project: Teiid
> Issue Type: Bug
> Components: AdminApi
> Affects Versions: 8.4
> Environment: Fedora 17, Teiid 8.4 Beta2, JBoss EAP 6.1 alpha
> Reporter: Mark Drilling
> Assignee: Ramesh Reddy
> Fix For: 8.4
>
> Attachments: Exception_getDDL.txt
>
>
> The admin.getSchema call to return DDL is failing for long schema (no problem with just a few tables). We had a different issue previously but this is still an issue with 8.4B2 in EAP6.1Alpha. Attaching server stacktrace.
--
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-2508) Admin api getSchema fails for long schema
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2508?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2508:
---------------------------------------
See my last comment. The newer DMR code supports both short and long string using different type identifiers s vs. S
For Mark to get this exception it means that his client does not support long strings and must be an older DMR version.
> Admin api getSchema fails for long schema
> -----------------------------------------
>
> Key: TEIID-2508
> URL: https://issues.jboss.org/browse/TEIID-2508
> Project: Teiid
> Issue Type: Bug
> Components: AdminApi
> Affects Versions: 8.4
> Environment: Fedora 17, Teiid 8.4 Beta2, JBoss EAP 6.1 alpha
> Reporter: Mark Drilling
> Assignee: Ramesh Reddy
> Fix For: 8.4
>
> Attachments: Exception_getDDL.txt
>
>
> The admin.getSchema call to return DDL is failing for long schema (no problem with just a few tables). We had a different issue previously but this is still an issue with 8.4B2 in EAP6.1Alpha. Attaching server stacktrace.
--
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-2508) Admin api getSchema fails for long schema
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2508?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2508:
-------------------------------------
I tried the salesforce schema did not have any issues.
> Admin api getSchema fails for long schema
> -----------------------------------------
>
> Key: TEIID-2508
> URL: https://issues.jboss.org/browse/TEIID-2508
> Project: Teiid
> Issue Type: Bug
> Components: AdminApi
> Affects Versions: 8.4
> Environment: Fedora 17, Teiid 8.4 Beta2, JBoss EAP 6.1 alpha
> Reporter: Mark Drilling
> Assignee: Ramesh Reddy
> Fix For: 8.4
>
> Attachments: Exception_getDDL.txt
>
>
> The admin.getSchema call to return DDL is failing for long schema (no problem with just a few tables). We had a different issue previously but this is still an issue with 8.4B2 in EAP6.1Alpha. Attaching server stacktrace.
--
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-2471) Allow permission conditions and masking to be pluggable
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2471?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2471:
---------------------------------------
I'm thinking that if we do go with the MetadataFactory, then we'll operate at the programatic grant/permission (with the methods shown above) level rather than using the xml definition directly. The paradigm is basically that the role definition is in the vdb (declares the name of the role, mapped role names, etc.). Permissions can then be granted to the named roles with the MetadataFactory.
> Allow permission conditions and masking to be pluggable
> -------------------------------------------------------
>
> Key: TEIID-2471
> URL: https://issues.jboss.org/browse/TEIID-2471
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.4
>
>
> The AuthorizationValidator or similar interface should allow for alternative implementations to be plugged in for providing permission conditions and column masking.
--
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-2329) Add support for Mongo DB as a data source
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2329?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2329:
-------------------------------------
Commited initial version of MongoDB support to github master.
This feature adds the support to integrate MongoDB as one of the supported sources in the Teiid. This commit consists of a connector module and translator module. The translator DOES NOT have capability to provide metadata to Teiid based on already existing MongoDB. The user is expected to define a schema that they want to use with MongoDB. This is designed explicitly keeping in mind of good segment of users that want move their data from RDBMS to MongoDB, or starting out with MongoDB, but know their schema and prefer to work with SQL and not get tangled with MongoDB specific dialect. The choice of MongoDB may be for scaling and performance.
This translator can convert SELECT, INSERT, UPDATE and DELETE calls appropriately the MongoDB specific dialect. There are extended metadata features available, that can let users build a single complex document in MongoDB based on multiple individual tables in the VDB Schema defined for MongoDB. Supports creation of indexes on MongoDB. Supports aggregation and functions exposed by the MongoDB. This translator uses MongoDB "aggregation" framework for all the queries, so selecting the MongoDB version that has support for "aggregation" framework is mandatory. I developed using MongoDB 2.4.1
Currently I have not added support for LOBs and Composite Keys and native queries. These are still pending, depending upon on time scale for 8.4 either get implemented or pushed to next version. Documentation will be added
> Add support for Mongo DB as a data source
> -----------------------------------------
>
> Key: TEIID-2329
> URL: https://issues.jboss.org/browse/TEIID-2329
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Fix For: 8.4, Open To Community
>
>
--
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-2511) NullPointerException in JDBCExecutionFactory.getDatabaseCalendar()
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2511?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2511:
---------------------------------------
The javadoc covers that. Generally the idea is that whomever constructs the instance will call start. With later EmbeddedServer's you can just use the addTranslator(Class) method, which will start the instance created.
> 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
12 years, 10 months
[JBoss JIRA] (TEIID-2511) NullPointerException in JDBCExecutionFactory.getDatabaseCalendar()
by RAKESH BALGURI (JIRA)
[ https://issues.jboss.org/browse/TEIID-2511?page=com.atlassian.jira.plugin... ]
RAKESH BALGURI commented on TEIID-2511:
---------------------------------------
Thanks Steve. I was not aware of this condition. Since in the deploy mode, the start() is invoked automatically, I though that start() would be invoked automatically in the case of the Embedded Server as well.
> 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
12 years, 10 months
[JBoss JIRA] (TEIID-2511) NullPointerException in JDBCExecutionFactory.getDatabaseCalendar()
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2511?page=com.atlassian.jira.plugin... ]
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
12 years, 10 months