GeoServer
  1. GeoServer
  2. GEOS-4075

Geos Web UI hangs when adding a new Layer from Oracle DS

    Details

    • Type: Bug Bug
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0.1
    • Fix Version/s: None
    • Component/s: Oracle
    • Labels:
      None
    • Environment:
      Win2003, Tomcat 6.0.18, Geos 2.0.1, Orcl 10.2 (on amazon EC2)
    • Number of attachments :
      1

      Description

      when attempting to add a new Layer from am Oracle Datastore the system hangs and then crashes (see attachment for stack). The layer is a polygon layer gtype 2003 with about 1.5M records. It is spatially indexed. The DDL for the table is here:

      drop table structures_geo;

      CREATE OR REPLACE TYPE ainxref AS VARRAY(300) OF NUMBER;
      CREATE OR REPLACE TYPE pinxref AS VARRAY(50) OF VARCHAR2(20);
      CREATE OR REPLACE TYPE addrxref AS VARRAY(300) OF NUMBER;

      create table structures_geo (
      SGID NUMBER, --sequence
      CODE VARCHAR2(50),
      BLD_ID VARCHAR2(20),
      HEIGHT NUMBER,
      ELEV NUMBER,
      AREA NUMBER,
      GEOMETRY SDO_GEOMETRY,
      SOURCE_FILE VARCHAR2(128),
      SOURCE_FILE_DATE VARCHAR2(50),
      AIN_LIST ainxref,
      PIN_LIST pinxref,
      ADDR_LIST addrxref
      );

      the varrays are dropped from the feature as expected

        Activity

        Hide
        Chris Hughes added a comment - - edited

        Oracle validation of the layer shows these errors

        COUNT SUBSTR(RESULT,1,5)
        1611 ORA-13356: adjacent points in a geometry are redundant
        1 ORA-13343: a polygon geometry has fewer than four coordinates
        409 ORA-13349: polygon boundary crosses itself
        7 ORA-13348: polygon boundary is not closed
        Show
        Chris Hughes added a comment - - edited Oracle validation of the layer shows these errors COUNT SUBSTR(RESULT,1,5) 1611 ORA-13356: adjacent points in a geometry are redundant 1 ORA-13343: a polygon geometry has fewer than four coordinates 409 ORA-13349: polygon boundary crosses itself 7 ORA-13348: polygon boundary is not closed
        Hide
        Chris Hughes added a comment -

        SELECT count
        from STRUCTURES_GEO g
        WHERE SDO_FILTER(g.geometry,
        SDO_GEOMETRY(2003, 2229, NULL,
        SDO_ELEM_INFO_ARRAY(1,1003,3),
        SDO_ORDINATE_ARRAY(6460000,1814000, 6461000,1815000))
        ) = 'TRUE';

        COUNT
        ----------------------
        188

        Show
        Chris Hughes added a comment - SELECT count from STRUCTURES_GEO g WHERE SDO_FILTER(g.geometry, SDO_GEOMETRY(2003, 2229, NULL, SDO_ELEM_INFO_ARRAY(1,1003,3), SDO_ORDINATE_ARRAY(6460000,1814000, 6461000,1815000)) ) = 'TRUE'; COUNT ---------------------- 188
        Hide
        Andrea Aime added a comment -

        Is the GUI hanging trying to add the new layer, or when you have GeoServer compute the native bounding box?
        With 1.5m layers + Oracle that is going to take forever, better fill the values manually

        Show
        Andrea Aime added a comment - Is the GUI hanging trying to add the new layer, or when you have GeoServer compute the native bounding box? With 1.5m layers + Oracle that is going to take forever, better fill the values manually
        Hide
        Chris Hughes added a comment -

        yes when Geos computes the bounding box - i didnt know that it looks at each geometry or does it look at the indices? anyway I did fill them in manually. The method I would recommend is

             select SDO_TUNE.EXTENT_OF(
             '<TABLE_NAME>','<GEOMETRY_COL>'
             ) from dual;
        

        though im not sure if it is supported in older versions of SDO. The manual method did resolve the issue but perhaps this could be a low priority feat request?

        Show
        Chris Hughes added a comment - yes when Geos computes the bounding box - i didnt know that it looks at each geometry or does it look at the indices? anyway I did fill them in manually. The method I would recommend is select SDO_TUNE.EXTENT_OF( '<TABLE_NAME>','<GEOMETRY_COL>' ) from dual; though im not sure if it is supported in older versions of SDO. The manual method did resolve the issue but perhaps this could be a low priority feat request?
        Hide
        Paul Joyce added a comment -

        This would be fixed by the fix to GEOT-1507

        Show
        Paul Joyce added a comment - This would be fixed by the fix to GEOT-1507

          People

          • Assignee:
            Andrea Aime
            Reporter:
            Chris Hughes
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: