[I'm putting this discussion back on the list where it belongs. There are a lot more on the list who might be able to help.]
Morten, turning on VERBOSE_LOGGING should show you all SQL statements. They should be on lines containing "[geotools.jdbc]". You might have to reload the GeoServer servlet (logging can be a bit twitchy). It looks like your SQL error has gone away. Rini thinks you should be seeing more in your error messages (see below). Niels added these diagnostics so might be able to help. Kind regards, Ben. -------- Original Message -------- Subject: RE: SV: [ExternalEmail] Re: [Geoserver-users] ORA-01427 in RC1, app-schema Date: Tue, 15 Feb 2011 10:36:54 +0800 From: Angreani, Rini (CESRE, Kensington) <[email protected]> Hmm, the error is there to isolate the problem to an attribute mapping. It was done for catching invalid attribute mapping, e.g. if the column it's mapped to doesn't exist. But, it should have the original exception printed as well, e.g. something like: java.lang.RuntimeException: Error applying mapping with targetAttribute gml:name[4] Error applying mapping with targetAttribute gml:name[4] Could not find working property accessor for attribute (DESCRIPTIO) in object (SimpleFeatureImpl:InvalidColumnGeologicUnit=[SimpleFeatureImpl.Attribute: NAME&lt;NAME id=gu.93&gt;=Yaugher Volcanic Group, SimpleFeatureImpl.Attribute: CODE&lt;CODE id=gu.93&gt;=-Py, SimpleFeatureImpl.Attribute: URN&lt;URN id=gu.93&gt;=urn:x-test:GeologicUnit:16777549126931093, SimpleFeatureImpl.Attribute: DESCRIPTION&lt;DESCRIPTION id=gu.93&gt;=Olivine basalt, tuff, microgabbro, minor sedimentary rocks]) No value for xpath: DESCRIPTIO So, without the full stack trace, it's hard to determine the cause. On 14/02/11 18:21, Lindegaard, Morten wrote: > Hi Ben, > > Thank you for the suggestions! > > I used verbose logging, but I didn't find the SQL. I'll take a closer look at > the view. > > I have attached a zip-file containing the workspace with my mapping files. > > However, I'm unable to reproduce the ORA-01427 error at the moment. So I'm > afraid it is no help. Since I tried various things to fix the error, I have > most likely changed something in the mapping files and forgotten about it. > > Right now, I run into this error: > java.lang.RuntimeException: Error applying mapping with targetAttribute > kms:harSamletFastEjendom > Error applying mapping with targetAttribute kms:harSamletFastEjendom > Error applying mapping with targetAttribute FEATURE_LINK > Index: 0, Size: 0 > > So that's what I'm trying to get around now... > > If there is anything in my mapping files that looks suspicious at a glance, > I'll be happy to know. > > Kind regards, > Morten > > Miljøministeriet, Kort& Matrikelstyrelsen, direkte tlf. 72545506. Officiel > kommunikation bedes dirigeret via e-mail [email protected] eller telefon 72545000 > > -----Oprindelig meddelelse----- > Fra: Ben Caradoc-Davies [mailto:[email protected]] > Sendt: 11. februar 2011 05:56 > Til: Lindegaard, Morten > Cc: [email protected] > Emne: Re: [ExternalEmail] Re: [Geoserver-users] ORA-01427 in RC1, app-schema > > Morten, here are some suggestions from a colleague: > > On 11/02/11 11:21, Warren, Peter (CESRE, North Ryde) wrote: > > Does Geoserver build SQL with subqueries? I wouldn't have thought > so. If it doesn't then this is likely an error in a view definition. > > If it does build SQL with subqueries then this could be caused by > duplicate feature_IDs used in the chaining. > > Note: We really don't have much to go on here so I could be wrong. > > > On 11/02/11 10:30, Ben Caradoc-Davies wrote: >> Morten, >> >> please turn on verbose logging and let us know if you can see the SQL >> that is generated when you get this error. >> >> Can we please see your app-schema mapping file? >> >> Kind regards, >> Ben. >> >> On 10/02/11 20:22, Lindegaard, Morten wrote: >>> Hi, >>> >>> I have installed 2.1-RC1 recently, and I have copied a configuration that >>> use the app-schema and oracle extensions from beta3 to RC1. >>> >>> The configuration nests features, and selects from various views and tables. >>> >>> It works fine in beta3, but RC1 fails with "java.lang.RuntimeException: >>> java.sql.SQLException: ORA-01427: single-row subquery returns more than one >>> row". >>> >>> Does anyone know of changes from beta3 to RC1 that would explain the change >>> in behaviour? >>> >>> Thanks in advance! >>> >>> Kind regards, >>> Morten Lindegaard >>> >>> >>> >> > -- Ben Caradoc-Davies <[email protected]> Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
