> Regardless of the number of connections I make to teiid only 1 connection from the connection pool is used.
Just to confirm you mean a connection pool that Teiid is consuming and not a connection pool with Teiid connections correct? Also, just making a connection to Teiid does not cause it to use any source connections.
> Where could I find this in the documentation?
Teiid behaves like any other consumer of container connections. With concurrent load (queries) against Teiid it is expected for it to consume the necessary source connections concurrently. While there are configuration properties that do influence the amount of concurrency, if you have a default install then you shouldn't have to mess with that just yet.
> Are there any upgrades to consider in version 8.4 of 8.5 regarding this functionality?
No, I think that we'll need to understand what you are seeing better before advising about next steps. What is your concurrent query load? What do your query plans look like? What are the pool sizings for the datasources?
With a connection pool I do indeed mean a connection pool that teiid is consuming.
The current load on Teiid is very low. Only one or 2 simultanious users/querys.
The querys I'm talking about below are all select querys.
One of my datasources is a Sybase Server to which I connect using jtds. When a certain query fails it seems like the connection to this sybase server is closed. Any other connections to teiid, that need the connection to sybase, fail. I'd expect Teiid to create new connections for these concurrent querys.
Is there some property to make teiid create a new connection when one is closed or fails?
> I'd expect Teiid to create new connections for these concurrent querys.
That's a function of the connection pool, rather than Teiid directly. The AS pool can be configured with test queries and other mechanisms that should purge connections that are no longer usable. See http://stackoverflow.com/questions/128527/is-there-any-way-to-have-the-jboss-connection-pool-reconnect-to-oracle-when-co… and Connection validation in JBoss AS 7 and the as docs.