[Geoserver-users] SQL 2008 1.7.2

jharpster · January 30, 2009, 11:16pm

Anybody have any luck connecting version 1.7.2 to SQL 2008 yet? We are unable to get a connection. Any tips are appreciated.

Cheers,
-jubal harpster

Justin_Deoliveira · February 2, 2009, 2:48pm

Hey Jubal,

I verified that it worked for 1.7.2. Is the extension showing up when you go add a new datastore? Or is it showing up and you are getting a connection error?

-Justin

Jubal.Harpster@anonymised.com wrote:

Anybody have any luck connecting version 1.7.2 to SQL 2008 yet? We are unable to get a connection. Any tips are appreciated.
Cheers,
-jubal harpster

------------------------------------------------------------------------

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword

------------------------------------------------------------------------

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

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

jharpster · February 2, 2009, 5:49pm

Hi Justin.

We are seeing the SQL 2008 datastore. But the logs are consistently
returning a connection error. The installation is very vanilla. Just a named
instance of SQL 2008 running on a VM.

Caused by: org.apache.commons.dbcp.SQLNestedException: Cannot create
PoolableConnectionFactory (Login failed for user 'oheight'.)
  at
org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1225)
  at
org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
  at
org.geotools.jdbc.JDBCDataStore.createConnection(JDBCDataStore.java:1134)
  ... 60 more
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for
user 'oheight'.
  at
com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown
Source)
  at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(Unknown Source)
  at com.microsoft.sqlserver.jdbc.TDSParser.parse(Unknown Source)
  at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(Unknown
Source)
  at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(Unknown Source)
  at com.microsoft.sqlserver.jdbc.SQLServerConnection.access$000(Unknown
Source)
  at
com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(Unknown
Source)
  at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
  at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown
Source)
  at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(Unknown
Source)
  at
com.microsoft.sqlserver.jdbc.SQLServerConnection.loginWithoutFailover(Unknown
Source)
  at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Source)
  at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)

Thanks.

Justin Deoliveira-6 wrote:

Hey Jubal,

I verified that it worked for 1.7.2. Is the extension showing up when
you go add a new datastore? Or is it showing up and you are getting a
connection error?

-Justin

Jubal.Harpster@anonymised.com wrote:

Anybody have any luck connecting version 1.7.2 to SQL 2008 yet? We are
unable to get a connection. Any tips are appreciated.

Cheers,
-jubal harpster

------------------------------------------------------------------------

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword

------------------------------------------------------------------------

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

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
View this message in context: http://www.nabble.com/SQL-2008-1.7.2-tp21790873p21794571.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

Apollolm · February 3, 2009, 9:31pm

OK...so we had a problem because we were using SQL Developer Edition.
Removed and installed Enterprise. Was able to get further. Used port 1466
(the TCP port SQL Said it was listening on) in the connection string in
GeoServer DataStore interface. FeatureType List was still not populating
with tables. Had to make SQL Login default Database point to our spatial
database. Finally was able to get list of tables showing up.

Now am getting error when trying to use OpenLayers preview of feature type
created on SQL 08 table with spatial column - Geoserver
java.lang.OutOfMemoryError: Java heap space Java heap space

Here's the pertinent portion from the log:

2009-02-03 13:22:00,558 ERROR [geoserver.ows] -
java.lang.OutOfMemoryError: Java heap space
2009-02-03 13:22:01,042 ERROR [geoserver.ows] -
java.lang.OutOfMemoryError: Java heap space
2009-02-03 13:22:01,042 WARN [geotools.jdb] - There is code leaving feature
readers/iterators open, this is leaking statements and connections!
2009-02-03 13:22:03,323 WARN [geotools.jdb] - There is code leaving feature
readers/iterators open, this is leaking statements and connections!
2009-02-03 13:22:04,073 ERROR [geoserver.ows] -
java.lang.OutOfMemoryError: Java heap space
2009-02-03 13:22:04,636 ERROR [[/geoserver].[dispatcher]] -
Servlet.service() for servlet dispatcher threw exception
java.lang.OutOfMemoryError: Java heap space
2009-02-03 13:22:05,636 ERROR [[/geoserver].[jsp]] - Servlet.service() for
servlet jsp threw exception
java.lang.ClassCastException: java.lang.OutOfMemoryError
  at
org.apache.jsp.WEB_002dINF.pages.errors.Exception_jsp._jspService(Exception_jsp.java:76)
  at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
  at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
  at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
  at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
  at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
  at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
  at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:691)
  at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:471)
  at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:403)
  at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
  at
org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:364)
  at
org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:213)
  at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:135)
  at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
  at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
  at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
  at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874)
  at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
  at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
  at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
  at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
  at java.lang.Thread.run(Unknown Source)
2009-02-03 13:22:09,714 ERROR [geotools.rendering] - Java heap space
java.lang.OutOfMemoryError: Java heap space
2009-02-03 13:22:10,214 WARN [geotools.jdb] - There is code leaving feature
readers/iterators open, this is leaking statements and connections!
2009-02-03 13:22:11,683 ERROR [geotools.rendering] - Java heap space
java.lang.OutOfMemoryError: Java heap space
2009-02-03 13:22:11,933 WARN [geotools.jdb] - There is code leaving feature
readers/iterators open, this is leaking statements and connections!
2009-02-03 13:22:18,449 ERROR [geotools.rendering] - Java heap space
java.lang.OutOfMemoryError: Java heap space
2009-02-03 13:22:18,949 ERROR [geotools.rendering] - Java heap space
java.lang.OutOfMemoryError: Java heap space
2009-02-03 13:22:19,699 WARN [geotools.jdb] - There is code leaving feature
readers/iterators open, this is leaking statements and connections!
2009-02-03 13:22:20,449 WARN [geotools.jdb] - There is code leaving feature
readers/iterators open, this is leaking statements and connections!

