Re: Communications link failure due to underlying exception...various network exceptions
Posted by:
mreichman
Date: February 15, 2007 07:58AM
Hi, it happened again after setting the option:
com.mysql.jdbc.CommunicationsException: 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:2357)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2803)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:812)
at com.mysql.jdbc.MysqlIO.nextRow(MysqlIO.java:1295)
at com.mysql.jdbc.MysqlIO.readSingleRowSet(MysqlIO.java:2262)
at com.mysql.jdbc.MysqlIO.getResultSet(MysqlIO.java:439)
at com.mysql.jdbc.MysqlIO.readResultsForQueryOrUpdate(MysqlIO.java:1970)
at com.mysql.jdbc.MysqlIO.readAllResults(MysqlIO.java:1387)
at com.mysql.jdbc.ServerPreparedStatement.serverExecute(ServerPreparedStatement.java:1195)
at com.mysql.jdbc.ServerPreparedStatement.executeInternal(ServerPreparedStatement.java:693)
at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1266)
at com.virage.util.database.SQLProcessor.handleQuery(SQLProcessor.java:398)
at com.virage.util.database.SQLProcessor.doExecuteQuery(SQLProcessor.java:213)
at com.virage.util.database.SQLProcessor.executeQuery(SQLProcessor.java:171)
at com.virage.store.db.DbAssetLoader.loadTextTracks(DbAssetLoader.java:800)
at com.virage.store.db.DbAssetLoader.load(DbAssetLoader.java:151)
at com.virage.store.db.AssetManagerImpl.getAssetList(AssetManagerImpl.java:89)
at com.virage.search.dre.DreAssetDataManager.writeAssetData(DreAssetDataManager.java:128)
at com.virage.search.dre.DreAssetDataManager.executeBulkIngest(DreAssetDataManager.java:363)
at com.virage.search.dre.DreEngineImpl.update(DreEngineImpl.java:703)
at com.virage.search.dre.DreEngineImpl.update(DreEngineImpl.java:626)
at com.virage.search.SearchManagerImpl.update(SearchManagerImpl.java:428)
at com.virage.search.UpdateSearchIndexMessageListener.doWork(UpdateSearchIndexMessageListener.java:99)
at com.virage.search.UpdateSearchIndexMessageListener.onMessage(UpdateSearchIndexMessageListener.java:47)
at com.virage.jms.SimpleGuardedMessageListener.onMessage(SimpleGuardedMessageListener.java:36)
at org.exolab.jms.client.JmsMessageConsumer.onMessage(JmsMessageConsumer.java:254)
at org.exolab.jms.client.JmsSession.onMessage(JmsSession.java:1023)
at org.exolab.jms.client.net.JmsSessionStubImpl.onMessage(JmsSessionStubImpl.java:478)
at sun.reflect.GeneratedMethodAccessor64.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.exolab.jms.net.orb.DefaultORB$Handler.invoke(DefaultORB.java:553)
at org.exolab.jms.net.orb.DefaultORB$1.run(DefaultORB.java:511)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)
** END NESTED EXCEPTION **
Last packet sent to the server was 118581 ms ago.
at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2515)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2803)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:812)
at com.mysql.jdbc.MysqlIO.nextRow(MysqlIO.java:1295)
at com.mysql.jdbc.MysqlIO.readSingleRowSet(MysqlIO.java:2262)
at com.mysql.jdbc.MysqlIO.getResultSet(MysqlIO.java:439)
at com.mysql.jdbc.MysqlIO.readResultsForQueryOrUpdate(MysqlIO.java:1970)
at com.mysql.jdbc.MysqlIO.readAllResults(MysqlIO.java:1387)
at com.mysql.jdbc.ServerPreparedStatement.serverExecute(ServerPreparedStatement.java:1195)
at com.mysql.jdbc.ServerPreparedStatement.executeInternal(ServerPreparedStatement.java:693)
at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1266)
at com.virage.util.database.SQLProcessor.handleQuery(SQLProcessor.java:398)
at com.virage.util.database.SQLProcessor.doExecuteQuery(SQLProcessor.java:213)
at com.virage.util.database.SQLProcessor.executeQuery(SQLProcessor.java:171)
at com.virage.store.db.DbAssetLoader.loadTextTracks(DbAssetLoader.java:800)
at com.virage.store.db.DbAssetLoader.load(DbAssetLoader.java:151)
at com.virage.store.db.AssetManagerImpl.getAssetList(AssetManagerImpl.java:89)
at com.virage.search.dre.DreAssetDataManager.writeAssetData(DreAssetDataManager.java:128)
at com.virage.search.dre.DreAssetDataManager.executeBulkIngest(DreAssetDataManager.java:363)
at com.virage.search.dre.DreEngineImpl.update(DreEngineImpl.java:703)
at com.virage.search.dre.DreEngineImpl.update(DreEngineImpl.java:626)
at com.virage.search.SearchManagerImpl.update(SearchManagerImpl.java:428)
at com.virage.search.UpdateSearchIndexMessageListener.doWork(UpdateSearchIndexMessageListener.java:99)
at com.virage.search.UpdateSearchIndexMessageListener.onMessage(UpdateSearchIndexMessageListener.java:47)
at com.virage.jms.SimpleGuardedMessageListener.onMessage(SimpleGuardedMessageListener.java:36)
at org.exolab.jms.client.JmsMessageConsumer.onMessage(JmsMessageConsumer.java:254)
at org.exolab.jms.client.JmsSession.onMessage(JmsSession.java:1023)
at org.exolab.jms.client.net.JmsSessionStubImpl.onMessage(JmsSessionStubImpl.java:478)
at sun.reflect.GeneratedMethodAccessor64.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.exolab.jms.net.orb.DefaultORB$Handler.invoke(DefaultORB.java:553)
at org.exolab.jms.net.orb.DefaultORB$1.run(DefaultORB.java:511)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)
The interesting part about this stack trace is that it still mentions ServerPreparedStatement classes. Could the option not properly be set here? Or does it still go through the same codebase, just fork off somewhere inside..
Subject
Written By
Posted
February 13, 2007 07:56AM
February 13, 2007 08:00AM
February 13, 2007 11:07AM
February 13, 2007 01:52PM
February 13, 2007 02:25PM
February 13, 2007 02:33PM
February 13, 2007 02:42PM
February 13, 2007 02:47PM
February 14, 2007 07:45AM
Re: Communications link failure due to underlying exception...various network exceptions
February 15, 2007 07:58AM
February 25, 2009 12:39AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.