See JRA-25034. This problem only occurs on 4.4.1, similar testing on 4.4.0 and other jira levels has not experienced this problem.

The problem occurs running JIRA CLI automated tests which:

1. Run a large number of SOAP and rest requests
2. Includes issue creates and issue clones
   • Some base clone operations JIRA Clone Plus Plugin see related https://studio.plugins.atlassian.com/browse/JCPP-36
   • Problems still occur after fix applied for that issue
3. Concurrent requests are made (and the problem seems to occur with higher levels of concurrency)

Numerous recreates have been attempted to narrow down the problem. Symptoms include:

1. Freezes creating or cloning issues (UI or via remote request)
2. Socket timeout on remote request

   Remote error: ; nested exception is: 
       [error] 	java.net.SocketTimeoutException: Read timed out
   

3. A project that cannot be deleted (completely) - delete says not found, create says already exists
   • this might be a side affect of the freezes and subsequent stopping or canceling
4. Restore from back freezes
5. Logs contain numerous entries like

   Existing issue found for key ZJIRACLI-29. Incrementing key.
   

Once the problem occurs, it is likely that jira needs to be restored from backup after deleting the DB.

Attached a log after automation and UI create issue freezes.

Recreate

You will need a JCLI gint test environment similar to what Trevor did in https://jira.atlassian.com/browse/JRA-25034?focusedCommentId=264065&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-264065 - use the latest snapshots

1. New 4.4.1 install
2. On install screen, import https://bitbucket.org/bob_swift/jira-cli/downloads/jira-cli-test-jira-4.2.4-export.zip and specify license
3. Run the test
   • -DmaxParallel=8 is the default for concurrent actions, if this is set to 1, it seems to work
4. Freeze and/or socket timeout
   • attached catalina.out after the test started freeze