Informix Message Service on NT4 SP4
Posted in 1999
Topics: Logging & Checkpoints
I had an interesting experience this week with Workgroup Server 7.22 on NT4. I've had this Informix instance running reasonably well for some time, but sometime over the holidays it got strange. It started taking about 20 minutes to restart after the server came up, and checkpoints began to take several minutes. Today I couldn't stand it any longer. On investigation it appears that the "Informix Message Service" broke. This is $INFORMIXDIR/bin/msgserv.exe, and apparently it normally runs as a service (daemon). Informix server seems to want to talk to this message service every time it wants to put something in the log. Like at checkpoints, and over and over during startup. It seems to wait 120 seconds for the message service to respond and then it gives up and gets the message in the log some other way. I renamed msgserv.exe to something else and the delays went away. I don't know quite what msgserv.exe does but things seem okay without it. I think this was broken by NT4 SP4. I can't prove it but that's the only significant thing that changed recently. Dwight Rudolph
Dwight Rudolph Jr wrote: > > I had an interesting experience this week with Workgroup Server 7.22 on NT4. > > I've had this Informix instance running reasonably well for some time, but > sometime over the holidays it got strange. It started taking about 20 minutes > to restart after the server came up, and checkpoints began to take several > minutes. > > Today I couldn't stand it any longer. On investigation it appears that the > "Informix Message Service" broke. This is $INFORMIXDIR/bin/msgserv.exe, and > apparently it normally runs as a service (daemon). > > Informix server seems to want to talk to this message service every time it > wants to put something in the log. Like at checkpoints, and over and over > during startup. It seems to wait 120 seconds for the message service to > respond and then it gives up and gets the message in the log some other way. > > I renamed msgserv.exe to something else and the delays went away. I don't > know quite what msgserv.exe does but things seem okay without it. > > I think this was broken by NT4 SP4. I can't prove it but that's the only > significant thing that changed recently. Search the IIUG archive of this group. There were some posts a month or two ago about problems with Service Pack 4 on NT4. Art S. Kagel