Hi, I've seen this exception on mysql quite regularly, it usually occurs when a bounced mail can't be delivered and goes into an endless loop. However I wondered if you were using the jdbc:odbc bridge or a full JDBC driver, as one issue with the bridge is that it isn't thread safe, and we, along with most jakarta projects, wouldn't recommend it for a production deployment.
We are also aware of certain issues regarding the db connection pool, and Serge has replaced some of the avalon classes with new ones of our own to address these. However as they appear in 2.0a2 then I can only assume that that is not really relevant. :-( d. > -----Original Message----- > From: David Shpil [mailto:[EMAIL PROTECTED]] > Sent: Monday, February 25, 2002 1:56 PM > To: James User > Subject: Spool manager on M$ SQL > > > Hi, all > > Lately I have started to evaluate James v2.0a2 with M$ SQL sever. > In a production env, I need a mail server to handle large amount of > small ( < 700b) messages. > To test James' behavior under such king of load, I run two threads, > which concurently sending and receiving mail through the server. > > So, here is my problem: > 1. Setting number of threads in spool manager to 1, makes James work > fine with 3-4 messages per second. If I increase message rate the > spool manager becomes overloaded and it takes a lot of time to get > mail delivered to local inbox. > 2. Setting number of threads in spool manager to 2 and more, causes > the following exception to be thrown (Full stack trace is attached) > > java.io.IOException: java.sql.SQLException: Giving up... no connections > available. > > I made the same test with different JDBC drivers: inet, ThinWeb, > jnetdirect; > and I got almost identical results. > > Did any of you ever consider this problem? > Are there any test results available for a comparison? > > > Regards, > > David. > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
