Accessing a JDBC source via ODATA creates stack trace in log

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