My Oracle Support Banner

Geocoder JDBC Error java.sql.SQLException: Connection Has Already Been Closed (Doc ID 1457361.1)

Last updated on FEBRUARY 03, 2022

Applies to:

Oracle Spatial and Graph - Version to
Information in this document applies to any platform.Symptoms

Geocoder request getting error java.sql.SQLException: Connection has already been closed.

[oracle.lbs.geocoder.server.Settlement, Wed Mar 21 10:15:38 CET 2012, ERROR] java.sql.SQLException: Connection has already been closed.
at weblogic.jdbc.wrapper.PoolConnection.checkConnection(
at weblogic.jdbc.wrapper.Connection.preInvocationHandler(
at weblogic.jdbc.wrapper.Connection.getMetaData(
at oracle.spatial.geocoder.server.GeocoderConfig.getConnection(
at oracle.spatial.geocoder.server.Settlement.resolveInDB(
at oracle.spatial.geocoder.server.Settlement.resolve(
at oracle.spatial.geocoder.server.GenericGeocoder.resolveCity(
at oracle.spatial.geocoder.server.GenericGeocoder.geocodeLoc(
at oracle.spatial.geocoder.server.GenericGeocoder.geocode(
at oracle.spatial.geocoder.server.GeocoderImpl.geocode(
at oracle.spatial.geocoder.GCServer.process(
at oracle.spatial.geocoder.GCServer.doPost(
at javax.servlet.http.HttpServlet.service(
at javax.servlet.http.HttpServlet.service(
at weblogic.servlet.internal.StubSecurityHelper$
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(
at weblogic.servlet.internal.ServletStubImpl.execute(
at weblogic.servlet.internal.ServletStubImpl.execute(
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(
at weblogic.servlet.internal.WebAppServletContext$
at weblogic.servlet.internal.WebAppServletContext.securedExecute(
at weblogic.servlet.internal.WebAppServletContext.execute(

[oracle.spatial.geocoder.GCServer, Wed Mar 21 10:15:38 CET 2012, DEBUG]

1. From the "Geocoder XML sample requests" page (http://host:port/geocoder/xmlreq.html) make the following reverse geocoding request (second form):

  longitude="0" latitude="0" >

2.After a while, longer than usual, the response is:
Message:Error in ReverseGeocoder
Nested exception is:
java.sql.SQLRecoverableException: No hay más datos para leer del socket

3. And then any other request to the reverse geocoder, even those that were working before the error, now always return the same error.

4. Then I tested the connection pool (named GeocoderDS-nonXA1-PROD, the only pool included in multi data source GeocoderMultiDS-nonXA-PROD, the one configured in geocoder) from the WLS admin console and it reported also an error.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.