I am using poolman 2.1 with apache tomcat 4. The problem i am facing is that
connection pool is not accessible through jndi whereas in server window
poolman gives confirmation that pool is bound to jndi name. However
connection is available and working through Poolman class. I m really stuck
at th
If you can, try out the 3.3. I find it much more stable and scalable
then 3.2.x.
Bojan
Endre Stølsvik wrote:
> I'm experiencing hangs when testing out a application with tomcat 3.2.3 on
> Sun's JRE 1.3.1_01 running on a Intel 733MHz Redhat 7.1 stock kernel,
> using only 2 PoolTcpConnector HTTP
I'm experiencing hangs when testing out a application with tomcat 3.2.3 on
Sun's JRE 1.3.1_01 running on a Intel 733MHz Redhat 7.1 stock kernel,
using only 2 PoolTcpConnector HTTP (min/max spare = 0) connections, but
with 150 clients, really hassling the server.
The server hangs for quite some