We have installed an OMERO server for use in our imaging facility (Oxford biochemistry / Micron advanced microscopy unit). The server is deployed on the department's hierarchical storage system, which means that data not accessed for >60 days remain only on tape. Obviously this means that access times for such archived data are slower than normal hard disk access - which is fine - the problem is, that the OMERO server seems to wait! Not only is the offending user's session frozen while OMERO waits for access to the file, but so are all other users' sessions, and nobody else can log in to the server! Can't some sort of multithreading solve this problem? (have we failed to set some flag properly during the install?) These sort of freezes become a very serious usability issue when the server is relied on by more than a handful of users - isn't there a way to ensure that no one user can freeze up the whole server?
Cheers,
Graeme