Symptom
-
On IQ Multiplex server, is frequently observed slowness. It has been noted that logging into the database was taking more than five minutes, and exiting from the database also takes significantly longer than expected.
- Messages in iqmsg file:
-
s_buf::WaitForSignal_DontCareIfBusy- Timed out on _condvar, timeout value= 10 secondssbuf= 0x121d2d0 btype= 14
s_buf::WaitForSignal_DontCareIfBusy- Timed out on _condvar, timeout value= 20 secondssbuf= 0x121d2d0 btype= 14
s_buf::WaitForSignal_DontCareIfBusy- Timed out on _condvar, timeout value= 10 secondssbuf= 0x1620960 btype= 14
s_buf::WaitForSignal_DontCareIfBusy- Timed out on _condvar, timeout value= 20 secondssbuf= 0x1620960 btype= 14
-
- Messages in srvlog file:
- W. Task 0x20fba00(Request task 279) is trying get forbid mutex held by task 0x20f6400(Request task 263) for more than 60000 ms
W. Task 0x20f6400(Request task 263) state: OS thread id=0x7f1bb34f3700
W. Task 0x20f6400(Request task 263) state: worker=0x7f22cc028610 wakend=0 waiting=0
W. Worker 0x7f22cc028610 state: wakend=0 waiting=0 in_atomic=0 is_dedicated=0 in_critical_section=0 allow_forbid=1
- W. Task 0x20fba00(Request task 279) is trying get forbid mutex held by task 0x20f6400(Request task 263) for more than 60000 ms
Read more...
Environment
SAP IQ
Product
SAP IQ all versions
Keywords
SAP IQ, slowness, logging, exiting, multiplex server, s_buf::WaitForSignal_DontCareIfBusy, mutex, timeout , 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.