IBM Support

O33 Read Queue Timeout Loop Max Exceeded Message in diag.log

Question & Answer


Why do I get " O33 Read Queue Timeout Loop Max Exceeded " messages in the diag.log


This message from the function clp_read_outputq indicates that a
frontend process timed out in receiving message from it's backend
process.The frontend process is running in a loop trying to receive the
message from it's backend and these messages are written to db2diag.log.

That is normal processing and mostly can be seen at diaglevel 4. when server is experiencing high loads.

Related Information

[{"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"DB2 Tools - db2diag.log","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.5","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 June 2018