Kevin A. Burton wrote:
> Use SHOW PROCESSLIST to see connected users.
Ah! That makes sense! So this is the "Threads_connected" value in a SHOW STATUS,
yes? I think what was confusing me is that when I do a SHOW PROCESSLIST, the
user is always the same - it's the "name" of the "user" that's accessing MySQL -
but each "user" listed has a unique ID - I take it that those are the
"connections" or entries in the pool? And the actual connections (NOT pooled)
are something else?
>> If anyone is familiar with the "maxActive" parameter for a Tomcat
>> connection pool, how does that correspond with the value of
>> max_connections? From the Tomcat docs, I read that "maxActive" is the
>> maximum # of db connections in a connection pool; from what I read on
>> the MySQL site, "max_connections" is the max number of simultaneous
>> client connections allowed - so should these be the same? Are these
>> looking at the same thing?
>
>
> No! Don't make them the same! This will prevent you from connecting to
> your DB even from the MySQL client... set maxActive from 5-10... for
> even a multithreaded app this will be sufficient.
Wha? Whoa, I *really* misunderstood this - my maxActive is set to 300! Yes,
maxActive is for the Tomcat DB pool, using DBCP. The docs for it said it was the
max # of connections in a connection pool - and since we have a kind of limit of
300 users, I took this to mean that I should set that (maxActive, that is) to
300, since that's the max # of entries in the pool I wanted. Umm, might I see
this as a memory problem - or would things just not work? max_connections is
currently 100(which I think is the default, I don't recall changing it), whereas
maxActive is 300.
Maybe there are some more docs I need to read...
Thanks!!!
--
Lynn Hollerman.
