Hi Jerry, thats really strange, i think we changed nothing in the pool handling. Maybe you give some more informations about your config.xml and tell us the mysql version + mysql jdbc connector version.
bye Norman JWM schrieb: > I am attempting to move up to 2.3.0 from 2.2.0a17. 2.3.0 runs somewhat... > Mail is passing through it, getting stored, etc. But after running a short > time, Outlook started popping up those "can't logon to POP.... give me > another password" popups. I'd hit enter and they'd go away, mail would > arrive. But then a few minutes later they'd start popping up again. > > I went to the logs and saw hundreds of the following error message (in all > the logs... not just POP): > > java.sql.SQLException: Cannot connect to MySQL server on 127.0.0.1:3306. Is > there a MySQL server running on the machine/port you are trying to connect > to? (java.net.BindException) > > (The answer is 'yes'... there is a MySQL server on that port... James talked > to it a few milliseconds before and a few milliseconds after each of these > messages...) > > My debug attempts so far: > > 1) I simply shut down 2.3.0 and fired up 2.2.0a17 again. It ran solid with > zero errors for several hours. Swapped back to 2.3.0, and started getting > errors within 10 minutes. NO other changes in the machine except the > version of James that is running. > > 2) I never recycled mysql during any of this. Same exact mysql for both. > So the old James can talk to the db consistently just fine, and the new > James can't seem to connect ever few times it tries. > > 3) There are no errors in the mysql log. So it doesn't look like a mysql > connection issue. > > I'm running with 40 max connections (same with both versions of the server). > But the default config file has 20. It also says to bump it up if I get a > certain error. But it's not this error message. > > I figure I could go in and start bumping it higher. But I don't like simply > opening throttles up with no idea why. > > So my question is... what has changed between 2.2.0a17 and 2.3.0 in the area > of db connections? This message seems to indicate a socket error with the > mysql server. But mysql never changes and it only fails with the new > version of James. > > I'm a software architect and can do debug. So feel free to talk as techie > as you like about this. > > Please give me some hints as to what might be happening. I can't move to > 2.3.0 until I figure this out. > > Thx. > > Jerry > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
