gvSIG bugs #2441
Exportando de shape a PostGIS se queda frito
Status: | Closed | % Done: | 0% | |
---|---|---|---|---|
Priority: | High | Spent time: | - | |
Assignee: | Juan Lucas Domínguez | |||
Category: | Database | |||
Target version: | 2.1.0-2222-testing | |||
Severity: | Add-on version: | |||
gvSIG version: | 2.1.0 | Add-on build: | ||
gvSIG build: | 2220 | Add-on resolve version: | ||
Operative System: | Add-on resolve build: | |||
Keywords: | Proyecto: | |||
Has patch: | No | Hito: | ||
Add-on name: | Unknown |
Description
Adjunto la capa.
Hasta las 70 o 75 mil geometrías las exporta rápido. A partir de ahí empieza a ir más lento hasta que se para y da un OutOfMemoryError. Tiene sobre 100 mil.
Con la 1.12 no hay problemas
http://www20.gencat.cat/dadesobertes/recursos/sigpac/2013/SIGPAC_03_AltPenedes.zip
Exception in thread "Thread-11" java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2798)
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:111)
at com.vividsolutions.jts.io.OutputStreamOutStream.write(OutputStreamOutStream.java:52)
at com.vividsolutions.jts.io.WKBWriter.writeCoordinate(WKBWriter.java:422)
at com.vividsolutions.jts.io.WKBWriter.writeCoordinateSequence(WKBWriter.java:414)
at com.vividsolutions.jts.io.WKBWriter.writePolygon(WKBWriter.java:362)
at com.vividsolutions.jts.io.WKBWriter.write(WKBWriter.java:322)
at com.vividsolutions.jts.io.WKBWriter.write(WKBWriter.java:299)
at org.gvsig.fmap.geom.primitive.impl.AbstractPrimitive.convertToWKBForcingType(AbstractPrimitive.java:586)
at org.gvsig.fmap.dal.store.jdbc.JDBCHelper.dalValueToJDBC(JDBCHelper.java:818)
at org.gvsig.fmap.dal.store.postgresql.PostgreSQLHelper.dalValueToJDBC(PostgreSQLHelper.java:897)
at org.gvsig.fmap.dal.store.jdbc.JDBCStoreProviderWriter.addToListFeatureValues(JDBCStoreProviderWriter.java:95)
at org.gvsig.fmap.dal.store.postgresql.PostgreSQLStoreProvider.addToListFeatureValues(PostgreSQLStoreProvider.java:225)
at org.gvsig.fmap.dal.store.jdbc.JDBCStoreProviderWriter.addToListFeatureValues(JDBCStoreProviderWriter.java:108)
at org.gvsig.fmap.dal.store.jdbc.JDBCStoreProviderWriter.perfomInsert(JDBCStoreProviderWriter.java:423)
at org.gvsig.fmap.dal.store.jdbc.JDBCStoreProviderWriter.access$000(JDBCStoreProviderWriter.java:60)
at org.gvsig.fmap.dal.store.jdbc.JDBCStoreProviderWriter$1.action(JDBCStoreProviderWriter.java:456)
at org.gvsig.fmap.dal.store.jdbc.JDBCHelper$3.run(JDBCHelper.java:267)
at org.gvsig.fmap.dal.resource.spi.AbstractResource.performExecution(AbstractResource.java:316)
at org.gvsig.fmap.dal.resource.spi.AbstractNonBlockingResource.execute(AbstractNonBlockingResource.java:57)
at org.gvsig.fmap.dal.store.jdbc.JDBCHelper.doConnectionAction(JDBCHelper.java:243)
at org.gvsig.fmap.dal.store.jdbc.JDBCStoreProviderWriter.append(JDBCStoreProviderWriter.java:473)
at org.gvsig.fmap.dal.feature.impl.DefaultFeatureStore.insert(DefaultFeatureStore.java:1020)
at org.gvsig.exportto.swing.prov.jdbc.ExporrtoJDBCService.export(ExporrtoJDBCService.java:191)
at org.gvsig.exportto.swing.impl.DefaultJExporttoServicePanel$Export.run(DefaultJExporttoServicePanel.java:256)
History
#1 Updated by Álvaro Anguix about 10 years ago
- Assignee set to Juan Lucas Domínguez
- Priority changed from Normal to High
- Target version set to 2.1.0-2222-testing
#2 Updated by Juan Lucas Domínguez about 10 years ago
- Status changed from New to In progress
#3 Updated by Juan Lucas Domínguez about 10 years ago
- Status changed from In progress to Fixed
Creo que está causado porque no se había deshecho el cambio de #2426 ya que Nacho y yo estamos constantemente ejecutando lo que hay en el trunk. En mi workspace no ocurre y con BN 2220 tampoco, así que lo cierro y si vuelve a pasar en el siguiente build, lo reabrimos.
#4 Updated by Ignacio Brodín about 10 years ago
He probado con una capa de 100 mil geometrías y no da problemas. Lo doy por resuelto.
#5 Updated by Álvaro Anguix about 10 years ago
- Status changed from Fixed to Closed