Metacat: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362010-01-20T18:46:35ZEcoinformatics Redmine
Redmine Bug #4680 (Resolved): Geoserver StringIndexOutOfBoundsExceptionhttps://projects.ecoinformatics.org/ecoinfo/issues/46802010-01-20T18:46:35ZMichael Daigledaigle@nceas.ucsb.edu
<p>Geoserver is throwing many StringIndexOutOfBoundsExceptions. There is a geoserver bug listed against version 2.4.4 that seems to address this. Note that we are running version 1.4.0. We should probably update geoserver.</p>
<p>The bug info that I found is:</p>
<p>International strings in DbfFileWriter cause StringIndexOutOfBoundsException<br />----------------------------------------------------------------------------</p>
<pre><code>Key: GEOT-1926<br /> URL: <a class="external" href="http://jira.codehaus.org/browse/GEOT-1926">http://jira.codehaus.org/browse/GEOT-1926</a><br /> Project: GeoTools<br /> Issue Type: Bug<br /> Components: data shapefile<br /> Affects Versions: 2.4.4<br /> Reporter: Alexey Noskov<br /> Assignee: Jesse Eichar<br /> Attachments: DbaseInternationalTest.java</code></pre>
<p>When storing some international string using DbfFileWriter, exception <br />StringIndexOutOfBoundsException may occur if two conditions are met:<br />1) String's length less then field size<br />2) String's size in bytes more, then field size</p>
<p>Problem in DbaseFileWriter, method getFieldString(int size, String s)</p>
<p>Loop <br />for( int index=size-1; currentBytes>size; index--)<br />need change to<br />for( int index=buffer.length()-1; currentBytes>size; index--)</p>
<p>Because, when storing string in buffer through buffer.replace( 0, size, s ), <br />it's size are truncated to length of s, and there are possible no symbol at <br />index size-1</p> Bug #4651 (Resolved): data packages losing data tables (and then finding them again)https://projects.ecoinformatics.org/ecoinfo/issues/46512010-01-07T21:46:52ZOliver Soongsoong@nceas.ucsb.edu
<p>This is on the dev server. I created soong.4 for the Kruger TPCs. soong.4.14 references four data tables containing zipped spatial data, soong.3.1, soong.5.1, soong.10.1, and soong.12.1. A month or so ago, those four data tables seemed to have been lost, and attempts to access them through both Kepler and the web returned file not found XML errors. I left soong.4 alone for daigle to take a look at and created a copy soong.28.5 for me to use. Today, soong.28.5 had the same problem, and the four tables it references, soong.29.2, soong.30.2, soong.31.2, and soong.33.2, are all missing and return file not found XML errors. At the same time, soong.4.14 works again, and soong.3.1, soong.5.1, soong.10.1, and soong.12.1 all exist again.</p>