Issue Summary

Timeout parameter in JSON import is not respected.
When importing a large JSON file that is expected to take more than 30 seconds to retrieve (30s is the default timeout), setting the timeout parameter (in millisecond) in the JSON import configuration greater than 30 seconds (e.g. 300000 or 5 minutes) does not do anything. The JSON import configuration UI keeps spinning. If you refresh the UI, then the whole import configuration goes away.
There is no entries recorded in the import log for this behavior.
Tested on JSM version 9.4.3 and 9.4.7

This is reproducible on Data Center: (yes)

Steps to Reproduce

1. Create a JSON import configuration to retrieve a JSON file via URL that is expected to take longer than the 30s default timeout
2. Set the timeout parameter greater than 30s, enough to accommodate the time it takes to download the JSON file

Expected Results

The expected result is that the JSON import configuration would respect the timeout setting and save the import configuration.

Actual Results

The actual result is that the import configuration UI keeps spinning. If you refresh the UI, then the whole import configuration goes away. There is no way to create a JSON import configuration with a timeout greater than 30s. Testing with timeout value less than 30s (e.g 20s) also produce similar result.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available