devxlogo

No Response from Server: Part II

Why Trust Us

Question:
This happened when I issued the NETSTAT command:

 TCP    informix:turbo         as2000:1260  CLOSE_WAITTCP    informix:turbo         as2000:1261  CLOSE_WAITTCP    informix:turbo         as2000:1262  CLOSE_WAITTCP    informix:turbo         as2000:1263  CLOSE_WAIT

Is this why we can’t get more connections? (I have NT4 Server, Informix 7.31 TC2, fewer than 100 users.)

Answer:
You’re on 7.31 TC2. What Service Pack is your NT 4.0 on? I believe 7.31 works with SP5 or later, but I’m not sure.

I’m not exactly sure how to do this, but could you try killing some of the TCP connections manually? Maybe by starting/stopping the network rather than doing a complete reboot. If you can regain connectivity after killing some of the TCP/IP sessions, then it’s pretty obviously a problem linked to the number of sessions. Otherwise, is there anything you have been able to do to restore connectivity other than stopping/starting the database?

E-mail me a copy of your ONCONFIG file and I’ll take a look at it.

Disclosure
devxblackblue

About Our Editorial Process

At DevX, we’re dedicated to tech entrepreneurship. Our team closely follows industry shifts, new products, AI breakthroughs, technology trends, and funding announcements. Articles undergo thorough editing to ensure accuracy and clarity, reflecting DevX’s style and supporting entrepreneurs in the tech sphere.

See our full editorial policy.

About Our Journalist

Charlie Frank

Charlie has over a decade of experience in website administration and technology management. As the site admin, he oversees all technical aspects of running a high-traffic online platform, ensuring optimal performance, security, and user experience.
View Author
Show More