Will, are you running 64-bit Java? If so, I strongly recommend using Oracle (AKA Sun) Java 6 with the JVM argument -XX:+UseCompressedOops to reduce memory footprint. Also, I am not sure that setting root's CATALINA_OPTS is the canonical [1] way of setting this. Can you see these options in the java process commandline?
ps auxwwwww | grep tomcat6 Under Debian Lenny we set JAVA_OPTS in /etc/default/tomcat6, which I have been advised is the canonical [1] location for configuring this service. I don't know if Ubuntu does the same. Kind regards, Ben. [1] canonical with a small c. :-) On 17/12/10 01:29, will.rog...@stfc.ac.uk wrote: > Thanks for the response - I've been tied up with other things a bit. > > After ensuring that the geometry column WAS registered (a number of my > experiments may have meant this wasn't the case), I'm instead getting a: > > java.lang.OutOfMemoryError: Java heap space > Java heap space > > Is this reasonably likely with what I'm trying to do, or does it tell me that > there's still something wrong? The request is: > http://localhost:8080/geoserver/wfs?request=GetFeature&typeName=hy-p:Watercourse&maxFeatures=1 > > I've attempted to increase the heap space as follows: > > w...@will-desktop:~$ sudo bash > [sudo] password for will: > r...@will-desktop:~# export CATALINA_OPTS="-Xmx512m -Xms512m" > r...@will-desktop:~# service tomcat6 restart > ... > [ > OK ] > > But I still get the error. I include the above because it is possible that > what I've done will not have the desired effect. Tomcat is running in an > Ubuntu virtual machine which has 1GB RAM allocated. > > Any more thoughts? Thanks for the help. > > Cheers, > Will > > > -----Original Message----- > From: Ben Caradoc-Davies [mailto:ben.caradoc-dav...@csiro.au] > Sent: 09 December 2010 03:14 > To: Rogers, Will (STFC,RAL,ESC) > Cc: geoserver-users@lists.sourceforge.net > Subject: Re: [Geoserver-users] app-schema mapping geometry column in PostGIS > > Will, > > I have a few more questions: > > - Can you publish this table as a GeoServer simple feature? For example, > can you use the GeoServer GUI to add a new data store for your database, > publish the rivers_polyline layer, and make a WFS GML 3.1 request > against it? This will help us diagnose whether it is the simple feature > layer or the app-schema layer that is having problems. > > - When you view the table as a GML 3.1 (WFS 1.1) simple feature, are the > geometries correctly encoded? > > - Are all your geometries in this column the same type? I don't think > GeoServer will like a mix. > > - Is this geometry column registered in geometry_columns? Bad Things > Will Happen if it is not correctly registered. > > Kind regards, > Ben. > > > On 09/12/10 00:09, will.rog...@stfc.ac.uk wrote: >> That was what we thought. But we don't know why it's null. >> >> 'select count(*) from rivers_polyline where the_geom is null' gives 0. >> >> It now looks like we should be able to map a LineString on to the >> GeometricPrimitivePropertyType, so we're not sure what else might be wrong. >> >> -----Original Message----- >> From: Ben Caradoc-Davies [mailto:ben.caradoc-dav...@csiro.au] >> Sent: 08 December 2010 05:35 >> To: Rogers, Will (STFC,RAL,ESC) >> Cc: geoserver-users@lists.sourceforge.net >> Subject: Re: [Geoserver-users] app-schema mapping geometry column in PostGIS >> >> On 07/12/10 20:18, will.rog...@stfc.ac.uk wrote: >>> The exception I get is: >>> <ows:ExceptionText> >>> org.geotools.feature.IllegalAttributeException:http://www.opengis.net/gml:GeometricPrimitivePropertyType >>> not nillable:null value:null >>> http://www.opengis.net/gml:GeometricPrimitivePropertyType not nillable >>> </ows:ExceptionText> >> [...] >>> Does anyone have any idea what's wrong with this? I can provide more >>> details if necessary. >> >> This error is caused by mapping a null from your database into a >> mandatory property. hy-p:geometry is a mandatory property of >> hy-p:SurfaceWaterType. The error is telling you that this property is >> not nillable and has a null value. >> >> What do you get for this? >> select count(1) from yourtablename where isnull(the_geom); >> >> app-schema supports conditional mappings of properties (even choosing >> between xlink:href and values) but I am not sure this will work in your >> case because geometries are handled as atomic types by GeoServer and >> app-schema has only limited ability to manipulate them: >> http://docs.geoserver.org/latest/en/user/data/app-schema/polymorphism.html >> > > -- Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
