Re: max number of connections

Jonathan Leffler wrote: > Your original message said 7.21; this one says 7.31. Which is > correct? It's critical because 7.21 is obsolete to the point of being > archaic whereas 7.31 is still supported. It's really 7.31, sorry for the typo. > > > Assuming it is 7.31, what are the NETTYPE settings you've got, and > which connection method are you using? If you had shared memory > connections and the nettype limited it to 10, you might run into some > problems. It should be of the type 'it takes a minute or more to fail > to connect' rather than the DBMS freezing (which would explain why > there are no errors in the log file). OTOH, if you're using oltlitcp > connections, then you should not run into this problem. If all > activity in the DBMS freezes, then this is somewhat different - more > likely a bug. > We use both ontlitcp for remote connections and onipcshm for local connections. NETTYPE is not defined in onconfig. How can nettype limit the number of shared memory connections? AFAICT, the remote connections actually freeze, there is a big gap in the tcpdump. I don't know if something happens in the local connections, is there a way to trace them in a way similar to tcpdump? --Micha

On Tue, 11 Nov 2003 12:42:00 -0500, Micha wrote: <SNIP>> We use both ontlitcp for remote connections and onipcshm for local > connections. NETTYPE is not defined in onconfig. How can nettype limit the > number of shared memory connections? AFAICT, the remote connections actually > freeze, there is a big gap in the tcpdump. I don't know if something happens > in the local connections, is there a way to trace them in a way similar to > tcpdump? NETTYPE exactly limits the number of concurrent shared memory connections as it drives the calculation of how many shared memory communication blocks to allocate when the engine starts up, this is a fixed value which is not reallocated at need. The default shared memory setting for NETTYPE if your ONCONFIG file does not have one is: NETTYPE ipcshm,1,50,<vptype>vptype is CPU if DBSERVERNAME is the shared memory connection (if more poll threads are specified than there are CPU VPs then the overflow are started in NET VPs) vptype is NET if DBSERVERALIASES contains the shared memory connection So normally one pollthread in the first CPU VP is started and 50 shared memory communication blocks are allocated along with 50 semaphores to latch them. Art S. Kagel