Actually, it seems like that there is only on stateless session bean that
initiates the connection pool problem. I have about 8 stateless session
beans that are called in sequence during the run of my application. Each of
these ejbs uses one connection to the database. If I specify in jboss.jcml
the maximum number of connections to be 5, I can run the application 4.5
times. During the fifth time, one of my ejbs will be waiting for a
connection indefinitely. If I increase the number of
connections to 10, I can run the application 9.5 times until it starts
hanging...

Thomas Kirsch



--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
List Help?:          [EMAIL PROTECTED]

Reply via email to