>From the documentation... In exclusive mode, new connections are rejected, and operations by other > connections are paused until the exclusive mode is disabled. When using the > value 1, existing connections stay open. >
This is exactly the functionality I was looking for, however, It does not seem to work correctly for me. Is there something I am missing? My other connection hangs for a few seconds and then closes with a "Connection is broken" exception. error: org.h2.jdbc.JdbcSQLException: "Connection is broken: > "java.net.ConnectException: > Connection refused: connect: 172.16.1.64:9090" [90067-179]" > caused by java.net.ConnectException: "Connection refused: connect" > I suspect I am using this feature it incorrectly. My goal - essentially lock-out/pause other connections while I drop and re-build my indexes. For a single connection this is easily accomplished with synchronization. However, If a remote connection is established at the time I would prefer to pause it during this reconstruction. Any suggestions? version: 1.4.179 url: "jdbc:h2:../data/audit/audit;AUTOCOMMIT=ON;AUTO_RECONNECT=TRUE;MVCC=TRUE;AUTO_SERVER=TRUE;AUTO_SERVER_PORT=9090" -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