jharpster wrote:

Anybody have any luck connecting version 1.7.2 to SQL 2008 yet? We are
unable to get a connection. Any tips are appreciated.

Cheers,
-jubal harpster

--
View this message in context: http://www.nabble.com/SQL-2008-1.7.2-tp21790873p21819403.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

Justin_Deoliveira · February 10, 2009, 3:12pm

Apologies for the late reply Ryan. This message was stuck in the approval queue

Andrea: any thoughts? Seems OOM errors emitting from the render... although i guess they could be coming from anywhere.

Apollolm wrote:

OK...so we had a problem because we were using SQL Developer Edition.
Removed and installed Enterprise. Was able to get further. Used port 1466
(the TCP port SQL Said it was listening on) in the connection string in
GeoServer DataStore interface. FeatureType List was still not populating
with tables. Had to make SQL Login default Database point to our spatial
database. Finally was able to get list of tables showing up.

Now am getting error when trying to use OpenLayers preview of feature type
created on SQL 08 table with spatial column - Geoserver
java.lang.OutOfMemoryError: Java heap space Java heap space

Here's the pertinent portion from the log:

2009-02-03 13:22:00,558 ERROR [geoserver.ows] - java.lang.OutOfMemoryError: Java heap space
2009-02-03 13:22:01,042 ERROR [geoserver.ows] - java.lang.OutOfMemoryError: Java heap space
2009-02-03 13:22:01,042 WARN [geotools.jdb] - There is code leaving feature
readers/iterators open, this is leaking statements and connections!
2009-02-03 13:22:03,323 WARN [geotools.jdb] - There is code leaving feature
readers/iterators open, this is leaking statements and connections!
2009-02-03 13:22:04,073 ERROR [geoserver.ows] - java.lang.OutOfMemoryError: Java heap space
2009-02-03 13:22:04,636 ERROR [[/geoserver].[dispatcher]] -
Servlet.service() for servlet dispatcher threw exception
java.lang.OutOfMemoryError: Java heap space
2009-02-03 13:22:05,636 ERROR [[/geoserver].[jsp]] - Servlet.service() for
servlet jsp threw exception
java.lang.ClassCastException: java.lang.OutOfMemoryError
  at
org.apache.jsp.WEB_002dINF.pages.errors.Exception_jsp._jspService(Exception_jsp.java:76)
  at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
  at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
  at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
  at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
  at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
  at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
  at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:691)
  at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:471)
  at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:403)
  at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
  at
org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:364)
  at
org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:213)
  at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:135)
  at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
  at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
  at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
  at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874)
  at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
  at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
  at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
  at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
  at java.lang.Thread.run(Unknown Source)
2009-02-03 13:22:09,714 ERROR [geotools.rendering] - Java heap space
java.lang.OutOfMemoryError: Java heap space
2009-02-03 13:22:10,214 WARN [geotools.jdb] - There is code leaving feature
readers/iterators open, this is leaking statements and connections!
2009-02-03 13:22:11,683 ERROR [geotools.rendering] - Java heap space
java.lang.OutOfMemoryError: Java heap space
2009-02-03 13:22:11,933 WARN [geotools.jdb] - There is code leaving feature
readers/iterators open, this is leaking statements and connections!
2009-02-03 13:22:18,449 ERROR [geotools.rendering] - Java heap space
java.lang.OutOfMemoryError: Java heap space
2009-02-03 13:22:18,949 ERROR [geotools.rendering] - Java heap space
java.lang.OutOfMemoryError: Java heap space
2009-02-03 13:22:19,699 WARN [geotools.jdb] - There is code leaving feature
readers/iterators open, this is leaking statements and connections!
2009-02-03 13:22:20,449 WARN [geotools.jdb] - There is code leaving feature
readers/iterators open, this is leaking statements and connections!

jharpster wrote:

Anybody have any luck connecting version 1.7.2 to SQL 2008 yet? We are
unable to get a connection. Any tips are appreciated.

Cheers,
-jubal harpster

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

Andrea_Aime3 · February 10, 2009, 3:30pm

Justin Deoliveira ha scritto:

Apologies for the late reply Ryan. This message was stuck in the approval queue

Andrea: any thoughts? Seems OOM errors emitting from the render... although i guess they could be coming from anywhere.

Yeah, with an OOM you get information just about the drop that
make the vase overflow, not about what actually filled the vase
before it.

I suggest Ryan adds the following flag to the GeoServer startup
parameters:

-XX:+HeapDumpOnOutOfMemoryError

This will trigger the generation of a dump file in the
java_<pid>_<date>_<time>_heapDump.hprof.txt form, inside the
directory in which the jvm is running.

Ryan, once you have that file, zip it, upload it somewhere
we can grab it, and let us know how to get it so that we
can check with a memory dump analyzer what filled your heap.

Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.