[Geoserver-users] Geoserver reports "org.h2.jdbc.JdbcSQLException: Database is already closed"

GeoServer GeoServer User
1

Hi all,
We are using:
GeoServer-2.2.5
Java 1.8

We suddenly could not connect to the Geoserver REST API from our Java code
anymore, Spring gave us this error:
org.springframework.web.client.ResourceAccessException: I/O error:
Connection refused; nested exception is java.net.ConnectException:
Connection refused

And then looking at the Geoserver log, we saw:
2015-10-01 15:36:57,598 ERROR [jdbc.JDBCMBWrapper] - Couldn't obtain JDBC
Connection to perform database shut down
org.h2.jdbc.JdbcSQLException: Database is already closed (to disable
automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db
URL) [90121-119]
                at org.h2.message.Message.getSQLException(Message.java:106)
                at org.h2.message.Message.getSQLException(Message.java:117)
                at org.h2.message.Message.getSQLException(Message.java:76)
                at org.h2.message.Message.getSQLException(Message.java:152)
                at
org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1328)
                at
org.h2.jdbcx.JdbcXAConnection$PooledJdbcConnection.checkClosed(JdbcXAConnection.java:505)
                at
org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1303)
                at
org.h2.jdbc.JdbcConnection.setAutoCommit(JdbcConnection.java:354)
                at
org.geowebcache.storage.metastore.jdbc.JDBCMBWrapper.getConnection(JDBCMBWrapper.java:183)
                at
org.geowebcache.storage.metastore.jdbc.JDBCMBWrapper.destroy(JDBCMBWrapper.java:618)
                at
org.geowebcache.storage.metastore.jdbc.JDBCMetaBackend.destroy(JDBCMetaBackend.java:265)
                at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
                at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
                at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
                at java.lang.reflect.Method.invoke(Method.java:606)
                at
org.springframework.beans.factory.support.DisposableBeanAdapter.invokeCustomDestroyMethod(DisposableBeanAdapter.java:208)
                at
org.springframework.beans.factory.support.DisposableBeanAdapter.destroy(DisposableBeanAdapter.java:165)
                at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroyBean(DefaultSingletonBeanRegistry.java:456)
                at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroySingleton(DefaultSingletonBeanRegistry.java:434)
                at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroySingletons(DefaultSingletonBeanRegistry.java:407)
                at
org.springframework.context.support.AbstractApplicationContext.destroyBeans(AbstractApplicationContext.java:854)
                at
org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:832)
                at
org.springframework.context.support.AbstractApplicationContext.close(AbstractApplicationContext.java:795)
                at
org.springframework.web.context.ContextLoader.closeWebApplicationContext(ContextLoader.java:361)
                at
org.springframework.web.context.ContextLoaderListener.contextDestroyed(ContextLoaderListener.java:70)
                at
org.mortbay.jetty.handler.ContextHandler.doStop(ContextHandler.java:574)
                at
org.mortbay.jetty.webapp.WebAppContext.doStop(WebAppContext.java:485)
                at
org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:64)
                at
org.mortbay.jetty.handler.HandlerCollection.doStop(HandlerCollection.java:169)
                at
org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:64)
                at
org.mortbay.jetty.handler.HandlerCollection.doStop(HandlerCollection.java:169)
                at
org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:64)
                at
org.mortbay.jetty.handler.HandlerWrapper.doStop(HandlerWrapper.java:142)
                at org.mortbay.jetty.Server.doStop(Server.java:281)
                at
org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:64)
                at
org.mortbay.jetty.Server$ShutdownHookThread.run(Server.java:559)

I tried to search online but wasn't able to find info on what might have
caused the database issue. I'm wondering if you have any hints for me?

Thanks
eting

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Geoserver-reports-org-h2-jdbc-JdbcSQLException-Database-is-already-closed-tp5227479.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

2

Hi,
it’s really hard to help since your GeoServer version is quite old, it’s a 2.2.x, the currently
supported versions are 2.7.x and 2.8.x (and a lot has changed in the codebase in the meantime).

I also think the two errors you’re seeing are not directly related, the first seems a runtime
error, the second is a shutdown error instead.

