home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
14.10.xC10 FixList
12.10.xC16.X5 FixList
11.70.xC9.XB FixList
11.50.xC9.X2 FixList
11.10.xC3.W5 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

Informix - Problem description

Problem IT43562 Status: Closed

A THREAD CAN CONSUME 100% CPU UTILIZATION IN A SOCKET BACK FLOW SCENARIO
LOOPING SEND() CALLS

product:
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10
Problem description:
While the socket back flow situation may be illustrative of
another network related issue, the server should not consume
100% cpu retrying send() calls that continually fail with
EAGAIN/EWOULDBLOCK errors.

This is especially painful on a single cpu vp IDS server

An example of a CDR NIF send thread showing this behavior can be
seen by monitoring
 output for a CDRNsT# thread which might show
something like:

 249    CDRNsT6                1cpu    04/16 23:45:05
189.8525  342044266    running
 249    CDRNsT6                1cpu    04/16 23:45:06
190.7593  342052426    running
 249    CDRNsT6                1cpu    04/16 23:45:07
191.6844  342058701    running

where you would see the CDRNsT# thread constantly running or
ready and if you ran a pstack against the 1cpu vp oninit process
you would likely catch a stack like:

#0  0xffffe410 in __kernel_vsyscall ()
#1  0x008fc941 in send () from /lib/libpthread.so.0
#2  0x08f107f5 in sendsocket ()
#3  0x08f65ee4 in tlSend ()
#4  0x08f6267f in slSQIsend ()
#5  0x08efc946 in ASF_Call ()
#6  0x08b49ac3 in nifasf_putsendbuf ()
#7  0x08b49f91 in nifasf_send ()
#8  0x08b45d30 in nifiSendBuf ()
#9  0x08b4694b in nifSend ()
#10 0x08b3e46d in nifiGenericStart ()
#11 0x08a7bde4 in cdrTrampolineThread ()
#12 0x08dfc36c in th_init_initgls ()
#13 0x08e2e52b in startup ()
#14 0x00000000 in ?? ()
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Users of Informix Server prior to 12.10.xC16.                *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Informix Server 12.10.xC16.                       *
****************************************************************
Local Fix:
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* Users of Informix Server prior to 12.10.xC16.                *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Informix Server 12.10.xC16.                       *
****************************************************************
Comment
Fixed in Informix Server 12.10.xC16.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.04.2023
18.05.2023
18.05.2023
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)