2607255 - IQ server goes to a Deadlock If hos_ABORT is Recursively Called by the Same Thread -- SAP IQ16.0 | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

2607255 - IQ server goes to a Deadlock If hos_ABORT is Recursively Called by the Same Thread -- SAP IQ16.0

Symptom

All of sudden IQ server encountered unresponsive ( or, hang ) status  and any following connections failed to connect to server. When dump couple of stacks, below thread showed important symbols.

  • Stack =>

 Thread 1522 (Thread 0x7fc0935da700 (LWP 20397)):
   .. __lll_lock_wait  ...
   .. _L_lock_791  ...
   .. pthread_mutex_lock  ...
   .. abort_handle_secondary(char const*)  ...
   .. hos_ABORT(char const*,   ...
   .. SigHndlr  ...
   ..  <signal handler called>
   .. hos_strncat(char*,  ...
   .. ucstkgenPrintheading(int, int)  ...
   .. DumpAllThreads(char const*,  ...
   .. hos_ABORT(char const*,  ...
   .. Throw(hos_exception const&)  ...
   .. hos_assertexception::ThrowException(char const*,  ...
   .. st_ErrorQueue::~st_ErrorQueue()  ...


Read more...

Environment

  • SAP IQ 16.0 SP11.x

Product

SAP IQ 16.0

Keywords

"server hang" ; "hos_ABORT" ; "abort_handle_secondary" ; "No answer" ; CR812970 ; CR#812970; 812970 ; stacktrace ; stktrc ; , 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 ONE Support launchpad (Login required).

Search for additional results

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