This behavior has to do with the implementation of the JDBC driver of the database (such as H2).  There is nothing that Aqua Data Studio can do about the drivers file locking mechanism.  Server based databases provide concurrency through semaphores which allow multi-use, while some embedded databases just use file locking.  The only way an embedded database would allow concurrency is if they used semaphores to synchronize access to the same file.  This is possible within one JVM, but it would be up to the driver to implement this.  If the driver limits one connection per database, then the driver is imposing the limit.  I don't believe that Apache Derby has this limit on their Embedded Database.

Also note that the H2 driver error is suggesting to run in Server Mode.

I understand the issue along with what the driver is doing-- what I'm asking for is that Data Studio provide some type of option in Server Properties to indicate this Server is restricted to a single connection and if set, maybe to share the connection between components such as the Server/Schema browser and Query Analyzers (obviously understanding that there would be restrictions such as possibly not being able to execute queries in two Query Analyzers, etc)-- or if it can't be shared, to at least complain that isn't a single connection server?

I also realize that H2 is suggesting running in Server Mode but the benefits of being able to quickly "spin up a database" directly within Data Studio for rapid prototyping, or ad-hoc data processing and analytics is what I'm attempting to do. I do realize that H2 has their "automatic mixed mode" but addressing this inside of Data Studio itself provides the ability to use other embedded database such as Hsqldb in addition to the concern that the first connection, when closed, may bring down other connections.

Thanks you for the consideration!