[Geoserver-users] ArcSDE 9.2 connection issues

GeoServer GeoServer User
1

Howdy,

I’m trying to hook up the latest nightly build of GeoServer 1.6 b3 to ArcSDE 9.2 for SQL Server using the latest available SDE data store from SourceForge. I’m running Tomcat 6.0.14 on Windows XP SP2.

I have placed the necessary files in the GeoServer webapps\geoserver\WEB-INF\lib directory:

  • icu4j_3_2.jar
  • gt2-arcsde.jar
  • jpe92_sdk.jar
  • jsde92_sdk.jar
  • commons-pool-1.3.jar
    When I restart Tomcat I can create a new datastore of type ArcSDE with the usual parameters (5151 port, yadda yadda) and it will let me Submit, Apply, restart Tomcat, and generally act nicely. Unfortunately, every time I try to create a New Featuretype based on an ArcSDE layer it bombs with an Unhandled Exception thrown: class java.lang.NullPointerException message. I can list the layers that I have permission for in sde just fine in the dropdown of available datasources, but clicking Submit on the Create New Feature Type page just fails every single time.

Here’s what the log looks like at failure:

form connection params { port=5151, dbtype=“arcsde”, pool.timeOut=1000, server=“localhost”, instance=“TestData”, pool.maxConnections=2, password=“woolpert”, user=“arcadmin”, pool.minConnections=2}
typeNames : (" TESTDATA.ARCADMIN.ORTHOS", “TESTDATA.ARCADMIN.PARCELS”, “TESTDATA.ARCADMIN.REAL_PROP”, “TESTDATA.ARCADMIN.SMAIN”, “TESTDATA.ARCADMIN.SMANHOLE”, “TESTDATA.ARCADMIN.STRNET”, " TESTDATA.ARCADMIN.ZONING")
log4j:WARN File option not set for appender [geoserverlogfile].
log4j:WARN Are you using FileAppender instead of ConsoleAppender?
18 Oct 17:15:42 INFO [ geoserver.global] - StdOut logging enabled. Log file also output to ‘c:\tomcat6014\webapps\geoserver\data\logs/geoserver.log’
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type ‘DS_giant_polygon:::giant_polygon’ (layer 1/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type ‘DS_poi:::poi’ (layer 2/14)
18 Oct 17:15:43 INFO [ geoserver.global] - Loading feature type ‘DS_poly_landmarks:::poly_landmarks’ (layer 3/14)
18 Oct 17:15:43 INFO [ geoserver.global] - Loading feature type ‘DS_tiger_roads:::tiger_roads’ (layer 4/14)
18 Oct 17:15:43 INFO [geoserver.global ] - Loading feature type ‘sfArchsites:::archsites’ (layer 5/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type ‘sfBugsites:::bugsites’ (layer 6/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type ‘sfRestricted:::restricted’ (layer 7/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type ‘sfRoads:::roads’ (layer 8/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type ‘sfStreams:::streams’ (layer 9/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type ‘states_shapefile:::states’ (layer 10/14)
18 Oct 17:15:43 INFO [ geoserver.global] - Loading feature type ‘tasmania_cities:::tasmania_cities’ (layer 11/14)
18 Oct 17:15:43 INFO [ geoserver.global] - Loading feature type ‘tasmania_roads:::tasmania_roads’ (layer 12/14)
18 Oct 17:15:43 INFO [ geoserver.global] - Loading feature type ‘tasmania_state_boundaries:::tasmania_state_boundaries’ (layer 13/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type ‘tasmania_water_bodies:::tasmania_water_bodies’ (layer 14/14)
log4j:WARN File option not set for appender [geoserverlogfile].
log4j:WARN Are you using FileAppender instead of ConsoleAppender?
18 Oct 17:15:43 INFO [geoserver.global] - StdOut logging enabled. Log file also output to ‘c:\tomcat6014\webapps\geoserver\data\logs/geoserver.log’
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type ‘DS_giant_polygon:::giant_polygon’ (layer 1/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type ‘DS_poi:::poi’ (layer 2/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type ‘DS_poly_landmarks:::poly_landmarks’ (layer 3/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type ‘DS_tiger_roads:::tiger_roads’ (layer 4/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type ‘sfArchsites:::archsites’ (layer 5/14)
18 Oct 17:15:43 INFO [ geoserver.global] - Loading feature type ‘sfBugsites:::bugsites’ (layer 6/14)
18 Oct 17:15:43 INFO [geoserver.global ] - Loading feature type ‘sfRestricted:::restricted’ (layer 7/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type ‘sfRoads:::roads’ (layer 8/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type ‘sfStreams:::streams’ (layer 9/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type ‘states_shapefile:::states’ (layer 10/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type ‘tasmania_cities:::tasmania_cities’ (layer 11/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type ‘tasmania_roads:::tasmania_roads’ (layer 12/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type ‘tasmania_state_boundaries:::tasmania_state_boundaries’ (layer 13/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type ‘tasmania_water_bodies:::tasmania_water_bodies’ (layer 14/14)
18 Oct 17:15:59 WARN [data.arcsde] - Figured Row-ID Column named ‘OBJECTID’ for table TESTDATA.ARCADMIN.PARCELS
18 Oct 17:15:59 WARN [action.RequestProcessor] - Unhandled Exception thrown: class java.lang.NullPointerException

I’m trying to generate support for GeoServer in my consulting company but this is a show stopper.Any ideas?

Cheers,

Dylan

2

The arcsde may have enough information there, but it'd probably be helpful if you upped the logging level (on Config -> Server -> Logging Profile) to GEOTOOLS_DEVELOPER_LOGGING and sent those logs, as they should include the stack trace and point to the developers exactly where the NPE is.

Chris

Dylan Thomas wrote:

Howdy,

I'm trying to hook up the latest nightly build of GeoServer 1.6 b3 to ArcSDE 9.2 for SQL Server using the latest available SDE data store from SourceForge. I'm running Tomcat 6.0.14 on Windows XP SP2.

I have placed the necessary files in the GeoServer webapps\geoserver\WEB-INF\lib directory:

    * icu4j_3_2.jar
    * gt2-arcsde.jar
    * jpe92_sdk.jar
    * jsde92_sdk.jar
    * commons-pool-1.3.jar

When I restart Tomcat I can create a new datastore of type ArcSDE with the usual parameters (5151 port, yadda yadda) and it will let me Submit, Apply, restart Tomcat, and generally act nicely. Unfortunately, every time I try to create a New Featuretype based on an ArcSDE layer it bombs with an Unhandled Exception thrown: class java.lang.NullPointerException message. I can list the layers that I have permission for in sde just fine in the dropdown of available datasources, but clicking Submit on the Create New Feature Type page just fails every single time.

Here's what the log looks like at failure:

form connection params { port=5151, dbtype="arcsde", pool.timeOut=1000, server="localhost", instance="TestData", pool.maxConnections=2, password="woolpert", user="arcadmin", pool.minConnections=2}
typeNames : (" TESTDATA.ARCADMIN.ORTHOS", "TESTDATA.ARCADMIN.PARCELS", "TESTDATA.ARCADMIN.REAL_PROP", "TESTDATA.ARCADMIN.SMAIN", "TESTDATA.ARCADMIN.SMANHOLE", "TESTDATA.ARCADMIN.STRNET", " TESTDATA.ARCADMIN.ZONING")
log4j:WARN File option not set for appender [geoserverlogfile].
log4j:WARN Are you using FileAppender instead of ConsoleAppender?
18 Oct 17:15:42 INFO [ geoserver.global] - StdOut logging enabled. Log file also output to 'c:\tomcat6014\webapps\geoserver\data\logs/geoserver.log'
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type 'DS_giant_polygon:::giant_polygon' (layer 1/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type 'DS_poi:::poi' (layer 2/14)
18 Oct 17:15:43 INFO [ geoserver.global] - Loading feature type 'DS_poly_landmarks:::poly_landmarks' (layer 3/14)
18 Oct 17:15:43 INFO [ geoserver.global] - Loading feature type 'DS_tiger_roads:::tiger_roads' (layer 4/14)
18 Oct 17:15:43 INFO [geoserver.global ] - Loading feature type 'sfArchsites:::archsites' (layer 5/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type 'sfBugsites:::bugsites' (layer 6/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type 'sfRestricted:::restricted' (layer 7/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type 'sfRoads:::roads' (layer 8/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type 'sfStreams:::streams' (layer 9/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type 'states_shapefile:::states' (layer 10/14)
18 Oct 17:15:43 INFO [ geoserver.global] - Loading feature type 'tasmania_cities:::tasmania_cities' (layer 11/14)
18 Oct 17:15:43 INFO [ geoserver.global] - Loading feature type 'tasmania_roads:::tasmania_roads' (layer 12/14)
18 Oct 17:15:43 INFO [ geoserver.global] - Loading feature type 'tasmania_state_boundaries:::tasmania_state_boundaries' (layer 13/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type 'tasmania_water_bodies:::tasmania_water_bodies' (layer 14/14)
log4j:WARN File option not set for appender [geoserverlogfile].
log4j:WARN Are you using FileAppender instead of ConsoleAppender?
18 Oct 17:15:43 INFO [geoserver.global] - StdOut logging enabled. Log file also output to 'c:\tomcat6014\webapps\geoserver\data\logs/geoserver.log'
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type 'DS_giant_polygon:::giant_polygon' (layer 1/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type 'DS_poi:::poi' (layer 2/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type 'DS_poly_landmarks:::poly_landmarks' (layer 3/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type 'DS_tiger_roads:::tiger_roads' (layer 4/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type 'sfArchsites:::archsites' (layer 5/14)
18 Oct 17:15:43 INFO [ geoserver.global] - Loading feature type 'sfBugsites:::bugsites' (layer 6/14)
18 Oct 17:15:43 INFO [geoserver.global ] - Loading feature type 'sfRestricted:::restricted' (layer 7/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type 'sfRoads:::roads' (layer 8/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type 'sfStreams:::streams' (layer 9/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type 'states_shapefile:::states' (layer 10/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type 'tasmania_cities:::tasmania_cities' (layer 11/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type 'tasmania_roads:::tasmania_roads' (layer 12/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type 'tasmania_state_boundaries:::tasmania_state_boundaries' (layer 13/14)
18 Oct 17:15:43 INFO [geoserver.global] - Loading feature type 'tasmania_water_bodies:::tasmania_water_bodies' (layer 14/14)
18 Oct 17:15:59 WARN [data.arcsde] - Figured Row-ID Column named 'OBJECTID' for table TESTDATA.ARCADMIN.PARCELS
18 Oct 17:15:59 WARN [action.RequestProcessor] - Unhandled Exception thrown: class java.lang.NullPointerException

I'm trying to generate support for GeoServer in my consulting company but this is a show stopper.Any ideas?

Cheers,

Dylan
!DSPAM:4005,4717fba741375332866982!

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

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

!DSPAM:4005,4717fba741375332866982!

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

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

!DSPAM:4005,4717fba741375332866982!

3

---------- Forwarded message ----------
From: Dylan Thomas <dvhthomas@anonymised.com>
Date: Oct 18, 2007 6:22 PM
Subject: Re: [Geoserver-users] ArcSDE 9.2 connection issues
To: Chris Holmes <cholmes@anonymised.com>

Chris - Did that and I get similar but (obviously!) more verbose results. However, nothing really that I can see for the specific error. I am wondering if the loop that is accessing the PE and SE libraries doesn’t get stuck, or perhaps it’s just one loop per layer in the database. At any rate, as soon as I select a valid SDE layer in the list it bombs. Thanks for any pointers that you can give me. BTW - I get the same OBJECTID error regardless of which layer I choose. Of course, that is the first column in the table.

Dylan

18 Oct 18:17:40 DEBUG [org.geotools.core] - ENTRY STATE_ABBR
18 Oct 18:17:40 DEBUG [org.geotools.filter] - made new logic factory
18 Oct 18:17:40 DEBUG [org.geotools.filter] - parsingExpression null
18 Oct 18:17:40 DEBUG [org.geotools.filter] - processing root null
18 Oct 18:17:40 DEBUG [org.geotools.filter] - processing literal [literal: null]
18 Oct 18:17:40 DEBUG [org.geotools.filter] - processing Times New Roman
18 Oct 18:17:40 DEBUG [org.geotools.filter] - made new logic factory
18 Oct 18:17:40 DEBUG [org.geotools.filter] - parsingExpression null
18 Oct 18:17:40 DEBUG [org.geotools.filter] - processing root null
18 Oct 18:17:40 DEBUG [ org.geotools.filter] - processing literal [literal: null]
18 Oct 18:17:40 DEBUG [org.geotools.filter] - processing Normal
18 Oct 18:17:40 DEBUG [org.geotools.filter] - made new logic factory
18 Oct 18:17:40 DEBUG [ org.geotools.filter] - parsingExpression null
18 Oct 18:17:40 DEBUG [org.geotools.filter] - processing root null
18 Oct 18:17:40 DEBUG [org.geotools.filter] - processing literal [literal: null]
18 Oct 18:17:40 DEBUG [ org.geotools.filter] - processing 14
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [ org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde ] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [ org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde ] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [ org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde ] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [ org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde ] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [ org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde ] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [ org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde ] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:57 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:57 DEBUG [org.geotools.data.arcsde] - com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:57 WARN [ org.geotools.data.arcsde] - Figured Row-ID Column named ‘OBJECTID’ for table TESTDATA.ARCADMIN.PARCELS
18 Oct 18:17:57 WARN [org.apache.struts.action.RequestProcessor] - Unhandled Exception thrown: class java.lang.NullPointerException

4

Dylan,

Somehow the version of the ArcSDE extension that's available with the latest
geoserver isn't quite the right one. I'm not quite sure what's up with this
bit

Can you try this procedure instead?

1) Get a nightly geoserver snapshot
2) Download a nightly gt2-arcsde-2.4-SNAPSHOT.jar file from here:
http://lists.refractions.net/m2/org/geotools/gt2-arcsde/2.4-SNAPSHOT/
3) Get the four jarfiles that make up the jsde_api 9.2 connection libraries
(you listed them below) You don't need commons-collection-1.3 anymore, I
don't think
4) Put all of 2 and 3 into the geoserver-nightly/WEB-INF/lib directory

Then try everything again.

I think that the version of #2 that's distributed in the latest ArcSDE
extension isn't the right version.

--saul

dvhthomas wrote:

---------- Forwarded message ----------
From: Dylan Thomas <dvhthomas@anonymised.com>
Date: Oct 18, 2007 6:22 PM
Subject: Re: [Geoserver-users] ArcSDE 9.2 connection issues
To: Chris Holmes <cholmes@anonymised.com>

Chris - Did that and I get similar but (obviously!) more verbose results.
However, nothing really that I can see for the specific error. I am
wondering if the loop that is accessing the PE and SE libraries doesn't
get
stuck, or perhaps it's just one loop per layer in the database. At any
rate,
as soon as I select a valid SDE layer in the list it bombs. Thanks for any
pointers that you can give me. BTW - I get the same OBJECTID error
regardless of which layer I choose. Of course, that is the first column in
the table.

Dylan

18 Oct 18:17:40 DEBUG [org.geotools.core] - ENTRY STATE_ABBR
18 Oct 18:17:40 DEBUG [org.geotools.filter] - made new logic factory
18 Oct 18:17:40 DEBUG [org.geotools.filter] - parsingExpression null
18 Oct 18:17:40 DEBUG [org.geotools.filter] - processing root null
18 Oct 18:17:40 DEBUG [org.geotools.filter] - processing literal [literal:
null]
18 Oct 18:17:40 DEBUG [org.geotools.filter] - processing Times New Roman
18 Oct 18:17:40 DEBUG [org.geotools.filter] - made new logic factory
18 Oct 18:17:40 DEBUG [org.geotools.filter] - parsingExpression null
18 Oct 18:17:40 DEBUG [org.geotools.filter] - processing root null
18 Oct 18:17:40 DEBUG [ org.geotools.filter] - processing literal
[literal:
null]
18 Oct 18:17:40 DEBUG [org.geotools.filter] - processing Normal
18 Oct 18:17:40 DEBUG [org.geotools.filter] - made new logic factory
18 Oct 18:17:40 DEBUG [ org.geotools.filter] - parsingExpression null
18 Oct 18:17:40 DEBUG [org.geotools.filter] - processing root null
18 Oct 18:17:40 DEBUG [org.geotools.filter] - processing literal [literal:
null]
18 Oct 18:17:40 DEBUG [ org.geotools.filter] - processing 14
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [ org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde ] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [ org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde ] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [ org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde ] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [ org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde ] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [ org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde ] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [ org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde ] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:57 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:57 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:57 WARN [ org.geotools.data.arcsde] - Figured Row-ID Column
named 'OBJECTID' for table TESTDATA.ARCADMIN.PARCELS
18 Oct 18:17:57 WARN [org.apache.struts.action.RequestProcessor] -
Unhandled
Exception thrown: class java.lang.NullPointerException

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
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/ArcSDE-9.2-connection-issues-tf4650519.html#a13298062
Sent from the GeoServer - User mailing list archive at Nabble.com.

5

Saul,

That did it. Thanks for your quick assistance. I’m now happily building queries against my data in ArcSDE and getting a demo ready for my colleagues. Cheers!

Dylan

On 10/19/07, sfarber <Saul.Farber@anonymised.com> wrote:

Dylan,

Somehow the version of the ArcSDE extension that’s available with the latest
geoserver isn’t quite the right one. I’m not quite sure what’s up with this
bit

Can you try this procedure instead?

  1. Get a nightly geoserver snapshot
  2. Download a nightly gt2-arcsde-2.4-SNAPSHOT.jar file from here:
    http://lists.refractions.net/m2/org/geotools/gt2-arcsde/2.4-SNAPSHOT/
  3. Get the four jarfiles that make up the jsde_api 9.2 connection libraries
    (you listed them below) You don’t need commons-collection-1.3 anymore, I
    don’t think
  4. Put all of 2 and 3 into the geoserver-nightly/WEB-INF/lib directory

Then try everything again.

I think that the version of #2 that’s distributed in the latest ArcSDE
extension isn’t the right version.

–saul

dvhthomas wrote:

---------- Forwarded message ----------
From: Dylan Thomas <dvhthomas@anonymised.com>
Date: Oct 18, 2007 6:22 PM
Subject: Re: [Geoserver-users] ArcSDE 9.2 connection issues
To: Chris Holmes < cholmes@anonymised.com>

Chris - Did that and I get similar but (obviously!) more verbose results.
However, nothing really that I can see for the specific error. I am
wondering if the loop that is accessing the PE and SE libraries doesn’t
get
stuck, or perhaps it’s just one loop per layer in the database. At any
rate,
as soon as I select a valid SDE layer in the list it bombs. Thanks for any
pointers that you can give me. BTW - I get the same OBJECTID error
regardless of which layer I choose. Of course, that is the first column in
the table.

Dylan

18 Oct 18:17:40 DEBUG [ org.geotools.core] - ENTRY STATE_ABBR
18 Oct 18:17:40 DEBUG [org.geotools.filter] - made new logic factory
18 Oct 18:17:40 DEBUG [org.geotools.filter] - parsingExpression null
18 Oct 18:17:40 DEBUG [ org.geotools.filter] - processing root null
18 Oct 18:17:40 DEBUG [org.geotools.filter] - processing literal [literal:
null]
18 Oct 18:17:40 DEBUG [org.geotools.filter] - processing Times New Roman
18 Oct 18:17:40 DEBUG [org.geotools.filter] - made new logic factory
18 Oct 18:17:40 DEBUG [org.geotools.filter] - parsingExpression null
18 Oct 18:17:40 DEBUG [org.geotools.filter] - processing root null
18 Oct 18:17:40 DEBUG [ org.geotools.filter] - processing literal
[literal:
null]
18 Oct 18:17:40 DEBUG [org.geotools.filter] - processing Normal
18 Oct 18:17:40 DEBUG [org.geotools.filter ] - made new logic factory
18 Oct 18:17:40 DEBUG [ org.geotools.filter] - parsingExpression null
18 Oct 18:17:40 DEBUG [org.geotools.filter] - processing root null
18 Oct 18:17:40 DEBUG [org.geotools.filter ] - processing literal [literal:
null]
18 Oct 18:17:40 DEBUG [ org.geotools.filter] - processing 14
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [ org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde ] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [ org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde ] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [ org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde ] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:40 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [ org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde ] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [ org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde ] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [ org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde ] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:54 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:57 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.client.SeConnection is in place.
18 Oct 18:17:57 DEBUG [org.geotools.data.arcsde] -
com.esri.sde.sdk.pe.PeCoordinateSystem is in place.
18 Oct 18:17:57 WARN [ org.geotools.data.arcsde] - Figured Row-ID Column
named ‘OBJECTID’ for table TESTDATA.ARCADMIN.PARCELS
18 Oct 18:17:57 WARN [org.apache.struts.action.RequestProcessor] -
Unhandled
Exception thrown: class java.lang.NullPointerException

This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

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/ArcSDE-9.2-connection-issues-tf4650519.html#a13298062
Sent from the GeoServer - User mailing list archive at Nabble.com.

This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

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