We are using Jenkins 2.332.3 and we integrated jenkins with jira. We use webhook in Jira to connect Jenkins and also use Jenkins JIRA TriggerVersion1.0.1.

This was working well since last week. However, We notice all of sudden the Jira change in status has stopped trigger the job and as workaround we have to restart jenkins service everytime this issue occurs. Is there any solution for this.

Both Jira & Jenkins are installed in AWS ec2 and in same subnet/network. When we check the logs in AWS we see REJECT from jenkins server in n/w logs. 

We suspect this happens on the jenkins side as the event triggers when the jenkins service is restarted.

Below or few stats:

Memory:

[root@ip-10-13-12-106 ~]# free -h
              total        used        free      shared  buff/cache   available
Mem:           3.8G        2.2G        376M        3.8M        1.2G        1.3G
Swap:            0B          0B          0B
[root@ip-10-13-12-106 ~]#