Can I keep the long running process in Jira Data Center Plugin

[Darshan Varasani]

We are working on developing a Jira Data Center Plugin where we are fetching the data from the third-party platform using REST API and based on the response we are creating the Jira ticket.

We have one Streaming rest API of the third-party platform which requires opening one HTTP connection and the platform would keep sending the data whenever new data is available. Can we use this API in our plugin to create a long-running process that would open one HTTP connection to keep listening to the streaming data being sent by the API and create the Jira tickets?

If we add implementation in our plugin to use this API by the long-running process which ideally should never end, will there be any problems during the Data Center APp approval process when we list the App in the Atlassian marketplace?

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

Yes, your app may fail validation because it creates a never-ending thread.  Atlassian might not catch it in the validation, but your buyers certainly will.

You need to rethink your app - a never-ending thread is poor design as it opens you up to memory leaks and it's not going to tolerate some forms of errors unless you do a whole pile of exception coding.  Does your code have monitoring of the thread in the app to make sure it is behaving, and kill and restart it when it fails?