Oninit cdi / Archive
Talk to an expert →

tlitcppoll thread assert failures

Posted in 2000

Topics: Error Codes & Troubleshooting, Logging & Checkpoints, Platform-Specific Issues

Katherine Olson — — source: Informix-list mailing list archive (1991-1998)

engine: 7.31.UC5 o/s: solaris 2.5.1 We've had 2 assert failures with the following message: _________________________________________________________________________________ 07:10:42 Assert Failed: No Exception Handler 07:10:42 Informix Dynamic Server Version 7.30.UC10 07:10:42 Who: Session(5, informix@, 0, 0) Thread(11, tlitcppoll, 0, 5) File: mtex.c Line: 314 07:10:42 Results: Exception Caught. Type: MT_EX_OS, Context: mem 07:10:42 Action: Please notify Informix Technical Support. 07:11:04 See Also: /af/af.bdde2 07:11:04 mtex.c, line 314, thread 11, proc id 17281, No Exception Handler. 07:11:04 PANIC: Attempting to bring system down 07:39:34 Requested shared memory segment size rounded from 972000KB to983040KB ____________________________________________________________________________________ 07:41:53 Checkpoint Completed: duration was 0 seconds. 07:43:09 Assert Failed: No Exception Handler 07:43:09 Informix Dynamic Server Version 7.31.UC5 07:43:09 Who: Session(11, informix@, 0, 0) Thread(17, tlitcppoll, 0, 11) File: mtex.c Line: 446 07:43:09 Results: Exception Caught. Type: MT_EX_OS, Context: mem 07:43:09 Action: Please notify Informix Technical Support. 07:43:09 See Also: /af/af.3f92ced 07:43:09 mtex.c, line 446, thread 17, proc id 18179, No Exception Handler. 07:43:09 PANIC: Attempting to bring system down 07:48:05 Requested shared memory segment size rounded from 972000KB to983040KB 07:48:17 Segment locked: addr=0xa000000, size=1006632960 Tech support can't do anything for us due the fact that the af.* files coming from the crashes contain no stack info. Has anyone seen this before, or have any new insights on tlitcppoll threads? We've read everything in the SA books on them. thanks much- Katherine

↪ replying to Katherine Olson
Art S. Kagel — — source: Informix-list mailing list archive (1991-1998)

Set the ONCONFIG file to save a core dump. If it happens again load the core file into a debugger and get a stack trace from the debugger to send to Informix. I had to do that for years as the DGUX releases do not do the stack trace thing ever. BTW the first trace says it's from Vers 7.30UC10 while the second says 7.31UC5. An attempt to avoid the bug by upgrading? Art S. Kagel Katherine Olson wrote: > > engine: 7.31.UC5 > o/s: solaris 2.5.1 > > We've had 2 assert failures with the following message: > > _________________________________________________________________________________ > > 07:10:42 Assert Failed: No Exception Handler > 07:10:42 Informix Dynamic Server Version 7.30.UC10 > 07:10:42 Who: Session(5, informix@, 0, 0) > Thread(11, tlitcppoll, 0, 5) > File: mtex.c Line: 314 > 07:10:42 Results: Exception Caught. Type: MT_EX_OS, Context: mem > 07:10:42 Action: Please notify Informix Technical Support. > 07:11:04 See Also: /af/af.bdde2 > 07:11:04 mtex.c, line 314, thread 11, proc id 17281, No Exception > Handler. > 07:11:04 PANIC: Attempting to bring system down > 07:39:34 Requested shared memory segment size rounded from 972000KB to> 983040KB > ____________________________________________________________________________________ > > 07:41:53 Checkpoint Completed: duration was 0 seconds. > 07:43:09 Assert Failed: No Exception Handler > 07:43:09 Informix Dynamic Server Version 7.31.UC5 > 07:43:09 Who: Session(11, informix@, 0, 0) > Thread(17, tlitcppoll, 0, 11) > File: mtex.c Line: 446 > 07:43:09 Results: Exception Caught. Type: MT_EX_OS, Context: mem > 07:43:09 Action: Please notify Informix Technical Support. > 07:43:09 See Also: /af/af.3f92ced > 07:43:09 mtex.c, line 446, thread 17, proc id 18179, No Exception > Handler. > 07:43:09 PANIC: Attempting to bring system down > 07:48:05 Requested shared memory segment size rounded from 972000KB to> 983040KB > 07:48:17 Segment locked: addr=0xa000000, size=1006632960> > Tech support can't do anything for us due the fact that the af.* files > coming from the crashes contain no stack info. Has anyone seen this > before, or have any new insights on tlitcppoll threads? We've read > everything in the SA books on them. > > thanks much- > Katherine

↪ replying to Katherine Olson
David Williams — — source: Informix-list mailing list archive (1991-1998)

In article <8f9te3$emh$1@news.xmission.com>, Katherine Olson <matisse@cfer.com> writes > > >engine: 7.31.UC5 >o/s: solaris 2.5.1 > >We've had 2 assert failures with the following message: > >________________________________________________________________________________ >_ > >07:10:42 Assert Failed: No Exception Handler >07:10:42 Informix Dynamic Server Version 7.30.UC10 >07:10:42 Who: Session(5, informix@, 0, 0) > Thread(11, tlitcppoll, 0, 5) > File: mtex.c Line: 314 >07:10:42 Results: Exception Caught. Type: MT_EX_OS, Context: mem >07:10:42 Action: Please notify Informix Technical Support. >07:11:04 See Also: /af/af.bdde2 >07:11:04 mtex.c, line 314, thread 11, proc id 17281, No Exception >Handler. >07:11:04 PANIC: Attempting to bring system down> Are you using a) HDR Data Replication? b) Enterprise Replication >thanks much- >Katherine > -- David Williams

↪ replying to Katherine Olson
Arkadiusz Socha — — source: Informix-list mailing list archive (1991-1998)

>07:10:42 Assert Failed: No Exception Handler >07:10:42 Informix Dynamic Server Version 7.30.UC10 >07:10:42 Who: Session(5, informix@, 0, 0) > Thread(11, tlitcppoll, 0, 5) > File: mtex.c Line: 314 >07:10:42 Results: Exception Caught. Type: MT_EX_OS, Context: mem >07:10:42 Action: Please notify Informix Technical Support. >07:11:04 See Also: /af/af.bdde2 >07:11:04 mtex.c, line 314, thread 11, proc id 17281, No Exception >Handler. >07:11:04 PANIC: Attempting to bring system down Yes I saw this section of log file and restarted server few times. Statistics seem to be ok. Couldn't find what was wrong. o/s: SCO Arek

Glossary