|
Problem IT16756
|
Status: Closed |
INAPPROPRIATE CALL TO DESTROY_SESSION AND AF MAY RESULT FROM LOSS OF REMOTE CONNECTION DURING QUERY PROCESSING
|
| product: |
INFORMIX SERVER / 5725A3900 / B70 - IDS 11.70 |
| Problem description: |
An SQL query that includes access to remote tables should
terminate with an error if the connection to the remote server
is lost. If the connection is lost at certain points in the
query processing then the error is incorrectly handled and an
attempt is made to terminate the session via a call to
destroy_session(). This may result in an Assert Failure being
raised together with a -408 error being returned to the
application.
The Assert Fail and stack for the sqlexec thread from an example
AF file:
Assert Failed: Condition Failed (Ignoring free of pool '5347'
(0xc000000165a12040) in use by blkpool), In (mt_shm_free_pool)
afstack
afhandler
affail_interface
mem_asfail
mt_shm_free_pool
destroy_session
sqsetconerr
asf_recv
_iread
_igetint
fetchahead
remfetch
rem_gettupl
remote_scan_next
inner_next
join_next
join_next
join_next
join_next
join_next
next_row
hash_process_all_groups
group_open
sort_open
prepselect
open_cursor
sql_open
sq_open
sqmain
listen_verify
spawn_thread
th_init_initgls
startup
Due to the nature of this problem an AF file may not always be
produced. The local session will be terminated with a -408 error
"Invalid message type received from the sqlexec process." |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* production environment *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to IBM Informix Server 11.70.xC9 *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.08.2016
09.06.2017
09.06.2017 |
| Problem solved at the following versions (IBM BugInfos) |
11.70.xC9
|
| Problem solved according to the fixlist(s) of the following version(s) |
