Why additional daemon is running with atlassian-cli-10.1.0 v compared to atlassian-cli-9.3.0 v ?

[Abdul Bazai]

command used: ps -ef | grep jira

(1) why port 7789 is required?
(2) it restarts even after force Kill

What is the cause?

What is the purpose of this PID 10452?

How can we stop this PID from running?

jiraadm   10452      1  0 Apr16 ?        00:03:25 /opt/app/workload/jiraCLI/atlassian-cli-10.1.0/jre/bin/java -Dorg.slf4j.simpleLogger.defaultLogLevel=info -Dorg.slf4j.simpleLogger.showDateTime=true -Dorg.slf4j.simpleLogger.dateTimeFormat=yyyy-MM-dd HH:mm:ss.SSSZ -jar /opt/app/workload/jiraCLI/acli/lib/acli-10.1.0.jar web -a startServer --port 7789

[Eloy Lafuente _stronk7_]

As commented by @Charles Pikscher first, you've to add this to your "acli-service.properties" file:

# This is disabled by default, so is not needed, but
actionLogging = false

# This is enabled by default, let's disable it
shareAnalytics = false

And with both disabled those "--port 7789" processes won't happen anymore.

Note that, if you're using the distribution downloads directly (jar) and you don't know where to put that file, you can use (it took some time to me to discover it):

java ... -DACLI_SERVICE_CONFIG=/path/to/acli-service.properties -jar /path/to/acli-x.y.z.jar

With that, those processes won't spawn anymore (it worked here).

In any case, unless I'm missing something, there is a real bug with those processes. For every Jira CLI invocation, we get one of those processes running FOREVER, in just 24h we got all our CI workers running out of processes / open descriptors because of this.

That should be fixed ASAP (if it has not, we aren't running the latest - at the time of writing this - 10.6.0 version, but a slightly older one in the 10.x series).

Hope it helps, ciao :-)

[Charles Pikscher]

If it helps anyone else, in my case, it seemed to be happening (processes that never exited) because I was running off a shared folder on the network, and the tool didn't have write permission to the folder, so it couldn't create a pid lock file or logs.

[Charles Pikscher]

You can disable it by adding "shareAnalytics = false" to your acli-service.properties file, see:

https://appfire.atlassian.net/wiki/spaces/ACLI/pages/60556783/Action+logging+and+anonymous+analytics#Configuring-logging-and-anonymous-analytics

[Charles Pikscher]

Anyone have a fix?  I upgraded to 10.5.0, that didn't help.  I'm seeing one of these processes spawn each time I use the ACLI on some desktops, and they aren't going away.