Hi guys, the problem is fixed, it was just a problem of colliding names in the created test-files.
Anyway, what aaime was saying is true. Using FileChannel on big objects is dangerous on windows and we should try to avoid using them, especially for shapefiles. If anyone is ever interested in replacing them, I created a class that wraps a buffered random access file as a subclass of ImageInputStream. Performances are pretty similar to file channels but they avoid using memory mapping. Simone. ------------------------------------------------------- Eng. Simone Giannecchini President/CEO GeoSolutions http://www.geo-solutions.it Via Carignoni 51 550141 Camaiore (LU) Italy Mobile: +39 333 81 28928 ------------------------------------------------------- ----- Original Message ----- From: "Andrea Aime" <[EMAIL PROTECTED]> To: "Geotools-Devel list" <[email protected]>; "Simone Giannecchini" <[EMAIL PROTECTED]> Sent: Wednesday, March 14, 2007 10:14 AM Subject: Build failure in arcgrid module > Hi, > building gt2 trunk today I got the following: > > GRAVE: > C:\progetti\geotools\trunk\modules\plugin\arcgrid\target\test-classes\org\geotools\gce\arcgrid\test-data\4796arcGrid56672.prj > > (Impossibile eseguire l'operazione specificata su un file la cui sezione > mappata dall'utente Þ aperta) > java.io.FileNotFoundException: > C:\progetti\geotools\trunk\modules\plugin\arcgrid\target\test-classes\org\geotools\gce\arcgrid\test-data\4796arcGrid56672.prj > > (Impossibile eseguire l'operazione specificata su un file la cui sezione > mappata dall'utente Þ aperta) > at java.io.FileOutputStream.open(Native Method) > at java.io.FileOutputStream.<init>(FileOutputStream.java:179) > at java.io.FileOutputStream.<init>(FileOutputStream.java:70) > at java.io.FileWriter.<init>(FileWriter.java:46) > at > org.geotools.gce.arcgrid.ArcGridWriter.writeCRSInfo(ArcGridWriter.java:496) > at > org.geotools.gce.arcgrid.ArcGridWriter.writeGridCoverage(ArcGridWriter.java:366) > at > org.geotools.gce.arcgrid.ArcGridWriter.write(ArcGridWriter.java:518) > at > org.geotools.gce.arcgrid.ArcGridReadWriteTest.writeGrassUnCompressed(ArcGridReadWriteTest.java:186) > at > org.geotools.gce.arcgrid.ArcGridReadWriteTest.runMe(ArcGridReadWriteTest.java:77) > at > org.geotools.gce.arcgrid.ArcGridBaseTestCase.testAll(ArcGridBaseTestCase.java:103) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at junit.framework.TestCase.runTest(TestCase.java:154) > at junit.framework.TestCase.runBare(TestCase.java:127) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > > The issue is intermittent, does not happen for every build. > I guess we may want to avoid using channels everywhere, they are > giving us more troubles than goodness. > Simone talked about its custom streams, which do not use channels, yet > do perform like them. Time to consider using those? > > Cheers > Andrea ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
