[shawkins]

> @Steven - unfortunately, at this moment i have only production environment , i cannot update now to newer release.

This would be more to just confirm behavior.  Ideally you could do that in a non-production environment.

[lukaszmro]

Hi, please find attached detailed log

edit:that was only a part...

How can i send you priv message with full log?

[lukaszmro]

Solved!

	</datasource>
	<datasource jndi-name="***" pool-name="***" enabled="true">
	<connection-url>****</connection-url>
	<driver>jaybird-2.2.5.jar</driver>
	<security>
	<user-name>***</user-name>
	<password>***</password>
	</security>

<timeout>

<blocking-timeout-millis>180000</blocking-timeout-millis>

<idle-timeout-minutes>3</idle-timeout-minutes>

</timeout>

<pool>

<min-pool-size>10</min-pool-size>

<max-pool-size>500</max-pool-size>

<prefill>true</prefill>

</pool>
	</datasource>

[rareddy]

Lukas,

Please explain the difference from before what you had? The configuration will not change the behavior of resultset being closed. Either you have a new driver with fixed error or one the times have been extended, in that case the problem has been just delayed not eliminated.

Ramesh..

[lukaszmro]

Hi,

After change DS def. i dont have any errors anymore in console.

It seems - for me - that error occurred, because teiid was waiting for query result which was not possible to receive from query.

And the reason for this was in pool.

Since i increased the pool and timeout - query can be finished and everything works fine.