Java.sql.SQLException: Communication link failure:, underlying cause: null

From Partner Documentation Wiki

Jump to: navigation, search
Legal Disclaimer
By using this Wiki, you are agreeing to these terms of use.
Partner Software
Documentation Resource for End-users and Developers.
1,759 articles in English


Scenario 1

Symptom: When attempting to start Partner Hub, the following message appeared on the screen:



The solution is to run UpdateCentralHub from the Master Install Applauncher, which can be done by following the instructions from Scenario 1 of Can't get checksum for shared package!


This was one of several error messages on a hub that would not start. The file PartnerHub\CentralHub\os\windows\jre\lib\i386\jvm.cfg did not exist in this case. It did exist in the same path of the Master Install.

Other errors appearing in the same log:

Java.sql.SQLException: Communication link failure:, underlying cause: null


This was one of several error messages on a hub that would not start. This particular error seems to be related to the SEDCSocket interface, but alone it does not seem to be the root cause of why the Partner Hub crashed. It appears that the error Could not open `PartnerHub\CentralHub\os\windows\jre\lib\i386\jvm.cfg was the primary reason why the Partner Hub crashed.

Log Snippett

 INFO 2008-10-20 07:24:58,825 [SEDCSocket] (com.partnersoft.v3x.apps.Staker.interfaces.ExternalInterfaceModule:SEDCSocket)
    Running SEDCSocket interface.
 INFO 2008-10-20 07:25:10,372 [ExchangeSocket request filler] (com.partnersoft.v3x.util.ConfigStore)
    Loading configuration from v3x/Platform/config/partner/Network.tof
 INFO 2008-10-20 07:25:11,403 [ExchangeSocket request filler] (com.partnersoft.v3x.apps.Staker.server.JobLibrary)
    Releasing job com.partnersoft.v3x.apps.Staker.CheckedOutJob@3cfa60
ERROR 2008-10-20 07:25:11,497 [ExchangeSocket request filler] (com.partnersoft.v3x.apps.Staker.server.JobLibrary)
    java.sql.SQLException: Communication link failure:, underlying cause: null


	at com.mysql.jdbc.MysqlIO.readFully(
	at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(
	at com.mysql.jdbc.MysqlIO.checkErrorPacket(
	at com.mysql.jdbc.MysqlIO.sendCommand(
	at com.mysql.jdbc.MysqlIO.sqlQueryDirect(
	at com.mysql.jdbc.MysqlIO.sqlQuery(
	at com.mysql.jdbc.Connection.execSQL(
	at com.mysql.jdbc.Connection.execSQL(
	at com.mysql.jdbc.Statement.executeUpdate(
	at com.mysql.jdbc.Statement.executeUpdate(
	at com.partnersoft.v3x.apps.Staker.server.JobLibrary.updateJobCheckedOutFlag(
	at com.partnersoft.v3x.apps.Staker.server.JobLibrary.releaseJob(
	at com.partnersoft.v3x.apps.Staker.server.SocketJobLibrarian$ReleaseJobRequest.processRequest(
	at com.partnersoft.v3x.apps.Staker.server.JobLibrary.processCustomRequest(
	at com.partnersoft.v3x.apps.Staker.server.SocketServer$
	at com.partnersoft.v3x.apps.Staker.server.ExchangeSocket$
	at Source)


 INFO 2008-10-20 07:25:11,903 [Thread-25] ($YonderFulfillment)
    Beginning Yonder fulfillment.
 INFO 2008-10-20 07:25:11,903 [Thread-25] ($YonderFulfillment)
    Connecting to client at /
 INFO 2008-10-20 07:25:11,981 [Thread-25] ($YonderFulfillment)
 INFO 2008-10-20 07:25:12,059 [Thread-25] ($YonderFulfillment)
    Closing connection to /
 INFO 2008-10-20 07:25:12,059 [Thread-25] ($YonderFulfillment)
    Yonder fulfillment complete.

Personal tools