jenkinsci / jenkinsci/gerrit-trigger-plugin

[JENKINS-68256] trigger.GerritServer#doWakeup: Could not start connection

Open
#950 0 comments 0 reactions 0 assignees View on GitHub
component:gerrit-trigger-plugin imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
226
Forks
289
PR merge metrics
No merged PRs in 30d

Description

Hi,

 

I have an issue that whenever our gerrit instance restarts, jenkins loses connection (nothing wrong about it) and cannot reconnect once the gerrit is up again. 

From logs there is an info with:

trigger.GerritServer#doWakeup: Could not start connection

and then it keeps repeating that it cannot connect to the instance. When I test the connection from settings it is successful.

I've tried to restart the connection from GUI in `Manage Jenkins` -> `Gerrit Trigger` but it didn't do anything - there are no indications in logs that it re-attempted the connection to gerrit.

The only thing that works is restarting the jenkins but it is not preferable. 

 

Environments:

Jenkins version: Jenkins 2.336

Gerrit Trigger version: 2.35.2

 

If there is anything more that you might need please let me know and I will try to provide additional info.

---
Originally reported by koool, imported from: trigger.GerritServer#doWakeup: Could not start connection


  • assignee: rsandell
  • status: Open
  • priority: Minor
  • component(s): gerrit-trigger-plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 1
  • imported: 2025-12-07

Raw content of original issue

Hi,

 

I have an issue that whenever our gerrit instance restarts, jenkins loses connection (nothing wrong about it) and cannot reconnect once the gerrit is up again. 

From logs there is an info with:



trigger.GerritServer#doWakeup: Could not start connection


and then it keeps repeating that it cannot connect to the instance. When I test the connection from settings it is successful.

I've tried to restart the connection from GUI in `Manage Jenkins` -> `Gerrit Trigger` but it didn't do anything - there are no indications in logs that it re-attempted the connection to gerrit.

The only thing that works is restarting the jenkins but it is not preferable. 

 

Environments:

Jenkins version: Jenkins 2.336

Gerrit Trigger version: 2.35.2

 

If there is anything more that you might need please let me know and I will try to provide additional info.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.