SearchEngineSummarizer loses database connection

From Ffej:

------------
There's a bug with SearchEngineSummarizer where occasionally the
database connection gets lost when we summarize the warehouse data. It
usually only effects Ask.com I think because we're creating so many
warehouse summarizers that don't actually do anything.
------------

From the log of the 9/1 run of Ask:
---------------------

• • BEGIN NESTED EXCEPTION **

com.mysql.jdbc.CommunicationsException
MESSAGE: Communications link failure due to underlying exception:

• • BEGIN NESTED EXCEPTION **

java.io.EOFException

STACKTRACE:

java.io.EOFException
at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:1913)
at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2304)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2803)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:812)
at com.mysql.jdbc.MysqlIO.secureAuth411(MysqlIO.java:3269)
at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:1182)
at com.mysql.jdbc.Connection.createNewIO(Connection.java:2670)
at com.mysql.jdbc.Connection.<init>(Connection.java:1531)
at
com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at com.carldunham.jst.db.Database.init(Database.java:203)
at com.carldunham.jst.db.Database.<init>(Database.java:188)
at com.carldunham.jst.db.Database.<init>(Database.java:169)
at
com.thesearchagency.db.util.DatabaseAccounts.getDatabaseURL(DatabaseAccounts.java:161)
at
com.thesearchagency.db.util.MultiplexDatabasePool.get(MultiplexDatabasePool.java:109)
at
com.thesearchagency.db.util.AccountDatabases.get(AccountDatabases.java:102)
at
com.thesearchagency.perf.WarehouseSummarizer$AccountWorker.run(WarehouseSummarizer.java:452)
at
com.carldunham.jst.concurrency.ThreadPool$WorkerThread.run(ThreadPool.java:248)

• • END NESTED EXCEPTION **

Last packet sent to the server was 1956 ms ago.

STACKTRACE:

com.mysql.jdbc.CommunicationsException: Communications link failure due to
underlying exception:

• • BEGIN NESTED EXCEPTION **

java.io.EOFException

STACKTRACE:
---------------------------

If this is solely effecting Ask impact is minimized, but if it were to effect
Google for a large account, the impact on the Account Managers would be more
substantial.

The effect appears to be that an account may not get data for that day.