BBL Stuck In Semaphore Op And Became Unresponsive
(Doc ID 2245799.1)
Last updated on MAY 19, 2020
Applies to:Oracle Tuxedo - Version 12.1.3 and later
Information in this document applies to any platform.
Application became unresponsive due to BBL became unresponsive.
A different symptom that also caused BBL became unresponsive and requires the same fix:
053038.machine!GWTDOMAIN.59572566.258.0: ERROR: msgrcv err(LIBTUX_CAT:666: ERROR: Message operation failed because the queue was removed): errno=36,qid=3148002,buf=540818248,bytes=-1,type=0,flag=0
053038.machine!GWTDOMAIN.20054268.258.0: ERROR: msgrcv err(LIBTUX_CAT:666: ERROR: Message operation failed because the queue was removed): errno=36,qid=12585183,buf=544110296,bytes=-1,type=0,flag=0
053039.machine!TMQUEUE_MQM.63439066.1.0: LIBTUX_CAT:1199: ERROR: Cannot re-attach: operating system error: errno = 22.
053039.machine!TMQUEUE_MQM.63439066.1.0: LIBTUX_CAT:268: ERROR: Failed to stop serving
053039.machine!GWTDOMAIN.62062998.1.0: LIBTUX_CAT:752: ERROR: semop system call failure for semaphore 4194344, errno 22
053039.machine!GWADM.62783876.1.0: LIBTUX_CAT:752: ERROR: semop system call failure for semaphore 4194344, errno 22
053044.machine!EACenPOSSrv.1180210.1.0: LIBTUX_CAT:1538: WARN: Could not lock Bulletin Board
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document