[teiid-issues] [JBoss JIRA] (TEIID-4799) Accessing a JDBC source via ODATA creates stack trace in log
Van Halbert (JIRA)
issues at jboss.org
Tue Mar 7 16:14:00 EST 2017
[ https://issues.jboss.org/browse/TEIID-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Van Halbert updated TEIID-4799:
-------------------------------
Attachment: stacktrace.txt
> Accessing a JDBC source via ODATA creates stack trace in log
> -------------------------------------------------------------
>
> Key: TEIID-4799
> URL: https://issues.jboss.org/browse/TEIID-4799
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12.8.6_3
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Attachments: stacktrace.txt
>
>
> When doing a get to a odata endpoint that will use a jdbc connection in data virtualization, there will be a transaction related stacktrace in the logs. This does not seem to create a problem but is confusing.
> Version-Release number of selected component (if applicable):
> 8.12.x
> How reproducible:
> Steps to Reproduce:
> 1. Add a JDBC datasource model in the Teiid Design Perspective
> 2. Add a Teiid Metadata view model using the JDBC source model
> 3. Deploy the view model in a VDB
> 4. Access the view model via an odata call
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the teiid-issues
mailing list