SAP Knowledge Base Article - Preview

3720670 - Hung connection/transaction on secondary node resulting in version buildup - SAP IQ

Symptom

  • On a secondary Multipltex server, drop a connection.
  • On IQMSG, "Cancellation request received" is printed.
  • However, the connection is still listed hours later in sp_iqtransaction, sp_iqconnection, sp_iqversionuse, sp_iqcontext.
  • This causes version pilling up.

In the stacks dumped with pstack, these functions can be found:

pthread_cond_destroy@@GLIBC_2.3.2 () 
hos_condvar::__Destruct() () 
st_fifo::~st_fifo()
st_fifo::~st_fifo() 
st_cursorIQtoSA::__Destruct()
st_cursorIQtoSA::~st_cursorIQtoSA() 
hos_vector_noerror::ClearAndDestroy() 
st_connection::DestroyAllCursors() () 
st_iqctl::DestroyAllCursors(UIConnection*, st_connection*) 
UIQCtl_DestroyAllCursors ()


Read more...

Environment

  • SAP IQ 16.1
  • Multiplex

Product

SAP IQ 16.1

Keywords

831603, CR831603, CR#831603, Multiplex, MPX , KBA , BC-SYB-IQ , Sybase IQ , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.