My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 215: "Communications link failure" exception causes merge failure
  Back to list
Status:  WontFix
Owner:  code-rev...@gtempaccount.com
Closed:  Sep 2009


Sign in to add a comment
 
Reported by code-rev...@gtempaccount.com, Sep 24, 2009
Reported by Sam Quigley <quigley@emerose.com> on Thu Jun 04 16:29:35 PDT 2009
Source: JIRA GERRIT-215
Affected Version: 2.0.12
Environment: MySQL JDBC driver / server

We've gotten the attached exception a couple of times now; when the exception
occurs, changesets end up getting stuck in the "Submitted, Merge pending"
state.  Other DB-related activity (commending on changes in other projects,
eg) works fine, however.  Restarting Jetty causes the merge to go through.

-sq
2009_06_04.stderrout.log.231609152
9.7 KB   View   Download
2009_06_01.stderrout.log.182758304
9.8 KB   View   Download
Sep 24, 2009
#1 code-rev...@gtempaccount.com
Comment by Shawn Pearce <sop@google.com> on Thu Jun 04 16:32:15 PDT 2009

Doesn't seem to be anything I can do about this.  Your MySQL server and JDBC
driver have somehow stopped talking to each other, resulting in Gerrit being
unable to use the database.

Maybe disable the c3p0 connection pool might help, so we always use a fresh
database connection, rather than one that is potentially stale and been killed
by the server?  MySQL opens connections pretty fast, faster than PostgreSQL
does.
Sep 24, 2009
#2 code-rev...@gtempaccount.com
Comment by Shawn Pearce <sop@google.com> on Fri Jun 12 16:25:45 PDT 2009

As I said, this looks like an error in MySQL or the connection pool and isn't
something we can fix directly in Gerrit.
Sep 24, 2009
#3 code-rev...@gtempaccount.com
Update by Shawn Pearce <sop@google.com> on Fri Jun 12 16:25:45 PDT 2009
Status: WontFix
Sign in to add a comment

Powered by Google Project Hosting