I know at some point the EPSG database happened to close itself due to lack of usage
(when all the recently used CRSs were cached) and a request with a new CRS ended
up triggering an error, but I don’t exactly remember when that was fixed.

But, as said, the two errors seem to be unrelated.

You might want to search in the ml archives from two years ago, there might be some clue.

Cheers
Andrea

···

On Fri, Oct 2, 2015 at 3:39 AM, eting123 <eting@anonymised.com> wrote:

Hi all,
We are using:
GeoServer-2.2.5
Java 1.8

We suddenly could not connect to the Geoserver REST API from our Java code
anymore, Spring gave us this error:
org.springframework.web.client.ResourceAccessException: I/O error:
Connection refused; nested exception is java.net.ConnectException:
Connection refused

And then looking at the Geoserver log, we saw:
2015-10-01 15:36:57,598 ERROR [jdbc.JDBCMBWrapper] - Couldn’t obtain JDBC
Connection to perform database shut down
org.h2.jdbc.JdbcSQLException: Database is already closed (to disable
automatic closing at VM shutdown, add “;DB_CLOSE_ON_EXIT=FALSE” to the db
URL) [90121-119]
at org.h2.message.Message.getSQLException(Message.java:106)
at org.h2.message.Message.getSQLException(Message.java:117)
at org.h2.message.Message.getSQLException(Message.java:76)
at org.h2.message.Message.getSQLException(Message.java:152)
at
org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1328)
at
org.h2.jdbcx.JdbcXAConnection$PooledJdbcConnection.checkClosed(JdbcXAConnection.java:505)
at
org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1303)
at
org.h2.jdbc.JdbcConnection.setAutoCommit(JdbcConnection.java:354)
at
org.geowebcache.storage.metastore.jdbc.JDBCMBWrapper.getConnection(JDBCMBWrapper.java:183)
at
org.geowebcache.storage.metastore.jdbc.JDBCMBWrapper.destroy(JDBCMBWrapper.java:618)
at
org.geowebcache.storage.metastore.jdbc.JDBCMetaBackend.destroy(JDBCMetaBackend.java:265)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.springframework.beans.factory.support.DisposableBeanAdapter.invokeCustomDestroyMethod(DisposableBeanAdapter.java:208)
at
org.springframework.beans.factory.support.DisposableBeanAdapter.destroy(DisposableBeanAdapter.java:165)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroyBean(DefaultSingletonBeanRegistry.java:456)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroySingleton(DefaultSingletonBeanRegistry.java:434)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.destroySingletons(DefaultSingletonBeanRegistry.java:407)
at
org.springframework.context.support.AbstractApplicationContext.destroyBeans(AbstractApplicationContext.java:854)
at
org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:832)
at
org.springframework.context.support.AbstractApplicationContext.close(AbstractApplicationContext.java:795)
at
org.springframework.web.context.ContextLoader.closeWebApplicationContext(ContextLoader.java:361)
at
org.springframework.web.context.ContextLoaderListener.contextDestroyed(ContextLoaderListener.java:70)
at
org.mortbay.jetty.handler.ContextHandler.doStop(ContextHandler.java:574)
at
org.mortbay.jetty.webapp.WebAppContext.doStop(WebAppContext.java:485)
at
org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:64)
at
org.mortbay.jetty.handler.HandlerCollection.doStop(HandlerCollection.java:169)
at
org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:64)
at
org.mortbay.jetty.handler.HandlerCollection.doStop(HandlerCollection.java:169)
at
org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:64)
at
org.mortbay.jetty.handler.HandlerWrapper.doStop(HandlerWrapper.java:142)
at org.mortbay.jetty.Server.doStop(Server.java:281)
at
org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:64)
at
org.mortbay.jetty.Server$ShutdownHookThread.run(Server.java:559)

I tried to search online but wasn’t able to find info on what might have
caused the database issue. I’m wondering if you have any hints for me?

Thanks
eting

–
View this message in context: http://osgeo-org.1560.x6.nabble.com/Geoserver-reports-org-h2-jdbc-JdbcSQLException-Database-is-already-closed-tp5227479.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–

==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.