Certain area's of JAS may need mutex to ensure correct functioning. Caching being one example (although overwrites don't matter too much) however there may be more areas where this applies...
Loading the initial configuration (when setting up the session) take too long. This should be cached (automagically detecting the cache method, i.e. mem, module, file) on a project by project basis and any subsequent config loads should use the cached version.
Report issues
We're currently not allowing issue reporting directly via ITS. Please use the feedback form to submit your issues.