Hello Vinicius,
Please use some tools like “netstat ano” (all systems) or https://docs.microsoft.com/en-us/sysinternals/downloads/tcpview (windows) to investigate open connections, their states (wait_close, established, ...) etc. As it will help to see the state of networking system before looking into problem – it may be configuration problem of system not products etc.
If squirrel client detects the closed connection I will bet on not properly closed connection from initiating side (APMSql server) than sql rest api – it will keep squirrel waiting for close etc. It is easier to process to close open connections than binded connections. So checking log of APMSql server for anything unusual (exception etc.) can also help.
If this is a test environment, you can try enable DEBUG logging in the APMSqlServer.properties
log4j.rootLogger=DEBUG,console, logfile
log4j.logger.org.teiid=DEBUG,teiidlog
log4j.logger.com.ca.apm.server=DEBUG,console,logfile
Increasing verbosity can help, but I will expect that disconnection should be in warn or at least info level, so maybe debug is too much for this kind of issue, also, I am not sure if teiid will not generate huge log in debug in your environment.
I hope this helps,
Regards,
Sergio