remote instances, and their tcp connections
Posted in 2004
Topics: Stored Procedures & SPL, Connectivity: ODBC / JDBC / .NET, Java & JDBC Development
One of my systems / business analysts asked me the following question: They run a Java program, which connects to Informix via JDBC. This session calls a stored procedure, which in turn does a select on another remote Informix instance. This select will obviously create a tcp connection to that remote instance from the local instance. When is this remote tcp connection terminated ? Does it stay open the entire time the session is active ? And (2), if this same session does multiple remote queries, will it use the same (open?) tcp connection repeatedly ? Hope my question is clear enough ... Dirk Moolman Database and Unix Administrator MXGROUP "People demand freedom of speech as a compensation for the freedom of thought which they seldom use." -Kierkegaard sending to informix-list
Dirk Moolman wrote: > One of my systems / business analysts asked me the following question: > > > They run a Java program, which connects to Informix via JDBC. This > session calls a stored procedure, which in turn does a select on another > remote Informix instance. > > This select will obviously create a tcp connection to that remote > instance from the local instance. When is this remote tcp connection > terminated ? Does it stay open the entire time the session is active ? > > And (2), if this same session does multiple remote queries, will it use > the same (open?) tcp connection repeatedly ? > > Hope my question is clear enough ... The connection is transient and exists only for the single query. If you will be accessing a remote server frequently in a session, and do not need to join to local tables, it is far faster to open a second direct connection to the remote server in you application and run a version of the stored procedure locally there. That connection will remain open as long as you don't close it. Art S. Kagel > Dirk Moolman > Database and Unix Administrator > MXGROUP