RE: Exceeding Number of Connections

We are having -908 problems but all users lock out when it occurs. After consultation with Informix they tell us that for tcp connections then these parameters are ignored and the no of sessions are allocated dynamically. Checking this out if you do an onstat -u this tells you the current sessions , maximum sessions allocated and maximum sessionsa since start up or onstat -z . The maximum allowed actually increases in blocks of 128 as more sessions are connected. We lock out at around 800 users but on a restart we can easily exceed 1024 sessions with no problem. The lock out are random. I suspect that we might be running out of memory or we have a sockets problem ( AIX ) Cheers > -----Original Message----- > From: Don Ignacio [SMTP:dignacio@openratings.com] > Sent: 18 October 2000 22:09 > To: 'Red Valsen'; informix-list@iiug.org > Subject: RE: Exceeding Number of Connections > > As far as I know this shouldn't occur. When you > specify in your NETTYPE the number of connections > it won't allow you to exceed that number. > > When you executed onstat -u are the session ids > unique? It's possible that a session (connection) > spawned more than one thread. And what you're seeing > are the multiple threads for the same session number. > > > Don > > -----Original Message----- > From: Red Valsen [mailto:red_valsen@yahoo.com] > Sent: Wednesday, October 18, 2000 1:48 PM > To: informix-list@iiug.org > Subject: Exceeding Number of Connections > > > What are the practical effects of exceeding the number of connections > that a poll thread is set to handle via onconfig file's NETTYPE > parameter? During functional testing, we inadvertently created over > 750 connections (as reported by onstat -u) with NETTYPE set to > tlitcp,1,128,NET. We observed no ill effects -- performance > degradation, slowness spawining additional connections, server dying, > etc. So what is actually happening here? Is the poll thread actually > doing any "work," or just establishing and disconnecting sockets? > > We're running IDS 7.31.UC4 on Solaris2.7/Intel (don't ask).