Wrong webhook communication

3digits - Desarrollo June 4, 2019

Dear support team,

We are writing you with the SEN of a Pre-production JIRA environment both because our client's SEN license is currently in a bidding process due to a renovation over the production environment and because it's from a configuration we are porting from the pre-production environment to the production environment.

For quick reference I will reduce the terms 'Production Environment' and the 'Pre-production Environment' to PRO and PRE respectively.

We are trying to port a webhook from PRE that works fine in its JIRA instance, but it is not functioning on PRO.

We believe the issue is the commWebhook_problem.pngunication with the webhook it is wrong. 

We are using Apache TomEE and a custom Java application we are reffering to as INJIRO to run a remote Debug of the process.

I'm attaching a screencap of the working result from PRE's Debug.

 

The Webhook in PRE triggers the method createIssue() from Webhook controller whenever it arrives to the status "Enviado a Rosmiman" and everything proceeds as planned.

However in PRO:

2019-05-17 09:34:13,363 httpclient-callbacks:thread-230 WARN anonymous     [c.a.webhooks.plugin.PublishTaskFactoryImpl$PublishTaskImpl] Server error - 503 when posting to web hook at 'http://localhost:9080/injiro-rest-api/v1/webhook/creacion/39594'

It generates an error 503. We think this is caused as it seems to be trying to create the issue as 'anonymous' instead of 'Administrador' (our Jira administrator User)?

What could cause this kind of error? It works just fine in PRE.

 

We await your answer.

Thank you very much

-Huberto.         hmartin@3digits.es

1 answer

1 accepted

0 votes
Answer accepted
JP _AC Bielefeld Leader_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 4, 2019

Hi Huberto,

in this case you're asking the Atlassian Community, users like you & not the Atlassian support team.

You might want to contact Atlassian support directly:

https://support.atlassian.com/contact/#/

Best

JP

3digits - Desarrollo June 5, 2019

Oh thank you, sorry for the slip-up

Suggest an answer

Log in or Sign up to answer